Channel Operations

Many Mirth Connect estates are run by one or two interface analysts, often someone who inherited channels they did not build. This engagement puts senior engineers behind that team, billed hourly against an agreed monthly allocation.

What it covers

• Monitoring and alerting: alerts on errored and queued messages, on channels that stop receiving, and on server and database health, routed to people who can act.
• PHI-safe logging and audit: what message content is stored, for how long, who can see it in the Administrator, and what lands in server logs and alert emails.
• Message store and queue growth: storage and pruning settings per channel, database maintenance, and the throughput tuning that keeps queues from backing up.
• Scheduled upgrades of the engine, Java runtime and operating system, tested against the regression harness before they reach production.
• On-call backup for incidents when your analyst is out, with access scoped to least privilege.
• Documentation and knowledge transfer: a living channel inventory, runbooks for the interfaces that page people at night, and pairing sessions so the knowledge stays in your team.

Staff augmentation

If you need hands rather than a project, our engineers join your interface team directly, work your ticket queue and change process, and follow your access and BAA requirements.

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.