Mapper

Runs a saved Mapping Project (authored in the visual Mapping editor). Accepts either a raw message or data an upstream node has already parsed. On Auto it selects the project's matching mapping by trigger event + version; you can instead pin one specific mapping.

Inputs

payload string

The raw message to map — HL7 v2, X12, JSON or C-CDA XML. The format is detected automatically. (Configurable input field.)

payload object

Alternatives, all handled automatically: an HL7 In envelope (the message is read from .raw); already-parsed data from the HL7 Parser node (hl7v2Data) — nothing is re-parsed; a C-CDA document from the CCDA Parse node (Structured JSON output), mapped with a C-CDA mapping; or any other object, treated as a JSON source.

mappingProjectId string

Override the configured Mapping Project for this message.

mappingTemplateId string

Override the pinned mapping for this message.

Outputs

payload object

The rendered/transformed output of the selected mapping.

mapping object

projectId, templateId (when pinned), sourceType, inputMode (raw or parsed), processingTimeMs, timestamp.

Details

Mapping = Auto routes by the message's trigger event. Pinning a specific mapping skips the routing — the most deterministic option, and it works whether the input is raw or already parsed. If the selected project or mapping has been deleted, or no mapping matches the message, the node emits a clear error to any connected Catch node. Parser/render errors are sanitized — they never echo message content.

Raw or parsed?

Both work. Feeding the message raw is the simplest wiring and is the only option that supports batch payloads (many messages in one payload). Putting the HL7 Parser node in front instead gives you structural validation the direct path does not perform, and lets other nodes in the flow work with the parsed structure — recommended for HL7. A batch that arrives already parsed is rejected with a clear error rather than silently rendered as one merged message.