In the Mirth Connect Administrator, create a new channel and configure the source connector as a TCP Listener on your designated MLLP port; set the mode to MLLP and configure the maximum connections appropriate for your expected message volume
In the source transformer, add JavaScript or drag-and-drop transformer steps to inspect MSH-9 (message type) and set a channel map variable (e.g., msg_type) to drive destination routing
Add multiple destination connectors — for each target system, add a TCP Sender destination configured with that system's MLLP host and port; set each destination's filter to check the channel map variable so only matching message types are forwarded to each destination
Configure the destination transformers for any field-level mapping required — use Mirth's JavaScript transformer with the msg object to access and modify HL7v2 segment fields before forwarding
Set the channel's message storage settings balancing audit requirements against database performance; for high-volume channels consider storing only metadata and errors rather than full message content
Deploy the channel and validate with test messages: use Mirth's Send Message feature in the channel dashboard to inject a test HL7v2 message and inspect the message detail view to confirm correct routing and transformation
Known gotchas
Mirth Connect's JavaScript transformer uses E4X XML syntax for HL7v2 access via the msg object — standard JavaScript XML APIs do not work here; refer to Mirth's HL7v2 template syntax for field access patterns
If a destination connector is down, messages queue locally in Mirth; configure queue behavior (retry interval, maximum retries, rotate on failure) explicitly or Mirth's defaults may cause unexpected behavior under sustained destination outages
Mirth Connect Community Edition does not include enterprise features like clustering or the advanced analytics dashboard; for production deployments requiring high availability, evaluate the NextGen Connect enterprise licensing
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp