If you work in payer or provider IT, you’ve heard both “HL7 v2” and “FHIR” used as if they’re competing standards you have to choose between. They’re not exactly rivals — they’re different generations of health data exchange that often run side by side. Here’s the plain-English difference and how to decide which belongs where.
HL7 v2: the workhorse that never left
HL7 version 2 has moved clinical messages between systems since the late 1980s — admissions, lab orders and results, pharmacy, scheduling. It’s a pipe-and-hat text format (segments like MSH, PID, OBR) that is compact, battle-tested, and deeply embedded in hospital and lab systems. It is not going away. The downside: it’s point-to-point messaging, loosely constrained, and every site implements it a little differently, so interfaces need custom mapping.
FHIR: the modern, API-first standard
FHIR (Fast Healthcare Interoperability Resources) is HL7’s modern standard, built on REST APIs, JSON/XML, and discrete “resources” (Patient, Claim, Coverage, Encounter). Instead of pushing a message and hoping it lands, a system queries an endpoint for exactly the resource it needs. That request/response model is why regulators chose FHIR for mandates like CMS-0057-F — it’s the natural fit for third-party apps, member portals, and payer-to-payer exchange.
The honest comparison
- Transport: HL7 v2 = messaging (often MLLP/TCP); FHIR = RESTful HTTP APIs.
- Format: HL7 v2 = pipe-delimited text; FHIR = JSON or XML.
- Access pattern: HL7 v2 = push a message; FHIR = query for a resource.
- Developer experience: HL7 v2 needs specialist integration engines; FHIR is approachable to any API developer.
- Where it’s strong: HL7 v2 for real-time clinical workflows inside a hospital; FHIR for external data sharing, apps, and regulatory APIs.
When to use which
You rarely rip out HL7 v2. The realistic pattern for a health plan or health system is both: keep HL7 v2 (and X12 EDI) for the internal and transactional flows that already work, and add a FHIR layer on top for everything outward-facing — member and provider apps, and the CMS-mandated APIs. The hard part isn’t choosing a standard; it’s mapping your existing HL7 v2 and X12 data into clean FHIR resources without losing fidelity.
That mapping work is exactly what trips plans up on the road to CMS-0057-F — and it’s where we spend most of our time. If you’re deciding how FHIR fits alongside your existing interfaces, a readiness assessment will map your current standards to where you need to be.