What standards does ClinicalSpan support?

ClinicalSpan supports HL7 v2.1 through v2.8, FHIR R4 output, REST APIs, TCP/MLLP, SFTP, file-based workflows, and database connections. Mapping profiles support HL7-to-HL7 and bidirectional HL7/JSON transformations.

Can we keep processing in our own environment?

Yes. On-premises deployment runs in your datacenter or private cloud. A hybrid option combines a SaaS control plane with on-premises processing. Review data flows and infrastructure requirements with the team before choosing a deployment.

How does ClinicalSpan handle security and PHI?

The platform provides encrypted archives, TLS connections, role-based access, audit trails, and configurable PHI retention and scrubbing. Its architecture is described as HIPAA-aligned, with an Enterprise BAA available on request. Discuss your organization's requirements during the security review.

How is ClinicalSpan priced?

Contact the team for a quote for your integration scope. Share your interface count, expected message volume, deployment requirements, and support needs. These details help frame the pricing conversation.

How long does implementation take?

Timing depends on interface complexity, mapping requirements, access to source and destination systems, and testing. A personalized demo is the starting point for discussing your use case and an implementation plan.

MIRTH CONNECT ALTERNATIVE

Moving off Mirth Connect 4.5.2? Compare your options.

Q: Is ClinicalSpan an alternative to Mirth Connect?

ClinicalSpan is an option for teams evaluating a different healthcare integration engine. Review your existing channels, transformations, scripts, and deployment requirements with our team to assess migration scope and compatibility.

Since version 4.6, Mirth Connect is available only under a commercial license. If your interfaces still run on 4.5.2, you have four realistic paths. Here's an honest comparison, including when ClinicalSpan is not the right choice.

Book a free migration assessment Jump to the comparison ↓

Last reviewed: November 2026

LICENSING SHIFT

What changed, and why it matters

On March 19, 2025, NextGen Healthcare announced ↗ that Mirth Connect would move from a dual open-source and commercial model to a single commercial license, starting with version 4.6.

Final OSS Release

Version 4.5.2

The last release under the open-source Mozilla Public License. No further core or community patches are published by NextGen on this branch.

Commercial License

Version 4.6 and Later

Available exclusively under commercial license agreements (Enterprise, Gold, or Platinum tiers) priced and contracted directly with NextGen.

Security & Fixes

New Releases

All upcoming feature releases, CVE vulnerability patches, and compliance updates now ship strictly under the commercial license.

For teams running 4.5.2, that means interfaces carrying patient data are on a version that no longer receives updates. Nothing breaks overnight, but the security and compliance risk grows with every month.

The community responded with open-source forks of 4.5.2, including Open Integration Engine (OIE) and BridgeLink. Both can import existing Mirth channels.

OBJECTIVE EVALUATION

Four paths, side by side

Every option below is a legitimate choice. The right one depends on your team, your budget and how many interfaces you run.

Criterion	Stay on Mirth 4.5.2	Move to an open-source fork (OIE, BridgeLink)	License Mirth 4.6+	Modern Alternative Switch to ClinicalSpan
License cost	Free	Free; paid support available from partners	Commercial license, quoted by NextGen	Quoted per scope: interfaces, volume, deployment and support
Security updates	None from NextGen	From the fork's community and maintainers	From NextGen	From ClinicalSpan
Existing Mirth channels	Keep as they are	Import directly	Upgrade in place	Reconfigured in a drag-and-drop UI, about 2–3 minutes per channel
Who you call for support	Your own team	Community or a paid partner	NextGen	ClinicalSpan
Mapping approach	JavaScript transformers per channel	JavaScript transformers per channel	JavaScript transformers per channel	Reusable mapping profiles, code translation and lookup tables
HL7 and FHIR	HL7 v2; FHIR through custom work	Same as 4.5.2, plus fork improvements	HL7 v2 and FHIR, per NextGen's tiers	HL7 v2.1–v2.8 and FHIR R4 output
PHI controls	Configure yourself	Configure yourself	Per NextGen's tiers	PHI scrubbing, retention windows, role-based access, AES-256 archives, TLS 1.2/1.3
Deployment	Self-hosted	Self-hosted	Self-hosted; some NextGen tooling not available in the EU or UK	Cloud, on-premises or hybrid
Migration effort	None now; grows later	Low	Low	About 2–3 hours to configure 10–20 channels, plus testing
BAA available	Not applicable	Depends on partner	Ask NextGen	Yes, on request

Option 1

Stay on Mirth 4.5.2

License cost: Free
Security updates: None from NextGen
Existing Mirth channels: Keep as they are
Who you call for support: Your own team
Mapping approach: JavaScript transformers per channel
HL7 and FHIR: HL7 v2; FHIR through custom work
PHI controls: Configure yourself
Deployment: Self-hosted
Migration effort: None now; grows later
BAA available: Not applicable

Option 2

Move to an open-source fork (OIE, BridgeLink)

License cost: Free; paid support available from partners
Security updates: From the fork's community and maintainers
Existing Mirth channels: Import directly
Who you call for support: Community or a paid partner
Mapping approach: JavaScript transformers per channel
HL7 and FHIR: Same as 4.5.2, plus fork improvements
PHI controls: Configure yourself
Deployment: Self-hosted
Migration effort: Low
BAA available: Depends on partner

Option 3

License Mirth 4.6+

