Free Mirth Connect Health Check: What to Expect in Your 60-Minute Audit

If you have ever asked yourself any of the following questions, the Health Check exists to answer them:

• “Is our Mirth Connect deployment in good shape, or are we sitting on hidden problems?”
• “Our previous integration engineer left. What's the state of what they built?”
• “We've never had an outside review. What would a senior engineer find?”
• “We have a compliance audit coming. Are we ready?”
• “Performance has been degrading. What's causing it?”
• “How much would it cost to fix what's wrong?”

The Health Check is designed to answer these specifically, in 60 focused minutes plus a written report. No vague consulting deliverable. No sales pitch dressed up as a discovery call. A senior engineer reviews your deployment, names what's broken (or confirms what's healthy), and tells you what fixing it would cost in our productized sprint or support packages — or whether you can fix it in-house.

For complete context on our pricing and offerings, see the pricing page and our support services guide. The fastest path to claim is the service page itself: Free Mirth Health Check.

The Free Mirth Health Check has a specific, bounded scope.

What it is:

• One 60-minute call with a senior Mirth Connect engineer (US-based architect)
• Structured walkthrough of your current Mirth deployment following our internal audit checklist
• Live Q&A so you can ask anything specific to your situation
• Written report delivered 2–4 business days after the call, with prioritized findings and ballpark effort estimates
• Free for qualifying organizations — no credit card, no commitment, no obligation to purchase afterward

What it is not:

• Not a sales call in disguise. The senior engineer leading it is the same person who would lead the engagement if you became a client — not a sales rep.
• Not a full HIPAA audit. That's a HIPAA Audit + Remediation Sprint, which is paid and substantially deeper.
• Not hands-on remediation. The Health Check identifies issues; remediation happens in subsequent sprint or support engagements.
• Not unlimited. It's 60 minutes plus a written report — that's the entire scope.

What you get out of it:a senior engineer's outside perspective on your deployment, documented in writing, free. Whether or not you ever work with us afterward, the written report is yours to keep.

The Health Check is free for qualifying organizations. What that means:

Qualifying:

• Production Mirth Connect deployment (or a pre-production deployment about to go live) carrying real HL7 or FHIR traffic
• US-based healthcare organization — hospitals, health systems, ambulatory networks, healthtech platforms, HIEs, labs, payers
• Decision-maker on the call — IT director, CTO, VP Engineering, integration team lead, or a delegate empowered to evaluate professional support
• Realistic budget context — your organization has at least an engineering operations budget that could accommodate $3,800/mo (Bronze tier floor) if you decided to engage afterward

Not qualifying:

• No Mirth deployment yet — you're researching whether to use Mirth Connect. (For this, the Mirth Connect complete guide and our comparison pages are better starting points.)
• Student / academic / personal projects — non-commercial use cases don't fit our service model
• Vendor evaluation only — organizations evaluating us against other vendors purely for procurement comparison are better served by the pricing page and a direct sales call rather than the Health Check
• Outside the US — our compliance posture (BAA, HIPAA, state regulations) is US-specific; non-US healthcare contexts have different regulatory needs

If you're not sure whether you qualify, request the Health Check anyway — we'll confirm fit on the intake form and either schedule the call or redirect you to better-fitting resources.

The 60-minute walkthrough follows our internal audit checklist, structured into five areas. The depth on each varies based on what your deployment surfaces.

3.1 Channel inventory and architecture (10–15 min):

• How many channels are deployed and what each does
• Source and destination systems per channel
• Message types and volumes
• Multi-tenant patterns (if applicable)
• HA architecture (if any)

3.2 Performance posture (10–15 min):

• JVM configuration — heap size, GC settings
• Database choice and configuration
• Queue depth and channel state patterns
• Recent incident history (any heap exhaustion, MLLP drops, channel stops?)

For technical context on performance, see Mirth Connect performance tuning and database configuration.

3.3 HIPAA and security baseline (10–15 min):

