AuroraMed v0.2.0 is a synthetic-data pilot. See exactly what's built →

Product tour

Audit and break-glass

See who opened which chart, prove the log has not been altered, and handle emergencies without hiding them.

Audit hash chainEach audit entry contains the hash of the previous one, so editing, deleting, reordering or truncating entries breaks the chain and is detected by the verify button.Entry 41Entry 42Entry 43Entry 44In the pilotDesigned, not builtSimulatedDecision / caution

Diagram: a tamper-evident chain. It is tamper-evident, not write-once storage; the database owner could rewrite it.

Break-glassA clinician without a care assignment opens a restricted chart, states a reason, gets time-boxed access, privacy staff are alerted, and a mandatory review follows.Restricted chartwithout assignmentReason codeand textTime-boxed accessand alert toprivacy staffMandatoryprivacy reviewIn the pilotDesigned, not builtSimulatedDecision / caution

Diagram: emergency access. Compartments are flags plus an attested purpose, not a consent engine.

What exists Pilot

  • Per-clinic SHA-256 hash chain with a verify button, filters and paging.
  • Read events for chart, lists and registration; per-patient access report.
  • VIP and restricted flags hide a patient from anyone without an assignment.
  • Disclosure log for privacy staff.

Open items Open

  • The chain is not write-once and has no external anchor.
  • No anomaly detection and no export.
  • Not patient-facing: patients cannot see their own access history yet.
  • No minors, reproductive-health or 42 CFR Part 2 logic.

See audit and break-glass on synthetic data

A short walkthrough. No patient information needed.

Request a demo
See the synthetic-data demo first.Request a demo