HL7 vs FHIR is a comparison between two generations of data exchange from the same standards body, and most healthcare organizations run both at once. HL7 v2, first published in 1987, moves pipe-delimited messages between systems such as an EHR and a lab. FHIR, which reached its first draft release in 2014, exposes similar data through web APIs that developers call on demand.
This article puts the two side by side, shows where each still fits, and spends extra time on the billing side, where FHIR’s claim and coverage resources and the CMS prior authorization rule are changing the workflow.
Key Takeaways
- HL7 v2 still carries most internal hospital interfaces and will for years.
- FHIR uses REST, JSON, and XML, so standard web tooling can work with clinical data.
- CMS and ONC rules point to FHIR R4 for patient access, provider access, payer-to-payer exchange, and prior authorization.
- FHIR touches billing mainly through prior authorization, eligibility, and patient access data, while HIPAA claims still travel as X12 transactions.
What HL7 v2 Handles Today
HL7 stands for Health Level Seven, a nod to the seventh layer of the OSI networking model, the application layer. Health Level Seven International publishes the HL7 standards family, and the v2 branch is the one most hospital interfaces still run on.
A v2 message is a block of text split into segments, and each segment is split into fields by pipe characters. An admission message carries the patient’s name, birth date, and visit details in a fixed order that the sending and receiving systems both agree on. Messages usually travel over a dedicated connection through an interface engine that routes and translates them. Each pair of systems tends to have its own interface, and each interface needs its own build and upkeep. Teams maintaining them can find more on implementing HL7 v2.x interfaces.
HL7 v3 arrived in 2005 with a heavier, more formal model and never displaced v2 for everyday messaging. Its document format, CDA, lives on in the C-CDA summaries that EHRs exchange.
What FHIR Changes About Data Exchange
FHIR, short for Fast Healthcare Interoperability Resources, is also published by HL7 and documented at hl7.org/fhir. Instead of one large message per event, it breaks data into resources, small units such as Patient, Observation, Medication, Claim, and Coverage. Each resource has a defined structure, its own URL, and a version history, and it can be read or written on its own.
Developers reach resources through ordinary HTTP calls. Reading a patient looks like GET [base]/Patient/123 and returns the resource as JSON or XML, depending on what the client asks. Creating, updating, deleting, and searching follow the same pattern for every resource type, so a developer who has learned one resource has learned the mechanics of the rest. Our guide to FHIR resources and billing data goes deeper on the resource model.
Versions matter. R4, released in 2019, was the first release with normative content, and it is the version that ONC certification and the CMS rules name. R5 followed in 2023 as a trial-use release, and HL7 has stated that R5 will not be submitted to ANSI as a normative standard. R6 is now in ballot. HL7 keeps the full history on its FHIR versions page.
HL7 v2 and FHIR Side by Side
| Aspect | HL7 v2 | FHIR |
|---|---|---|
| Data structure | Pipe-delimited segments and fields in a fixed order | Resources with defined elements, in JSON or XML |
| Transport | Usually a dedicated connection such as MLLP, often routed through an interface engine | HTTP with REST conventions |
| Exchange pattern | Event-driven messages with acknowledgments | Request and response, with optional subscriptions |
| Security | Handled outside the standard, such as VPNs and TLS tunnels | OAuth 2.0 and TLS, commonly through SMART on FHIR |
| Coded data | Coding system identifiers in fields, with frequent local codes | CodeableConcept elements that point to code systems by URL |
| Tooling | Interface engines and specialized HL7 libraries | Standard web tooling, FHIR servers, and SDKs |
| Typical use | Internal feeds between EHR, lab, radiology, and admission systems | Patient apps, payer APIs, and data sharing across organizations |
The exchange pattern is the row people most often get wrong. HL7 v2 is event-driven and mostly asynchronous. A system sends a message when something happens, such as a registration, and the receiver returns an acknowledgment. FHIR’s REST API is request and response, so a client asks for a resource and gets an answer in the same call.
Security and coding differ in similar ways. The FHIR specification leaves authentication to profiles built on OAuth 2.0, and SMART App Launch is the common one. A v2 message has no authentication of its own and inherits whatever protection the network provides. Both standards can carry LOINC, SNOMED CT, RxNorm, and ICD-10 codes, but FHIR requires a value to declare which code system it comes from, which helps when data crosses organizational lines.
Where Each One Fits and How They Connect
A hospital might keep v2 feeds running between its EHR, lab, and radiology systems while exposing a FHIR API for a patient portal and for payer data requests. Replacing a working v2 interface rarely pays for itself, so most organizations add FHIR at the edges and leave stable internal feeds alone. New work, particularly anything patient-facing or payer-facing, starts on FHIR.
Moving data between the two takes mapping. Segments and fields have to be translated into resources and elements, and v2 codes into FHIR code systems. HL7 publishes mapping guidance, and integration engines do much of the work. Round trips can lose detail because the two models do not express everything the same way, so test with real messages before trusting a mapping.
What FHIR Means for Billing, Eligibility, and Prior Authorization
FHIR carries financial and administrative data too. Coverage, Claim, ClaimResponse, and ExplanationOfBenefit describe insurance, billed services, and payer decisions. ExplanationOfBenefit, for example, is how payers expose adjudicated claim data to patient apps under the CMS patient access rules.
None of this retires the X12 transactions that HIPAA names for claims and remittance. An 837 still goes out and an 835 still comes back. FHIR reaches billing through the workflow around the claim, and prior authorization is where that shows most.
The CMS Interoperability and Prior Authorization final rule (CMS-0057-F), issued in January 2024, adds Provider Access, Payer-to-Payer, and Prior Authorization APIs to the Patient Access API required by the 2020 rule. API compliance dates generally begin January 1, 2027, and some operational requirements, including faster prior authorization decisions, started in 2026. CMS has also said it will not enforce the HIPAA X12 278 requirement against entities that use an all-FHIR prior authorization API.
Authorization problems tend to resurface as denials, so cleaner authorization data should shrink a category of rejections that denial management teams currently chase by phone and fax.
Limits to Plan For
FHIR is a framework, so two FHIR servers are not interoperable by default. Implementation guides such as US Core narrow the choices, and each payer API depends on guides layered over the base specification. Large data pulls are heavy for a request-and-response API, which is why bulk export has a guide of its own. Some areas, genomics among them, still lean on extensions. And v2’s long history means tested interfaces and trained staff that FHIR ecosystems are still building.
HL7 vs FHIR Questions
Is FHIR replacing HL7 v2?
Organizations are adding FHIR for new patient-facing and payer-facing work and leaving working v2 interfaces in place. Replacement happens interface by interface, usually when a system is upgraded or retired.
Which FHIR version should I build against?
R4 for US work. ONC certification and the CMS rules name R4 and the implementation guides built on it. R5 is a trial-use release that HL7 will not submit to ANSI as normative, and R6 is still in ballot.
Does FHIR replace X12 837 and 835 transactions?
Claims and remittance remain X12 under HIPAA. FHIR’s financial resources appear in patient access and payer APIs, and CMS lets plans offer a FHIR-only prior authorization API.
Is an HL7 v2 interface secure?
The standard leaves security to the network. Well-run v2 interfaces sit behind VPNs or TLS tunnels with access controls and logging, since the message itself carries no authentication.
Medwave on the Payer Side of Interoperability
Interoperability rules change how payers, EHRs, and practices exchange data, and the results land on the billing and credentialing desk. Medwave takes care of medical billing, credentialing, and payer contracting for practices with its own in-house staff, which keeps us close to the authorization and denial problems these rules are meant to ease.
Co-Founder and COO of Medwave, bringing more than 25 years of hands-on experience in healthcare revenue cycle management, payer contracting, and medical credentialing.

