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

My main use case for Mirth Connect Health Check is interface automation.

I use Mirth Connect Health Check for interface automation by filling out forms and registration information directly using a Mirth Connect Health Check channel rather than putting information in the front end.

I chose to automate those particular tasks with Mirth Connect Health Check because it is very fast and very structured and easy to implement.

Mirth Connect Health Check has positively impacted my organization by enabling us to use any kind of data transfer or interface connection, so it has made huge progress in our efficiency and data movement strategy.

I have noticed time saved and fewer errors since implementing Mirth Connect Health Check. Instead of manually moving data from one system to another, we can directly use API and create a Mirth Connect Health Check channel to move data directly into the system.

The best features Mirth Connect Health Check offers include the ability to use the database, ability to use JavaScript, as well as reliability and powerful file format tools including XML, HL7, FHIR, and Excel.

Out of those features, the database makes the biggest difference in my daily work because we need to move data from one location to another, and much of the time the data is stored in a database.

Mirth Connect Health Check can be improved by implementing more features and making it easier and more intuitive for new users.

More training videos would be beneficial as an improvement in documentation or training resources.

I rate it an eight because if it were easier to learn for a beginner, that would make it a ten, and also if it were AI-powered so that you don't have to do everything in JavaScript from scratch.

I have been using Mirth Connect Health Check for a year.

Mirth Connect Health Check is stable.

Mirth Connect Health Check's scalability is good because you can scale it.

I have not had a bad customer support experience.

I did not use anything before choosing Mirth Connect Health Check.

I have seen a return on investment. We have saved at least 70 hours per week on manual tasks that would need to be done by a person since we have a Mirth Connect Health Check channel that moves that data.

My experience with pricing, setup cost, and licensing was acceptable. We had some learning curve when it comes to setting up, but eventually we figured it out. While the cost can be a burden for a company starting to implement, for a large enterprise, the rates are competitive.

Before choosing Mirth Connect Health Check, I did not evaluate other options and went straight to Mirth Connect Health Check.

On a scale of one to ten, I rate Mirth Connect Health Check an eight.

Regarding Mirth Connect Health Check's AI capabilities, I think the governance and security need to be really strict, especially since data can be exposed if AI is not secure.

Regarding Mirth Connect Health Check's AI capabilities, I find it fairly reliable.

The advice I would give to others looking into using Mirth Connect Health Check is to use YouTube resources to learn, read documentation, and try to learn JavaScript and HL7 and FHIR basics before jumping into Mirth Connect Health Check.

My main use case for Mirth Connect Health Check was working on interfaces from equipment in my previous role, where Mirth Connect Health Check was used for handling different documents between hospital pharmacies and our products.

I was working with XML files and Mirth Connect Health Check was translating these files from our pharmaceutical robots to the informatic systems of the concerned customers, the hospitals. I did not experience any particular issues with Mirth Connect Health Check, and we did not have to escalate tickets.

Mirth Connect Health Check positively impacted my organization because it made our job possible; this was the way we used to interact with the software of the hospitals.

Mirth Connect Health Check helped us collaborate with the hospitals because this was the software we used to integrate our products in their systems.

The best features that Mirth Connect Health Check offers in my experience is that it was very clear to use.

What specifically made it easy or clear for me was the documentation we used, which I think was in-house. The interface and the way it handled file translations made the product straightforward to work with.

I chose eight out of ten because on our side, it was sometimes difficult to understand what was expected from us to change in the files and in the format, but this is not necessarily related to Mirth Connect Health Check's performance. This is an overall score for the usability. If Mirth Connect Health Check had been a more graphical or AI-driven solution at that time, the score would likely improve to nine or ten.

I used Mirth Connect Health Check for almost two years.

Mirth Connect Health Check is stable.

Mirth Connect Health Check worked at that time, but we did not have a very large organization, so I am not sure how well it performs concerning scalability.

Mirth Connect Health Check was in place when I joined the organization and also when I left, so I did not previously use a different solution.

I would rate Mirth Connect Health Check an eight on a scale of one to ten.

Governance and security is a very important topic, being that Mirth Connect Health Check deals with health information data.

I would advise others looking into using Mirth Connect Health Check to ensure security controls are in place so that ingested files from our company are not interfered with by malicious actors.

My main use case for Mirth Connect Health Check is to use it as a connector between my software and the interface of the hospital, specifically the software that manages all the storage of drugs in the pharmacy. I use it so my software can be informed of the database of drugs and the connection of all the dispensation lines for all patients, so my robots can dispense these doses.

Mirth Connect Health Check helps me manage that connection by allowing me to translate HL7 messages into JSON messages. I use Mirth Connect Health Check to translate HL7 messages into JSON messages, and I have to do a lot of manual setup, particularly with dates that require quite a few lines of code in JavaScript because some of the translation needs to be done with JavaScript as they are not already automated. However, for many other things, Mirth Connect Health Check already works well. I just take the field from the HL7 and bring it to the JSON field, and it already does the connection.

Mirth Connect Health Check has impacted my organization positively, though not in any particular way. It is a tool, and as a tool, you need to use it at your best to receive the best result.

The best features Mirth Connect Health Check offers are its versatility. I can use it with many different kinds of messages. I do not have to change all my software anytime I try to interface with a new hospital with a different management system. I just have to change the Mirth connector, and with usually just a few small changes, I can make it work.

