OIE + OpenShare
vs Cloverleaf.
Cloverleaf (by Infor) is a long-established enterprise integration platform with deep legacy-format support and a large hospital-system installed base. OIE + OpenShare offers open-source licensing, zero engine costs, and a modern experience layer. Here’s the honest comparison.
Long-established enterprise vs modern open-source.
Cloverleaf and OIE take fundamentally different approaches to healthcare integration.
Open Integration Engine
OIE is the community fork of Mirth Connect, free under MPL 2.0 with no per-interface licensing. OpenShare adds browser-based administration, VPN-free remote access via Gateway, and direct encrypted data exchange via Exchange. No centralized cloud. No per-transaction fees.
- Open-source under MPL 2.0
- No per-communication-point fees
- Purpose-built browser admin (OpenShare Console)
- VPN-free remote access + built-in direct exchange
Cloverleaf by Infor
Cloverleaf is a commercial enterprise integration platform with decades of deployment history in large hospital systems. Known for broad format support including HL7, FHIR, API, EDIFACT, X12, and legacy proprietary formats. Backed by Infor, a large enterprise software company. Enterprise licensing and support.
- Deep legacy-format support (HL7, FHIR, EDIFACT, X12 + more)
- Large-enterprise hospital system footprint
- Infor enterprise backing and support
- Long deployment track record
Feature-by-feature comparison.
OIE + OpenShare vs Cloverleaf. Legacy depth vs open-source agility.
| Capability | OIE + OpenShare | Cloverleaf (Infor) |
|---|---|---|
| Engine type | OIE (open-source fork of Mirth Connect) | Cloverleaf (proprietary, by Infor) |
| Open source | ✓ | ✗ |
| License | MPL 2.0, free | Enterprise license (commercial) |
| Browser adminOpenShare Console adds DICOM viewer, channel analytics, real-time message browsing | OpenShare Console (purpose-built) | Web-based management console |
| VPN-free remote accessOpenShare Gateway; Cloverleaf requires traditional network access | ✓ | ✗ |
| Direct data exchangeCloverleaf does not include a native direct exchange network | Built-in, E2E encrypted | ✗ |
| HL7 v2 / FHIR / X12 | ✓ | ✓ |
| Legacy format supportCloverleaf's deep legacy-format support is a real differentiator for complex environments | HL7, FHIR, DICOM, X12, common formats | Broad: HL7, FHIR, EDIFACT, X12, legacy proprietary formats |
| DICOM support | ✓ | ✓ |
| Enterprise footprintCloverleaf has significant deployment history in large hospital systems | Growing community adoption | Large-enterprise installed base |
| Vendor backing | Community + Saga IT | Infor (large enterprise software vendor) |
| Deployment | Docker, Kubernetes, any cloud | On-premises / cloud (enterprise deployment) |
An honest comparison.
We believe in transparency. Here’s where each product is the right fit.
- Zero engine licensing cost (MPL 2.0 open-source)
- No per-communication-point or enterprise license fees
- OpenShare Console: purpose-built browser admin with DICOM viewer + analytics
- VPN-free remote access via OpenShare Gateway
- Built-in encrypted data exchange between organizations
- Open stack, no single-vendor dependency
- Deep legacy-format support: EDIFACT, X12, legacy proprietary formats, and more
- Large-enterprise hospital system deployment track record
- Infor enterprise backing for large-scale procurement and support
- Decades of production history in complex enterprise environments
The bottom line: Cloverleaf’s strength is depth, deep legacy-format support and a long track record in large hospital systems. If your environment has complex legacy format requirements or you need an established enterprise vendor, Cloverleaf is worth considering. For most healthcare organizations starting fresh or migrating from Mirth Connect, OIE + OpenShare delivers the integration capabilities you need at zero licensing cost with a modern tooling layer.
Frequently asked questions.
How does Cloverleaf compare to OIE + OpenShare?
Cloverleaf (by Infor) is a long-established enterprise integration platform with deep support for legacy healthcare formats, a large-enterprise installed base, and broad HL7, FHIR, API, and legacy format coverage. OIE + OpenShare provides comparable HL7, FHIR, DICOM, and X12 integration at no licensing cost, with a modern browser admin layer, VPN-free remote access, and built-in direct data exchange. Cloverleaf leads in legacy-format depth and large-enterprise footprint; OIE + OpenShare leads in cost and modern tooling.
Who makes Cloverleaf?
Cloverleaf is made by Infor, a large enterprise software company. Infor acquired Cloverleaf as part of its healthcare IT portfolio. Cloverleaf has been in use in large hospital systems and healthcare enterprises for many years and has a substantial installed base.
Does OpenShare work with Cloverleaf?
OpenShare (Console, Gateway, Exchange) is designed to run on top of OIE and other Mirth Connect-compatible engines. It is not compatible with Cloverleaf, which uses a different proprietary engine architecture. Evaluating OIE + OpenShare as a Cloverleaf alternative would involve migrating integration logic to OIE.
What legacy formats does Cloverleaf support?
Cloverleaf is well-regarded for broad legacy healthcare format support including HL7 v2, FHIR, API integration, EDIFACT, X12, and various proprietary legacy formats. This depth of legacy-format support is a genuine strength for large organizations with complex, long-standing integration requirements. OIE (as a Mirth Connect fork) supports HL7 v2, FHIR, DICOM, X12, and common healthcare formats, sufficient for most organizations, though specialized legacy format scenarios may favor Cloverleaf.
Is Cloverleaf open source?
No. Cloverleaf is a commercial proprietary platform by Infor. OIE is open-source under MPL 2.0 and free to use, run, and modify. OpenShare Console (browser admin) and secure remote access are always free; exchanging data on the network is a flat per-server monthly membership.
