FHIR and HL7 v2 integration services
We build FHIR R4 and HL7 v2 integrations between your app, portal, remote monitoring tool or CRM and the EHRs your customers use. Use FHIR when your app needs to query or write data through an API, and HL7 v2 when the other side already sends event feeds that way. Most US projects need both, so we plan each data flow on its own.

What is the difference between FHIR and HL7 v2?
HL7 v2 is a messaging standard. The FHIR specification describes it as using messages composed of reusable segments, and calls it one of HL7's most widely adopted standards, prominent in inpatient settings. One system sends a message when something happens, such as an admission or a lab result, and the other processes it.
FHIR is built around resources. The FHIR overview says the basic building block is a resource and all exchangeable content is defined as one: a Patient, an Observation, an Encounter. Apps read, search, create and update resources through a web API. FHIR also supports an event-based messaging style similar to v2.
FHIR R4 (4.0.1) is a mix of normative and trial-use content, and it is the version US certification rules point to. HL7 has since published R5, but certified EHR APIs are built on R4.
When should your integration use FHIR, and when HL7 v2?
Use FHIR when your app asks questions: show this patient's medications, pull recent labs, list upcoming appointments. Use it for patient-facing apps and for apps that launch inside the EHR, where SMART on FHIR handles sign-in.
Use HL7 v2 when the other side already sends or accepts v2, when you need a push feed of events as they happen, or when you are connecting into a hospital's interface engine that its integration team already runs.
Many products need both: FHIR for the app's on-demand reads and a v2 feed for real-time events. We make the choice separately for each data flow.
What does SMART on FHIR add?
SMART App Launch is the HL7 guide that defines how apps authorize with a FHIR server. It describes patterns based on OAuth 2.0 for client apps to authorize, authenticate and integrate with FHIR-based systems, and it lets the EHR pass launch context, such as the current patient, into the app.
It covers apps launched from inside an EHR session, apps a user opens on their own, and Backend Services for headless clients with no user involved. Permissions are expressed as scopes, so an app asks only for the data it needs, and a reviewer can approve each one.
The current published version of the guide is 2.2.0. Which version a given EHR supports is part of what we confirm in the audit.
What do US rules require from certified EHR APIs?
ONC's §170.315(g)(10) criterion sets the API that certified EHRs must offer. It requires FHIR R4 (4.0.1), US Core, SMART App Launch for authorization, and Bulk Data for requests about groups of patients. The baseline versions are US Core 6.1.0, SMART App Launch 2.0.0, Bulk Data 1.0.0 and USCDI v3, with later versions approved for vendors that adopt them.
The rule also sets behavior your app must handle. Refresh tokens for confidential apps must be valid for at least three months, the server must revoke an app's access at a patient's direction within one hour, and the API documentation must be available at a public link without preconditions.
US Core itself is now at version 9.0.0, but what matters for a build is the version the customer's EHR certified, which may be older. We build against that version and test against the EHR's capability statement.
What can you read and write, and what needs approval?
Reads through FHIR R4 and US Core are the predictable part, because certified EHRs must support them. Writes vary by vendor and by resource, so we check the EHR's capability statement for each one and confirm with the customer that it is enabled.
An HL7 v2 interface needs the customer's integration team to set up the feed on its side, and every feed needs its own mapping. The FHIR specification notes that while some v2 elements map to FHIR core, a large percentage do not, and that mappings usually have to be done implementation by implementation. Local extensions called Z-segments are opaque without explanation from the sender, so we ask for samples early.
In both cases the customer approves what your app may see and change, and its security team reviews how you handle the data.
What do we need from you to start?
The systems you need to connect to, with a sponsoring customer or partner for each, and a contact in its IT or integration team. For HL7 v2, sample messages and the interface specification from the sending system save weeks of guessing.
A signed BAA before we touch PHI, the list of features in the first release, and one person on your side who owns the integration decisions.
If the work targets a specific EHR, access to its developer program and sandbox in your company's name, so credentials stay with you.
What drives timeline, cost and risk?
We do not publish a price, because the drivers differ by project: the number of data flows, how many need writes, how many v2 feeds need custom mapping, and how many customers or EHRs you connect to.
The common risks are assuming FHIR replaces v2 where it does not, building against a newer US Core than the customer's EHR supports, and leaving v2 mapping until late. We cover these in the audit and test with real sample data before launch.
On every project we sign a BAA before PHI, scope access so each clinician sees only their own patients, and run a penetration test before launch.
How we run a FHIR and HL7 integration
- 1
5-day free technical audit
We read your product, your data flows and the vendor's current documentation, then list every read and write your features need and the API or interface that serves each one. You get a written report, whether or not you hire us.
- 2
Scope and dated plan
From the report we agree the scope, the order of work and a plan with dates, including the points where we wait on the vendor or your customer. We sign a BAA before any PHI is in reach.
- 3
Build in the vendor sandbox
We build each data flow against the vendor's sandbox or a test feed with sample messages, reads first, then writes and mappings. For any part of a vendor's platform we work from its documentation and sandbox.
- 4
Testing
We test each flow against the EHR's capability statement and sample data, including failures and token expiry, then repeat the main flows in the customer's test environment.
- 5
Go-live with a penetration test
Before launch we run a penetration test and fix what it finds, then go live with the customer and watch the first days of real traffic. Access is scoped so each clinician sees only their own patients.
FHIR and HL7 integration questions
1Is FHIR replacing HL7 v2?
Not as a drop-in replacement. The FHIR specification presents them as different standards and notes that a large percentage of v2 elements do not map to FHIR core. The API that ONC requires from certified EHRs is FHIR-based, while many hospital event feeds still run on v2, so most integrations use both for years.
2Which FHIR version should we build on?
FHIR R4 (4.0.1) for US EHR integrations, because that is the version ONC's certification criterion requires. Within R4, build to the US Core version the customer's EHR certified, which may be older than the latest published US Core, and check the EHR's capability statement.
3What is US Core?
US Core is the HL7 guide that sets minimum constraints on FHIR resources for US use. It lists the elements, extensions and value sets that must be present and the minimum interactions for each profile, and its annual releases track changes to USCDI. Certified EHR APIs must support it.
4Do we need SMART on FHIR?
If your app connects to a certified EHR's FHIR API, yes, because that API uses SMART App Launch for authorization. It covers user-facing apps launched from the EHR or on their own, and Backend Services for server-to-server access with no user.
5Can you test without a live EHR?
Mostly. Epic and Oracle Health both publish developer sandboxes, and for v2 we build against sample messages and a test feed. Sandbox data is not the customer's data, so we always repeat the main flows in the customer's test environment before launch.
6How do you work on a FHIR or HL7 project?
For any part of a vendor's platform, we work from its documentation and sandbox, and from the FHIR and HL7 specifications themselves. The 5-day free technical audit ends with a written report on what each data flow needs, which you can use with us or with another team.
Sources and further reading
- HL7 FHIR R4: Overview
- HL7 FHIR R4: Comparison with HL7 v2
- HL7 SMART App Launch Implementation Guide
- HL7 US Core Implementation Guide
- ONC (ASTP): §170.315(g)(10) Standardized API for patient and population services
- Epic on FHIR: developer site and sandbox
- Oracle Health: FHIR R4 service root URLs (open and secure sandbox)