Mirth

  • Continuity of Care Document Integration using Mirth Connect

    Mirth Connect is the Swiss Army knife of open source integration engines with specific Healthcare support for HL7 message integration. A Continuity of Care (CCD) Document is an XML file containing a patient summary clinical document whereas the HL7 Clinical Document Architecture (CDA) is an XML-based markup standard intended to specify the encoding, structure, and semantics of clinical documents […]

  • Custom Web Service Connections from Mirth Connect

    Mirth Connect is the Swiss Army knife of open source integration engines with specific Healthcare support for HL7 message integration. Mirth has out of the box connectors for FTP, HTTP (GET/POST), JMS, SMTP, LLP and Web Services but if the out of the box capabilities is not sufficient, we can use the “JavaScript Writer” destination to create our own custom connector.

    In the open source version of Mirth Connect, there is no support for secure HTTPS. This is available from Mirth in their commercial offering but in this blog entry, I’m going to take you through using the JavaScript writer destination to create our own simple HTTPS sender.

  • Parsing Continuity of Care (CCD) using Mirth and MDHT

    Mirth Connect is the Swiss Army knife of open source integration engines with specific Healthcare support for HL7 message integration. A Continuity of Care (CCD) Document is an XML file containing a patient summary clinical document. Mirth has support for CCD and CDA documents in their commercial offering but you can also use the open source Model Driven Health Tools library from the Open Health Tools project for free if you have some time and patience.

    In this blog entry, I’m going to take you through the process to integrate the MDHT libraries into an existing Mirth Connect installation and then create a very simple channel to parse a CCD document and extract information from it. Specifically, we will:

    • Download and install the MDHT Run-time JARS
    • Configure and add code to a channel in Mirth to load the content of a CCD document
    • Extract fields from the CCD document and populate the channel variables map
  • Mirth Connect with Microsoft Azure Queue Storage

    Mirth Connect is the Swiss Army knife of open source integration engines with specific Healthcare support for HL7 message integration (though it works just as well when dealing with many types of data formats outside of HL7). Windows Azure enables you to build, deploy, scale and manage applications across a global network of Microsoft-managed data centers.

    Mirth Connect uses the concept of channels and queues to ingest, filter, transform and send messages from one system to another. It has built in support for many protocols such as file systems, FTP sites, databases and web services. In this blog post I’m going to demonstrate how we can extend the built-in capabilities to use Mirth Connect to send messages directly to a Windows Azure Queue:

    Windows Azure Queue storage is a service for storing large numbers of messages that can be accessed from anywhere in the world via authenticated calls using HTTP or HTTPS. A single queue message can be up to 64KB in size, a queue can contain millions of messages, up to the 100TB total capacity limit of a storage account.

    By pairing an on-premise or cloud hosted the instance of Mirth Connect with Azure queues we are able to scale by having one or more instances (or channels within an instance) of Mirth Connect pushing messages to the queue while having an independent number of queue consumers receiving messages and performing business activities on them. We are also able to eliminate a single point of constraint and failure providing greater resiliency.