Skip to content
Engine comparison · checked 7 November 2026

Mirth vs Rhapsody vs Iguana: a sourced comparison

A healthcare integration engine comparison of Mirth Connect, the Open Integration Engine, Rhapsody and Iguana, with InterSystems and the cloud HL7 services alongside: licensing, scripting, standards, hosting, monitoring, skills, cost of ownership and what it costs to switch.

Overhead view of a team working on laptops, phones and notes around a shared wooden table
At a glance
  • Four engines, one tableMirth, Open Integration Engine, Rhapsody, Iguana
  • Every row sourcedVendor pages and release notes, dated
  • Our bias declaredWe mostly work on Mirth and its fork
  • Decision checklistSkills, standards, support, cost, exit

Mirth, Rhapsody or Iguana: the short answer

There is no overall winner. Mirth Connect, now licensed per server by NextGen, and its free fork the Open Integration Engine suit teams with JavaScript skills who want to own and run the engine. Rhapsody suits large health systems and HIEs that want one commercial vendor, wide standards coverage and a hosted option. Iguana suits teams who like scripting in Lua with a small, direct vendor. Choose on the skills you can hire, hosting, support and five-year cost, not licence price alone.

Healthcare integration engine comparison

A comparison from people who mostly work on one of the engines. Read it with that in mind

Most of our interface work is on Mirth Connect and the Open Integration Engine, so we know those two far better than the others, and we have a commercial interest in projects that use them. To keep this page useful anyway, every factual row below comes from a vendor’s own page, release notes or a government advisory, dated, and linked. Where a vendor publishes nothing, such as a price list, the table says so instead of guessing. We are not a partner or reseller of NextGen, Rhapsody, iNTERFACEWARE, InterSystems, AWS, Microsoft or Google.

The choice matters more than it used to. NextGen’s move to a commercial-only Mirth in 2025 sent many open-source users looking, Rhapsody and iNTERFACEWARE have both changed their product line-ups, and the cloud platforms now handle parts of the job that once needed an engine. The answer for a 40-interface lab network is rarely the answer for a statewide HIE.

If you already know you are staying in the Mirth family, go straight to our Mirth Connect migration guide. If you are still choosing, the table, the checklist and the cost section below are the parts to share with your team. We can also run the selection for you as a fixed-scope piece of work, described further down, and support the result through our interface engine and Mirth Connect services.

How we compared them

We read each vendor’s current public material in the first week of November 2026: product pages, brochures, release notes, licence pages and, for Mirth, the CISA advisory. We did not run benchmarks, and we do not quote throughput figures, because vendor numbers are not comparable with each other. Rhapsody’s documentation and NextGen’s user guide sit behind logins, so for those two some detail comes from brochures and public release notes. Check anything decisive with the vendor in writing.

The four engines side by side

Mirth Connect (NextGen)Open Integration EngineRhapsodyIguana (iNTERFACEWARE)
Who makes itNextGen HealthcareCommunity maintainers and an elected steering committee; Eclipse Foundation incubating project since September 2026Rhapsody, Boston (renamed from Lyniate in 2023; Hg bought the Rhapsody business from Orion Health), which also sells the Corepoint engineiNTERFACEWARE, a small company building integration software since 1997
Current release4.7 line; CISA names 4.7.2 or later as fixed for the 2026 flaws4.7.0, 21 October 2026Not published openly; documentation needs a loginIguana 6.2 and IguanaX 10.1.119 offered side by side; 6.3 in progress
LicensingCommercial since 4.6; annual fee per server, not per interface; Enterprise, Gold and Platinum tiers; free licence for non-profit research studiesOpen source (MPL 2.0), no fee; paid support from independent vendors if you want itCommercialCommercial; terms agreed with each organisation
Published priceNoneFreeNone foundNone; terms agreed per customer
How you build interfacesChannels with filters and transformers in JavaScript (Rhino), able to call Java; reusable code templatesSame model as Mirth; imports Mirth channel exportsGraphical routes and filters; JavaScript filters and a mapper that generates JavaScript; a development kit for custom componentsScripts in Lua in the Translator editor, with message definition files for HL7
StandardsHL7 v2 and v3, X12, NCPDP, DICOM, XML, JSON, delimited; FHIR through a commercial extensionAs Mirth 4.5.2, without NextGen’s commercial FHIR extension; FHIR handled with HTTP and JSON in codeHL7 v2 and v3, FHIR, CCDA, NCPDP, X12, IHE profiles, DICOM, XML, JSON (vendor brochure)HL7 v2, X12, JSON, XML and web APIs, scripted in Lua
Where it runsYou host it: Windows, Linux, macOS, containersYou host it; container build added in 4.7.0Windows, Linux or AIX on your servers, or Rhapsody as a Service; Corepoint also as SaaS or iPaaSYour servers: Windows, Linux, macOS
MonitoringDashboard and alerts; Mirth Command Center for environment metrics in all paid tiersDashboard and alerts; community plugins such as Sentinel for queue depth, error rate and inactivity alertsRhapsody Dashboard across environments, alerts, REST API for engine healthWeb dashboard and logs per channel
High availabilityClustering through a commercial extensionNo clustering in the core; a standby server and runbookVendor states it can be configured for availabilityAsk the vendor; not described on its public pages
Admin interfaceDesktop Administrator via launcherDesktop Administrator; browser-based administrator plugin since August 2026Rhapsody IDE (a Windows application) and a web Management ConsoleBrowser
Skills market (our view)Widest: years as free software mean many integration engineers have used itSame skills as MirthSpecialists common in large health systems and HIEs, fewer and dearer elsewhereSmaller pool; Lua is quick for developers to pick up
Typical buyer (our view)Hospitals, labs and health-tech vendors wanting vendor backing for a familiar engineTeams with in-house skills who want no licence fee and open codeLarge health systems, HIEs and public bodies wanting one accountable vendorVendors and mid-sized providers who prefer code to configuration screens

