The Medical Record Has More Than One Clock

By Kanwar Partap Singh Gill, MD · Family medicine physician · 5 November 2026

• The question a chart rarely answers directly
• Four days, four different clocks
• The clocks a reviewer keeps apart
• Five records, read for what they establish
• Why separate clocks make a review fairer
• Knowing, receiving and being responsible are different questions
• Timestamps need an interpreter
• What the finished chronology looks like
• A fair review looks both ways
• What a review of this issue can deliver

The question a chart rarely answers directly

When care is questioned, the decisive issue is often not what the record says but when its information existed, and for whom. A clinician is judged on what was available, or reasonably obtainable, at the moment of decision. Yet an electronic record presents a single orderly sequence of dated documents, and each of those dates may measure something different: when the patient was seen, when a note was typed, when it was signed, when a result was finalized, when it reached an inbox, when someone opened it, and when someone acted.

Collapsing those moments into one timeline is a common error in a medical chronology. It can make a careful clinician look negligent, and it can make a genuine gap disappear. Separating them is slow work, and it is the foundation on which every other part of a record review rests.

Four days, four different clocks

The Wednesday signature cannot, by itself, establish that the Monday clinician knew the Tuesday result during Monday's encounter; the result did not yet exist. Nor does it establish that the clinician saw the result on Wednesday while signing. Completing a visit note and reviewing a result are separate tasks, often performed in separate parts of the system. The Thursday call shows that someone acted on Thursday. It does not show that no one tried earlier, or that Thursday was the first day anyone could have.

A reviewer who writes "the clinician signed the note Wednesday, after the critical result was available, and did nothing" has merged three clocks into one sentence. A reviewer who writes "nothing shows the clinician was aware of the result" has stopped too early. The useful questions sit between those two statements: to whom was the result routed, who was covering, what does the system record about access, and what did the organization expect to happen to a critical value on a Tuesday afternoon?

The clocks a reviewer keeps apart

Occurrence

When the care, symptom, specimen collection or conversation actually happened.

Entry

When the information was typed, dictated, drafted or imported. A note can be opened during a visit and completed hours or days later.

Signature

When the author finalized the entry. What a signature attests depends on the workflow; it is not a statement about everything visible elsewhere in the chart at that moment.

Availability

When a result or outside report was finalized and became viewable in the system, which may differ from when it was routed to anyone.

Routing and receipt

To whom the item was sent: the ordering clinician, a covering clinician, a shared pool, a departed clinician's queue. Delivery to an inbox is not the same as a person seeing it.

Acknowledgement

A recorded action marking the item as reviewed. An acknowledged result is not the same as a communicated result.

Communication and action

When the patient was told, an order placed, a referral made or the plan otherwise changed, and whether that action was completed.

These events sometimes fall within minutes of one another and sometimes weeks apart. The chronology records each one the evidence supports and marks the rest as unknown rather than estimating them.

Five records, read for what they establish

Consider a fictional record assembled from five items. The middle column states only what each item itself establishes; the right column states what it leaves open.

The table looks modest. Its discipline is that the middle column never borrows from the right. Each open question names a record that could answer it: routing data, a coverage schedule, a telephone log, a custodian's explanation of what the signature workflow required. That turns a vague suspicion into a specific discovery request, or into a finding that the question cannot be answered on the available material.

Why separate clocks make a review fairer

A later diagnosis makes an earlier symptom look obvious. Once a reader knows the potassium was dangerous, or that the cough was cancer, ambiguous findings in the earlier record take on a clarity they did not have when the clinician faced them. This is hindsight bias, and it operates on careful readers as well as careless ones.

The corrective is reconstruction. The reviewer rebuilds the presentation as it was documented: the complaint, the examination, the competing explanations, the tests pending, the plan and its contingencies. Only then does the question become answerable: on what was available, or reasonably obtainable, did the situation call for a different response? Sometimes the answer is yes. Sometimes the reconstruction shows a defensible decision made under real uncertainty, and the later event says nothing about its quality.

Knowing, receiving and being responsible are different questions

A result sitting somewhere in an electronic system does not automatically establish that a particular clinician received or understood it. Conversely, the absence of a documented acknowledgement may raise a serious process question when other evidence establishes that prompt follow-up was needed. The evidence must support the particular inference being drawn.

What the clinician actually knew is also distinct from what the clinical situation reasonably required the clinician or care team to seek, review or follow up. Ordering a test ordinarily creates a follow-up task. Who held that task when the ordering clinician was away, and whether anyone was assigned to it at all, is a question about the organization's design as much as about individual diligence. Missing or misrouted information may itself be part of the process under review. Nonreceipt alone does not resolve whether the clinical response was appropriate.

Timestamps need an interpreter

A printed record may show one time per entry while the underlying system holds several: created, last edited, signed, cosigned, printed. A "last modified" value may reflect an automated process rather than a person. A result's finalization time may differ from the time it was released to the ordering clinician's inbox. These distinctions depend on the specific system and its configuration.

A records custodian or a qualified EHR forensic specialist explains what a field means and extracts audit data in a way that can be validated. The clinical reviewer interprets the clinical significance of what that evidence establishes, and should not assign meaning to an unfamiliar field merely because it looks precise. Useful additional evidence often includes routing records, coverage schedules, telephone and messaging logs, outside reports, and written descriptions of how the relevant workflow operated at the time.

ONC's SAFER Guides give separate attention to test results reporting and follow-up and to clinician communication. They are useful references for examining the processes that connect information to action. They do not decide responsibility or the standard of care in an individual case.

What the finished chronology looks like

A good chronology preserves uncertainty instead of resolving it by assumption. Continuing the example, four rows might read as follows.

The chronology can state that a result was finalized at a particular time, that a call was documented later, and that the interval between them remains unexplained. It should not fill that interval with an invented account of knowledge, intent or inaction.

A fair review looks both ways

The same discipline that exposes a gap protects against an unfounded one. The result may have been routed to another responsible team. An action may appear in a separate record, such as a covering clinician's message or a nurse's telephone log. The Monday clinician may have been off duty with documented coverage. A planned interval before a recheck may have had a reasonable clinical basis.

An apparent delay may also remain clinically concerning after every one of those possibilities is examined: a critical value routed to a pool no one monitored, an acknowledgement with no communication, a coverage arrangement that existed on paper and nowhere else. A defensible decision under uncertainty, an unresolved documentation problem, a process failure and a medically supportable allegation are different conclusions. The chronology's value is that it lets the evidence decide which one is warranted.

What a review of this issue can deliver

A source-linked chronology that keeps each clock separate, marks every entry documented, inferred or unknown, names the records needed to close each gap, and states which conclusions the evidence supports and which it does not. That chronology is the core of Medical Record Review and Case Assessment and of results questions in Primary Care Decisions and Diagnostic Follow-Up. A fictional example appears among the work samples, and the step-by-step method is set out in How a Review Is Organized.