HL7 & FHIR integration, done properly
I connect clinical systems to modern platforms — HL7 v2 and FHIR R4 pipelines, Mirth Connect channels, validated conversions and low-risk data migration. Remote, and used to working on critical systems.
Interoperability stopped being optional
The pressure to interoperate is real in every market — the 21st Century Cures Act and TEFCA in the US, NPHIES in Saudi Arabia, the DSQ ecosystem and Law 25 in Québec. The moment your systems have to exchange with a hospital, a payer or a national platform, they need clean HL7 and FHIR.
And the work is unforgiving: a mis-mapped field or a dropped message in a clinical feed is not a bug ticket, it is a patient-safety problem. It needs someone who has built these pipelines under real constraints — not learned them from a slide deck.
What I build
Interface engine channels
Mirth Connect channels — or a Spring Boot microservice — that receive, transform, route and acknowledge clinical messages, with per-message error reporting.
HL7 v2 ↔ FHIR R4 mapping
Field-level mapping with conformance validation, so what leaves your system is actually valid FHIR — not almost-valid.
Message types
ADT, SIU, ORM / ORU, MDM and custom Z-segments — scheduling, orders, results, documents, demographics.
FHIR bundle generation
Turning internal records into HL7-conformant FHIR R4 bundles for submission to hospital or national platforms.
Data migration
Moving patient and reference data between systems with a cutover plan, validation and rollback safety.
On-prem, behind your VPN
Everything can run inside your infrastructure. No PHI has to leave your walls, and I work behind your VPN when required.
Standards & tools I work with
Healthcare integration I have shipped
All case studiesMAIE — medical availability integration engine
→One endpoint that any provider can send to, whatever their format, with identifier resolution, de-duplication and per-slot error reporting.
Healthcare ITFHIR R4 Bundle Generator for Healthcare Systems
→99% conformance to FHIR profiles and a clean, independently deployable service that analytics and partner platforms can consume.
Healthcare ITHealthcare Integration with Mirth Connect
→Secure, validated data flow between critical systems, fewer integration errors, faster delivery of new interfaces, and live visibility into every channel.
Healthcare integration FAQ
HL7 v2 or FHIR — which one do we need?
Usually both, for a while. Legacy hospital systems still speak v2; national platforms and new APIs are FHIR. A good integration layer bridges the two rather than forcing a rip-and-replace.
Do you work with Epic, Cerner, Oscar, Meditech…?
I integrate with whatever exposes an interface — HL7 feeds, FHIR APIs, flat-file exports, database views. I do not need to be a certified admin of the source system to connect to it.
How is PHI handled?
By default nothing leaves your infrastructure: the interface engine, the mapping code and any storage run on your servers. I can work behind your VPN and sign a BAA / NDA before any data is shared.
Do you produce the mapping specification or just the code?
Both. I document the field-level mapping and the message flow so your team can audit and maintain it — the spec is a deliverable, not a black box.
Can you do a short assessment first?
Yes. A 1–2 week discovery: I review the systems and messages involved, define the mapping and the risks, and deliver a plan you can act on with or without me.
Do you work with clients outside Canada?
Yes — most of this work is remote. I have delivered HL7/FHIR integration for teams in different time zones and work in English, French and Arabic.
Have a clinical feed or a FHIR submission to build?
A 30-minute call is enough to tell whether I can help and what it would take.