Compliance-first delivery
A senior Mirth Connect team that keeps your interfaces flowing
Mirth Connect is one of the most widely used healthcare integration engines, and it is only as good as the channels built on it. Common problems we see are channels copied and patched over the years until nobody understands them, JavaScript transformers with no error handling, alerts that never fire, servers stuck on old versions, and uncertainty about licensing since the 2025 move to a commercial licence and the community Open Integration Engine fork.
Our engineers design channels, filters and transformers; build reusable JavaScript and Java code templates; configure MLLP, HTTPS, SFTP and database connectors with two-way TLS; and wire up reliable delivery with queuing, error handling, alerting and reprocessing. We take over existing environments with a documented review, plan and run version upgrades or migrations to the Open Integration Engine, and support the whole estate under a retainer. Message formats and partner work are covered by our wider HL7, FHIR and EDI integration practice, and round-the-clock operations by interface engine support.
You get channels that are documented and maintainable, monitoring that tells you about failures before clinicians do, and a clear path on versions and licensing. We frequently connect Mirth to OpenEMR and to health information exchanges, and our HL7 vs FHIR guide explains when each standard fits.
- Channel, filter, transformer and code-template development
- HL7 v2, FHIR, X12 EDI, CCDA and custom formats
- Version upgrades and migration to the Open Integration Engine
- Secure connectivity: MLLP, HTTPS, SFTP with two-way TLS
- Monitoring, alerting, reprocessing and managed support
What's Included
Everything you need, delivered by a senior, security-first team.
Channel Development
New inbound/outbound channels for labs, EHRs, HIEs, payers and devices — designed for reliability and easy maintenance.
Transformers & Mapping
Custom JavaScript/Java transformers, code templates and mapping logic that get the data exactly right.
Upgrades & Migration
Planned upgrades between Mirth versions and migration to the community Open Integration Engine, without interrupting live feeds.
Secure Connectivity
Two-way SSL/TLS, VPN and secure MLLP configuration for HIPAA-aligned message exchange.
Monitoring & Alerting
Proactive channel monitoring, error alerting, dashboards and documented message reprocessing.
Managed Support
Retainer-based support with response-time SLAs, on-call cover and change management.
End-to-end Mirth Connect integration services
Mirth Connect is one of the most widely used healthcare integration engines, relied on by hospitals, labs, diagnostic vendors and health-tech companies to move clinical data between systems. It receives a message in one format and protocol, transforms and validates it, applies routing and filtering, then delivers it reliably — with error handling and reprocessing so nothing is silently lost. We design, build, upgrade and support that entire pipeline.
Channel types and message formats we build
- HL7 v2 — ADT, ORM/OMG, ORU, SIU, MDM and DFT messages, including partner-specific Z-segments.
- FHIR R4 — expose or consume FHIR resources and bridge HL7 v2 ↔ FHIR; see FHIR interoperability.
- X12 EDI — 270/271 eligibility, 837 claims and 835 remittance.
- C-CDA and documents — generate, validate and route clinical documents to EHRs and HIEs.
- Custom — delimited, XML, JSON and database-to-database channels.
Protocols and connectivity
We configure the transport your partners require — MLLP over TCP, HTTP/S and web services, SFTP, JMS and database connectors — secured with TLS (including mutual TLS) and site-to-site VPN where needed.
Mirth Connect, NextGen Connect and the open-source forks
From version 4.6 (2025), NextGen moved Mirth Connect to a commercial licence. The community continued the open-source codebase as forks such as the Open Integration Engine (OIE) and BridgeLink. We work across these options and help you choose a path — staying on a supported open-source fork, or planning a licence and upgrade strategy — without disrupting live interfaces.
| Option | Consider when | Key questions |
|---|---|---|
| Stay on an older open-source Mirth release | Short term only, while planning | Security patching, Java version support |
| Move to an open-source fork (e.g. OIE) | You want to stay open source | Community activity, extension compatibility |
| Licensed NextGen Connect | You want vendor support and new releases | Licence cost per channel or server |
Take over, fix or build from scratch
Whether you have inherited undocumented channels that fail at 2am, need a new lab or EHR interface, or want a fully managed integration environment, we meet you where you are: a documented handover, a reliability and security review, then fixes, new development or ongoing interface engine monitoring and support.
Mirth best practices we apply
- Channels and code templates kept in version control and promoted between environments, not edited live.
- Reusable code templates rather than copy-pasted JavaScript in every transformer.
- Message pruning and database maintenance so the engine does not slow down over time.
- Queueing, retries and dead-letter handling for every outbound destination.
- Alerts on errors, queue depth and stopped channels routed to people who can act.
- Hardened servers, least-privilege accounts and audit logging.
Related reading
If you are deciding between standards, HL7 vs FHIR: A Practical Guide explains the trade-offs. Mirth is often the engine behind our HL7, FHIR and EDI integration and OpenEMR integration projects.
How We Work With Your Mirth Environment
Review
Inventory channels, versions, licensing, errors and security; agree priorities.
Fix & Document
Repair failing channels, add error handling and document every interface.
Build & Upgrade
Develop new interfaces and plan version upgrades or OIE migration.
Support
Monitoring, alerting and SLA-backed support with change management.
Frequently Asked Questions
Mirth Connect is a healthcare integration engine used to route, transform and monitor messages between systems — for example sending HL7 v2 lab results into an EHR, exchanging C-CDA documents with an HIE or exposing FHIR APIs. It handles filtering, transformation, error handling and delivery.
From version 4.6 (2025) NextGen moved Mirth Connect to a commercial licence. The open-source codebase continues as community forks such as the Open Integration Engine (OIE) and BridgeLink. We work with both the commercial and open-source paths and help you choose and migrate.
Yes. We take over existing implementations with a documented handover, review channels for reliability and security, fix problem interfaces and provide ongoing monitoring and support under an SLA-backed retainer.
Yes. We inventory channels and extensions, test them on the target version or fork in a staging environment, plan the Java and database changes, and cut over with a rollback plan.
New channels are usually fixed-price once specifications are reviewed. Upgrades start with a fixed-price assessment. Ongoing support is a monthly retainer sized by the number of channels and the response times you need.
Mirth can be configured to support HIPAA-compliant exchange with TLS encryption, access controls, audit logging and secure infrastructure. We deploy it in hardened, HIPAA-aligned environments and document the controls for your compliance programme.
Ready to get started with Mirth Connect Services?
Book a free consultation — we'll map a secure, practical path forward.