• TLS posture on MLLP listeners and senders
• Certificate inventory and expiration calendar
• Audit logging completeness
• Access control matrix (or lack thereof)
• Credential management hygiene
• BAA chain coverage

For the deeper compliance perspective, see HIPAA compliance for integration engineers.

3.4 Operational readiness (10 min):

• On-call rotation and response capability
• Runbook documentation maturity
• Monitoring and alerting coverage
• Backup and disaster recovery posture
• Change management discipline

3.5 Open Q&A (5–10 min):your specific concerns, anything we didn't cover, or deeper-dive on a finding that surfaced during the audit.

The report is delivered 2–4 business days after the call. Structure:

Findings summary. A concise overview — typically a single page — summarizing the overall health rating and the top 3–5 findings.

Prioritized findings list. Each finding categorized by severity:

• P1 — Critical: Active risk to production, breach exposure, or imminent failure. Fix within days.
• P2 — High: Significant gaps that should be remediated in weeks, not months.
• P3 — Medium: Best-practice gaps that improve posture but aren't strictly urgent.

For each finding: what we found, why it matters, recommended remediation approach, and a ballpark effort estimate (in days or weeks).

Remediation pathways. Where each finding sits relative to our productized offerings:

• Sprint-scoped fixes: mapped to specific sprint packages with public pricing
• Operations-scoped fixes: mapped to Bronze, Silver, Gold, or Enterprise tiers
• In-house-fixable: clear enough that your team can do it without outside help, with pointers to documentation

Optional next-step recommendation.If we identify a clear best-next-step (typically a sprint engagement or a support tier), we'll name it explicitly with the relevant pricing — but only as a recommendation, never as a commitment.

Across hundreds of Health Checks across US healthcare organizations, the same patterns appear repeatedly. The ten findings we see most often:

1. No retention or pruning policy. Mirth's database grows aggressively without active pruning. The single most common finding — production databases growing into hundreds of GB, with no archival or deletion strategy. See Mirth Connect database configuration for the technical detail.
2. Inconsistent TLS posture. Some channels use TLS, some don't. “Internal network” rationalizations that don't survive HIPAA audit scrutiny.
3. Inadequate audit logging. Mirth logs message processing but not admin actions at a HIPAA-grade level. Auditors can't see who deployed what when.
4. Shared admin accounts. Single admin login used by the entire integration team. No attribution of changes to individuals.
5. No documented access control matrix. “Who has access to Mirth admin?” answered with shrugs rather than written documentation.
6. Plaintext credentials in configuration. Database passwords, SFTP keys, API tokens in mirth.properties or channel configurations as plaintext.
7. Missing on-call rotation. Single engineer handles all incidents. No documented escalation. No coverage during vacations or sick days. Burnout precursor.
8. No recent backup verification. Backups exist but haven't been test-restored in 6+ months. Backups that haven't been verified aren't backups — they're files.
9. Outdated patching. Mirth, JVM, database, or OS running on unsupported or unpatched versions. CVEs sitting unaddressed.
10. Missing or weak BAA chain. BAAs in place with hospital customers but missing for vendors handling PHI (monitoring, support, cloud provider, etc.). Common audit finding.

If 3+ of these patterns describe your deployment, you have material risk that's worth addressing. The Health Check tells you which ones apply and what fixing them would cost in our productized packages.

Three typical outcomes:

Outcome A — Sprint engagement (most common). The Health Check identifies a specific bounded project — install hardening, FHIR adapter build, eClinicalWorks $export setup, HIPAA remediation, engine migration. You engage one of our productized sprints with public pricing and a fixed timeline.

The most common sprint paths after a Health Check:

• Mirth Installation Sprint — from $4,500 for net-new deployments
• HIPAA Audit + Remediation Sprint for compliance-driven findings
• FHIR R4 Adapter Sprint — from $13,500 for FHIR capability additions
• Engine Migration Sprint — from $34,500 for cross-platform migrations
• eClinicalWorks $export Sprint — from $13,500 for eCW bulk-data integrations

