Connectors

Protocols & Custom Connectors

MLLP (HL7)

Healthcare messaging: send HL7 v2 messages over MLLP
Signs in with
Connection details
Runs on
Cloud or On-Prem Worker
Operations
3
Ready-made triggers
0

Connect MLLP (HL7)

  1. In Neblex open Connect › Connections and click New Connection.
  2. Search for MLLP (HL7) and give the connection a clear name.
  3. Fill in the fields. Secret values are encrypted and never shown again.
  4. Click Test, then Create Connection.
If the system is only reachable inside your network, choose an On-Prem Worker under Test from and run the flow on that Worker. See On-Prem Workers.
FieldWhat to enter
Connection setupRequired
HostRequired
PortOptionalExample: 2575
Use TLSOptionalTurning this off sends traffic and credentials without transport encryption. Use plaintext only for a customer-controlled endpoint that explicitly requires it.
Connection stringRequiredSecretPaste an mllp:// or mllps:// connection string.

Use it in a flow

  1. Open a flow, open the node library and search for MLLP (HL7).
  2. Drag it onto the canvas and choose an Operation and your connection.
  3. Map the operation's fields from earlier steps, or click Map with Matt.
  4. Use Test this step to see what it returns, then save.

To start a flow from MLLP (HL7) without a ready-made trigger: a Poll for changes trigger can check one of its list operations on a schedule and pass on only what is new; if MLLP (HL7) can send webhooks, a Webhook trigger receives them at its own URL.

Operations

3 operations in 2 groups. Each one is a step you can add to a flow.

Connection1
Test the connectionpingOpen the vetted MLLP TCP/TLS endpoint and complete the TLS handshake when configured.
Message2
Send an HL7 messagesendFrame and send a UTF-8 HL7 v2 message, correlate MSA-2 to MSH-10, and fail on malformed or negative ACKs by default.
Send byte-exact HL7sendRawDecode and send an exact HL7 v2 byte sequence for legacy character encodings, with the same ACK correlation and rejection policy as Send.