Interfaces that move clinical data cleanly, every single time.
We architect, build, deploy, and support the integrations that connect EHRs, laboratories, pharmacies, and healthcare applications — with Mirth Connect at the core and a production-first mindset throughout.
Deep, hands-on Mirth Connect engineering
Mirth Connect (NextGen Connect) is where we live. From greenfield channel architecture to rescuing an interface engine that's dropping messages, we handle the full lifecycle — and we write clean, maintainable JavaScript transformers your next engineer can actually read.
- Channel architecture, development, and deployment
- JavaScript development inside Mirth Connect
- Message routing, filtering, and validation
- Error handling, retry logic, and alerting
- Interface monitoring, troubleshooting, and optimisation
- Reusable channel templates, mappings, and patterns
Standards, formats, and systems we work with
HL7 v2 interfaces
ADT, ORM, ORU, SIU, DFT, and custom messages — engineered with mapping, validation, and resilient error handling.
FHIR, JSON & REST
FHIR, JSON, REST API, CSV, and SFTP integrations, including SMART on FHIR workflows and modern API consumers.
Data transformation
HL7-to-FHIR, HL7-to-JSON, and custom transformation logic, built to be testable and maintainable.
EHR / EMR integration
Epic, Oracle Health / Cerner, athenahealth, eClinicalWorks, Veradigm, Meditech, and similar systems.
LIS, RIS, HIE & more
Laboratory, radiology, pharmacy, billing, registry, HIE, and healthcare API integrations.
Compliance workflows
SMART on FHIR, PDMP, ASAP 4.2, prescription, cannabis healthcare, and compliance-reporting workflows.
Fluent in the language of health data
Interoperability is far more than HL7. We work across the messaging standards, document formats, terminologies, and national networks that real clinical data depends on.
Messaging & documents
- HL7 v2.x — ADT, ORM, ORU, SIU, DFT, MDM, VXU
- FHIR R4 & US Core
- C-CDA / CDA documents
- X12 EDI — 270/271, 276/277, 834, 835, 837
- NCPDP / eRx (SCRIPT)
- DICOM imaging
Terminologies & codes
- LOINC
- SNOMED CT
- ICD-10-CM / PCS
- CPT / HCPCS
- RxNorm
- UCUM units
Networks & frameworks
- SMART on FHIR & CDS Hooks
- IHE profiles — XDS.b, PIX/PDQ, XCA
- TEFCA / QHIN
- Carequality & CommonWell
- eHealth Exchange
- Regional & state HIEs
Security & compliance
- HIPAA privacy & security
- Consent management
- ATNA audit logging
- PDMP reporting
- ASAP 4.2
- De-identification
Mirth-first — fluent across the ecosystem
Mirth Connect is our home, and we also work with the other engines and managed FHIR platforms healthcare teams run — so we can meet you wherever your integration lives, cloud or on-prem, and connect you to national exchange networks.
- Mirth Connect / NextGen Connect (primary)
- Rhapsody, Cloverleaf & InterSystems (Ensemble / IRIS / HealthShare)
- Managed FHIR — GCP Healthcare API, Azure Health Data Services, AWS HealthLake
- Custom FHIR façades & API gateways
- MLLP, SFTP, HTTPS & message-queue transports
From requirement to monitored production interface
Specification & mapping
We capture message specs, trigger events, and field-level mappings — and confirm them against sample messages before building.
Channel build
Source, filters, transformers, and destinations built in Mirth with clean JavaScript, validation, and clear naming.
Test & harden
Edge cases, malformed messages, and failure paths tested; retry logic and alerting wired so nothing fails silently.
Deploy & monitor
Deployment, dashboards, and alerting go live — with documentation and ongoing production support available.
Common questions
Which HL7 message types do you support?
We build and maintain HL7 v2 interfaces including ADT, ORM, ORU, SIU, DFT, and custom message types — with mapping, validation, and robust error handling.
Can you transform HL7 into FHIR or JSON?
Yes. We deliver HL7-to-FHIR, HL7-to-JSON, and custom data transformation, typically implemented as JavaScript transformers inside Mirth Connect.
Do you support existing Mirth Connect channels?
Absolutely. We take over, troubleshoot, optimise, and monitor existing Mirth Connect / NextGen Connect deployments and provide ongoing production support.
Can you integrate with our specific EHR?
We work with Epic, Oracle Health / Cerner, athenahealth, eClinicalWorks, Veradigm, Meditech, and similar systems, as well as LIS, RIS, HIE, pharmacy, billing, and registry systems.
Have an interface to build — or one that's misbehaving?
Send us the message specs or the symptoms. We'll tell you how we'd approach it.