X12 and NCPDP
The EDI standards that move American healthcare's money and prescriptions. Positional, terse, decades old — and still carrying more clinical-financial traffic daily than FHIR has moved in its lifetime.
In one line
X12 carries American healthcare's administrative and financial transactions; NCPDP carries its retail pharmacy traffic. They are unglamorous, positional EDI formats that predate the web — and they are mandated by HIPAA, which is why they will outlive most of the people predicting their replacement.
The transactions that matter
If you work US revenue cycle, these numbers are your vocabulary:
| Transaction | What it does |
|---|---|
| 270 / 271 | Eligibility enquiry / response — is this person covered? |
| 276 / 277 | Claim status enquiry / response — where is my money? |
| 278 | Prior authorisation request / response |
| 837 | Claim submission — professional, institutional or dental |
| 835 | Remittance advice — what was paid, what was cut, and why |
The 837 → 835 pair is the heartbeat of the American revenue cycle. You submit an 837; weeks later an 835 comes back and tells you, in codes, how much of your work is going unpaid. Reading an 835 fluently is a genuinely valuable skill — it's what the ERA reader exists to teach.
NCPDP SCRIPT is the e-prescribing standard between prescriber and pharmacy; NCPDP Telecommunication handles pharmacy claims in real time. When a US pharmacist tells a patient "your insurance rejected it" while they wait at the counter, that round-trip is NCPDP.
Why it looks the way it looks
An X12 segment is pipe-and-asterisk delimited, positional, and unreadable without a spec:
CLM*26463774*100***11:B:1*Y*A*Y*I~
Every field is identified by where it sits, not by a name. There are no labels. To know what
11:B:1 means you consult the implementation guide, and the implementation guide is long.
This was not incompetence. It was bandwidth. These formats were designed when transmitting data cost real money per character, and terseness was the whole point. Judging them by 2026 standards is like criticising a telegram for lacking emoji.
HIPAA is the reason they persist
Here's the thing engineers underestimate: X12 is not merely entrenched, it is legally mandated. HIPAA's Administrative Simplification rules name specific X12 versions as the standard for covered transactions. A US payer cannot simply decide to accept FHIR claims instead — the format is regulation, not preference.
That is why "FHIR will replace X12" has been said for a decade and hasn't happened. FHIR is winning the clinical exchange and going nowhere near the mandated financial one. The two coexist, and the bridge between them is a permanent job.
The contrast that makes India interesting
This is the comparison worth internalising, especially if you work both markets.
The US built its clinical record and its claim in two different universes. The chart speaks HL7 and FHIR; the claim speaks X12. They share no data model, so every claim is a re-keying of clinical reality into an alien format — and an entire industry exists to bridge that gap.
India, arriving later, skipped it. NHCX profiles claims on
FHIR R4 — the same standard the clinical side already speaks. A Claim can reference the
actual Condition that justifies it, rather than a shadow copy.
Whether India delivers on that is unproven. But the architecture is one the US spent thirty years and enormous money failing to reach — and it's a live example of a late-mover advantage that a leapfrogging health system genuinely captured.
Learning it
Do not try to memorise segment layouts; nobody does. Learn the shape: the envelope (ISA/GS/ST), the loops, the fact that hierarchy is expressed by HL segments rather than nesting, and the CARC/RARC codes that explain a denial. Then read real 835s until the shape stops being alien.
That skill is unglamorous, in demand, and — because CPT sits inside these claims — a large part of why India's RCM industry exists at all.