Outcome B — Ongoing support engagement. The Health Check reveals operational coverage gaps — single-engineer dependency, no 24/7 capability, missing on-call, etc. You engage one of our support tiers:

• Bronze — $3,800/mo for small clinics
• Silver — $6,800/mo for production deployments (most common)
• Gold — $12,500/mo for hospital networks
• Enterprise — from $28,000/mo for IDNs and Fortune 500

Outcome C — In-house remediation. The Health Check confirms your team can handle the findings without outside help. We leave you with the report and pointers to relevant documentation. No engagement, no further obligation, no sales follow-up.

This is a real outcome.Roughly 20–30% of Health Checks end here, and that's fine. The Health Check filters good-fit prospects from poor-fit prospects efficiently for both sides.

Combined outcomes. When the Health Check identifies both project work and ongoing operational needs, the typical path combines a sprint engagement with a follow-on support tier — with our automatic 10% discount on the first month of support for sprint clients.

This question gets asked frequently enough to answer directly.

Efficient filtering. The Health Check identifies fit fast. Organizations with real needs and budget become clients; organizations without either save us a longer sales process. Both sides save time.

Trust signaling.Hospital procurement and healthcare CTOs evaluate dozens of integration vendors per year. Vendors who lead with a free, deliverable-producing engagement signal confidence in their work — vendors who require paid discovery often have weaker substance to lead with. Free Health Check is our “let our work speak for itself” mechanism.

Self-qualification. By the time a Health Check is complete and the report delivered, both parties have enough information to know whether to engage further. The lengthy back-and-forth of typical enterprise sales cycles compresses into one focused interaction plus a written deliverable.

Brand consistency.Our brand position is “All Numbers Public — most healthcare consultancies hide pricing; we don't.” Offering a free, scoped, deliverable-producing first engagement is the operational expression of that same transparency.

The Free Mirth Health Check is genuinely free for qualifying organizations. There is no hidden charge, no automatic enrollment, no follow-on commitment.

The call is most useful when the right people attend and you can speak to your deployment. To get maximum value:

Before the call:

• Confirm the right attendees: someone with Mirth admin access who can describe channels in detail, plus an executive sponsor who can act on findings
• Pull a channel inventory if you have one (or be prepared to walk through the live admin console)
• Note recent incidents — last 6 months of significant production issues
• Identify your top 2–3 concerns so we can prioritize coverage during the 60 minutes

Things we'll ask about:

• Current Mirth version and deployment topology
• Database choice and rough size
• Number of channels and their general purposes
• Recent incidents or chronic problems
• Compliance context (any active audits, hospital security reviews, certifications in progress)
• What prompted you to schedule the Health Check

What you don't need:

• You don't need admin access prepared in advance — we work from your team's screen-share during the call, not direct access
• You don't need to prepare a presentation — the structure is our checklist, not a formal deliverable from your side
• You don't need to have answers ready for everything — “I don't know” is a valid finding (and often itself a P2)

Three steps:

1. Submit the intake form at /support/mirth-health-check. Brief — takes 3–4 minutes.
2. We confirm fit and schedule. Typically within 1 business day. If you don't qualify, we'll redirect you to the appropriate resource (typically a comparison page, the pricing page, or a sales-call form).
3. 60-minute call + written report. The call happens within 1–2 weeks of scheduling. The report follows 2–4 business days after.

No credit card. No commitment. No obligation. Whether you ever work with us afterward, the report is yours to keep — a senior engineer's outside perspective on your Mirth Connect deployment, documented in writing, free. Most engagements with us start here, and the same engineer who runs the audit is the one who would lead the follow-on engagement.

Claim My Free Mirth Health Check →

If you already know which package you need, you can also go directly to Bronze ($3,800/mo), Silver ($6,800/mo), Gold ($12,500/mo), Enterprise (from $28,000/mo), or our integration sprints. The complete Mirth Connect support catalog is open at /pricing.