Our experts are ready to understand your business goals.
Mirth Connect sits at the center of most healthcare integration estates, moving HL7 v2 traffic between EHRs, laboratories, billing platforms, and clinical applications. The engine is powerful and deliberately unopinionated, which means the quality of the outcome depends entirely on how the channels are designed. Untested transformers, unbounded queues, and unmonitored destinations accumulate quietly until a feed fails overnight and no one can say which downstream system stopped receiving data. Taction Software has built and supported production Mirth Connect environments since 2013 for hospitals, digital health vendors, and revenue cycle organizations, with 250+ healthcare and EHR integrations completed.
We design channel topology before writing code: source connector strategy, routing logic, destination fan-out, and where message state lives. The result is an estate your engineers can read without reverse engineering someone’s JavaScript.
ADT, ORM, ORU, SIU, DFT, MDM, and VXU interfaces built against real vendor specifications, not idealized standards. We handle Z-segments, non-conformant delimiters, and the vendor quirks that break textbook parsers.
Transformers written as small, testable functions with code templates shared across channels. No thousand-line inline scripts, no copy-pasted logic that has to be patched in fourteen places when a field mapping changes.
Every channel gets defined failure behavior: what retries, what dead-letters, what pages a human. Alerts route to email, Slack, or your incident tooling with enough context to act on immediately.
We tune queue thresholds, thread counts, message storage settings, and database pruning so throughput holds under peak load. Storage mode choices are made deliberately against your retention and replay requirements.
Channel inventories, interface specifications, and runbooks are written as part of delivery. Your team can operate the environment without depending on the consultant who built it.
Most Mirth Connect work is not one interface. It is a growing web of feeds that each carry clinical or financial consequence when they stop. We scope engagements around the flows that matter to your operation, then build them so each one can be tested, monitored, and replayed independently. Whether the goal is connecting a single lab to an EHR or standing up the integration layer for a national digital health platform, the engineering discipline is the same. The sections below cover the categories of work we deliver most often across hospital, vendor, and payer facing environments.
Bidirectional connections between Epic, Cerner, Meditech, athenahealth, NextGen, eClinicalWorks, or Allscripts and your application. Demographics, orders, results, scheduling, and documents mapped to your internal data model with reconciliation logic.
LIS and RIS connectivity covering order entry, status updates, result delivery, and corrected result handling. We map result value types, abnormal flags, and reference ranges correctly rather than dumping OBX segments downstream.
DFT charge capture, eligibility responses, claim status, and remittance flows into billing and RCM platforms. This is the work we delivered for Coronis Health, connecting HL7 sources into their revenue cycle operation through Mirth Connect.
Vitals, infusion, telemetry, and wearable data ingested from connected medical devices and IoMT endpoints, normalized into observations your clinical systems can store, trend, and alert against reliably.
We place a FHIR façade over existing v2 traffic, exposing R4 resources through Mirth Connect HTTP listeners and supporting FHIR Subscriptions for event driven downstream consumers.
Connections into health information exchanges, national networks, and payer APIs, including the patient access and provider directory patterns advanced by the CARIN Alliance and mandated under CMS interoperability rules.
CCDA generation and consumption, MDM document routing, and DICOM metadata handoff between imaging systems and clinical repositories, with correct patient and encounter identifier resolution on every message.
Mirth Connect’s licensing model changed materially and many teams are still running on assumptions that no longer hold. NextGen moved the engine to a proprietary license beginning with version 4.6 in March 2025, which means organizations upgrading past 4.5.x are making a commercial licensing decision, not a routine version bump. At the same time, a community fork called Open Integration Engine continues the open source lineage under the Mozilla Public License 2.0. We help clients evaluate the three viable paths honestly, including the one where staying on a commercially licensed NextGen build is the right answer.
If you depend on commercial extensions, vendor support, or advanced clustering, licensing with NextGen is often the pragmatic choice. We help you scope license tiers against actual channel volume and support expectations.
OIE forked from the last open source Mirth Connect release and keeps API compatibility, so most channel configurations port with limited rework. We test, migrate, and validate the estate before any production cutover.
Some organizations stay on 4.5.x while they plan. That is defensible short term but not indefinitely, because security patching stops. We document the risk window and build a dated decision path.
We provide the technical facts your legal and procurement teams need. Final license interpretation should be confirmed with NextGen and your own counsel, and we scope engagements to support that review rather than replace it.
A Mirth Connect instance handling PHI is regulated infrastructure, not a middleware utility. The engine ships with sensible defaults, but defaults do not satisfy an auditor asking how encryption keys are stored, who accessed the Administrator console last quarter, or how long message content is retained. We deploy Mirth Connect into AWS, Azure, GCP, or on-premise environments with the controls documented and evidenced. Our team has served 200+ organizations across healthcare software delivery, and security architecture is scoped into the build rather than retrofitted after a risk assessment surfaces gaps.
TLS on every listener and sender, encryption at rest for the message database, network segmentation, and least privilege service accounts. BAAs and shared responsibility boundaries are confirmed before deployment begins.
Clustered or active-passive deployments with health checks, automated failover, and tested recovery procedures. We validate that queued messages survive node loss rather than assuming the documentation is accurate.
Console access logging, channel change history, and message retention windows configured to your policy. Pruning is scheduled deliberately so storage growth stays predictable and legal hold requirements remain satisfiable.
Database credentials, API keys, and certificates moved out of channel scripts and into vault backed resources. Certificate expiry is monitored, because expired TLS certificates cause more interface outages than code defects.
Where data flows to external parties, routing respects patient authorization state. We integrate channel logic with your consent management source of truth so disclosures stay defensible.
Migration work carries the highest risk in the Mirth Connect world, because the old system rarely stops while the new one starts. Interfaces have to run in parallel, message parity has to be proven, and clinical users cannot be the ones who discover a mapping defect. We run migrations with a shadow-and-compare method: the new channels process live traffic without writing downstream, outputs are diffed against the incumbent engine, and cutover only happens when discrepancies reach zero or are documented and accepted by your team.
Rhapsody, Cloverleaf, Iguana, Ensemble, and BizTalk estates rebuilt in Mirth Connect. We reverse engineer undocumented mappings from live message samples rather than trusting interface specifications written years ago.
When the core system changes, every interface changes. Our EHR migration work covers dual-feed periods, identifier remapping, historical data backload, and the decommissioning sequence for retired channels.
Upgrades across Mirth Connect major versions, including Java runtime changes, deprecated connector replacement, and library conflicts in custom-lib. Regression tested against captured production message sets before deployment.
Mature environments accumulate duplicate, dormant, and orphaned channels. We inventory the estate, identify what is actually carrying traffic, and retire the rest with evidence rather than guesswork.
Building an interface is a project. Keeping 80 interfaces running is an operation, and the two require different disciplines. Most integration failures we are called into are not exotic: a trading partner changed a field without notice, a certificate expired, a queue filled because a downstream endpoint went quiet at 3 a.m. Our managed support model covers monitoring, triage, and change work under a defined SLA, so your internal engineers are not the single point of failure. Support can cover an environment we built or one we inherit after a full estate audit.
Message flow, queue depth, error rate, and endpoint availability monitored continuously with thresholds tuned per channel. We detect stalled feeds before the receiving department reports missing data.
Defined severity tiers with response commitments, on-call escalation, and root cause documentation after every Sev1. Recurring incidents get engineering remediation rather than repeated manual restarts.
Channel changes move through version control, a staging environment, and documented approval. Production is never the place where a new transformer is tested for the first time.
We work directly with lab, payer, EHR, and vendor counterparts on specification changes, connectivity testing, and conformance issues, which removes a significant coordination burden from your internal team.
Integration engines are commodity software. The difference between an estate that runs quietly for years and one that consumes an engineer every week is entirely in how it was built. Taction Software was founded in 2013 and our CEO brings 20+ years of personal experience in healthcare technology leadership. We have delivered 500+ software projects and 250+ healthcare and EHR integrations, including production Mirth Connect work for Coronis Health in revenue cycle, Voyant Health, and CHIPSS. We build interoperability infrastructure that your team can own after we hand it over.
We do not build integration layers for logistics or retail. Every engineer on a Mirth Connect engagement works in healthcare data full time and knows what an ORU R01 correction actually means clinically.
Our teams work fluently across HIPAA, the ONC certification criteria, CMS interoperability rules, and information blocking obligations, so architecture decisions account for compliance exposure from the start.
HL7 v2, FHIR R4, CCDA, X12, DICOM, and NCPDP handled by the same team, which matters when a single workflow crosses three standards before it reaches its destination.
Source controlled channels, documented decisions, and direct access to the engineers doing the work. No account manager layer between you and the person who wrote the transformer.
Mirth Connect engagements vary widely in scope, from a single urgent interface build to a multi-facility integration program running across a hospital network. We scope by interface count, standards complexity, environment requirements, and support expectations rather than quoting a flat rate that fits nobody. Fixed-scope work is priced fixed. Ongoing estates run on retainer sized to channel count and SLA tier. Every engagement starts with a paid discovery phase that produces an interface inventory and architecture plan you own outright, whether or not you continue with us.
$40,000 to $80,000. A defined set of interfaces, a single environment, and standard HL7 v2 or FHIR flows. Suitable for digital health vendors connecting to their first health system partners.
$80,000 to $200,000. Multi-environment Mirth Connect deployment, engine migration, FHIR enablement, HA configuration, and full documentation. The typical shape of a platform build or legacy engine replacement.
$200,000 and above. Multi-facility estates, complex payer and HIE connectivity, phased cutover programs, and embedded engineering capacity working alongside your internal integration team.
Priced against active channel count, SLA tier, and after-hours coverage. Available standalone for environments we did not build, following a completed estate audit and remediation plan.
We do not quote integration work from a requirements document alone, because the document and the production traffic almost never match. The first phase is discovery against real messages and real systems, which is where undocumented Z-segments, dormant channels, and quietly failing destinations surface. That assessment is delivered as a written artifact with an interface inventory, architecture recommendation, risk register, and phased delivery plan. You own it regardless of what happens next. Only after that do we commit to a scope, timeline, and fixed price for the build itself.
One to three weeks reviewing existing channels, message samples, trading partner specifications, infrastructure, and compliance posture. Output is a documented inventory and a prioritized findings list.
We define channel topology, error handling standards, naming conventions, environment strategy, and the testing approach. Delivery is sequenced so the highest risk interfaces are proven earliest.
Channels are developed against captured message sets, then run in parallel with existing systems where one exists. Cutover proceeds only when output parity is demonstrated.
Go-live with hypercare coverage, followed by structured handover: runbooks, channel documentation, and working sessions with your engineers so operational ownership genuinely transfers.
Not for new versions. NextGen moved Mirth Connect to a proprietary license beginning with version 4.6 in March 2025. Releases up to 4.5.x remain under the previous open source terms, and the community fork Open Integration Engine continues under the Mozilla Public License 2.0. We help teams assess which path fits their risk and budget position, and we recommend confirming final license terms with NextGen and your own legal counsel.
Mirth Connect handles both. We commonly place a FHIR R4 layer over existing v2 traffic using HTTP listeners, JSON serialization, and resource mapping logic, including support for subscription based delivery to downstream consumers. For high-volume FHIR API workloads, we sometimes recommend a dedicated FHIR server alongside Mirth Connect rather than inside it, and we will tell you when that is the better architecture.
A standard ADT or ORU interface against a cooperative trading partner typically takes two to four weeks including testing. Timelines extend when the partner is slow to provide test environments, when the specification does not match actual message output, or when custom Z-segment handling and complex terminology mapping are involved. Partner responsiveness is usually the largest variable, not engineering effort.
Yes. We start with an estate audit covering channel inventory, error patterns, infrastructure, security configuration, and undocumented logic. That audit produces a remediation list, which we either execute or hand to your team. Managed support begins once the environment reaches a stable, documented baseline, because taking on an SLA for an unknown estate is not fair to either party.
Yes. We build interfaces against Epic Bridges and Interconnect, Oracle Health Cerner, Meditech, athenahealth, NextGen, eClinicalWorks, and Allscripts environments. The technical work is straightforward; the coordination, conformance testing, and connectivity approval processes with each vendor are where experience shortens the timeline meaningfully.
Yes. We deliver structured enablement covering channel development, transformer patterns, error handling standards, deployment practice, and troubleshooting methodology, tailored to your actual estate rather than generic curriculum. Training is included as standard in build engagements and available separately for teams that already run Mirth Connect internally.
Your email address will not be published. Required fields are marked *
Our expert reaches out shortly after receiving your request and analyzing your requirements.
If needed, we sign an NDA to protect your privacy.
We request additional information to better understand and analyze your project.
We schedule a call to discuss your project, goals. and priorities, and provide preliminary feedback.
If you're satisfied, we finalize the agreement and start your project.