Regarding versatility and ease of interfacing with different hospital systems, every time I have to change, I change it as quickly as possible. The initial setup involves a lot of manual changes and a lot of JavaScript script to write, but in the following hospitals, usually there are just some specific fields to change, assuming you do not agree on something totally different, but that is between you and the hospital and how it works.

Mirth Connect Health Check can be improved by maybe rearranging for better string manipulation, because sometimes when you have to move data from an inbound message to an outbound message, you have to do some string manipulation and that could be made easier. With JavaScript you can do everything, but it would be nice to have it in an easier way.

I have been using Mirth Connect Health Check for only one year.

The accuracy and reliability of Mirth Connect Health Check's output has been consistent for me after a little tuning. I noticed at the beginning there were a few more errors, but after a while, I understood how to fix them and it is pretty reliable.

Mirth Connect Health Check is stable in my experience. I have not used it extensively enough yet, but it is stable.

Mirth Connect Health Check's scalability is good. I noticed that with a very high number of messages, it still managed to do everything fine.

I did not use a different solution before Mirth Connect Health Check. I used Mirth Connect Health Check after a little bit of research.

Installing it on Linux is a bit harder than installing it on a Windows machine. An easier install for Linux can be made.

The return on investment for what I do, which is probably basic, is usable, so I can use the free version and be satisfied with it.

My experience with pricing, setup cost, and licensing is that we are still using the free version, so pricing is very good because it is free. Otherwise, for us that we are a small company, we would not be able to afford it.

Before choosing Mirth Connect Health Check, I evaluated other options, and the alternative was to create a Python or a C++ script myself.

On a scale of 1 to 10, I would rate Mirth Connect Health Check an eight.

I chose eight because it is good and does its job. There is not anything specific so far that made me give it a nine or 10, but it is good at what it does.

Mirth Connect Health Check is deployed in my organization on-premises. We prefer to have it locally, so all the connections are more secure.

My advice for others looking into using Mirth Connect Health Check is that I have no specific recommendations.

I used Mirth Connect Health Check to ensure that our Mirth Connect is up and running and we do not have any downtime.

We have hosted Mirth Connect on a server, and to ensure Mirth is running, we set up some background services that keep checking for the service. Instead of that, we have an endpoint for this health check, and I use that endpoint by providing the IP address of the server to get the status, such as the version. I was using version 4.4.2. When I hit that endpoint, I get that version, and if I am getting that version, that means our service is up and running successfully, and I do not have to worry about Mirth being down.

It is just for monitoring and to ensure there is no downtime. Mirth Connect Health Check is deployed on a public cloud or private cloud that can be accessed only within the organization. I use Azure as our cloud provider.

It has helped me save some time, and using this, I made sure that I am very accurate about our downtime, and I do not have to rely on any third-party service or microservices to ensure that Mirth is up and running.

If I want to go manually and log into the server to check that, it takes almost 30 minutes, but with Mirth Connect Health Check, it is just one click away, and I get the response status.

Mirth Connect Health Check offers features for managing performance and checking for downtime, and I do not have to manage any credentials for this. I do not have to pass any credentials for this; it just gives me a status of Mirth Connect.

I do not have to hardcode any administrator password for that engine, which keeps a security perspective very good because I am not storing any username and password.

Feature-wise, using this provides downtime prevention, and I can also use it after updating Mirth Connect to validate that the update went through successfully on the new version. I believe this is the main thing.

There are some things I have to look for, basically just having the ability to check if Mirth is up and running. I cannot check the data inside Mirth Connect, such as the channels, or whether they have any errors or anything. It is limited to the status of Mirth Connect, so I feel I need to start adding the channel information and the channel statuses also.

If a database crashes but Mirth web service is still running and working, I will get a 200 response or the version. That means our database is not working, but Mirth Connect is up. So that is incorrect information. I do not face this issue too frequently, but still, it should be improved.

I have been using Mirth Connect Health Check for the past four years, and I have been using the health check for almost two years.

It is perfectly stable; it is 100% stable right now. It is not complicated—just hit an endpoint and I get the response.

I believe it can scale and improve many things. It is just one endpoint for Mirth Connect Health Check, and I do not have to keep track or have problems handling another endpoint. It is pretty good; I have not faced any issues, and I believe it can scale very much.

I previously used some microservices that required me to manage that service, consuming extra memory and causing issues, and I had to maintain that service again. With Mirth Connect Health Check, I do not have to maintain anything; it is just an endpoint, and I hit it to get the response based on which I do checks.

Definitely, if I am spending 30 minutes checking Mirth Connect health status, I am saving 30 minutes for a server.

I am not sure about pricing and setup cost because that is managed by the management, who decide and give me access.

I evaluated the microservices, which was an in-house tool I developed to check Mirth health continuously.

I give Mirth Connect Health Check an 8 out of 10 because it is a must-needed tool that decreased some time monitoring Mirth Connect services.

I chose 8 out of 10 because it is just checking Mirth status and Mirth Connect health; that is it. Nothing else, such as no channel checks or error checks or database connection checks. I believe if those are included, it will definitely be a 10 out of 10.

I feel Mirth Connect Health Check is getting HIPAA compliant, which follows regulation in the US, so I believe it is secure to use, speeding up tasks and ensuring I am compliant.

The output is 100% accurate, and I do not think there is any accuracy problem. But as I said, if the channel is not working or the database connection is not working, I still get the response saying 200, which means the server is fine, and Mirth is working fine.

I would say Mirth Connect Health Check is a perfect tool or service to check on Mirth if I have 100 clients and servers running 100 Mirth Connect instances. Instead of checking manually, it saves a lot of time and is pretty quick.