Home / Solutions / Healthcare
Patient-scoped memory that reconstructs.
Patient-scoped, encrypted, reconstructable memory, with care-team barriers and audit-preserving erasure.
$ mem.recall_at(subject="patient-8821", query="anticoagulant", as_of="2025-06-01") # → "Apixaban 5mg" (the active therapy then, not the discontinued Warfarin)
Proof points
Built for the chart.
AES-256-GCM keyed by patient or member identifier, so memory is segregated by subject at rest.
Patient-level deletion that's provable: destroy the key, keep the audit trail.
Department and care-team isolation enforced at the database layer via row-level security.
Reconstruct the chart context that was active on any date, for a decision or a review.
Technical safeguards mapped to controls. See compliance →
Patient, encounter, provider, condition, medication, ICD-10, NPI, CPT, and HCPCS normalization.
See it: as-of recall
Reconstruct the chart on any date.
The demo
Update, scope, reconstruct, erase.
Update a dose. Recall only the current value. Reconstruct the admission view. Erase the patient cryptographically. Every step is auditable.
Connector priorities
Where the records live.
FHIR, HL7, Epic / Cerner export paths, claims systems, provider directories, clinical document stores, and identity gateways.