Patient-Controlled Records and Emergency Access
Medistry is a patient medical-record portability platform with a locked-phone emergency break-glass scan, built for Nigeria.
Records That Follow the Patient
A person’s medical history should be available to the clinician who needs it, and to nobody else.
Patient-owned
Patients approve every hospital-to-hospital share, by in-app approval or a one-time code, and can revoke it at any time.
Emergency-ready
A locked phone should not cost a life. A random code on a card or wristband opens a minimal, audited emergency path for verified clinicians.
Append-only
Records are versioned and never hard-deleted. Every read, write and break-glass lands in a hash-chained audit log.
Interoperable
HL7 FHIR R4 resources let Medistry exchange data with hospital systems instead of replacing them.
Trusted by Design
Patients own their records. Clinicians earn access. Every action leaves a trace.
Medistry stores clinical data with field-level encryption, never hard-deletes a record, and logs every access in a tamper-evident chain, so patients and regulators can always see what happened and when.
Common Questions
What does an emergency code reveal when it is scanned?
Nothing personal. The gate only confirms the code is valid. Unless the patient turned on the optional public badge (blood group, genotype, critical allergies and an emergency contact), a verified clinician must sign in first.
Who can start a break-glass session?
Only a clinician whose MDCN licence has been checked and who signs in with an authenticator code and states a clinical reason. Repeated failed sign-ins lock the account.
How long does emergency access last?
60 minutes, read-only. The full multi-year history needs a second, distinct clinician to co-sign.
Can a patient see who looked at their record?
Yes. The patient portal lists every access, including break-glass events, and lets the patient dispute anything suspicious.
Is this real patient data?
No. This environment runs on synthetic patients, facilities and clinicians held in memory, and resets whenever the server restarts.