Services
Four ways we work on a Mirth Connect estate
From the first inventory to the on-call rota
Most engagements start with the same question: what exactly is running in the engine, and what does the 2025 license change mean for it? From there the work follows the estate, not a package. All of it is billed hourly, time and materials, as a project or as staff augmentation; scope, staffing and timeline are agreed in a first conversation.
Channel Estate and License-Exposure Assessment
An inventory of every channel, connector, custom transformer, code template and downstream dependency, the Mirth Connect version each environment runs, and what the commercial-only licensing from 4.6 means for each of them. You get a ranked risk list and a written stay, buy or migrate recommendation with effort ranges and a sequence.
Upgrade or Fork Migration
We execute the path you chose: an upgrade of a frozen estate to a supported commercial Mirth Connect release, or a migration of the channels to Open Integration Engine or BridgeLink. Every channel is parity-tested against replayed message sets before cutover, with a rollback plan that has been rehearsed.
Interface Build and FHIR Enablement
New interfaces on the engine you run: HL7 v2 feeds, CCDA, X12, DICOM routing, flat files and APIs, to and from EHR, lab, imaging, billing and payer systems, plus mapping of v2 content to FHIR resources where API obligations require it.
Channel Operations and Interface Team Augmentation
Retained senior support for a running estate: monitoring and alert design, PHI-safe logging, queue and message-store growth, scheduled upgrades, on-call backup and the documentation that lets a small team take a holiday.
Chartferry is independent. We are not affiliated with, endorsed by, or a reseller of NextGen Healthcare, and we use the name Mirth Connect only to describe the product we work on.