Basic TCP Transmission Mode

Item	Name	Default Value	Description
A	Start of Message Bytes		The bytes before the beginning of the actual message. Only valid hexadecimal characters (0-9, A-F) are allowed.
B	End of Message Bytes		The bytes after the end of the actual message. Only valid hexadecimal characters (0-9, A-F) are allowed. If this is not specified, the only way a connector knows whether a message has been received is if the socket timeout is reached or if the remote side closes the socket.

Mirth® Connect by NextGen Healthcare User Guide

TCP Transmission Modes

The transmission mode determines how to receive message data from the incoming byte stream, and how to send responses out. The following transmission modes are supported on the TCP Listener / TCP Sender (and Serial Listener / Sender extension): Basic TCP Transmission Mode MLLP Transmission Mode An additional transmission mode is made available via an extension: ASTM E1381 Transmission Mode Parent topic: TCP Listener

Mirth® Connect by NextGen Healthcare User Guide

MLLP Transmission Mode

This transmission mode implements the Minimal Lower Layer Protocol (MLLP) specified by HL7, and is often used when transmitting HL7 v2.x messages. There are two versions of MLLP, v1 and v2. The first version is similar to the Basic TCP Transmission Mode in that it only specifies sequences for the start/end message bytes. The second version builds on the first with "reliable delivery assurance", by having each system send a protocol-level ACK or NAK immediately after every received frame. By default only MLLPv1 is enabled, as it is the most common use-case. Item Name Default Value Description A Start of Message Bytes 0x0B <VT>) The MLLP Start Block bytes before the beginning of the actual message. Only valid hexadecimal characters (0-9, A-F) are allowed. B End of Message Bytes 0x1C0D (<FS><CR>) The MLLP End Data/Block bytes after the end of the actual message. Only valid hexadecimal characters (0-9, A-F) are allowed. C Use MLLPv2 No Select Yes to use the MLLPv2 bi-directional transport

Mirth® Connect by NextGen Healthcare User Guide

TCP Listener

This source connector listens for messages coming in over a TCP connection. It can either listen on a TCP interface/port and wait for clients to connect, or connect to an external server. There are options to decide when to keep connections open, and how many clients can connect at once. Configurable transmission modes allow you to decide how to receive inbound messages and send responses. When sending responses, you can choose to send the data back on the same connection, or on a new connection. Supported property groups: Listener Settings Source Settings Item Name Default Value Description A Transmission Mode MLLP The transmission mode determines how to receive message data from the incoming byte stream, and how to send responses out. For additional information, see TCP Transmission Modes. B Sample Frame <VT> <Message Data> <FS> <CR> An example of a valid incoming message. This is dependent on the Transmission Mode. C Mode Server Select Server to listen for connections from clients.

Mirth® Connect by NextGen Healthcare User Guide

Byte Abbreviations

The s section to the right of the transmission mode dialog allows you to easily drag-and-drop bytes into the components to the left, without having to remember the actual hexadecimal values. These also show up as labels next to the byte fields: Parent topic: Basic TCP Transmission Mode

Mirth® Connect by NextGen Healthcare User Guide

TCP Sender

This destination connector opens a new TCP client connection and sends messages over it. You can decide whether to keep a connection open, and if so for how long. Configurable transmission modes allow you to decide how to send outbound messages and receive responses. Supported property groups: Destination Settings Item Name Default Value Description A Transmission Mode MLLP The transmission mode determines how to send message data out on the socket byte stream, and how to receive responses. For additional information, see TCP Listener B Sample Frame <VT> <Message Data> <FS><CR> This is dependent on the Transmission Mode and displays an example of how an outgoing message frame is expected to look. C Mode Client Client: The TCP Sender will initiate new connections outbound to a remote server, and then send messages outbound on that connection. Server: The TCP Sender will open a server socket and listen for incoming connections. If queuing is enabled, messages will continue to queue until

Mirth® Connect by NextGen Healthcare User Guide

Advanced Queue Settings

Item Name Description A Retry Count Before Queue/Error The maximum number of times the connector attempts to send the message before queuing or erroring. B Retry Interval (ms) The amount of time (in milliseconds) that should elapse between retry attempts to send messages. This interval applies to both the queue and initial retry attempts. C Rotate Queue If enabled, when any message fails to be sent from the queue, the connector will place the message at the end of the queue and attempt to send the next message. This will prevent a single message from holding up the entire queue. If the order of messages processed is important, this should be disabled. D Regenerate Template Regenerate the template and other connector properties by replacing variables each time the connector attempts to send the message from the queue. If this is disabled, the original variable replacement is used for each attempt. E Include Filter/Transformer If enabled, the filter and transformer is re-executed before

Basic TCP Transmission Mode

Recommendations

TCP Transmission Modes

MLLP Transmission Mode

TCP Listener

Byte Abbreviations

TCP Sender

Advanced Queue Settings

TCP Transmission Modes

MLLP Transmission Mode

TCP Listener

Byte Abbreviations

TCP Sender

Advanced Queue Settings