Tag Archives: hl7

Mirth Connect – Tips and Tricks

mirth partner 1

Two weeks ago, I introduced the Mirth Connect interface engine and shared its impact on one of my client engagements at Galen Healthcare Solutions. Through that experience I was constantly learning new ways to make Mirth safer, faster, and easier to use. After almost six months of development work, I wanted to share some tips on how you can optimize Mirth Connect.

  • Add channel metadata to troubleshoot faster: You may already be storing useful information about incoming messages in channel variables, such as the MRN of a patient, an identifier for a hospital, or the HTTP response code of a message you are POSTing via Mirth™. By adding these channel variables to the metadata of a channel, you can view the values for these variables on the message log screen and also speed up your searches when using the Advanced search filter and specifying the metadata you have defined.

    In the message log screen for your channel you can see your new metadata, adding important information to your message log. Use the Advanced search option with metadata specified to experience faster search results.
    In the message log screen for your channel you can see your new metadata, adding important information to your message log. Use the Advanced search option with metadata specified to experience faster search results.

  • Don’t catch errors gracefully: You don’t often hear this, but in your Mirth™ JavaScript code, you may not want to catch errors gracefully. If you wrap your code in try/catch blocks but do not throw the error, Mirth™ will let the message continue processing and anything could happen with a broken message downstream. Throw your errors to let the message fail.

    Wrap your JavaScript code in try/catch blocks to capture errors and make sure to throw the error so that the message gets set to ERROR and does not continue being processed.
    Wrap your JavaScript code in try/catch blocks to capture errors and make sure to throw the error so that the message gets set to ERROR and does not continue being processed.

  • View the rest of my tips and tricks on Galen Healthcare Solution’s blog

Connecting Healthcare Systems Securely and Efficiently

mirth partner 1

How would you securely and efficiently transport millions of records of patient health information between two disparate systems? How would you manage such an automated process that could transform the data to fit into each system’s database architecture, all the while being alerted to any errors as they occur in real-time?

In one of my largest client engagements as a technical consultant since joining Galen Healthcare Solutions last summer, I’ve been tasked with building a solution to these questions. The goal was to achieve interoperability between a patient portal and a popular electronic medical record system and the key was to find the right kind of interface engine. We ultimately decided to put to use Mirth Connect.

On Galen’s blog, I’ve written about my initial thoughts on Mirth Connect:

One year ago an organization approached us with the need to integrate their patient portal solution into a popular EMR. Connecting hundreds of practices and millions of patients through their portal required a special kind of interface engine. At the core, we needed something that could transport data quickly, reliably, and securely, but we also needed one at an attractive price point that offered a variety of data transformation features.

With dozens of interface engines available on the market, we ultimately chose one out of Costa Mesa, California: Mirth™ Connect. A year later, they have hundreds of thousands of secure patient-provider messages, CCDs, and lab results flowing through this interface engine on a monthly basis. You may never have heard of it before, but after our experience with Mirth™ Connect, we think you should. Read more…