Patient Journey Reconstruction Versus Traditional Chronology

Most medical-legal reviews produce a chronology. Someone reads the chart, extracts the dated entries, and arranges them in order. A chronology is useful and necessary. It is also limited in a specific way: it inherits whatever the printed chart says, in the order the chart presents it. If the chart is incomplete, so is the chronology. Patient journey reconstruction is a different exercise. It rebuilds what actually happened, across every available source, and tests the printed sequence against the system evidence.

The distinction is worth making precise, because the two are easy to conflate.

A traditional chronology summarizes. It takes the entries at face value and lists them. Its unit is the note, and its timeline is the timeline the notes assert.

A reconstruction reconciles. Its unit is the event, and it draws on every source that bears on that event: clinical notes, orders, results, medication administration records, flowsheets, and the audit trail. Where a chronology asks what the chart says happened, a reconstruction asks what actually happened, and whether the sources agree.

That difference changes what the analysis can surface. A chronology built from printed notes will show a note dated at a clinical time. A reconstruction will also ask when that note was created and whether it was edited, using the audit trail. A chronology will list a result as available. A reconstruction will ask whether anyone opened it. A chronology will record a documented assessment. A reconstruction will check the access log to see whether the chart was even open at that time. In one documented matter, that kind of cross-checking revealed shift notes authored after a patient’s death and backdated, and in another it showed a medication entry created minutes after resuscitation had begun. A chronology reading the printed record alone would have shown neither.

The method matters as much as the result. A defensible reconstruction is transparent and reproducible. It states its sources, separates fact from inference, and flags where a timestamp requires interpretation or where the native system is needed to resolve a question. It does not present system events as conclusions they cannot support. This discipline is what allows a reconstruction to hold up under scrutiny rather than collapse into speculation.

None of this makes chronologies obsolete. A clean chronology is often the first step, and for straightforward matters it may be enough. Reconstruction earns its cost when the timeline is contested, when documentation timing is in question, when a case spans multiple departments or systems, or when the printed sequence and the clinical outcome do not seem to fit. Those are the cases where the difference between what the chart says and what the system shows is likely to be decisive.

The language is deliberate. Physician Case Review reconstructs the patient journey rather than summarizes the chart, because the two are not the same activity. One repeats the record. The other tests it.