Mapping Workflows
Convert HL7 v2, X12, and JSON messages into FHIR R4 or any other target format — visually, with the mapping engine, no custom parsing code.
About Mapping
Most integration work isn't moving data — it's reshaping it. An HL7 v2 admit message, an X12 eligibility response, a FHIR Observation: each needs to become a different shape before the next system can use it. ConnectHealth's visual mapping engine builds that transform once, as a reusable mapping project, instead of hand-writing parsing code per format pair.
These workflows show the mapping engine doing the real work: a trigger feeds a raw message into a Mapper step, which runs a saved mapping project and hands off the transformed result — nothing else in the flow needs to know how the conversion happened.
What you can do
- Convert between HL7 v2, X12, and JSON/FHIR — any source format to any target format
- One reusable Mapper step per message type, driven by a saved mapping project
- Built-in synthetic payloads — run every example immediately, no connection to configure
- The same mapping that runs here is the one built visually in the Mapping Engine guide
Requirements
Set up these connections in the Workflow Builder before running any workflow in this category.
None — fully self-contained
Every workflow below is triggered by an Inject node carrying a built-in synthetic payload, so it runs immediately after import with no connection to configure. Point the trigger at a real listener (an HL7 In node, a FHIR webhook, etc.) to use it against live traffic.
Workflows
3 ready-to-use workflows — open any to see the full flow and download it.
HL7 v2 ADT to FHIR Patient
Convert an HL7 v2 ADT^A01 admit message into a FHIR R4 Patient resource with the visual mapping engine — no custom parsing code.
FHIR Observation to HL7 ORU
Convert a FHIR R4 Observation (a vitals reading) into an HL7 v2 ORU^R01 results message — the format most legacy EHRs and lab interfaces still expect.
X12 271 to FHIR Coverage
Convert an X12 271 eligibility response into a FHIR R4 Coverage resource — structured data instead of a raw EDI stream.