Taction Software — FHIR Integration with Mirth Connect
Free · No call required

Free Mirth Connect Health Check

A senior Mirth engineer reviews your instance and sends you a written report on what's at risk. No cost, no call required, no sales follow-up unless you ask for one.

Part of our Mirth Connect support practice — senior HL7 and FHIR R4 engineers, based in the US.

Reviewed by a senior engineer, not a script. Reply in 48 hours.

What you get

A written 12-point audit report, covering channel health, version and license risk, performance headroom, security and HIPAA gaps, and single points of failure, delivered in 48 hours.

The report tells you:

Channel health

We go through your channels one at a time and record which ones have no error handling, no retry logic, and no alerting. Then we tell you what actually happens when each of those fails — whether the message is queued, dropped silently, or left in an error state nobody is watching. Most teams discover at least one channel where a failure produces no signal anywhere: no email, no dashboard, nothing. The message just stops arriving, and someone downstream notices days later.

Version and license risk

We identify exactly which Mirth or NextGen Connect build you are running, what has changed since it shipped, and which of those changes are security fixes rather than features. Then we map your upgrade path and flag the breaking changes on it — the JavaScript engine differences, the connector behavior changes, the database migration steps that are not reversible. If you are on an unsupported version, you will know what that exposes you to and what the shortest safe route off it looks like.

Performance headroom

Heap allocation measured against your actual workload, database growth rate, message retention and pruning schedule, queue depths, and transformer execution time. From that we estimate how much more volume your current setup will absorb before it degrades — not a generic figure, but one based on your channel count, message sizes, and destination latency. If you are planning to triple throughput next quarter, this is the section that tells you whether that lands or falls over.

Security and HIPAA gaps

TLS versions and cipher suites on every listener and sender, where credentials are stored and whether any of them sit in plaintext, whether your audit log captures the events an investigator would ask for, and — the one that catches most teams — whether PHI is being written into your Mirth logs or error messages. We check this against what auditors currently ask for, not what was acceptable five years ago.

Single points of failure

Backups, replication, and what would genuinely happen if the instance died tonight rather than what the runbook claims. That includes the human single points of failure. If one person understands your interfaces — if the transformer logic lives in their head and nowhere else — that goes in the report, in writing, because it is usually the largest risk in the environment and the hardest one to raise internally without something to point at.

The twelve findings, in order

1

Channel Architecture Review

Are your channels designed for maintainability or did they grow organically into a tangle? We map your current architecture and flag the anti-patterns.

2

Error Handling & Resilience

What happens when an ACK doesn't come back? When a destination is down? When a malformed message arrives? We test your failure paths.

3

Performance Bottlenecks

We look at queue depths, transformer execution time, database round-trips, and threading configuration to identify where throughput is being lost.

4

Java Heap & JVM Tuning

The single most common production issue with Mirth. We check your heap settings against your actual workload and flag tuning opportunities.

5

Database Health

Is your Mirth database growing unbounded? Are you on the right pruning schedule? Is the database itself sized correctly?

6

Security Configuration

TLS versions, cipher suites, certificate management, API authentication, user access controls, and password policies — checked against current HIPAA expectations.

7

PHI Handling & Audit Logging

Where does PHI sit in your message store? Is your audit log capturing the right events? Could you produce evidence for an OCR investigation tomorrow?

8

Monitoring & Alerting

What do you know is broken right now? In most environments we audit, the answer is less than the team thinks. We check what's monitored and what isn't.

9

Disaster Recovery Posture

Backups, replication, RTO/RPO assumptions, documented runbooks. We pressure-test what would actually happen if your Mirth instance died tonight.

10

Upgrade Readiness

Are you on a supported version? What's blocking an upgrade to the latest NextGen Connect release? What breaks if you upgrade?

11

Channel Documentation Score

Could a new engineer take over your channels tomorrow? We rate documentation quality and flag the channels that are bus-factor risks.

12

Cost & Resource Optimization

Are you over-provisioned? Under-provisioned? Running on infrastructure that doesn't fit your workload? We flag the obvious efficiency gains.

What we need from you

Whichever of these you can share: a channel export (XML, PHI-stripped is fine); your Mirth version and deployment details; recent error logs if you have failures.

We can work from partial information. If you can only share the version and a rough description of what is worrying you, we will still tell you what we can — a version number on its own determines which known issues and security fixes apply to you, and that is a useful finding by itself. Nobody gets turned away for sending too little.

Why it's free

