# Mirth Connect deployment checklist

Engineering review aid, not a vendor certification. Check the documentation and licence for the exact deployed version. Mirth Connect 4.6 introduced commercial licensing.

## Before the change

- Record engine, Java, extension and driver versions.
- Export channels and code templates into version control, excluding credentials and patient data.
- Back up the database and configuration using your environment's documented process; test restore.
- Externalize environment-specific endpoints and secret references. Do not store credentials in channel exports.
- Confirm network access, certificates, identities, minimum permissions and destination contracts.

## Functional and failure tests

- Use synthetic messages representing each supported event and required field.
- Test identifier namespaces, time zones, terminology and missing-value rules.
- Confirm ACK/error behavior and distinguish transient delivery retries from durable error queues.
- Test duplicate delivery and out-of-order messages against agreed business behavior.
- Test a destination outage, restart and replay. Confirm messages are not silently lost.
- Verify logging and monitoring avoid unnecessary patient data.
- Measure queue growth and recovery under representative load; do not invent a throughput target.

## Release and recovery

- Agree the change window, owner, acceptance checks and rollback trigger.
- Preserve the previous configuration and validate rollback before promotion.
- Promote reviewed configuration, verify credentials and connectivity, then run a synthetic smoke test.
- Observe queue depth, failures, acknowledgements and downstream acceptance.
- Record the deployed revision, observations, known limitations and support handover.

Companion guide: https://alabenaicha.me/insights/mirth-connect-channel-architecture