OIE + OpenShare
vs Rhapsody.
Rhapsody (formerly Lyniate) was KLAS top-rated in 2024 and is battle-tested at enterprise scale. OIE + OpenShare gives you open-source freedom, zero licensing fees, and a modern experience layer, without the per-communication-point costs. Here’s an honest look at both.
Different tools, different trade-offs.
OIE and Rhapsody take fundamentally different approaches to healthcare integration.
Open Integration Engine
OIE is the community-maintained fork of Mirth Connect, licensed under MPL 2.0. It’s binary-compatible with Mirth Connect, same channels, same API, same database schema. OpenShare adds the experience layer: browser-based administration, VPN-free remote access, and direct data exchange. Zero engine licensing cost.
- Open-source under MPL 2.0
- Free with no per-interface fees
- Modern browser admin (OpenShare Console)
- VPN-free remote access + direct exchange
Rhapsody (formerly Lyniate)
Rhapsody is a commercial enterprise healthcare integration engine with a long track record. KLAS top-rated in 2024 with a score of 93.1. Known for high throughput at scale, a mature drag-and-drop IDE, and 24/7 enterprise support. Used by 1,700+ organizations in 31 countries (per Lyniate). Per-communication-point licensing.
- KLAS top-rated 2024 (#2, 93.1)
- Enterprise-grade throughput
- 24/7 support via Rhapsody Health
- Visual drag-and-drop IDE
Feature-by-feature comparison.
OIE + OpenShare vs Rhapsody. Enterprise credentials vs open-source flexibility.
| Capability | OIE + OpenShare | Rhapsody (formerly Lyniate) |
|---|---|---|
| Engine type | OIE (open-source fork of Mirth Connect) | Rhapsody (proprietary) |
| Open source | ✓ | ✗ |
| LicenseRhapsody: ~£19,500/yr for 10-point license + 22% annual support (per case study) | MPL 2.0, free | Per-communication-point (commercial) |
| Browser adminOpenShare Console adds DICOM viewer, channel analytics, real-time message browsing | OpenShare Console (purpose-built) | Desktop IDE + limited web console |
| VPN-free remote accessOpenShare Gateway; Rhapsody requires VPN or limited HTTPS console access | ✓ | ✗ |
| Direct data exchangeOpenShare Exchange is direct org-to-org, no centralized cloud; Envoy is a federated hub | Built-in, E2E encrypted | Rhapsody Envoy (centralized network) |
| HL7 v2 / FHIR / X12 | ✓ | ✓ |
| DICOM supportRhapsody routes DICOM; OIE + OpenShare Console includes a built-in DICOM viewer | ✓ | Routing support |
| Performance at scaleRhapsody case studies cite ~10x throughput over Mirth Connect at high volume (inferential for all orgs) | Proven for most healthcare orgs | Enterprise-grade (~10x Mirth at scale) |
| Vendor support | Community + Saga IT | Rhapsody Health 24/7 with SLAs |
| KLAS ratingKLAS top-rated 2024 | New | #2 (93.1) |
| Cloud deployment | Docker, Kubernetes, any cloud | AWS (Rhapsody as a Service) |
* Performance claim (~10x throughput over Mirth Connect) sourced from published Rhapsody case studies. Results vary by workload and environment.
An honest comparison.
We believe in transparency about where each product is the right fit.
- Zero engine licensing cost (MPL 2.0 open-source)
- No per-communication-point fees
- OpenShare Console: purpose-built browser admin with DICOM viewer + analytics
- VPN-free remote access via OpenShare Gateway
- Direct encrypted data exchange via OpenShare Exchange
- Open stack, no vendor lock-in
- Proven enterprise throughput, case studies cite ~10x over Mirth at scale
- 24/7 dedicated support with formal SLAs via Rhapsody Health
- KLAS top-rated 2024 (#2, 93.1), sustained customer satisfaction track record
- Mature drag-and-drop IDE purpose-built for rapid interface development
- Rhapsody Envoy: established federated exchange network (1,300+ orgs)
- Single commercial vendor accountability for enterprise procurement
The bottom line: If you need proven enterprise throughput at massive scale, a single vendor support contract, and a mature visual IDE, Rhapsody is an excellent product. If you want open-source flexibility, zero licensing fees, and modern browser-based tooling without VPN dependencies, OIE + OpenShare is the alternative worth evaluating.
Frequently asked questions.
Is OIE + OpenShare a replacement for Rhapsody?
OIE + OpenShare covers the core integration capabilities Rhapsody provides, HL7, FHIR, DICOM, X12 processing, browser-based administration, and data exchange, at no licensing cost. Rhapsody has advantages in raw throughput at scale and 24/7 enterprise support. For organizations where those factors are essential, Rhapsody may still be the right choice. For organizations that want open-source flexibility, zero licensing fees, and modern browser admin with VPN-free remote access, OIE + OpenShare is a strong alternative.
How does Rhapsody’s performance compare to OIE?
Rhapsody case studies cite approximately 10x throughput improvement over Mirth Connect at enterprise scale, a significant performance advantage for high-volume environments. OIE is the community fork of Mirth Connect and inherits the same underlying engine architecture. For organizations processing millions of transactions per day, Rhapsody’s performance credentials are a real differentiator. For the majority of healthcare organizations, OIE’s throughput is sufficient and the cost savings are substantial.
Does OpenShare work with Rhapsody?
OpenShare (Console, Gateway, Exchange) is designed to run on top of OIE and other Mirth Connect-compatible engines. It is not compatible with Rhapsody, which uses a different proprietary engine architecture. If you run Rhapsody today and want to evaluate OIE + OpenShare, that would involve migrating your channel logic to OIE.
What is Rhapsody’s licensing model?
Rhapsody uses per-communication-point (connection point) licensing. Published case studies reference costs such as approximately £19,500 per year for a 10-point license plus 22% annual support. OIE is free and open-source under MPL 2.0 with no per-interface fees. OpenShare Console and secure remote access are always free; exchanging data on the network is a flat per-server monthly membership.
Who provides support for OIE?
OIE is community-maintained, with Saga IT as active contributors. Saga IT offers professional services for OIE deployments. This differs from Rhapsody, which provides dedicated 24/7 enterprise support through Rhapsody Health with formal SLAs. Organizations that require a single commercial vendor with contractual support guarantees may prefer Rhapsody.
