# Reading the hospital data stack: EHR clinical data versus claims
Mrs. Alvarez arrives for a total knee replacement. Her surgeon documents everything in Epic: the pre-op assessment, the implant serial number, the anesthesia record, two doses of a blood thinner, a mild post-op fever, and three days of physical therapy notes.
Two weeks later, the billing office sends a UB-04 claim to her insurer. That claim reduces her entire stay to a handful of codes and a dollar amount. Almost none of the physical therapy notes appear. The fever is gone. The implant serial number is nowhere.
Same patient. Same admission. Two datasets that tell different stories. Hospital leaders spend enormous effort reconciling them, and understanding why is the foundation of hospital data literacy.
EHR (Electronic Health Record): the clinical system of record. Epic and Oracle Health (formerly Cerner) dominate the US market. The EHR captures what happened to the patient clinically: vitals, medications, notes, labs, images, orders.
Claims: the billing system's output, sent to payers (insurers, Medicare, Medicaid) to get paid. For a hospital inpatient stay, the standard format is the UB-04 (also called the CMS-1450), an institutional claim form defined by the National Uniform Billing Committee.
The EHR answers "what did we do for the patient?" The claim answers "what will we bill, and how do we justify it?" These are related but not identical questions.
Follow Mrs. Alvarez through both systems.
On the UB-04, all of that collapses into structured codes:
Notice the compression. Days of clinical narrative become perhaps a dozen codes. That compression is where the two datasets diverge.
The EHR records clinical reality. The claim records billable, defensible reality. If a nurse documents a symptom that never becomes a formal diagnosis, it lives in Epic but never reaches the claim.
A trained medical coder (or increasingly, computer-assisted coding software) reads the chart and translates it into codes. That translation involves judgment. Did the fever count as a documented complication? Only if a physician wrote a diagnosis that supports it. This is why hospitals invest in CDI (Clinical Documentation Integrity) teams whose job is to ensure the chart supports accurate coding.
Epic data exists in real time. The claim is assembled after discharge, sometimes weeks later, and may be corrected and resubmitted. So on any given day, the two systems disagree simply because the claim has not caught up.
Epic knows the implant serial number for a device recall. The claim does not care. Conversely, the claim carries the final DRG that drives revenue, a field that does not naturally "live" in the clinical chart.
Imagine you pull both records for Mrs. Alvarez. Simplified, they look like this:
EHR (Epic) extract
------------------
encounter_id: 88213
admit_ts: 2026-03-02 06:41
procedure_note: "TKA, right knee, cemented implant"
implant_serial: ZX-4471-A
meds_given: [enoxaparin x2, acetaminophen x6, ...]
vitals_rows: 214
pt_sessions: 3
discharge_ts: 2026-03-05 11:20
UB-04 claim extract
-------------------
encounter_id: 88213
drg: 470 (major joint replacement, no MCC)
principal_dx: M17.11 (osteoarthritis, right knee)
icd10_pcs: 0SRC0J9
revenue_codes: [0360 OR, 0250 pharmacy, 0420 PT]
total_charges: [amount]
from_date: 2026-03-02
thru_date: 2026-03-05Same encounter_id links them. But the EHR has 214 vitals rows and an implant serial; the claim has a DRG and revenue codes. Neither is "complete." A hospital analyst who wants the full picture must join both.
Note the DRG detail: 470 versus 469 differs by whether the stay had an MCC (Major Complication or Comorbidity). If Mrs. Alvarez's post-op fever had been documented as a qualifying diagnosis, the stay might have grouped differently and reimbursed at a higher rate. That single documentation decision moves money. This is exactly why CDI exists, and why regulators scrutinize it.
Hospital executives make decisions from both datasets, and the gaps cause real problems.
Quality reporting. Public quality programs often use claims because claims are standardized and available across all hospitals. But claims miss clinical nuance. A patient who was genuinely sicker may look like a "complication" in claims data if documentation was weak. The Agency for Healthcare Research and Quality maintains widely used claims-based quality indicators that illustrate both the power and the limits of billing data.
Revenue integrity. If the EHR shows care that never made it onto the claim, the hospital may be under-billing. If the claim shows more than the chart supports, that is a compliance risk. Reconciliation protects both.
Population health and value-based care. In arrangements where hospitals are paid for outcomes, leaders need clinical detail (from the EHR) matched to cost detail (from claims). Neither alone is enough.
A modern development matters here: FHIR (Fast Healthcare Interoperability Resources), the industry standard for exchanging healthcare data via APIs. Federal rules now require certified EHRs to expose data through FHIR APIs, which makes it easier to pull structured clinical data programmatically rather than scraping notes. You can explore the standard at HL7 FHIR.
FHIR helps on the clinical side. It does not replace claims. The two data models remain distinct because their purposes remain distinct. FHIR just makes the clinical half more accessible for analytics.
Knowledge check
1. What is the fundamental distinction between the questions the EHR and the claim are designed to answer?
2. Why does the physical therapy detail, the implant serial number, and the post-op fever largely disappear on the UB-04 claim?
3. An analyst wants to know the exact times each medication dose was administered during Mrs. Alvarez's stay. Which dataset should they use and why?
4. Select ALL correct answers about what the EHR captures that the UB-04 claim typically does not.
Select all the correct answers.
5. Select ALL correct answers about why hospital leaders must reconcile EHR and claims data.
Select all the correct answers.
Think of it as choosing the right tool.
Use claims when you need:
Use the EHR when you need:
Use both, joined, when you need:
A practical trap for new analysts: assuming a claims count equals a clinical count. "How many patients got a blood thinner?" is an EHR question. The claim only shows a pharmacy revenue code, not each dose. Ask the claim a clinical question and you will get a confidently wrong answer.
The divergence is not a flaw to eliminate. It reflects two legitimate workflows: caring for patients and getting paid for that care. The reconciliation work (coders, CDI specialists, revenue integrity analysts, and increasingly automated tools) is a permanent feature of hospital operations, not a temporary bug.
For a non-technical leader, the key insight is this: when someone shows you a "hospital metric," your first question should be "is this from the clinical record or the claim?" The answer changes what the number can and cannot tell you.