HL7 Inbound & Transformation
Catches an inbound HL7 message from an outside system, checks and acknowledges it, then transforms it into FHIR and hands it off — with every step logged.
The workflow
The complete flow, exactly as it runs in the Workflow Builder. Scroll to explore, or use the zoom controls.
Requirements
Set up these connections in the Workflow Builder before importing or running this workflow.
Buffers incoming HL7 messages so nothing is lost if the destination system is briefly slow or unavailable.
The system that receives the translated FHIR record once the inbound message has been validated and acknowledged.
About this workflow
Hospitals, labs, and partner systems still talk in HL7 — a messaging format that's been the industry standard for decades. This workflow is the receiving end of that conversation: it listens for inbound HL7 messages, makes sure each one is valid, confirms receipt, and transforms it into FHIR before handing it off — automatically, with a clear record of what happened.
The problem
Plenty of systems still only send HL7 — there's no way around it. Someone has to build a way to catch that traffic reliably, tell the sender whether each message landed or failed, and turn it into something modern systems can actually use. Get any of that wrong and messages get silently dropped or a bad one slips through unnoticed.
How it works
An inbound HL7 message arrives through a queue, so nothing is lost even if the next step is briefly busy. It's validated and parsed, then an acknowledgment goes straight back to the sender — accepted if the message was valid, rejected with a reason if it wasn't.
A valid message is mapped from HL7 into a FHIR record and sent on to its destination system. Every step along the way — the ack, the mapping, the handoff — is written to an audit log, and anything that fails validation is caught and logged instead of silently lost.
Why it matters
The sender always knows whether their message landed. Nothing gets dropped, because it comes through a queue instead of a fire-and-forget request. Downstream systems get clean, modern FHIR instead of raw HL7, and every step leaves an auditable trail of exactly what arrived and what happened to it.
Who it's for
Teams that need to accept inbound HL7 from hospitals, labs, or legacy partner systems, and MedTech vendors bridging HL7-only senders into a modern FHIR-based stack.
How to build this workflow
Recreate it in the Workflow Builder by wiring these steps in order — or download it above and import it directly.
Step 1: Message Arrives
A hospital, lab, or partner system sends an HL7 message. It lands in a queue first, so nothing is lost even if the next step is briefly busy.
Step 2: Checked & Parsed
The message is validated and parsed. Anything malformed is caught right here, before it can cause problems downstream.
Step 3: Confirmation Sent Back
An acknowledgment goes straight back to the sender — accepted if the message was valid, rejected with a reason if it wasn't.
Step 4: Translated to FHIR
A valid message is mapped from HL7 into a modern FHIR record, ready for today's systems to use.
Step 5: Delivered & Logged
The FHIR record is sent on to its destination, and every step along the way is written to an audit log.