Mirth Connect Connect 3.0 introduces hundreds of new features over Mirth Connect 2. It features a new internal messaging engine, designed and written from the ground up by Mirth, focusing on durability (guaranteed delivery), performance, and configurability.

System-wide Queuing & Automatic Message Recovery

Mirth Connect 3.0 introduces the concept of system wide queuing into the channel workflow you are already familiar with. As messages are processed through a channel, data is persisted in a way that allows any message to resume processing where it left off (from any state) in the case of a system failure or a channel halt.

Source Queue - ACK now, process later The new source queue allows for any channel to receive and acknowledge messages faster than it can process them, and then send the messages out at its own pace. Destination Queue - Now available for all destination connectors Destination Queues are now more configurable and are available on every connector. Queued messages are now stored in the database, which means faster performance, less storage space, and no more queue files on the file system.

Message Storage

The new message store in Mirth Connect 3.0 allows you to view more information about your messages and persist it more efficiently. Each channel creates and maintains its own message store, which improves performance, decreases maintenance, and allows for many new features!

Message Browser - A fresh new look The updated Message Browser is now much more responsive and includes many new features: Tree view that visually links your destinations to your source message

More message metadata and custom columns

Additional message data like response content and sent content

Count your search results or jump to a specific page

Search on specific message content or individual connectors Customizable Message Storage - Get the most performance out of your channel Storing all of your messages can be expensive, so use the new storage configuration options to decide exactly how much data you want (or need) to store. If you don't need to persist message content at all, use the new Metadata storage mode to only store information about the messages processed, including dates and times, statuses, and even custom fields.

Custom Metadata - Decide what information in your messages is important to you Do you often search for specific information from your messages like a Patient ID in the message browser? Now you can map fields from incoming messages into custom metadata. This data will be stored along with your message data for searching and optionally displayed as a new column in your message browser! Message Archiver - Archive your messages before they are pruned Automatically archive and compress messages before they are pruned. Optionally archive as raw text or as importable messages including all metadata. Messages can also be manually archived at any time using the updated Message Exporter.

Message Processing

Destination Chaining - Synchronization is no longer all-or-nothing Individual destinations or chains of destinations can now be configured to process simultaneously. The Post-processor will always execute after all destinations have completed, and the source connector can respond immediately when a message is received, or at the end after the Post-processor has executed. This new feature allows multi-threaded destinations to be linked together while maintaining message order through the overall channel. Response Transformer - Modify or act on a response A Response Transformer can now be configured on each destination. It operates just like the Transformer you are used to, but the message content is the response that is returned from the destination. This allows you to modify the response however you see fit in the friendly Transformer interface. You can even modify the status of the message based on the response and re-queue or error the message.

Channel Dashboard