Mirth Connect - Friendly Wizard-HL7 and Mirth processing tool

Example

An HL7 ADT (Admit, Discharge, Transfer) message is received from an EHR, and a Mirth Connect channel is configured to convert the ADT message into a format that the hospital’s billing system can process.

Scenario

In a real-world scenario, a hospital using multiple systems for different departments needs to ensure that patient demographic information is consistent across the EHR and billing systems. Mirth Connect handles this by receiving ADT messages from the EHR, transforming specific fields like PID (Patient Identification) or PV1 (Patient Visit Information), and routing the transformed message to the billing system.

Example

A channel is set up to filter out specific HL7 ORU messages that do not meet certain criteria, such as messages missing mandatory OBX (Observation Result) segments.

Scenario

For example, in a laboratory environment, only test results that include OBX segments are required for downstream systems. The Friendly Wizard allows users to write JavaScript filters that automatically discard messages lacking these segments, ensuring that incomplete messages do not overload or crash receiving systems.

Example

Mirth Connect integrates with a PACS (Picture Archiving and Communication System) by transforming DICOM image metadata into an HL7 message format.

Scenario

In a radiology department, imaging results are stored in a PACS system, but the hospital's EHR system uses HL7 for all other clinical data. Using Mirth Connect, the imaging data is mapped and transformed from the DICOM format into HL7 to update the patient’s medical record in the EHR. This ensures that all patient data is centrally located and accessible from any department.