Listener Settings

Item	Name	Description
A	Local Address	If All interfaces is selected, the connector will listen on all interfaces, using address 0.0.0.0. If Specific interface is selected, the connector will listen on the specific network interface address given in the accompanying field.
B	Local Port	The TCP port on which to listen for connections.

Mirth® Connect by NextGen Healthcare User Guide

Source Connector Properties

This section refers to the actual connector-specific settings. The sections are labeled according to the connector types, for example, "HTTP Listener", "JavaScript Reader". For additional information on connectors in general, refer About Channels and Connectors. Here is a list of source connectors supported by Mirth® Connect Source Connectors Channel Reader DICOM Listener Database Reader File Reader HTTP Listener JMS Listener JavaScript Reader TCP Listener Web Service Listener Additional source connectors are made available as extensions: Email Reader Serial Connector FHIR Connector Interoperability Connector Suite Parent topic: Source Tab

Mirth® Connect by NextGen Healthcare User Guide

Connector-Specific Properties

Every connector has its own custom set of properties. The properties you configure for a TCP Listener will be different from a Database Writer and so on. Here is a list of source and destination connectors supported by Mirth® Connect: Source Connectors Channel Reader DICOM Listener Database Reader File Reader HTTP Listener JMS Listener JavaScript Reader TCP Listener Web Service Listener Destination Connectors Channel Writer DICOM Sender Database Writer Document Writer File Writer HTTP Sender JMS Sender JavaScript Writer SMTP Sender TCP Sender Web Service Sender Additional connectors are made available as extensions: Email Reader Serial Connector NextGen Results CDR Connector FHIR Connector Interoperability Connector Suite Parent topic: Connector Components

Mirth® Connect by NextGen Healthcare User Guide

Source Connectors

This section refers to the actual connector-specific settings for the source connector. The section is labeled according to the connector type, e.g. "HTTP Listener", "JavaScript Reader". For additional information on connectors in general, go here: About Channels and Connectors Here is a list of source connectors supported by Mirth® Connect by NextGen Healthcare: Channel Reader DICOM Listener Database Reader File Reader HTTP Listener JMS Listener JavaScript Reader TCP Listener Web Service Listener Additional source connectors are available as extensions: Email Reader Serial Connector FHIR Connector Interoperability Connector Suite Channel Reader DICOM Listener Database Reader File Reader HTTP Listener JMS Listener JavaScript Reader TCP Listener Web Service Listener

Mirth® Connect by NextGen Healthcare User Guide

Frequently Asked Questions

This section addresses the most common questions users have about Mirth® Connect by NextGen Healthcare. What is Mirth® Connect? Mirth® Connect is a versatile, standards-based healthcare integration engine that speeds bi-directional message routing, filtering, and transformation between disparate health-info systems over various messaging protocols (e.g., HL7, X12, EDI, DICOM, XML). Is Mirth® Connect the same as "Mirth"? Yes. Mirth 1.0 was released in 2006 by WebReach, Inc. Based on the success of the Mirth application, WebReach, Inc. was renamed "Mirth Corporation" in 2009. To avoid confusion between the new company name and its products, the Mirth application was renamed Mirth® Connect. As of early 2016, Mirth Corporation, as a business entity, no longer exists, having been absorbed into the Quality Systems, Inc. family of products in Sept. 2013. QSI has since become NextGen Healthcare, and Mirth® Connect lives on with other former Mirth Corporation products as part of the "Mirth Solu

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

Choose a Source Connector

This is done simply by selecting a connector type from the drop-down menu at the very top of the tab: After selecting a source connector type, the settings shown here are broken up into different categories depending on the type of connector chosen: Listener Settings Polling Settings Source Settings HTTP Authentication Settings Source Connector Properties Parent topic: Source Tab

Listener Settings

Recommendations

Source Connector Properties

Connector-Specific Properties

Source Connectors

Frequently Asked Questions

TCP Sender

Choose a Source Connector

Listener Settings

Source Connector Properties

Connector-Specific Properties

Source Connectors

Frequently Asked Questions

TCP Sender

Choose a Source Connector