Mapping Engine Overview
What the visual mapping engine does, which formats it converts between, and how the Tree, Table, and Liquid views stay in sync as you build a mapping.
The mapping engine is a visual editor for converting healthcare data from one format into another — no custom parsing code, no hand-written transform scripts. Point it at a sample message, wire the fields you care about to your target shape, and save a mapping project you can reuse anywhere in a workflow.
What you can map
Sources: HL7 v2.x messages, X12 EDI transactions, and plain JSON. Targets: JSON (including FHIR R4 resources), HL7 v2.x, and X12. A mapping project can convert any source format into any target format — for example, an HL7 v2 ADT admission message into a FHIR R4 Patient resource, or an X12 270 eligibility check into a FHIR Coverage resource.
57 starter templates ship out of the box across the most common HL7 v2 message types (ADT, ORU, SIU, DFT, MDM, VXU, and more) and the standard X12 transaction sets (270/271, 276/277, 278, 820, 834, 835, 837), so most projects start from a working template rather than a blank canvas.
Three synced views of the same mapping
Every mapping project is one underlying set of field connections, shown three ways — switch freely between them and every change stays in sync:
- Tree — drag a wire from a source field to a target field on a visual canvas. The fastest way to build and review a mapping's overall shape.
- Table — every mapped field as a spreadsheet-style row, with conditions and repeating-segment rules editable inline. Best for auditing a large mapping at a glance.
- Liquid — the compiled transform template itself, fully editable by hand for cases the visual tools don't cover. Hand edits flow back into the Tree and Table views automatically.
An Auto-Map assistant can also suggest field matches based on name and data-type similarity — accept the ones you want, adjust or dismiss the rest, and refine by hand in any of the three views.
Where mapping fits into a workflow
A saved mapping project is a reusable asset — reference it from a Mapper step in any workflow to transform messages in flight, or export it (optionally bundled together with the workflow that uses it) to move between environments.