One sealed platform.
- Licensed per communication point: every interface you add raises the bill
- Desktop IDE, licensed per seat
- Annual support contract on top
- Roadmap, pricing, and portability on the vendor’s terms
Compare
The open-sourceintegration engine.
OIE + OpenShare gives you what Rhapsody and Corepoint offer: browser-based administration, secure remote access, and a data exchange network, without the per-interface licensing fees.
The engine went commercial. The stack went open.
Rhapsody and Corepoint led the commercial integration-engine market for years. Then NextGen took Mirth Connect commercial in March 2025, and the community forked it as the Open Integration Engine. Pair the fork with OpenShare and you get what the commercial healthcare integration engines sell, on a stack you own.
An engine you own, a layer that completes it.
- OIE, the community fork of Mirth Connect: same channels, extensions, API, and database schema. MPL 2.0, $0, forever.
- OpenShare completes it: browser console, VPN-free remote access, monitoring, and end-to-end encrypted direct exchange.
- No lock-in at either layer: the engine is open source and the tooling works with any Mirth-compatible fork.
Engine license$0, open sourcevs per-communication-point fees
AdministrationAny browser, freevs desktop IDE seats
Site-to-site exchangeE2E direct, built invs VPNs between sites
Compare all major integration engines.
OIE + OpenShare vs the full commercial landscape. Deep-dives linked below.
| Capability | OIE + OpenShare | Rhapsody | Corepoint | Cloverleaf | Iguana |
|---|---|---|---|---|---|
| Open Source | ✓ | ✗ | ✗ | ✗ | ✗ |
| License model | Free (MPL 2.0) | Per comm. point | Per comm. point | Enterprise license | Per-channel |
| Browser admin | OpenShare Console | Limited web console | ✓ | ✓ | ✓ |
| HL7 v2 / FHIR / X12 | ✓ | ✓ | ✓ | ✓ | ✓ |
| VPN-free remote access | ✓ | ✗ | ✗ | ✗ | ✗ |
| Direct data exchange | Built-in, E2E encrypted | Rhapsody Envoy | Community Exchange | ✗ | ✗ |
| Cloud deployment | Docker, K8s, any cloud | AWS (RaaS) | AWS | On-prem / cloud | On-prem / cloud |
| KLAS rating | New | #2 (93.1, 2024) | #1 (95.2, 2024) | Rated | Rated |
Feature-by-feature: Rhapsody & Corepoint.
How OIE + OpenShare stacks up against the two KLAS-leading commercial integration engines.
| Capability | OIE + OpenShare | Rhapsody | Corepoint |
|---|---|---|---|
| Engine | OIE (open-source) | Proprietary | Proprietary |
| License | Free (MPL 2.0) | Per-communication-point | Per-communication-point |
| Admin Console | Browser-based | Desktop IDE + Web Console | Browser-based |
| HL7 v2.x | ✓ | ✓ | ✓ |
| FHIR | ✓ | ✓ | ✓ |
| DICOM | ✓ + built-in viewer | Routing support | ✓ |
| X12 / EDI | ✓ | ✓ | ✓ |
| Remote Access | No VPN required | VPN or HTTPS console | VPN or web services |
| Direct Data Exchange | Built-in, E2E encrypted | Rhapsody Envoy (centralized) | Community Exchange |
| Open Source | ✓ | ✗ | ✗ |
| Cloud Deployment | Docker, Kubernetes, any cloud | AWS (RaaS) | AWS |
| KLAS Rating | New | #2 (93.1, 2024) | #1 (95.2, 2024) |
| Vendor Support | Community + Saga IT | Rhapsody Health 24/7 | Rhapsody Health 24/7 |
Why organizations are switching.
Zero licensing fees
OIE is free and open-source under MPL 2.0. OpenShare Console (browser admin), remote access, and monitoring are free, always. Exchanging data on the network is a flat per-server/month membership.
Rhapsody~£19,500/year for 10-point license + 22% annual support (per published case study, UK market)
CorepointPer-communication-point licensing + action point fees
No-VPN remote access
The OpenShare Gateway establishes an encrypted outbound connection, no inbound firewall rules, no VPN infrastructure to maintain. Access your integration engine from any browser, anywhere.
RhapsodyVPN required, or limited web management console for monitoring only
CorepointVPN required, or CareAgent web services for limited access
Direct data exchange
Send and receive healthcare data directly between organizations. End-to-end encrypted, no centralized cloud, no per-transaction fees. Your data stays on-premise, OpenShare handles the signaling, not the data.
RhapsodyRhapsody Envoy, centralized federated network (1,300+ orgs)
CorepointCommunity Exchange, separate product offering
Migration is simpler than you think.
From Mirth Connect
OIE reads Mirth Connect’s database directly. Point OIE at your existing database and everything carries over, channels, extensions, message history, users. Zero re-work.
See the migration path →From Rhapsody or Corepoint
Your channel logic, HL7 mappings, FHIR transformations, routing rules, ports to OIE via standard healthcare data formats. Different architecture, same integration patterns.
Talk to our migration team →Frequently asked questions.
How does OIE + OpenShare compare to Rhapsody?
OIE + OpenShare provides the same core capabilities as Rhapsody, HL7/FHIR/DICOM processing, browser-based administration, and data exchange, without per-communication-point licensing fees. OIE is open-source under MPL 2.0 and binary-compatible with Mirth Connect. OpenShare adds browser admin, VPN-free remote access, and end-to-end encrypted direct data transfer. Rhapsody offers a mature desktop IDE and 24/7 vendor support through Rhapsody Health.
How does OIE + OpenShare compare to Corepoint?
Corepoint Integration Engine has been the #1 KLAS-rated integration engine for 16 consecutive years as of the 2024 report. OIE + OpenShare provides comparable integration capabilities, HL7, FHIR, DICOM, X12, with open-source licensing, VPN-free remote access, and built-in direct data exchange. Corepoint uses per-communication-point licensing while OIE is free under MPL 2.0. OpenShare Console and secure remote access are always free; exchanging data on the network is a flat per-server monthly membership.
Can I migrate from Rhapsody or Corepoint to OIE?
Yes. While there is no direct database migration path from Rhapsody or Corepoint to OIE (they use different architectures), your channel logic, HL7 mappings, FHIR transformations, routing rules, can be rebuilt in OIE. Organizations already on Mirth Connect have an even easier path: OIE reads the Mirth Connect database directly with zero re-work.
Is OIE production-ready?
Yes. OIE is a binary-compatible fork of Mirth Connect, which has been in production at thousands of healthcare organizations for nearly two decades. OIE uses the same codebase, same database schema, same API, and same channel architecture. It is actively maintained by the open-source community with Saga IT as active contributors.
What does OpenShare add on top of OIE?
OIE is the integration engine that runs your channels and processes HL7, FHIR, DICOM, and X12. OpenShare is the experience layer on top. The Console replaces the legacy Java desktop client with browser-based administration, Gateway provides VPN-free remote access to your own servers, and Exchange adds end-to-end encrypted direct transfer between organizations. Console, Monitoring, Drivers, and Gateway access are free forever; only the cross-organization network is paid.
Do I have to use OIE, or does OpenShare work with other Mirth forks?
OpenShare is fork-agnostic. The Gateway plugin installs on Mirth Connect, OIE, BridgeLink, or any Mirth Connect-compatible engine, and the process is the same regardless of fork. We recommend OIE because it is open-source under MPL 2.0 and binary-compatible with Mirth Connect, but you are not locked into a single engine.
