Skip to content
AIM Digital Technologies

Guides··3 min read

HL7 vs FHIR: A Plain-English Guide to EHR Integration in 2027

HL7 v2 vs FHIR explained for founders and developers: what each standard does, when to use which, SMART on FHIR, how integrations with Epic and other EHRs work, timelines and cost.

Short answer: HL7 v2 is the older standard hospitals use to push event messages between internal systems. FHIR is the modern web API standard for requesting health data as JSON. If you are building a new app, start with FHIR and SMART on FHIR; add HL7 v2 only where the data you need is not available through FHIR.

HL7 v2 vs FHIR at a glance

HL7 v2FHIR (R4)
StyleEvent messages pushed between systemsREST API: apps request and write resources
FormatPipe-delimited text segmentsJSON or XML
Typical useAdmissions (ADT), orders (ORM), results (ORU), scheduling (SIU)Patient apps, clinician apps, payer APIs, analytics
TransportMLLP over a private network or VPNHTTPS with OAuth 2.0
ConsistencyVaries by hospital; each interface needs mappingMore uniform, especially with US Core profiles
Developer experienceNeeds an interface engine and specialist knowledgeFamiliar to any web or mobile developer
Best forReal-time feeds inside a health systemThird-party apps and patient access

How widely available is FHIR?

Widely. In the United States, certified EHRs must offer a standardized FHIR API under federal health IT rules. About 9 in 10 hospitals enabled patient access to their data through an API in 2024, according to the federal health IT office (ASTP/ONC), and 2 in 3 hospitals reported using a FHIR API for patient access in 2022 (ONC Data Brief 68). Smaller, rural and independent hospitals lag behind, so check each target customer.

The pieces you will meet

  • FHIR resources. The building blocks: Patient, Practitioner, Encounter, Appointment, Observation, Condition, MedicationRequest, DocumentReference and more.
  • US Core. The US profile of FHIR that defines which fields must be supported, so data looks similar across vendors.
  • SMART on FHIR. App launch and authorization: OAuth 2.0 scopes, single sign-on and patient context.
  • Bulk FHIR. Exports of data for many patients at once, used for analytics and population health.
  • Interface engine. Software such as Mirth Connect that receives, transforms and routes HL7 v2 messages.
  • Integration platforms. Services that offer one API across many EHRs for a recurring fee.

Which should you use?

You are building…Start with
A patient-facing app that shows recordsFHIR patient access APIs
A clinician app that opens inside the EHRSMART on FHIR
A product that reacts to admissions or new lab results in real timeHL7 v2 ADT and ORU feeds, or FHIR Subscriptions where offered
Analytics across a whole patient populationBulk FHIR export
A product for many small practices on different EHRsAn integration platform, then direct connections for big customers

How an EHR integration project runs

  1. Define the data. List exactly which fields you need to read and write, and map them to FHIR resources.
  2. Register with the vendor. Create a developer account and app registration in the EHR vendor's program.
  3. Build against the sandbox. Use synthetic patients to build authorization, reads, writes and error handling.
  4. Security and privacy review. Complete the vendor's and the hospital's questionnaires; expect questions about encryption, access and BAAs.
  5. Pilot with one site. Validate real-world data quality, which is always messier than the sandbox.
  6. Monitor. Track failures, token expiry and version changes, with alerts and a replay queue.

Common mistakes

  • Assuming every hospital on the same EHR exposes the same data. Configurations differ.
  • Leaving the vendor and hospital reviews until the code is finished.
  • Storing more patient data than the product needs.
  • Ignoring write-back. Reading is easy; writing notes or orders needs more approval and testing.
  • Treating the integration as finished at go-live. APIs and profiles change.

Cost and timeline

With our team, a read-only FHIR integration with one EHR typically costs $2,000–$4,000 and takes 4–8 weeks of engineering. A SMART on FHIR app costs $4,500–$8,250, and a set of HL7 v2 interfaces $3,750–$7,000. See EHR and EMR development and integration, or read the HIPAA compliance checklist before you handle real records.

FAQ

Frequently asked questions

Can't find your answer? Ask our team.

What is the difference between HL7 and FHIR?

HL7 v2 is an older, event-based messaging standard: systems push pipe-delimited messages such as admissions, orders and results to each other. FHIR is a modern web API standard, also from HL7, where apps request JSON resources such as Patient, Appointment and Observation over HTTPS. FHIR is easier for app developers; HL7 v2 is still everywhere inside hospitals.

Is FHIR replacing HL7 v2?

Gradually, for app and patient access. US regulations require certified EHRs to offer standardized FHIR APIs, so new apps start there. Inside hospitals, HL7 v2 interfaces for admissions, orders and lab results will remain in use for years, so many integrations use both.

What is SMART on FHIR?

A standard for launching third-party apps from inside an EHR. It uses OAuth 2.0 to sign the user in and passes the app the current patient and encounter, so a clinician can open your app from the chart without another login.

How long does it take to integrate with Epic or Oracle Health?

The engineering for a read-only FHIR integration is usually 4–8 weeks. Production access takes longer because the vendor and each hospital review the app and its security. Plan for a few months end to end, and start the paperwork early.

How much does EHR integration cost?

With our team, a read-only FHIR integration with one EHR typically costs $2,000–$4,000, a SMART on FHIR app $4,500–$8,250 and a set of HL7 v2 interfaces $3,750–$7,000. Vendor program fees are separate.

Should a startup use an integration platform such as Redox?

Often, yes, at the start. Integration platforms give you one API to many EHRs and handle much of the connection work, for a recurring fee. Building direct integrations costs more up front but less per connection at scale. Many companies start with a platform and go direct for their largest customers.

Free consultation

Turn ideas from this article into a product

Tell us about your project and get a free 30-minute consultation with a senior engineer. You'll leave with clear next steps, whether you work with us or not.

  • Reply within one business day
  • NDA on request, 100% IP ownership
  • Clear scope, timeline and estimate
  • Talk directly to senior engineers

Mon–Fri, 10:00–19:00 Islamabad time

Prefer email or a call?

reachus@aimdigital.tech+92 315 2333303 Book a call

We reply within one business day. Your details are kept confidential and we're happy to sign an NDA. See our privacy policy.

Free consultationCall