Security

Privacy without friction.

Security is not a bolt-on. New Loka treats isolation, access control, and local ownership as default behavior, while keeping the workflow fast enough for real clinics.

Strong partitioning

Data isolated by design

Access control

Role-based visibility

Patient-centric

Direct handoff ready

Fast workflow

No remote latency

Local encryption

Protected storage is part of the default local-first model.

Minimal exposure

Fewer moving parts mean fewer places where sensitive data can leak.

No cloud lock-in

Data ownership stays with the clinic or patient, not a vendor account.

Threat Model

Security has to work in the real world, not just in the happy path.

The biggest risks are usually practical ones: shared devices, weak access discipline, lost hardware, and unreliable infrastructure. The system needs to handle those conditions gracefully.

Device loss

Data should remain protected if a phone, tablet, or workstation is misplaced.

Shared environments

Multiple users may share a workstation, so sessions and permissions need to be clear.

Network instability

Security should not depend on a constant high-quality connection to a remote server.

Over-broad access

Partitioning should reduce how much a user can see by default, not after the fact.

Controls that matter to users

Role-based access control

Limit who can read, edit, export, or share specific records.

Data partitioning

Keep patient, provider, clinic, and department boundaries explicit.

Auditability

Track important access and changes so teams can review what happened later.

Backup and export

Allow safe offline backups and controlled transfer into other systems.

Security UX

Security should be visible, but not obstructive.

Users should know when they are in a protected session, who they are acting as, and what is being shared, without having to understand the implementation details.

  • Clear permission prompts before anything leaves the local boundary.
  • Session and account boundaries that make shared-device use less risky.
  • Fast workflows that do not force the user to trade safety for speed.