Troubleshooting

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

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

Unable to Launch Mirth® Connect Administrator

The login window indicates if there is any issue: Login window with error displayed. If you do not have connectivity from your local machine to the Mirth® Connect server over the HTTPS port (default 8443), you will see the following: Warning: There was an error connecting to the server at specified address. Please verify that the server is up and running. Make sure the URL you are using is correct, and verify whether you have network connectivity to the server. Verify that the Mirth® Connect server is actually running. If you installed as a service, you can view the current status from the Server Manager. Parent topic: Troubleshooting

Mirth® Connect by NextGen Healthcare User Guide

Out of Memory Errors

By default, the max Java heap size for the Mirth® Connect server is set to 256 MB. For large production instances you typically want to increase this value. You can do this from the Server Manager: Or, you can edit the appropriate *.vmoptions file in your installation directory. Note: When changing the max Java heap size, you must restart your Mirth® Connect server / service for it to take effect. Out of memory errors can also happen on the client-side, usually when attempting to view very large messages through the message browser: Animage of an out of memory error If this is the case, first you may want to consider using attachment handlers on your channel. To change the max heap size for the client-side Administrator, open the 8080 launch page in a browser: Image of the launch page Select the cog icon next to the Launch button, and change the max heap size. Then select the launch button. The JNLP file you download will have the "max-heap-size" attribute set to the value yo

Mirth® Connect by NextGen Healthcare User Guide

Opening the Java Client Console

If an error occurs on the Mirth® Connect server, you will typically see one or more entries appear in the Logs. If an error occurs in the Mirth Connect Administrator, it is possible that it is isolated to the client-side only, and so nothing will appear in the server-side logs. In cases like this, it is useful to enable the Java Client Console to see any exceptions that occur on your client-side Java virtual machine (JVM). To enable the console, first open the Java Control Panel: In your System Preferences (on OSX) or the Control Panel (on Windows), open the Java section. A new dialog will appear: Select on the Advanced tab. Select Show console. Select Apply, then select OK. Now when you launch the Administrator, you will see a second window also pop-up: Any exceptions that are logged to stdout / stderr on the client side will appear in that console. Parent topic: Troubleshooting

Troubleshooting

Recommendations

Frequently Asked Questions

Source Connector Properties

Connector-Specific Properties

Unable to Launch Mirth® Connect Administrator

Out of Memory Errors

Opening the Java Client Console

Frequently Asked Questions

Source Connector Properties

Connector-Specific Properties

Unable to Launch Mirth® Connect Administrator

Out of Memory Errors

Opening the Java Client Console