Local-first data

Local medical software without cloud patient-record storage

See where Clinosys stores clinical data, what is encrypted and which connected services remain occasional or optional.

Verified 8 September 2026

Real software capture

Synthetic patient record stored in the local Clinosys application
Real synthetic-profile capture: the clinical profile, history and documents are accessed from the local application.

“No cloud” should describe a verifiable architecture, not a slogan. In Clinosys, the primary clinical database is installed on the practice computer. Consultations, prescriptions and notes are not automatically replicated to a remote host.

A clear data boundary

1

Local database

The clinical SQLite database lives in the host computer’s data profile.

2

Field encryption

Sensitive medical fields use AES-256-GCM before they are stored.

3

Separated keys

A clinic passphrase protects keys loaded only while the app is unlocked.

4

Limited services

Licensing, updates and extensions can communicate without copying clinical records.

What local-first changes for a Moroccan practice

The practice can read its records without relying on a cloud vendor’s uptime and can identify the computer hosting the database and the location of its backups.

This model still requires protected devices, named accounts, strong passwords, off-device backups and routine restore tests. Software provides controls; governance remains a practice responsibility.

  • No default replication of clinical data
  • Separate users and roles
  • Audit trail for sensitive actions
  • Local backups with SHA-256 checksums

Law 09-08 is broader than server location

Health data is sensitive. Keeping it local may reduce data flows, but practices still need patient information, access controls, documented processing and any applicable CNDP formalities.

Clinosys supplies technical building blocks—encryption, roles, logs and backups—that the controller must include in its procedures. A demo can map who accesses what in your practice.

Local medical storage questions

Does Clinosys send consultations to a cloud?

Not by default. The main clinical database is local. Occasional services such as licensing or updates can communicate without consultation content.

Does local storage automatically satisfy Law 09-08?

No. Storage location is only one factor. The practice must also manage legal basis, notices, access, retention, incidents and applicable CNDP steps.

Can I identify the database location?

Yes. Clinosys uses an identifiable local data profile on the host machine, with backups managed separately inside that profile.

Map your data flow before rollout

Request a demo with a fictional patient and follow each data item from reception to backup.