Academy
⌘K
Getting Started
  • Platform Overview
  • AWS Marketplace Setup
  • Quickstart Guide
Connections
  • Overview
Workflow Builder
  • Overview
  • Nodes Catalog
Helix AI Assistant
  • Overview
Mapping Engine
  • Overview
Workflow Library
  • Overview
  • HL7
  • FHIR
  • Insurance
  • Agentic
  • Mapping
Security & Infrastructure
  • Architecture
  • HIPAA Compliance
  • Performance & Scalability
← Back to ConnectHealth
Get Started
Back to Mapping Engine Guide

Quick Start

Build one mapping start to finish — an HL7 v2 admit message to a FHIR Patient resource — and see how the Tree, Table, and Liquid views stay in sync with a live output preview.

This walkthrough builds one mapping start to finish: a synthetic HL7 v2 admit message (ADT^A01) transformed into a FHIR R4 Patient resource. It's the fastest way to see how the three views — Tree, Table, and Liquid — stay in sync as you work, and how a live preview shows you the exact output before you save anything.

The three panes

Every mapping project opens to the same three-pane layout: Source on the left (the fields available in your input message), Target in the middle (the fields your output shape needs), and Output on the right (a live, continuously-updating preview of what your mapping actually produces). Wires drawn between Source and Target are what define the mapping — there's no separate "compile" step to remember.

The mapping editor with an HL7 v2 source tree on the left, FHIR target fields in the middle connected by wires, and a live JSON output preview on the right
The three panes, outlined: Source on the left, Target in the middle, Output on the right. Every teal wire is one field connection between Source and Target; Output updates live as you draw or remove them.

Wiring a field

To connect a field, drag from a source field's connection point to a target field's connection point (or click one, then the other) — the wire draws in real time as you move, and drops onto whichever field you release over:

Animated demonstration of dragging from a source field's connection point to a target field's, drawing a wire in real time
Watch a real connection being made — drag from a source field's port to a target field's, or click one then the other.

Here's that same gesture applied to this walkthrough's own fields — the HL7 PID.5.1 and PID.5.2 positions, the patient's family and given name, wired to the FHIR name[0].family and name[0].given[0] fields:

HL7 Family Name and Given Name source fields wired to FHIR Family and Given target fields 1 2 3
1 — the source field, showing its HL7 position and the live value from the pasted sample. 2 / 3 — the matching target fields; each one shows a small "← Family Name" / "← Given Name" tag once wired, so you can always see what's feeding it without following the wire by eye.

A target field can also carry a filter — a small transform applied to the value in flight. This template uppercases the family name on the way through:

Live output panel showing the rendered FHIR Patient JSON, with family name uppercased 4
4 — the source value was Doe; the live output shows DOE, because a filter is attached to this field mapping. The Output panel always reflects filters, conditions, and repeating-group rules exactly as they'll render in production — nothing here is a simplified preview.

Faster with Auto-Map

Rather than wiring every field by hand, Auto-Map suggests connections based on field names and data types — accept the ones you want, adjust or dismiss the rest, and refine by hand in any of the three views. It's usually the fastest way to get a mapping most of the way there, especially when your source and target field names are already similar.

This same wiring mechanism — drag a source field to a target field, optionally attach a filter or a condition — is identical no matter which formats you're converting between. See the any-to-any mapping reference for worked examples across every supported source and target combination, including X12 and JSON.