Sources: NextGen licensing announcement, NextGen Mirth product page, CISA ICSMA-26-253-01, Open Integration Engine, Rhapsody company facts, Corepoint, iNTERFACEWARE downloads and licensing approach. BridgeLink, Innovar Healthcare’s Mirth fork, sits close to the OIE column with commercial support from Innovar; it released 26.9.0 on 1 October 2026.

Also on the shortlist: InterSystems and the cloud platforms

OptionWhat it isWhat it handlesWhat you still build
InterSystems HealthShare Health ConnectCommercial engine on the IRIS data platform; 2026.1 (March 2026) added a Mirth migration tool, 2026.2 followed in JulyHL7 v2, FHIR, X12 and DICOM, with graphical transformation and process editors and ObjectScript or Python for codeInterfaces, and the specialised skills to run it; strongest where InterSystems products already run
Google Cloud Healthcare APIManaged HL7v2, FHIR and DICOM storesReceives HL7 v2 through an open-source MLLP adapter on GKE, parses and stores it, and publishes notificationsAll routing and transformation logic, usually in your own pipeline
Azure Health Data ServicesManaged FHIR service; the older Azure API for FHIR was retired on 30 September 2026$convert-data turns HL7 v2, C-CDA and JSON into FHIR R4 with Liquid templatesAn MLLP listener, orchestration, error handling and replay
AWSHealthLake (managed FHIR R4) and B2B Data Interchange (X12)FHIR storage and search; X12 5010 HIPAA transactions; a CCDA-to-FHIR conversion agent announced in March 2026HL7 v2 reception and transformation, often with an engine running on AWS

Sources: InterSystems 2026.1 announcement, Google HL7v2 concepts, Microsoft $convert-data and migration FAQ, AWS HealthLake features, AWS B2B Data Interchange. The pattern across all three clouds: they store and convert well, but none replaces an engine’s routing, queuing, retries and per-partner quirks on its own.

When each one fits

Mirth Connect under a NextGen licence

Pick it when you already run Mirth, your team writes JavaScript, and you want vendor-backed patches, Command Center and the commercial extensions without rewriting anything. Think twice when you run many small servers, because the fee is per server, or when the only reason is that nobody has time to evaluate the fork.

Open Integration Engine

Pick it when you have people who can run the engine themselves, you want open code and no licence fee, and your channels do not lean on NextGen’s paid extensions. Its 4.7.0 release is described by the project as recommended for production. Think twice when you need a single vendor to answer the phone at 3 a.m. and have no support contract with anyone; community support is generous but not a service level.

Rhapsody

Pick it when you are a large organisation with many partners and standards, you want one accountable vendor, a hosted or managed option and product features such as dashboards and EMPI or terminology add-ons from the same company. Think twice when your budget is small, your team is small, or you cannot easily hire people who know it. Corepoint, from the same vendor, is pitched at teams without a large IT department and is worth a separate look.