License cost: Commercial license, quoted by NextGen
Security updates: From NextGen
Existing Mirth channels: Upgrade in place
Who you call for support: NextGen
Mapping approach: JavaScript transformers per channel
HL7 and FHIR: HL7 v2 and FHIR, per NextGen's tiers
PHI controls: Per NextGen's tiers
Deployment: Self-hosted; some NextGen tooling not available in the EU or UK
Migration effort: Low
BAA available: Ask NextGen

Recommended Path

Switch to ClinicalSpan

License cost: Quoted per scope: interfaces, volume, deployment and support
Security updates: From ClinicalSpan
Existing Mirth channels: Reconfigured in a drag-and-drop UI, about 2–3 minutes per channel
Who you call for support: ClinicalSpan
Mapping approach: Reusable mapping profiles, code translation and lookup tables
HL7 and FHIR: HL7 v2.1–v2.8 and FHIR R4 output
PHI controls: PHI scrubbing, retention windows, role-based access, AES-256 archives, TLS 1.2/1.3
Deployment: Cloud, on-premises or hybrid
Migration effort: About 2–3 hours to configure 10–20 channels, plus testing
BAA available: Yes, on request

RECOMMENDED APPROACH

Which path fits your team?

Stay on 4.5.2 for now if

you run a few low-risk interfaces and have a migration already planned for the next few months.
Just don't leave it open-ended. Unpatched software carrying PHI becomes harder to justify in every audit.

Move to an open-source fork if

your team is comfortable maintaining Mirth-style channels and JavaScript transformers.
you want to keep existing channels with the least change, and you're happy relying on community or partner support.

License Mirth 4.6+ if

you're heavily invested in Mirth, your channels are complex, and you want to stay with the original vendor.
the license cost fits your budget.

Consider ClinicalSpan if

you're planning to rebuild or clean up interfaces anyway, and want reusable mappings instead of per-channel scripts.
you need HL7 v2 and FHIR R4 output from one platform.
you want monitoring, encrypted archives, message resend and PHI controls built in, rather than assembled.
you'd prefer a hosted or hybrid option, so your team doesn't have to run the infrastructure.

MODERN ARCHITECTURE

What changes when you move to ClinicalSpan

Mappings you reuse

Build a mapping profile once and apply it across channels, with code translation and lookup tables instead of per-channel scripts.

Know where every message went

Trace message events, get alerts on failures, search the encrypted archive and resend single messages or failed batches.

PHI controls built in

Scrubbing rules, retention windows, role-based access, AES-256 archives and TLS 1.2/1.3. Enterprise BAA available on request.

Run it where you need it

Cloud, on-premises or hybrid, so processing stays within your data-residency and governance requirements.

STEP-BY-STEP TRANSITION

How a migration works

Inventory

You share your channel list, message types, connectors and volumes. No patient data needed.

Assessment

We map each channel to ClinicalSpan and flag what moves easily, what needs rework, and what to retire.

Pilot

We migrate one channel end to end and run it alongside Mirth, so you can compare output before switching.

Cutover

Channels move in planned batches, each with its own rollback point.

Fast visual configuration: Channels are set up in ClinicalSpan's visual, drag-and-drop interface, with no scripting. Each channel takes about 2–3 minutes to configure, so a typical set of 10–20 channels takes 2–3 hours.

Flexible resourcing: Your team can configure channels themselves, or ClinicalSpan's team can do it for you. Or start with us configuring the first few channels, then take over.

FREQUENTLY ASKED QUESTIONS

Questions about leaving Mirth

Is Mirth Connect still free?

Version 4.5.2 and earlier remain available under their original open-source license. Version 4.6 and later require a commercial license from NextGen Healthcare.

Is it safe to keep running Mirth 4.5.2?

It still runs, but it no longer receives updates from NextGen. For interfaces that carry patient data, unpatched software becomes a growing security and compliance risk. Most teams treat staying on 4.5.2 as temporary.

What are the open-source forks of Mirth Connect?

The best-known are Open Integration Engine (OIE) and BridgeLink. Both are based on Mirth 4.5.2 and can import existing Mirth channels.

Is ClinicalSpan an alternative to Mirth Connect?

Yes. ClinicalSpan is a healthcare integration platform that handles HL7 v2.1–v2.8, FHIR R4 output, REST APIs, MLLP/TCP, SFTP and databases, with channel-based routing, reusable mapping profiles, monitoring and message resend.

Can ClinicalSpan import my Mirth channels?

Channels aren't imported as files. Instead, each one is set up in ClinicalSpan's drag-and-drop interface, with no scripting, which takes about 2–3 minutes per channel. A typical set of 10–20 channels takes 2–3 hours to configure, and each channel is then tested against your sample messages before cutover.

Who configures the channels during a migration?

Your choice. Your own team can set up channels in ClinicalSpan's drag-and-drop interface, or ClinicalSpan's team can configure them for you. You can also mix the two: we configure the first few channels, and your team handles the rest.

Can we keep data processing on our own servers?

Yes. ClinicalSpan can run in the cloud, on-premises, or in a hybrid model with a hosted control plane and on-premises processing.

Do you sign a BAA?

Yes. An enterprise BAA is available on request.

TRANSITION PLANNING

Get a free Mirth migration assessment

Share your channel list, message types and volumes. We'll tell you what moves easily, what needs rework, and which path makes sense for your team, even if that isn't ClinicalSpan. No patient data needed.

Book your assessment