Roadmap

Mirth Connect 1.9

Advanced Alerting – The ability to do state and metrics based monitoring globally or by channel. For more information, see Improving Mirth Connect Alerts: Request for Feedback.
Modularized components – A large architectural change to Mirth Connect. Mirth Connect currently uses extensions and plugins, but in 2.0 we will be introducing the concept of modules. Each module will be an OSGi-based implementation of a core component in Mirth Connect. This will allow core Mirth Connect components to be easily replaced, such as Alerts, users, and even Mule.
Renaming Channel to Interface – All Channels in Mirth Connect will now be known as Interfaces.

Mirth Connect 2.0

User Roles – The ability to assign specific privileges to a user or group of users in Mirth Connect. Some possible roles might be read-only (only seeing messages and deployed channels), operator (read-only with the ability to start/stop a channel and reprocess a message), developer (can create and modify channels, but not users or settings), and administrator (no restrictions).
Auditing – In addition to user roles, a more advanced auditing system will be included with audit trails of individual users.
Channel hot-deploy – Adds the ability to make changes to individual channels/interfaces and re-deploy them without affecting the entire configuration and deploying all channels. This is especially useful for modifying channels after they are already in production.
Statistics and message history reporting – Report generation for statistics, including time based metrics about message history for the Mirth Connect Server, individual channels, and individual connectors.
Document reporting – Report generation for specifications about a specific interface in Mirth Connect. This will help in generating document specifications for interfaces created in Mirth Connect.
Profile based message validation – Allow automatic validation of messages based on a specific profile or message specification such as HL7v2.5.