Chapter 1: The Record Behind the Record
IN THIS LESSON
A working model of how EHR systems are built, whatever the vendor: separate modules, encounters, non-standard status words, interfaces with their own clocks, logging as a separate subsystem, and the print template that decides what reaches paper.
Chapter 1 · The Record Behind the Record
After this lesson you will be able to
- Name six structural features of an EHR that affect how you scope a request and read a response.
- Explain why a printed or PDF chart is a rendering, not the record itself.
You do not need to be an engineer
A working knowledge of how EHR systems are generally built helps you scope requests and interpret responses, whatever the vendor platform: Epic, Oracle Health (Cerner), MEDITECH, athenahealth, and others. The six features below hold across platforms.
Six things that are true of almost every EHR
1. Modules behave differently
Notes, flowsheets, orders, and the medication administration record (MAR) are often separate subsystems with their own revision behavior, even inside one EHR. What is true of how a progress note keeps its history may not be true of a flowsheet row or a MAR entry.
2. Encounters organize everything
Documents attach to an encounter or visit record. That matters when you scope a request by date range, because a date range and an encounter are not always the same thing.
3. Status words are not standardized
Draft, preliminary, final, signed, locked, and amended mean different things in different systems. Always confirm what a given system means by each term.
4. Interfaces carry their own clocks
Outside data, such as labs, monitors, and pharmacy, posts on its own timestamps. Those can differ from when a clinician reviewed or acted on the data.
5. Logging is separate from documentation
Access and audit logging is usually a separate technical subsystem, often requiring IT involvement to extract. That is why routing matters: the department that copies the chart is usually not the department that can pull the log.
6. What prints is a rendering
A printed or PDF chart is a report generated from the database using a print template. The template decides which version, which fields, and which timestamps appear. Two printouts of the "same" note can differ.
Hold on to this
Every printout is a rendering. Ask which version, which template, and which of several possible signature times it displays.
Why the sixth point changes how you read a chart
When you hold a certified copy of a record, you are holding the output of a report definition. Someone, at some point, configured that report to show certain fields and hide others. A template can print only the current version of a note. It can show the time a note was first signed and omit the time it was later re-signed. It can drop an on-screen status flag.
None of that is necessarily improper. It is how reports work. It does mean that "the chart says" is shorthand for "this template, on this date, printed this version."
| What you see on paper | What may sit behind it |
|---|---|
| One note | Several saved versions |
| One signature time | Creation, signature, co-signature, and re-signature times |
| A status of "signed" or "final" | A status history, and a system-specific definition of each word |
| A lab result with a time | Collection, verification, transmission, and posting times, on different systems |
| No sign of who looked at it | An access log in a separate subsystem |
The capstone case is built on this lesson. Keep it in mind.
Key takeaways
- Modules have their own revision behavior. Do not assume a note, a flowsheet, and a MAR entry keep history the same way.
- Status words are not standardized. Ask the facility to define its own terms.
- Interfaces post on their own clocks.
- Logging lives in a separate subsystem, usually reached through IT.
- A printed chart is a rendering produced by a print template.
Check yourself
Answer each question in your own words before you open the answer.
1. Two certified copies of the same note, printed a year apart, show different text. Name two explanations you would want to rule in or out before saying anything about the difference.
Show the answer
The note may have been revised between the two print dates, so each printout shows the version that was current at the time. Or the two printouts may have used different print templates that display different versions or fields. Both are questions for version history and print settings.
2. Why might the HIM department be unable to produce an audit trail alone?
Show the answer
Access and audit logging is usually a separate technical subsystem. Extracting it often requires IT involvement.
3. A lab result shows 03:47 in the EHR. What does that time tell you by itself?
Show the answer
Only that the EHR shows the result at that time. Interfaces carry their own clocks and queues, so collection, verification in the lab system, and posting to the EHR may each have a different time.
Downloads for this lesson
Next: The Two Rules. Two sentences that decide how you read every timestamp in this course.