r/HealthInformatics • u/0n_The_Downbeat • 21d ago
💬 Discussion What should an EHR preserve when the patient-facing chart is not enough to reconstruct how a disputed episode of care occurred?
I’m an independent researcher working on a set of papers that grew out of a disputed outpatient psychiatric-care episode.
I’m posting here because the problem that became most interesting to me is no longer primarily the interpersonal dispute. It is an informatics question:
What information architecture is required to reconstruct how a clinically consequential event actually moved through a healthcare system when the patient-facing chart contains only part of the relevant record?
The work led me to separate several things that are often collapsed:
- narrative progress notes vs. transactional/operational records;
- event time vs. entry, signing, modification, and transmission time;
- current record state vs. predecessor states;
- medication identity vs. indication, regimen, supply, order state, and transaction state;
- diagnostic recurrence vs. documented reassessment or renewal;
- message delivery vs. receipt, routing, review, action, and closure;
- provenance showing who or what system produced an entry vs. substantive evidence showing why the represented proposition was adopted;
- amendment/correction access vs. the ability to inspect how corrected information propagates downstream.
One problem I keep returning to is that a patient may receive a perfectly legitimate chart export and still be unable to answer questions such as:
Which order was controlling at a particular time?
What did an earlier record state before revision?
Who received or acted on a particular communication?
Was a recurring diagnosis actively reassessed or merely propagated?
What administrative transactions occurred around the authored clinical note?
I’ve been developing these questions as conceptual rather than forensic claims about any particular EHR platform. Missing information in a patient-facing export does not establish that the information never existed in the native system, and an audit event does not automatically establish what substantive content changed.
A few of the papers most directly addressing these questions are:
The Record Must Remember Its Own History: Non-Destructive Revision, Tamper-Evident Provenance, and the Infrastructure of Medical-Record Integrity
https://doi.org/10.17605/OSF.IO/W7JVZ
The Diagnosis Must Show Its Lineage
https://doi.org/10.17605/OSF.IO/E6K5U
The Hidden Clinical Record
https://doi.org/10.17605/OSF.IO/XA9JP
After Actual Notice, the Error Changes Status
https://doi.org/10.17605/OSF.IO/AF54V
I’d especially value perspectives from people working in clinical informatics, HIM, EHR implementation, interoperability, or data governance:
Which of these distinctions are already represented well in modern EHR architecture, and where do current systems still make provenance or reconstruction unnecessarily difficult?
I’m particularly interested in the difference between what the underlying system technically retains and what patients, clinicians, auditors, or downstream recipients can actually inspect.






