What is your primary use case for Mirth Connect Health Check?

My main use case for Mirth Connect Health Check is for healthcare integrations, particularly the HL7 FHIR interface. A specific example of how I use Mirth Connect Health Check for those integrations involves CCDA to FHIR conversion. I receive CCDA files from the source, read the XML CCDAs, and transform that data as a FHIR bundle. Based on the mapping standards, I map all CCDA fields to FHIR properties according to the resource. Once the parsing is completed, I generate the FHIR bundle for each CCDA. When mapping those sensitive fields to FHIR properties, I encounter challenges, particularly for a couple of properties that are sometimes optional. These properties will be present on CCDA, but sometimes they won't be. I need to handle this based on conditions, such as whether the value is present or not. If I do not add that condition, it will not tightly populate the data, leading to an error on the FHIR store. I must ensure the value is present in the input, and if it is present, then I need to populate it; otherwise, I should not populate any empty data. Apart from my main use case, I have used Mirth Connect Health Check in a different situation where I need to sync the source system's data to the destination system. In the source system, there is a dental PM system where the daily appointments are stored in their database. I need to read that, and the appointment data needs to be updated in another system's database. For this particular use case, I used Mirth Connect Health Check to implement.

My main use case for Mirth Connect Health Check is to parse incoming HL7 messages to deal with my internal health systems and convert JSONs to HL7 messages for external health EHR or EMRs, which was my major use case. I created a channel which opens a port where we receive the HL7 message, parse it inside the channel, and use it to transmit through to my systems and vice versa. Another use case was to create a heartbeat monitor which lets me know the health of my overall systems. It worked in parallel and created a well-defined system for me.

My main use case for Mirth Connect Health Check is primarily for data transmission from a different source to a different destination. As a source application, if I am using HL7 or XML or JSON, the outbound requires a different data format such as a FHIR resource. A quick specific example of how I use Mirth Connect Health Check for data transmission is that it is mostly used in our organization for different health clinical applications. Those clinical scenarios are pushed into the respective repository system or clinical devices. I mainly use Mirth Connect Health Check as an interface engine. In my case, I am transforming those HL7 formats.

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.