HL70 inputs → 1 output

HL7 In

Receives inbound HL7 v2 messages from a hospital over a dedicated VPC connection (MLLP on port 2575).

Details

This node registers with the global MLLP server on deploy. Incoming messages are matched to this connection using a composite routing key — all three parts must match:

Incoming IP — The hospital's dedicated private network Incoming IP (from the VPN configuration).
Sending Facility (MSH.4) — Facility identifier in the message header.
Sending Application (MSH.3) — Application identifier in the message header.

A message matching only one or two parts is not delivered — it is rejected with an error ACK and the rejection is recorded in the audit log. Connections missing any routing-key part are excluded from routing entirely and shown with an incomplete routing key flag in the selector.

Outputs

payload.raw string: Raw HL7 v2 message text (MLLP framing stripped).
payload.msh object: Parsed MSH segment: sendingApplication, sendingFacility, messageType, eventType, messageControlId, dateTime.
payload.connectionId string: UUID of the integration that matched this message.
payload.sourceIp string: Source IP of the hospital's HL7 engine.
payload.receivedAt string: ISO 8601 timestamp of when the message arrived.
hl7.messageType string: Shortcut: HL7 event type (e.g. "ADT").
hl7.sendingApplication string: Shortcut: MSH.3 value.
hl7.sendingFacility string: Shortcut: MSH.4 value.
hl7.messageControlId string: Shortcut: MSH.10 — the unique message ID echoed in the ACK.
_hl7SendAck function: Internal. ACK callback for the HL7 Response node. Do not modify or use directly.

Connection Requirements

Required: The selected connection must have HL7 enabled with all three routing-key parts configured: Incoming IP, Sending Facility (MSH.4) and Sending Application (MSH.3). A connection missing any part is excluded from routing and its messages are rejected.

Required: Wire an HL7 Response node at the end of the flow to send the ACK back to the hospital. A 30-second safety timeout will auto-send AE if no response is sent.

Typical Flow

┌──────────┐   ┌────────────┐   ┌──────────────┐   ┌─────────────┐
│  HL7 In  │──▶│ HL7 Parser │──▶│  Your Logic  │──▶│ HL7 Response│
└──────────┘   └────────────┘   └──────────────┘   └─────────────┘

Message Filter

Optionally filter by HL7 message type (MSH.9.1). Comma-separate multiple types: ADT,ORU,ORM. Leave blank to receive all message types on this connection.

Best Practices

Always wire HL7 Response at the end — even if only to send AA
Use a catch node to handle flow errors and wire that to a HL7 Response with msg.ackCode = 'AE'
Use HL7 Parser immediately after this node to get structured segment data
Keep the connection's Incoming IP, Sending Facility and Sending Application in sync with the hospital's HL7 engine — all three must match for delivery

┌──────────┐ ┌────────────┐ ┌──────────────┐ ┌─────────────┐ │ HL7 In │──▶│ HL7 Parser │──▶│ Your Logic │──▶│ HL7 Response│ └──────────┘ └────────────┘ └──────────────┘ └─────────────┘