Iguana

Pick it when your developers prefer writing code to configuring screens, you value a small vendor you can talk to directly, and on-premises hosting is a requirement. Think twice when you need clarity on which generation to standardise on: iNTERFACEWARE currently supports both Iguana 6 and IguanaX and describes its direction as gradual convergence, so ask which one it recommends for a new installation and why.

InterSystems or a cloud platform

Pick InterSystems when you already run its products and have the skills. Pick a cloud service when your target is a FHIR store or analytics platform and an engine, or a small amount of code, can feed it. Pairing them is common: an engine handles HL7 v2 partners while the cloud service holds FHIR data. Our HL7 to FHIR conversion guide covers that middle step.

A decision checklist

  1. Interfaces: list every feed with message type, trigger events, volume, peak and partner. Count the ones that are not HL7 v2.
  2. Standards: do you need FHIR, X12, DICOM or IHE profiles inside the engine, or can another component handle them?
  3. Availability: how long can a feed be down before patients are affected? That sets your recovery time, and so whether you need clustering or just a tested standby.
  4. Hosting: on-premises only, your own cloud account, or the vendor’s hosting? Where must data stay?
  5. Skills: JavaScript, Lua, ObjectScript or graphical configuration. Can you hire for it where you are, and who covers holidays?
  6. Support: vendor contract, independent support firm, in-house only, or a mix? What response time do you actually need overnight?
  7. Monitoring: can it alert on queue depth, silent feeds and error rates, and send those alerts where your on-call team looks?
  8. Security and audit: how quickly does the vendor or project publish fixes? Mirth’s September 2026 advisory is a fair test question for any vendor: how would you have handled it?
  9. Cost over five years: see the next section. Ask every vendor for a written quote with renewal terms.
  10. Exit: can you export interface definitions in a readable form, and how hard would leaving be in five years?

Total cost of ownership: what to count

None of the commercial engines publishes a price list today, and we will not guess one. These are the lines to put in your model, with the vendor’s written quote in the first.

Cost lineWhat drives itHow engines differ
Licence or subscriptionServers, environments, tiers, interfaces or volume, renewal upliftMirth charges per server, so test and disaster-recovery servers count; the fork is free; Rhapsody and Iguana quote per organisation
HostingServers, database, storage for message history, backups, network linksSimilar for self-hosted engines; a vendor-hosted option moves this into the subscription
Building interfacesNumber and complexity of feeds, partner testingDriven by your team’s fluency more than by the engine
Running and supportOn-call cover, incident handling, partner changes, upgradesVendor support is in the fee for commercial engines; for the fork you staff it or buy it
Upgrades and security fixesRelease cadence, testing effort, Java or OS changesA regression test harness cuts this on any engine
Training and hiringLocal skills market, staff turnoverCheapest where the skills are common in your market
MonitoringBuilt-in features versus add-on toolsSome vendors bundle dashboards in paid tiers; open-source users add plugins or their own tooling
ExitInterfaces to rebuild, partners to re-testLowest between Mirth and its forks, highest across vendor families

What switching engines really costs

Between Mirth and the Open Integration Engine or BridgeLink, channels import directly, so the work is mostly testing, Java and extension replacement; our migration guide covers it. Between vendor families nothing imports cleanly: a Mirth JavaScript transformer becomes a Lua script or a Rhapsody route, rewritten and re-tested. Vendors offer help: Rhapsody markets an Intelligent Mapper that analyses legacy engines, and InterSystems added a Mirth migration tool in 2026.1. Treat these as accelerators, not as a replacement for testing with real messages.

Typical effort to rebuild and test one interface on a new engine, from our own estimates, confirmed per project:

  • Simple feed (for example, ADT with light field mapping): 1–2 engineer-days.
  • Typical clinical feed (lab orders and results with code tables): 3–6 engineer-days.
  • Complex feed (several destinations, database look-ups, custom acknowledgements, payer-specific X12): 5–10 engineer-days.

Add partner coordination, a parallel run and staff retraining. For 60 interfaces that is a project of months, which is why the cheapest engine on paper is often the one you already run.

Illustrative scorecard for two invented organisations

Illustrative, not client work. Weights and scores are our judgement for invented profiles; use your own. Scores are 1 to 5, weighted to a total out of 5.

