For Current Mirth Connect Users

Mirth is now paid.
The question is: what comes next?

Since NextGen closed Mirth Connect's open-source path in March 2025, organizations face a clear choice: pay for a self-managed toolkit, freeze on v4.5.2, or move to a managed platform. intely.io gives you a third option — or a bridge to get there.

Book a 30-min Assessment See Your Options ↓

Flexible by Design

Two ways intely.io fits your roadmap

You don't have to choose between protecting your existing Mirth investment and moving to a modern platform. intely.io works both ways — on your schedule.

Option A

Complement

Keep Mirth on your existing HL7 channels. Bring intely.io in alongside for AI, FHIR, and new hospital connections.

No disruption to existing Mirth channels
AI and FHIR workloads on intely.io immediately
Relay agent — new sites live in days, no VPN
We build and manage the new layer
Pay only for new connections added

Option B

Migrate Over Time

Move channels from Mirth to intely.io in phases — by hospital or use case — with zero downtime and full parallel validation.

Parallel build — Mirth stays live throughout
Validate each interface; nothing goes dark
Typical full migration: 4–8 weeks per scope
Gain FHIR, 99.9% SLA, and managed ops
Flat monthly pricing by connection count

The March 2025 licensing change: NextGen closed the open-source path at v4.5.2. New versions (4.6+) require a commercial license. Organizations staying on 4.5.2 receive no security patches or updates going forward.

Complementing Mirth

What intely.io handles while Mirth keeps running

Think of intely.io as the modern layer alongside Mirth — handling the workflows it was never designed for.

AI Application Connectivity

SUKI and Nuance DAX integrate via FHIR APIs, not HL7 v2. Mirth's channel model requires custom transforms to bridge that gap. On intely.io, FHIR-based AI connectivity is native.

New Hospital Connections

Custom HL7 interface builds routinely run 40–80 contractor hours per connection. intely.io's relay agent brings new hospital sites live in days — no VPN negotiation required.

FHIR R4 & Smart Apps

FHIR R4 Smart App Launch, multi-EMR orchestration, and ADT event triggers are native. Let Mirth route legacy HL7 v2 while intely handles the FHIR layer.

HL7 Spec Change Management

When a partner updates their HL7 spec, Mirth requires your team to scramble. On intely.io, spec changes are absorbed by our managed service.

Real-Time ADT Events

Admission, discharge, and transfer events need sub-second routing. intely.io's event-driven architecture handles this natively — no MLLP tuning required.

24/7 Managed Operations

Interface failures on self-managed Mirth require your team to respond. On intely.io, our ops team owns uptime — 99.9% SLA, proactive monitoring, and incident response included.

AI is the New Integration Layer

Modern workflows Mirth wasn't built for

Mirth's channel architecture requires custom JavaScript transforms and manual MLLP tuning for every AI workflow. On intely.io, these are configured — not built from scratch.

SUKI Ambient AI Documentation

Nuance DAX Clinical Notes

Epic-to-AI Model Data Pipelines

Real-Time ADT Event Triggers

FHIR R4 Smart App Launch

Multi-EMR Orchestration

Bidirectional EHR Connectivity

Clinical Decision Support APIs

The gap: AI tools like SUKI and Nuance DAX connect via FHIR APIs. Mirth was designed for HL7 v2 channels. Bridging them requires custom JavaScript transforms in Mirth — or native FHIR support in intely.io.

Full Cost Comparison

What you're actually paying on Mirth

Cost Factor	Mirth (Commercial)	intely.io
License	Annual commercial license (3 tiers)	Flat monthly by connection count
New hospital connection	40–80 contractor hrs @ $150–250/hr	$0 — our team builds it
HL7 spec change	Your team's burden to remap channels	Managed service absorbs it
AI/FHIR workflow	Custom JS transforms per workflow	Platform-native; no custom code
VPN per hospital site	Hospital IT coordination required	Relay agent — no VPN needed
Interface failure at 2am	Your on-call team's problem	99.9% SLA — our problem

When You're Ready to Migrate

Migration in four steps — your team does none of the HL7 work

Whether you migrate now or in 18 months: parallel build, validated cutover, zero disruption. We own the interface layer from day one.

01	Audit & Inventory We map every Mirth channel, document each interface, and identify the hospital systems, protocols, and data flows in scope — with timeline estimates before we write a single line of config. Channel mapping · Protocol inventory · Scope definition
02	Parallel Build Our team rebuilds each interface on intely.io while your Mirth channels stay live. Zero disruption to operations — your patients and clinicians never notice. Zero downtime · Mirth stays live · Intely team builds
03	Parallel Testing & UAT Both systems process the same messages simultaneously. Data accuracy checks, completeness validation, and timing comparisons run until your team signs off. Parallel processing · Data accuracy checks · Your sign-off required
04	Clean Cutover & Decommission Cutover on a date you control. Mirth decommissioned. Your team never touches the interface layer again — we own operations, monitoring, and incident response 24/7. You set the date · 99.9% SLA · Fully managed ops

Customer Spotlight

"intely.io cut our manual integration work by 80% and let us onboard new hospital clients 50% faster. We went from building integrations to deploying them."

— VP of Technology, HOPCo · 900+ orthopedic providers nationwide

80%

Less manual integration work

50%

Faster hospital client onboarding

20%

Improvement in data integrity

Common Questions

What teams ask before they start

QCan we use intely.io without migrating off Mirth?

Yes — Option A is the most common starting point. Deploy intely.io for new connections, AI/FHIR workflows, and modern integrations while Mirth keeps running your existing channels.

QWhat happens to our existing Mirth channels?

We rebuild every channel in parallel on intely.io. Your Mirth channels stay live until we've validated the new connections and your team signs off. Nothing goes dark.

QHow long does a full migration take?

Typically 4–8 weeks per scope depending on number of interfaces and EHR systems. The more standardized your current Mirth config, the faster we move.

QDo we lose any functionality by migrating?

No — you gain: native FHIR R4 support, the relay agent (no more VPNs), AI workflow readiness, and 24/7 managed ops. The only thing you lose is the maintenance burden.

QWhat exactly changed with Mirth's licensing in March 2025?

NextGen closed the open-source path at v4.5.2. New versions (4.6+) require a commercial license. Organizations on 4.5.2 can stay, but receive no security patches or updates going forward.

QWhat does flat monthly pricing mean?

A predictable fee based on connection count — no per-transaction fees, no volume surprises. Makes total cost transparent as your integration footprint grows.

Mirth is now paid.The question is: what comes next?