HL7 Transform
Category: Healthcare Standards
Node id: hl7-transform
Standards: HIPAA, GDPR, SOC2
Transforms HL7v2 messages by modifying fields, segments, applying value mappings, or executing conditional rules
What it does
- Field-level transformations: set, append, prepend, replace, remove, uppercase, lowercase, trim
- Segment-level operations: add, remove, reorder
- Value mapping with dictionary-based substitution
- Conditional rule engine with field value evaluation
- Regex-based field replacement
- Configurable segment insertion position (start, end, after)
Use cases
- Modify HL7 messages to comply with downstream system requirements
- Map coded values between sending and receiving systems
- Add or remove segments for interface compatibility
- Apply conditional transformations based on message content
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
message | text | Yes | Raw HL7v2 message string |
value | text | No | Override value for field transformation |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Transform result (message, original, segment_count, transformed) |
success | boolean | No | Whether the transformation succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Transform Type | transform_type | enum | Yes | field | field, segment, mapping, rules | Type of transformation to apply |
| Segment ID | segment_id | string | No | Target segment ID (e.g., MSH, PID, PV1) | ||
| Field Number | field_number | number | No | min 1 | 1-based field number within the segment | |
| Action | action | enum | No | set, append, prepend, replace, remove, uppercase, lowercase, trim, add, reorder | Action to perform on the field or segment | |
| Value | value | string | No | Value to set, or pattern->replacement for replace action |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Mappings | mappings | json | No | Array of value mapping definitions for mapping transform type | ||
| Rules | rules | json | No | Array of conditional transformation rules | ||
| Segment Order | segment_order | json | No | Desired segment order for reorder action | ||
| Position | position | enum | No | end | start, end, after | Insert position for segment add action |
| After Segment | after_segment | string | No | Segment ID to insert after (when position is 'after') | ||
| Fields | fields | json | No | Field values for new segment (segment add action) |
Errors
| Code | Description |
|---|---|
MESSAGE_REQUIRED | HL7 message input is missing |
PARSE_FAILED | HL7 message could not be parsed |
SEGMENT_NOT_FOUND | Target segment ID not found in message |
INVALID_REGEX | Replace action contains an invalid regex pattern |
Runtime notes
- result.message contains the rebuilt HL7 string — wire it to downstream HL7 nodes
- result.original preserves the input for diff/audit; both are full HL7 message strings
- For replace action, use 'pattern->replacement' syntax in value (regex supported)
- Mapping transform applies value_map substitution only when the current field value matches a key
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..