Because it's how we show our work. Describing our own expertise on a services page proves nothing — anyone can write that. Handing you a specific written assessment of your own environment proves something, so that is what we do instead.

Most teams who take the health check don't buy anything, and that's fine. The ones who do, buy because the report was specific enough to be useful on its own. That is the entire mechanism; there is no other catch to go looking for.

Who this is for

You inherited a Mirth instance and don't know what's in it

The engineer who built it has left, the documentation is thin or absent, and you are responsible for something you did not design. The report gives you an inventory and a risk ranking — a starting point that does not depend on reverse-engineering the whole thing yourself first.

One person on your team understands the interfaces and you know that's a risk

You already know this is a problem. What you may not have is a written, external assessment saying so in terms a budget holder will act on. That is a large part of what the report turns out to be useful for.

You're about to increase message volume and don't know if the setup will hold

A configuration that is comfortable at fifty thousand messages a day can fall over at half a million. We would rather tell you which component gives out first before the go-live than diagnose it afterwards at 2am.

An auditor asked a question you couldn't answer

Usually about audit logging, PHI handling, or access control. We check the same things auditors check and tell you plainly where the evidence exists and where it does not.

Request the health check

Reviewed by a senior engineer, not a script. Reply in 48 hours.

Reviewed by a senior engineer, not a script. Reply in 48 hours.

Need something faster?If a channel is down right now, don't wait on the health check — send us the error or call +1 307 459 0850.

FAQ

Frequently Asked Questions

Common questions about the Health Check itself.

What is a Mirth Connect health check?
A Mirth Connect health check is a structured review of your Mirth deployment covering channel architecture, error handling, performance, security, HIPAA compliance, and upgrade readiness. Our free version is asynchronous — you send us what you can share, and a senior engineer returns a written 12-point audit report within 48 hours. A 30-minute screen-share is available if you would rather walk us through it, but it is not required.
Is the Mirth Connect health check really free?
Yes, completely free with no obligation. We don't ask for a credit card and we don't follow up with a sales sequence. Some teams who take the audit eventually hire us for paid work, which is why we can afford to give the audit itself away.
Will you try to sell me something on the call?
There doesn't have to be a call at all — the default is a written report and nothing else. If we do speak, we'll mention what we offer only when it's directly relevant to a finding, for example if we spot a HIPAA gap and you ask how to fix it. We won't pitch you unprompted, and we won't follow up the report with a sales sequence. The report is yours whether you ever talk to us again or not.
Do you need access to our Mirth Connect server?
No, and we don't want it. We work entirely from what you choose to send us — a channel export, your version and deployment details, recent error logs. We never request credentials and never connect to your environment. PHI-stripped exports are fine, and we can work from partial information.
How is this different from reading the Mirth Connect documentation?
The documentation tells you what's possible. The audit tells you what's actually happening in your environment, what's wrong with it, and what to do about it. It's the difference between a textbook and a second opinion.
What if our setup is embarrassing?
Every Mirth Connect deployment we've ever audited had issues — including the ones run by engineers who'd been doing this for years. There is no embarrassing setup. There are just setups that have been audited and setups that haven't.
Who performs the Mirth Connect audit?
A senior Mirth Connect engineer with significant production experience. The same engineers who handle paid engagements perform the free audits. Not a sales engineer, not a recent hire.
How long does the Mirth Connect health check take?
Your side takes about five minutes — fill in the form and attach whatever you can share. The written audit report is delivered within 48 hours of your submission. If you choose to add the optional 30-minute screen-share, allow for that on top.
What if I'm not on Mirth Connect yet but I'm evaluating it?
We do pre-deployment architecture reviews too. Submit the form and say so in the description — we'll adjust what we review and tell you what the deployment would actually involve for your use case.
What if I can only share the Mirth version and nothing else?
Then we'll work from that. A version number alone tells us which known issues and security fixes apply to you and what your upgrade path looks like, which is a useful report on its own. The more you can share, the more specific the findings get — but partial information is normal and we don't turn requests away for it.
Do you sign a BAA before we send anything?
We sign BAAs when the engagement requires it, and you're welcome to ask for one before sending anything. In practice most health check submissions don't need one, because PHI-stripped channel exports and configuration files contain no patient data. Strip the exports and the question usually goes away.
What happens after I get the report?
Nothing, unless you ask. The report is yours to keep, share internally, or use to support a budget conversation. There's no sales sequence attached to it. If you want help acting on the findings, our support plans and pricing are public and you can come to us — we won't chase you.