Documentation Time Is Not Always Event Time

The medical chart looks definitive. A note is dated and timed, a vital sign sits in a flowsheet, a medication shows an administration time. Read on paper, the record seems to settle the question of what happened and when. It often does not, because the printed chart shows the time a clinician entered, not always the time an event occurred. In modern electronic health records, those two times can diverge, and the difference can matter a great deal.

Consider what an electronic health record, or EHR, actually stores. Behind the formatted note is an audit trail, the system’s own log of activity on the chart. It records when an entry was created, when it was viewed, when it was modified, and often from which device. Practitioners describe the audit trail as the chart’s black box. It captures the sequence of events that the printed report smooths over.

The gap between event time and documentation time is not a technicality. In one reported matter, a patient died unexpectedly after surgery, and the printed record suggested stable vital signs and timely care throughout the day. The audit trail told a different story. Shift notes had been authored after the patient died and carried earlier dates, and flowsheet entries had been revised without any sign of the change in the legal medical record. Nothing on the printed page revealed the edits. The metadata did.

The same principle appears in smaller details. In another matter, a medication was charted as administered at 02:03. The audit log showed the entry was actually created several minutes after resuscitation had already begun. The printed time and the true time were not the same, and only the system evidence exposed the difference.

None of this means that a late entry is proof of wrongdoing. Clinicians document after the fact for legitimate reasons. Care during a busy shift is often charted later. When an EHR goes down, staff document on paper and enter the information when the system returns. A late entry, properly labeled, is ordinary and appropriate. The question is never simply whether an entry was late. The question is whether the timing and the disclosure were proper, and whether the printed record fairly represents the sequence of care.

That is why documentation timing deserves careful, neutral analysis rather than assumption. Timestamps require interpretation. Systems record events in ways that depend on configuration, shared workstations, proxy access, and even clock settings. A timestamp read in isolation can mislead as easily as it can clarify. The value comes from reconciling the many timestamps in a record, documentation, orders, results, medication administration, flowsheets, and the audit trail, and asking whether they agree. When they do not, the discrepancy is worth understanding.

For attorneys, the practical lesson is about timing and scope. The audit trail is usually not part of the standard medical record, so it must be specifically requested. It is most useful when it is reviewed early, before depositions, so that testimony can be tested against the system evidence rather than after positions have hardened. Knowing that event time and documentation time can differ is the first step toward asking for the records that show both.

The printed chart is a report generated from a far larger system. It is a starting point, not the whole story. Reading the record well means reading the evidence behind it, and doing so with the discipline to separate what the data show from what they do not.