HL7 Workflows
Move device data, lab results, and clinical messages into the EHR in real time — using HL7, the messaging standard hospitals have relied on for decades.
About HL7
HL7 v2.x is the messaging standard that has quietly run hospitals for decades. When a patient is admitted, a lab result comes back, or an appointment is booked, an HL7 message carries that event between systems. It's text-based, pipe-delimited, and everywhere — almost every EHR, lab, and device speaks it.
These workflows take HL7 messages (or simple JSON from a device) and move the data into the EHR in real time — parsing the message, mapping it to the right format, and filing it against the right patient and visit.
What you can do
- Parse and transform HL7 v2.x messages — ADT, ORU, ORM, SIU and more
- File device readings and results straight into the patient's chart
- Create encounters and link clinical data to the right visit
- Runs over a simple HTTP endpoint — no heavy interface engine needed
Requirements
Set up these connections in the Workflow Builder before running any workflow in this category.
EHR Connection
A connection to your EHR system (Epic, Cerner, etc.) with HL7 interface support. Used to receive and file ADT, ORU, and other v2.x messages against the right patient and visit.
Backend System Auth
System-level credentials that let the workflow authenticate with the EHR without a user present — typically a client ID and secret issued by the EHR vendor.
Workflows
2 ready-to-use workflows — open any to see the full flow and download it.
Real-Time Remote Patient Monitoring in Epic
Stream vitals from remote monitoring devices straight into the patient's Epic chart — the visit is created and every reading filed automatically.
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.