Download Mirth Connect
The last open-source Mirth Connect release was 4.5.2. The community continues it as the Open Integration Engine (OIE). Download the free, open-source engine: installer, Docker, or the MirthSync Git plugin.
Where Did Mirth Connect's Open-Source Download Go?
The free, open-source Mirth Connect lives on as the Open Integration Engine (OIE): fully compatible with your existing Mirth channels, code templates, and configurations.
Why OIE Exists
Mirth Connect was the most widely used open-source healthcare integration engine for over a decade. In 2025, NextGen Healthcare transitioned Mirth Connect to commercial licensing, ending the open-source distribution model that thousands of healthcare organizations relied on. The Open Integration Engine is the community fork that continues open-source development.
Full Mirth Connect Compatibility
OIE maintains full compatibility with existing Mirth Connect channels, code templates, JavaScript transforms, and server configurations. Organizations running Mirth Connect can transition to OIE without modifying their existing interfaces. OIE supports the same standards: HL7 v2, FHIR R4, DICOM, X12, and custom message formats.
Saga IT's Role
Saga IT builds and distributes OIE packages, develops the OpenShare Gateway that connects your servers to the OpenShare integration platform, and provides professional OIE consulting services including migration planning, channel development, cloud deployment, and managed support.
Choose Your Package
Three download options, all free. Register on OpenShare to access installer downloads.
OIE Installer
The Open Integration Engine: a free, open-source fork of Mirth Connect. Available for Linux, Windows, and macOS.
- New integration engine installations
- Replacing Mirth Connect with a free alternative
- On-premise server deployments
MirthSync Plugin
Version control and deployment for Mirth Connect and OIE: pull, push, and sync channels directly from the Administrator.
- Source control for Mirth channels
- Team collaboration on channel development
- CI/CD pipeline integration
Docker Image
Run OIE in a container. Pull and start in seconds. No installer, no dependencies.
- Cloud-native and containerized deployments
- CI/CD pipelines and ephemeral environments
- Quick evaluation without local install
Operate, Share & Monitor From the Browser
Install the OpenShare Gateway on any Mirth Connect or OIE server to operate your integration servers, monitor your whole fleet, and share channels and data with partner organizations, all from one browser console.
Operate
Run and administer your Mirth Connect and OIE servers from any browser: channel management, message browser, and deploys. No Java desktop client, no open ports.
Monitor
Fleet monitoring across every server: channel health, message throughput, and error rates. Configurable alerts notify your team when channels fail or queues back up.
Share
Publish channels and exchange HL7 messages, FHIR resources, and files with partner organizations over encrypted gateway tunnels. Outbound-only: no inbound firewall changes or dedicated circuits required.
Moving from Mirth Connect?
OIE is fully compatible with Mirth Connect channels and configurations. Your existing interfaces transfer without modification. For organizations that need professional migration support (including compatibility assessment, parallel-run validation, and zero-downtime cutover), our integration team has deep experience across both platforms. For background on why teams are migrating, see Mirth Connect alternatives in 2026.
Common Questions
The last fully open-source Mirth Connect release was 4.5.2. After NextGen Healthcare moved later versions (4.6 and up) to commercial licensing, the open-source lineage continues as the Open Integration Engine (OIE): a free, community-maintained engine that is fully compatible with existing Mirth Connect channels, code templates, and configurations. Download OIE as an installer, pull the Docker image, or add the MirthSync plugin for Git-based version control.
The Open Integration Engine (OIE) is a free, open-source healthcare integration engine forked from Mirth Connect after NextGen Healthcare transitioned Mirth Connect to commercial licensing. OIE is fully compatible with existing Mirth Connect channels, code templates, and configurations. It is maintained by the open-source community and supported professionally by Saga IT.
Yes. OIE is free and open-source software, licensed under the same open-source terms as the original Mirth Connect codebase. There are no per-server fees, per-message fees, or subscription costs for the integration engine itself. Saga IT offers optional professional support and consulting services for organizations that need expert assistance.
The OpenShare Gateway is a plugin for Mirth Connect and OIE servers that connects them to OpenShare, an integration platform built on OIE. It powers three capabilities from one browser console: operating your integration servers (channel management, message browser, deploys, no Java client, no open ports), monitoring your whole fleet (channel health, throughput, error-rate alerting), and sharing channels and data with partner organizations over encrypted gateway tunnels. The plugin is included pre-installed in the full OIE package or available as a standalone download for existing servers.
Yes. OIE maintains full channel format compatibility with Mirth Connect: your existing channels, code templates, JavaScript transforms, and configuration maps transfer without modification. For professional migration assistance including compatibility testing, parallel-run validation, and zero-downtime cutover, see our OIE consulting services.
Yes. Saga IT provides professional consulting and support for OIE deployments, including migration from Mirth Connect, channel development, cloud-native deployment on AWS and Azure, CI/CD implementation with MirthSync, and 24/7 managed services. Visit our OIE services page for details.
OIE requires JDK 11 or later, runs on Linux, Windows Server, or macOS, and needs a minimum of 4 GB RAM (8 GB recommended) with 2 GB of disk space. The OpenShare Gateway requires outbound HTTPS access on port 443 to connect to OpenShare. Connections are outbound-only, so no inbound firewall changes are needed. Both Docker images and traditional installers are available.
Need Help with OIE?
Whether you're migrating from Mirth Connect or deploying a new integration engine, our team can help.