Skip to content
Open Integration Engine™ Free. Open Source. Trusted.

About

Open Integration Engine is an open source integration engine for healthcare: a flexible, standards-based tool for connecting disparate systems and moving clinical data reliably between them.

Connectors

  • TCP / MLLP

    Native HL7 v2 transport. The standard way of moving clinical messages between systems.

  • HTTP / HTTPS

    REST and SOAP web services, inbound and outbound. JSON, XML, multipart, and custom payloads.

  • JDBC

    Direct database integration. Read and write to PostgreSQL, MySQL, Oracle, SQL Server, and more.

  • File / SFTP / FTP

    Read and write files on local volumes, network shares, or remote SFTP / FTP servers.

  • Messaging

    SMTP for email; JMS, AWS SQS, and other queues for asynchronous integration.

  • DICOM

    Medical imaging data exchange with DICOM-conformant PACS, modalities, and imaging workflows.

…and anything else you can build with the plugin SDK.

Capabilities

  • Data transformation

    Convert between HL7 v2, FHIR, DICOM, X12, JSON, XML, and custom formats with a visual mapper and JavaScript transformers.

  • Message routing

    Rule-based routing and filtering by content, source, or custom logic.

  • Custom scripting

    Full JavaScript access to every message, globals, config maps, and external services.

  • Real-time monitoring

    Live message tracking, queue counts, and alerts on failures or SLA breaches.

  • Plugin architecture

    Extend the engine with connectors, transformers, and admin UI plugins without forking.

  • Durable, queued delivery

    Messages persist to the database, retry on failure, and survive restarts. Clinical data does not get dropped.

Who it's for

  • Integration engineers

    Building and maintaining the interfaces between clinical, financial, and operational systems.

  • Health IT teams

    Moving data between EHRs, labs, imaging, pharmacy, and billing. Reliably, at scale.

  • EHR and app vendors

    Shipping interoperability to their customers without rolling their own engine.

  • Researchers and informaticists

    Building dependable data pipelines for informatics, analytics, and research workflows.

Why OIE

Healthcare integration is its own discipline. OIE is built for it, not a general-purpose ESB retrofitted for clinical workloads. The engine speaks healthcare standards natively, the plugin ecosystem targets healthcare problems specifically, and the community is made up of people who ship clinical integrations for a living.

The architecture is modular and extensible: add connectors, custom transformers, or domain plugins without modifying the core. Deployment runs anywhere the JVM runs: on-premises, in your cloud, or in a container.

A brief history

OIE originated as a fork of Mirth Connect, the widely-adopted open source integration engine originally developed by WebReach, later acquired by Quality Systems, and now stewarded by NextGen Healthcare. The fork was created to preserve fully-open, community-governed healthcare integration tooling after the commercial steward began shifting toward a proprietary direction.

Read about how the project is governed →

Acknowledgments

OIE stands on the shoulders of the original Mirth Connect team and the many contributors who shaped the engine over the years it was developed as open source. And we're grateful to the broader open source healthcare community that continues to show up every day.