OSS Mirth® Connect Package by Innovar Enterprise Ed. (Not NextGen)

My main use case for Mirth Connect Health Check is to gather data for my healthcare client. We used to gather data from the clinical instruments in Mirth Connect and then translate that data through Mirth Connect to our company application that was for QC data. Then we used to translate that data in the reporting format for our healthcare client.

A quick specific example of how I used Mirth Connect Health Check in that process is by handling diagnostic data. The type of diagnostic data I collected includes all the blood reporting data for lab results. We used to get the data in our Mirth Connect application through something called grabber in our application. Grabber was a programming language that used to connect to the instrument using Mirth Connect. There used to be a configuration in Mirth Connect with a server ID, server IP address, and port number. That configuration used to communicate with the application, and then we used to capture the data from the instrument using Mirth Connect Health Check. Mirth Connect Health Check was a receiver. From there we used to collect data in our application using that terminal server that was a physical device with its own IP address and port number.

One main challenge I faced was because I was using a 32-bit application, and the amount of data that we were collecting was significant since it was our country's biggest laboratory, processing thousands of samples every day. The limitation of Mirth Connect Health Check was handling a huge amount of data, and since the application memory was very low, it sometimes hung. However, we used to process data part by part. There was also a higher memory version of Mirth Connect Health Check available. When we migrated to that version, our experience became much easier. Mirth Connect Health Check is a very useful tool to use.

The best features Mirth Connect Health Check offers include easy connectivity to protocols, and through those channels, I can always grab the data.

Protocol admin feature helps in my daily work by providing one-to-one channel communication with the instrument because I used to connect hundreds of clinical instruments with Mirth Connect Health Check, each having their own IP address. There is never a data collision, and that is one of the cool features we had, allowing for one-on-one communication. That was the biggest feature.

Mirth Connect Health Check has positively impacted my organization because all the data comes into a single application, and we do not need separate applications to grab the data.

Having all the data in a single application helped my team by saving time and improving accuracy. We did not have to browse through different applications or pay vendors for their applications, making it a go-to tool for all the data with a very user-friendly UI. Everything worked perfectly, saved our time, and the data improved and became more accurate without collision.

An improvement point I see for Mirth Connect Health Check is a heavier version in terms of memory.

I chose eight out of ten because it is not a web application.

I have used Mirth Connect Health Check for around three years or three and a half years.

Mirth Connect Health Check is 100% stable.

Mirth Connect Health Check's scalability is there because it can expand and be installed on different servers as well, making it more scalable.

Customer support was not that great at that time, but I would say it was not too bad either.

Before Mirth Connect Health Check, I used to collect data in our network in a folder. When I heard about Mirth Connect Health Check, it was an application with more cool features because I could create all the instruments in one single stop without having to use different folders.

In terms of money, I estimate my organization saves probably around $10,000 Canadian annually.

I did not evaluate other options because Mirth Connect Health Check was a one-stop shop for us.

I would advise others looking into using Mirth Connect Health Check to look for its capability in handling data. If that suffices your requirements, definitely go ahead, and also check for a web-based version if available.

Regarding Mirth Connect Health Check's AI capabilities, it provides the fundamental features that you would expect, such as user roles, permissions, and admin controls. These controls should be tied to least privilege or probably named accounts. For security purposes, deployment should be secure, with regular patching and database security.

I have not used Mirth Connect Health Check with AI, so I would not be in a perfect situation to answer that about its accuracy and reliability of output.

I believe I have covered the main points. I gave this product a rating of eight out of ten.