Mirth Connect

Overview

Mirth Connect is an integration engine for moving clinical data between separate health information systems. It is best suited to healthcare organizations with integration staff who can build and maintain interfaces; its breadth is useful, but customers operate the engine and support their own interfaces.

It brings together a wide range of healthcare formats, transports, and deployment options. The main qualification is commercial and operational: licenses for version 4.6 and later are proprietary and paid, and the customer remains responsible for running the software.

Key features

Mirth Connect routes messages in both directions, with filtering, transformation, real-time synchronization, and workflow orchestration. Supported formats include HL7 v2.x and v3.x, CSV and other delimited text, DICOM, EDI/X12, XML, JSON, NCPDP, and raw data. Transfer methods include MLLP, TCP/IP, HTTP, files, databases, SFTP, FTP, SMB, WebDAV, email, DICOM, JMS, SOAP, and custom Java or JavaScript. That range can help integration teams connect systems that differ in both data format and transport, though the organization must design and support the resulting interfaces.

Transformation tools cover protocol conversion, advanced mapping, and channel mapping, with channels users can create, test, and deploy. The product page also describes an enterprise API with read/write access across more than 800 EHR and practice management integration routes, a FHIR-enabled Patient Access API, and SMART on FHIR support. NextGen says the engine is used in over 40 countries and handles the exchange, import, and export of 340 million clinical documents annually; these figures point to substantial use, not a substitute for assessing a particular deployment's requirements.

Organizations can self-host or use NextGen's co-located US data centers or AWS cloud environment. That choice gives teams options for where the engine runs, but does not transfer responsibility for maintaining and operating a licensed engine from the customer. Extensions are available only with a Mirth Connect license, not as individual purchases.

Pricing

Mirth Connect's listed plans use flat-fee annual licensing per server, with custom pricing for the paid tiers. The complimentary Mirth Connect for Research plan costs nothing and is limited to active research studies affiliated with a non-profit institution; eligibility is verified. It is a narrow option for qualifying studies rather than a general free tier.

Enterprise includes unlimited support cases per year, 50 channel analytics, SSL Manager, and Mirth Command Center access. Gold adds 24x7 phone support and 100 channel analytics, while Platinum includes 24x7 phone support and 200 channel analytics. Both Gold and Platinum include extensions; the Enterprise plan's listed inclusions do not. All three paid plans have unlimited support cases, but the higher tiers add phone coverage and progressively more channel analytics. Contact sales for Gold and Platinum pricing; Enterprise also has custom pricing. Starting with version 4.6, a purchased license is required to upgrade, and the license is proprietary.

Platforms

The installer supports Windows, Linux, and macOS. The product's platform coverage also includes API, web, and self-hosted environments. Self-hosting suits organizations that want to run the engine themselves; NextGen-hosted options are co-located US data centers and AWS.

Who it's for

Mirth Connect fits healthcare organizations that need to exchange data across disparate systems and have the staff to build, operate, and support interfaces in-house. Its format and protocol breadth, mapping tools, and deployment choices are relevant to complex integration work. It is a weaker fit for buyers seeking a turnkey service that takes responsibility for interface operations, or for teams that cannot support a licensed engine.

Pros and cons

• Broad format and transport coverage: Support for healthcare standards, common data formats, and many transfer methods helps bridge systems with different integration requirements.
• Flexible mapping and deployment: Users can create, test, and deploy channel mappings, while organizations can self-host or use NextGen's co-located US data centers or AWS.
• Customer-owned operations: The customer maintains and operates the engine and builds and supports interfaces, making internal integration capacity a prerequisite.
• Paid proprietary upgrades: Version 4.6 and later require a purchased license, and extensions are only available with a license, limiting the appeal of a free starting point for general use.

Alternatives

For billing-focused workflows rather than an integration engine, medical billing software and revenue cycle management software are relevant categories. Organizations comparing hosted integration services can also browse integration platform as a service software.

• Office Ally Practice Mate is a freemium, web- and Windows-based option with a free Practice Mate plan covering appointment scheduling, patient billing, configurable superbills, a patient ledger, and reports; transactional fees may apply.
• PracticeSuite Medical Billing is a paid alternative with custom pricing, modular features, and unlimited administrative users, suited to buyers seeking medical billing software rather than a general integration engine.
• Nextech is a paid option for buyers considering software available on iOS, macOS, web, and Windows.
• Oracle Health Revenue Cycle is a paid alternative with custom pricing for organizations looking specifically at revenue cycle products.
• Tebra has a Practice Essentials low-volume plan starting at $199 a month per provider for 100 or fewer claims per month, for readers comparing a priced billing option.
• EZClaim offers a First (Single) User annual plan priced at $189 a month; additional users and clearinghouse fees may add cost, making it a billing option to compare when that workflow is the priority.
• TotalMD is a paid alternative with a free trial for buyers considering medical billing software.
• AKASA Platform is a paid API- and web-based alternative.

Verdict

Choose Mirth Connect if your healthcare organization needs broad message routing and transformation and has the staff to build, operate, and support interfaces. Its strongest case is the combination of format and protocol coverage, mapping capabilities, and deployment options. Look elsewhere if you need a provider to take on interface operations, or if proprietary licensing and paid upgrades do not suit your requirements.