Why should you care?

Wrong access or missing audit logs is not just a bug — it is a compliance failure. MongoDB can fit document-shaped charts if security is designed in.

See it live — copy this example

Open mongosh or MongoDB Compass, select database nosqlverse, then run the example. Change one field and run again.

db.patients.insertOne({
  _id: "pat-1",
  mrn: "MRN1001",
  name: "Anon",
  // sensitive fields encrypted at app/QE layer in production
  phone_enc: BinData(6, "AQID"),
  tenantId: "hospital-west"
})
db.encounters.insertOne({
  patientId: "pat-1",
  tenantId: "hospital-west",
  type: "checkup",
  notes: "Routine vitals normal",
  at: new Date(),
  clinicians: ["dr-9"]
})
db.encounters.createIndex({ tenantId: 1, patientId: 1, at: -1 })
db.audit.insertOne({
  actor: "dr-9", action: "READ_ENCOUNTER", patientId: "pat-1", at: new Date()
})
db.encounters.find({ tenantId: "hospital-west", patientId: "pat-1" }).sort({ at: -1 })

Run Example »

Edit the code below and click Run to see the result in Toolliyo’s live editor.

What happened?

• patients and encounters are tenant-scoped to a hospital.
• Sensitive phone is stored encrypted.
• Every read can write audit.
• Indexes support patient timelines without cross-tenant leakage.

Practice next

1. Insert patient + encounter + audit sample.
2. Query encounters for one patient.
3. Deny a find missing tenantId in your app layer tests.
4. Add an immutable audit collection (append-only user).
5. Separate coding/billing collection from clinical notes.

Remember

Tenant + patient scoped documents. Encrypt sensitive fields; audit access. RBAC for clinicians vs billing.

Hospital encounter chart

Clinicians open a patient’s timeline; each open writes audit; phones stay encrypted.

Outcome: Care delivery works and compliance can prove who accessed what.