Case Studies

Real Mirth Connect Projects — See How Healthcare Teams Got Integration Right

Every case study below is a real engagement we delivered. Some clients are named with permission. Others are anonymized to protect confidentiality — but the architecture diagrams, message volumes, and outcomes are real. If something here looks like your project, scroll down and book a call. We’ve probably seen your problem before.

Book a Scoping Call See Sprint Packages

Filter by what matters to you

Browse case studies

Real projects, grouped by the kind of work we did, the systems involved, and the type of organization that hired us.

By type of work

MigrationNew IntegrationHIPAA RemediationPerformance OptimizationManaged ServicesFHIR Implementation

By EHR / system

EpicOracle Health (Cerner)athenahealthNextGeneClinicalWorksMeditechAllscriptsCustom Systems

By organization type

HospitalHealth SystemDiagnostic LabHealth-Tech StartupSpecialty ClinicPayer

Featured projects

Featured case studies

Four representative engagements covering migration, new integration, HIPAA remediation, and performance work.

MigrationEpicHospital

How a Regional Health System Cut Iguana License Costs by Migrating 14 Channels to Mirth Connect

Industry: Hospital · 400 beds · Midwest US

The challenge

Annual Iguana renewal had grown to a six-figure line item. The integration team wanted to move to open-source Mirth Connect but had 14 production channels handling ADT, orders, results, and billing — with no documented test plans and no room for downtime.

The result

All 14 channels migrated within 11 weeks. Zero production downtime. License costs eliminated. Engineering team trained on Mirth before go-live.

Channels migrated

0 min

Production downtime

11 weeks

Timeline

Discuss a similar project →

New IntegrationEpicHealth-Tech Startup

How a Health-Tech Startup Shipped Their First Epic Integration in 6 Weeks Without Hiring a Full-Time Integration Engineer

Industry: Health-tech startup · Care coordination platform

The challenge

A Series A startup needed a working Epic integration for their first hospital pilot. They had two backend engineers, no HL7 experience, and a 60-day deadline.

The result

Full ADT and orders integration shipped in 6 weeks. Epic Connection Hub registration completed. Internal team trained to handle ongoing maintenance.

6 weeks

Time to first pilot

ADT + Orders

Integration scope

FTE engineers hired

Discuss a similar project →

HIPAA RemediationMulti-EHRDiagnostic Lab

How a Diagnostic Lab Passed a Surprise HIPAA Audit After a 2-Week Remediation Sprint

Industry: Independent diagnostic lab

The challenge

A routine HIPAA gap assessment turned up critical findings in their Mirth Connect deployment — weak TLS configuration, gaps in audit logging, and PHI sitting in plain text in the message store.

The result

All Critical and High findings remediated in 2 weeks. Audit logging brought to OCR-defensible standard. Lab passed follow-up audit with zero findings.

100%

Critical findings closed

2 weeks

Remediation window

Follow-up audit findings

Discuss a similar project →

Performance OptimizationathenahealthSpecialty Clinic

How a Specialty Clinic Reduced ADT Processing Latency from 4 Seconds to Under 200ms

Industry: Multi-location specialty clinic

The challenge

ADT messages from athena were taking up to 4 seconds to reach downstream systems. The bottleneck was killing real-time scheduling workflows and creating phantom appointments.

The result

Channel architecture redesigned. Throughput increased 20×. Latency reduced from 4s to 180ms p95.

4,000 ms

Latency (p95) before

180 ms

Latency (p95) after

20×

Throughput gain

Discuss a similar project →

How we work — and why these outcomes are reproducible

We don’t run every project the same way, but every project includes the same fundamentals.

Map current state before proposing future state

Every engagement starts with a discovery pass over your channels, message volumes, environments, and the people who maintain them.

Test in staging before touching production

No channel reaches prod until it has run side-by-side with the existing flow against real (or realistic) traffic for the duration we agreed in scope.

Document what we built so your team can maintain it

Channel inventories, runbooks, and architecture diagrams ship with the code. We do not leave you dependent on us.

Measure outcomes against a baseline

We capture before-state metrics during discovery so the after-state can be proven to your CFO, not just claimed in a status email.

If you’ve worked with consultants who skipped any of these steps, you already know why we do them all. For ongoing engagements, see our productized Mirth Connect support packages.

Want results like these?

Most projects start with a 30-minute scoping call. We’ll listen to what you’re trying to do, ask the questions that surface the real complexity, and tell you whether your project is something we’re the right fit for. If we’re not, we’ll tell you who is.

Book a Scoping Call Claim a Free Mirth Health Check

Prefer email? Reach us at info@tactionsoft.com or visit our contact page. We typically reply within 4 business hours.

Don’t see your situation here?

These are featured case studies. We’ve delivered many engagements that aren’t published — either because clients prefer confidentiality, or because the project was straightforward enough that there wasn’t much of a story to tell. If your situation looks different from anything above, book a call anyway. We’ll tell you honestly whether we’ve handled something similar.

Talk to a Solutions Architect →

FAQ

Frequently Asked Questions

What to expect from our case studies and from a first conversation.

Are these real projects?

Yes — every case study on this page describes a real engagement we delivered. Some clients are named with permission. Others are anonymized to protect confidentiality, but the architecture diagrams, message volumes, timelines, and outcomes are real and unmodified.

Why are some clients anonymized?

Healthcare organizations frequently have confidentiality clauses in their vendor agreements, or simply prefer not to publicize their integration partners. Anonymization is at the client's request. Where a client has approved being named, we use the real name; where they haven't, we describe them by size, region, and EHR.

Can I talk to one of your past clients before signing?

Yes. Once a scoping call confirms a likely fit, we'll connect you with a reference client whose project most closely matches yours. Most prospective buyers find a 20-minute peer-to-peer reference call more useful than any written case study.

My situation isn't shown here — does that mean you can't help?

Not at all. The case studies on this page are featured engagements with publishable detail. We have delivered many engagements that aren't published — either because clients prefer confidentiality, or because the project was straightforward and didn't produce a story worth writing up. Book a scoping call and we'll tell you honestly whether we've handled something similar.

How do these projects translate into a package I can buy?

Every project on this page maps onto one of our productized offerings. Migrations map to the Iguana, Rhapsody, or Corepoint migration sprints. New EHR integrations map to the FHIR R4 Adapter Sprint or a custom sprint. HIPAA work maps to the HIPAA Audit + Remediation Sprint. Ongoing operations map to Bronze, Silver, or Gold managed support. See the full catalog on the integrations and support hubs.

Senior US-based Mirth Connect engineers · HIPAA-trained, BAA available · Trusted by hospitals, labs, and health-tech teams across North America. Built by Taction Software.