What a Printed Electronic Health Record Shows — and What It Leaves Out

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

• A report, not a screen
• The legal medical record and the working record
• Encounter types and what they imply
• Results and in-basket messaging
• Signatures, cosignatures and attestations
• Addenda and late entries
• Templates, smart text and copy-forward
• Problem lists and medication lists are living summaries
• Scanned outside records
• Ambient-AI drafts
• What to request, from a clinical-meaning standpoint
• Where audit-trail forensics begins
• What a careful reading concludes
• What a review of this issue can deliver

A report, not a screen

When counsel requests a patient's chart, what usually arrives is a report: hundreds or thousands of pages generated from a database according to rules someone configured. The clinician who cared for the patient never saw those pages. She saw screens: a chart summary with recent vital signs in a sidebar, a results view that graphed a value over time, an inbox with a flag on one item, an alert that fired and was dismissed, a flowsheet with hourly rows. Much of that may not appear in the production, and what does appear is rearranged by document type, separated from its context and stamped with times whose meaning is not self-evident.

This is not a reason to distrust the production. It is a reason to read it as what it is. Dr. Gill uses a widely used enterprise EHR in his daily practice and reads records from the clinician's side of the screen. The observations below are general to enterprise EHR systems such as those widely used in U.S. health systems; the specifics of any one system depend on its configuration and the organization's policies.

The legal medical record and the working record

Healthcare organizations define a "legal medical record": the information they designate as the business record of care and produce in response to requests. The definition varies. It commonly includes signed notes, orders, results, medication administration and scanned documents. It may or may not include staff messages, secure chat, clinical decision-support alerts and the responses to them, flowsheet rows not configured to print, draft or pended notes, and the metadata showing who viewed what and when.

The gap between the legal medical record and the working record is where many clinical questions live. If the dispute is whether a nurse told a physician about a falling blood pressure, the answer may sit in a messaging function the production omitted. If it is whether a clinician saw a warning, the answer may sit in decision-support logs no one requested.

Encounter types and what they imply

EHRs organize documentation into encounters, and the label can mislead. Office visits, telephone encounters, refill encounters, orders-only encounters, results-only encounters, portal messages and scanned-document encounters all appear in a production as dated entries, often with a clinician's name attached. Only some involved seeing the patient. A "visit" on a given date may be a refill authorization; a result "reviewed" on a date may sit in an encounter the system created automatically when the result arrived. The reviewer reads the encounter type before reading the content.

Results and in-basket messaging

Results usually reach clinicians through an inbox: a queue of results, messages, refill requests and documents awaiting signature. The production may show the result and sometimes an acknowledgement. It rarely shows which queue the result sat in, who else could see that queue, or how many items it held. Staff messages ("patient called asking about results") and their replies may be produced as separate telephone encounters, embedded in notes, or omitted altogether. A result note, the clinician's brief interpretation attached to a result, may print with the result or somewhere else entirely.

Signatures, cosignatures and attestations

A note can be in progress, pended, signed, cosigned or addended, and each state has its own time. "Electronically signed by" records that a user finalized the entry in the system; what the signature attests depends on the workflow. A supervising physician's cosignature on a resident's or physician assistant's note may reflect anything from a detailed review to a routine queue action, and attestation language ("I have seen and examined the patient") is often templated. The production usually shows the final state and a single time. The date of service and the date of signature may be days apart, and both may differ from when the content was first entered.

Addenda and late entries

Addenda are a normal part of clinical documentation: a clinician adds a result, clarifies a plan or corrects an error. A well-designed system labels the addendum, dates it and preserves the original. CMS guidance for Medicare review expects amendments, corrections and delayed entries to identify their date and author and to be clearly and permanently denoted; that expectation is useful context, with its program-specific scope kept in view. A production may show only the current version of a note, and prior versions can often be requested. An addendum's timing relative to an adverse event is worth noting. On its own, it establishes nothing about intent.

Templates, smart text and copy-forward

Much of a modern note is not typed. Templates supply structure and default text; smart phrases insert standard paragraphs; linked data elements pull in vital signs, medications and results; copy-forward carries a prior note's content into a new one. These tools save time and can carry errors. A normal examination may be an unedited template default. A history may be last year's, copied forward. A medication list may reflect what was true when the data refreshed, not when the clinician saw the patient.

Problem lists and medication lists are living summaries

The problem list and the medication list are not notes. They are continuously edited summaries. Depending on how the report was designed, a printout may show the list as it stood when the report was run rather than when a particular visit occurred. Changes to each list, with who made them and when, are usually recorded in a history that the standard production omits. When a dispute turns on whether a diagnosis or medication was on the list at a given moment, the list history should be requested and its meaning confirmed with the custodian.

Scanned outside records

Outside records, faxed results, consent forms and handwritten documents enter the EHR as images. A scanned item may carry several dates (created, received, scanned, indexed) and only one may print. Whether a clinician could have seen a scanned document at a given time depends on when it was indexed and whether any task drew a clinician's attention to it. A document present in the chart is not the same as a document brought to someone's attention.

Ambient-AI drafts

Where ambient-AI drafting is used, one encounter may generate a recording, a transcript, a machine draft, clinician edits and a final signed note. Which of these are retained, for how long and where depends on the product, its configuration and the organization's policies; some may never become part of the legal medical record. Counsel who need to compare the draft with the final note should ask early what exists. California Penal Code §632 addresses consent of all parties to recording a confidential communication, and AB 1637 (Stats. 2026, ch. 536), adding Business and Professions Code §2266.1, concerns authorship and alteration of physician patient notes. Their bearing on a matter is for counsel.

What to request, from a clinical-meaning standpoint

The right request depends on the clinical question. As a starting list for the period in dispute:

• All versions of each disputed note, with addenda and the times of creation, signature and cosignature
• Flowsheets (vital signs, nursing assessments, withdrawal or pain scores) at their native time resolution
• The medication administration record, with scheduled and actual times and reasons for held doses
• Orders, with creation, signature, release and discontinuation details
• Results, with finalization, routing and acknowledgement information and any result notes
• Staff and secure messages, telephone encounters and patient-portal messages
• Problem-list and medication-list histories
• Scanned media, with receipt, scan and index dates
• Referral, authorization and scheduling records
• Decision-support alerts and responses, where relevant
• Ambient-AI recordings, transcripts and drafts, if retained
• Audit data for specific encounters and users, extracted by a qualified specialist
• Documentation of how the production report was configured

Disclosure of protected health information in litigation proceeds under rules such as 45 CFR 164.512(e), which addresses disclosures for judicial and administrative proceedings, including qualified protective orders. Those mechanics belong to counsel. The clinical contribution is identifying which records the clinical question actually requires, so that requests are targeted rather than sweeping.

Where audit-trail forensics begins

What a careful reading concludes

A careful reading cuts both ways. A note that seems missing may exist under a different encounter type. A puzzling time may be an artifact of how the report prints. A diagnosis that appears from nowhere may trace to a scanned outside record. Equally, a real gap remains real after those explanations are checked: a critical message that exists nowhere, a list changed after an event with no clinical reason recorded, an examination the patient's documented condition contradicts. Separating artifacts from substance early keeps counsel from building on either.

What a review of this issue can deliver

An orientation to the production as produced (what it contains and what it appears to omit, given the clinical question) with a targeted request list, followed by a clinical reading of the disputed entries in which each finding is tied to its source and each artifact explained. This work sits within Clinical Documentation and Record Consistency and Medical Record Review and Case Assessment. Timing questions are developed in The Medical Record Has More Than One Clock, and AI-drafted notes in A Medical Note Can Change Meaning Without Changing Much Text.