CriterionWeight A / BLicensed MirthOIERhapsodyIguana
Fit with current team skills25 / 105523
Standards needed15 / 254354
Support model15 / 254254
Licence and running cost25 / 103523
Monitoring and availability10 / 204353
Cost to leave later10 / 104523
Total, profile A4.004.053.203.30
Total, profile B4.003.354.103.50

Profile A is a three-hospital group with two JavaScript-literate interface engineers, 60 mostly HL7 v2 feeds and a tight budget. Profile B is a regional HIE with many partners and standards, a 24-hour support requirement and appetite for a hosted service. The same engines, weighted differently, give opposite answers, and the margins are small. That is the point of doing the exercise rather than reading a ranking.

How we help

Help choosing an engine, and moving to it

Effort is given in typical engineer-days and confirmed as a fixed price per phase after a short scoping call. You deal with vendors directly for trials and quotes; we help you ask the right questions.

Engine selection assessment

The problem

You need to choose or confirm an engine, and the decision has to survive scrutiny from finance, security and clinical teams.

How we do it

We inventory your interfaces, agree weighted criteria with your team, prepare the questions for each vendor, build a five-year cost model around the quotes you receive, and write up a recommendation with the risks of each option. Typical effort: 5–10 engineer-days.

What you get

  • Interface inventory and requirements matrix
  • Vendor question set
  • Weighted scorecard with your weights
  • Five-year cost model and recommendation
Selection steps

How an engine selection assessment runs

About three to four weeks elapsed, mostly waiting on vendor answers.

Week 1

Inventory and criteria

Interface list from your current engine or spreadsheets, and weighted criteria agreed with IT, security, finance and a clinical lead.

Week 2

Vendor questions

You send our question set to the shortlisted vendors and request written quotes with renewal terms; we review answers as they arrive.

Week 3

Scoring and cost model

Scorecard with your weights and a five-year cost model built from the quotes, with the assumptions written down.

Week 4

Recommendation

A readout with the recommendation, the runner-up and what would change the answer, plus a migration outline.

Senior engineers firstYour first call is with someone who will do the work, not a sales script.
You own everythingCode, configuration, reports and documentation stay in your accounts and are handed over.
We run our own products15 live platforms we build and operate, so we feel production pain too.
Honest about fitIf a cheaper route or another provider suits you better, we will say so.
FAQ

Questions about Mirth, Rhapsody and Iguana

Neither is better in general. Mirth, or its free fork the Open Integration Engine, usually costs less and suits teams who write JavaScript and run their own servers. Rhapsody usually suits large organisations that want one accountable vendor, broad standards support and a hosted option. Weigh your skills, support needs and five-year cost.

It depends on your developers. Iguana scripts are written in Lua, which experienced programmers pick up quickly, while Mirth uses JavaScript, which more people already know. In our experience Mirth has the larger pool of engineers who have used it, so hiring is usually easier. Try building one real interface in each before deciding.

None of the three vendors publishes a price list as of November 2026. NextGen charges a flat annual fee per server for Mirth, iNTERFACEWARE agrees terms with each organisation, and Rhapsody does not publish prices. The Open Integration Engine is free. Ask each vendor for a written quote including renewals and every environment you need.

Its maintainers describe release 4.7.0, published on 21 October 2026, as generally available and recommended for production use, and the project is now incubating at the Eclipse Foundation. Whether it is ready for you depends on having someone to support it, in-house or under contract, since the project offers community help rather than a service level.

Partly. Google, Microsoft and AWS store and convert healthcare data well, and Microsoft converts HL7 v2 to FHIR, but none of them on its own provides the routing, queuing, retries and per-partner handling an engine gives you. Many organisations run an engine for HL7 v2 partners and a cloud FHIR service behind it.

Within the Mirth family, channels import and the work is mostly testing. Between vendor families every interface is rebuilt and re-tested, typically one to ten engineer-days each depending on complexity, plus partner coordination and a parallel run. For a large estate that is months of work, so include it in any cost comparison.

No. We are not a partner or reseller of NextGen, Rhapsody, iNTERFACEWARE, InterSystems, AWS, Microsoft or Google. Most of our interface work is on Mirth Connect and the Open Integration Engine, which is a bias you should weigh when reading this comparison. You obtain licences and trials from vendors directly.

Both engines are sold by the same company, Rhapsody. Rhapsody Integration is aimed at complex, high-volume environments, while the company presents Corepoint as a menu-driven engine suited to teams without a large IT department, available as SaaS, on your own infrastructure or as an integration platform service.

Last updated