Switch from Mirth Connect to MessageFoundry

How the migration works

Follow the staged engine migration process below for your Mirth channels.

1. List each channel’s source and destination connectors, filters, transformers, and code templates.
2. Recreate each channel as MessageFoundry connections, routers, and handlers. Review and refine any AI-generated translations of JavaScript transformers.
3. Replay representative messages through both engines and compare outputs. Then run MessageFoundry alongside Mirth to check live traffic without cutting over.
4. Move interfaces in waves. Keep Mirth available for rollback until each interface is proven in production.

A Mirth channel that receives over MLLP, filters, and forwards becomes ordinary Python:

from messagefoundry import MLLP, inbound, outbound, router, handler, Send

# Source + destination connectors — wired together by name
inbound("IB_ADT", MLLP(port=2575), router="adt_router")
outbound("OB_EHR", MLLP(host="ehr.internal", port=6000))

# Filter — the Mirth "filter" tab, as a plain function
@router("adt_router")
def route(msg):
    if msg["MSH-9.1"] != "ADT":
        return []          # not ADT -> UNROUTED
    return ["adt_handler"]

# Transformer — review and refine what the AI drafts
@handler("adt_handler")
def handle(msg):
    msg["PID-5.1"] = msg["PID-5.1"].title()
    return Send("OB_EHR", msg)