View all Alchemy Loop products← Alchemy Loop portfolio
Mirth Connect change management
Mirth Commander
Build on TEST. Prove it. Ship it to PROD.
MirthCommander replaces manual channel exports and imports with a reviewed, recorded release: compare what differs, promote only after every check passes, and restore production automatically if anything fails.
Mirth Connect 4.5.2 · TEST and PROD on the same version · MySQL change support · Runs inside your network
RELEASE CONTROLREADY TO PROVE
Dependencies presentPROD backed upRead-back verification
BACKUP→WRITE→READ BACK→DEPLOY→PROVE
The release problem
A manual export is not a controlled release.
TEST and PROD drift, dependencies are missed, and the previous version is often an old export file—if anyone can find it.
Hotfixes and local changes make it hard to know what TEST and PROD actually contain.
A channel can depend on settings, shared code, ports, connected channels and database changes.
A release needs a known before-state and a verified path back to it.
TEST and PROD, side by side
See every difference before it becomes a production change.
Channels follow the same group tree your team uses in Mirth Administrator. Comparisons change nothing.
TESTDIFFERENCEPROD
ADT InboundDestination addedADT Inbound
Claims RouterFilter rule changedClaims Router
Shared code libraryFunction updatedShared code library
Plain-English explanations first. Line-by-line detail when needed. Passwords stay hidden; setting values are never shown.
Promotion gates
One failed check blocks the promotion—and says what to fix.
Before a channel moves, MirthCommander checks both live servers and the dependencies that have to be there for the release to work.
The channel is running cleanly in TEST.
PROD is running what it has saved.
Required settings and shared functions exist in PROD.
Channels it feeds are available.
The required port is free.
TEST and PROD use the same Mirth Connect version.
Tables and columns used by its queries exist in PROD.
Verified deployment
PROD is not simply imported. It is backed up, changed, read back and proven.
- 01Back up PROD
Create an encrypted copy of the current production channel before anything changes.
- 02Write and read back
Write the channel, then read it back to prove PROD holds exactly what TEST has.
- 03Deploy and prove it
Deploy the change and verify the running version is the intended version.
- 04Roll back if needed
If any step fails, restore the prior version and record Mirth's reason.
Database changes follow the same discipline
Versioned MySQL scripts, with a path back.
Compare TEST and PROD database changes—including scripts, tables, columns and lookup data—then promote them with a backup, verification and automatic undo on failure.
CHANGE 024 · READYAdd payer_identifier column
UP: add column · VERIFY: column exists · DOWN: remove column
BACKUP → APPLY → VERIFY → UNDO IF NEEDEDClaude on TEST only
Ask for a channel change in plain English. A person still applies it.
Claude can review a channel, prepare a new one in the right group, or propose a filter change—but it never has access to PROD.
“Add a filter for incomplete patient identifiers.”
Claude prepares the channel or change for review on TEST.
A person approves the change. MirthCommander backs up TEST, writes, reads back and deploys it.
A complete release record
Every production change has a before-state, a proof path and a history.
See the outcome of every required release check.
Keep the complete promotion and rollback sequence.
Retain the encrypted before-state needed for recovery.
Record who made each change and when it happened.
The activity log is hash-chained so tampering is evident.
Product demonstration
Watch a Mirth release become a controlled process.
The demonstration shows MirthCommander comparing TEST and PROD, running release checks, protecting the existing production state and keeping a recoverable record.
Demo duration: 6 minutes 49 seconds.
Coming soon
Independent AI second opinions as advice—not a release gate.
An independent review from Claude and OpenAI is planned for each proposed change. The release checks and a person remain the decision-makers.
MIRTH CONNECT RELEASES, WITHOUT THE SCRAMBLE