Channel Estate Assessment
Know what runs in your engine before you decide
The licensing change put a decision in front of every organisation running a free Mirth Connect 4.x install: buy the commercial license, hold position on the build you have, or migrate the channels to an open fork. None of those is a good decision without knowing what is actually in the engine. This assessment produces that picture and a recommendation.
What we inventory
- Every channel in every environment: source and destination connector types, enabled state, message volume, last deploy, and which upstream and downstream systems it touches.
- Custom code: JavaScript filters and transformers, response transformers, preprocessor and postprocessor scripts, deploy scripts, global scripts and code template libraries, with the ones that reach outside the engine (database calls, file system, Java classes) flagged.
- Extensions and plugins in use, including any commercial extensions, and anything custom-built against the engine's Java APIs.
- Platform: Mirth Connect version per environment, Java runtime, operating system, the backing database for configuration and message storage, message storage and pruning settings, and how deployments and backups actually happen today.
- People and process: who changes channels, how changes are tested, where alerts go, and what is written down.
What we rank
Each channel gets a business-risk rating (what breaks clinically or financially if it stops), a fragility rating (custom code, undocumented behaviour, error history) and a migration-effort rating. Those three numbers are what make the stay, buy or migrate recommendation defensible to a CIO and a compliance officer.
What you get
- A channel inventory you can keep and maintain.
- A license-exposure summary per environment: what version it runs, what the licensing change means for it, and what it costs to stay where it is (security patching, Java and OS support, staff risk).
- A written stay, buy or migrate recommendation, with effort ranges for each path and a proposed sequence.
- A short list of fixes worth doing regardless of the path: alerting gaps, message-store growth, single points of failure.
We are independent of NextGen Healthcare and of the fork sponsors, so the recommendation is about your estate, not about a license we resell. For many estates the cheapest answer is to keep the commercial license and fix the channels; we will say so when it is.
Chartferry is independent. We are not affiliated with, endorsed by, or a reseller of NextGen Healthcare, and we use the name Mirth Connect only to describe the product we work on.