Mirth Connect → MedHook

Your way off Mirth, without a big-bang cutover.

Mirth Connect 4.6 and later are commercial-only, and 4.5.2 was the last open-source release. MedHook reads your existing Mirth server and rebuilds your channels as workflows and your VPNs as GCP tunnels, in your own project.

Plan a migrationSee how channels convert
  1. 01

    Connect

    Point MedHook at your Mirth server. Read-only. Mirth 3.x, 4.x and Open Integration Engine.

  2. 02

    Rebuild

    Channels become workflows. Remote endpoints become tunnels, prefilled from your firewall configs.

  3. 03

    Prove it

    Replay last week's traffic and compare MedHook's output with what Mirth sent, field by field.

  4. 04

    Cut over

    One interface at a time. Each hospital gets a packet. Mirth stays up as the fallback.

This is the strangler fig pattern: MedHook takes over from Mirth one interface at a time while Mirth keeps running. How the strangler fig migration works

What converts

Most channels convert directly. The rest get flagged with a reason and, where it helps, a proposed rewrite.

TCP Listener / Sender (MLLP)MLLP trigger / destination on a tunnelDirect
Filters and mappersFilter and data map stepsDirect
JavaScript transformersSandboxed JS transformDirect
Code template librariesShared transform modulesDirect
Global and channel mapsWorkflow variablesReview
E4X XML scriptsJS rewrite with diffReview
Custom Java / JARsNot supported in the sandboxRebuild
Plain FTPSFTP or Cloud StorageRebuild

Send us a Mirth export.

We'll run it through the converter and walk you through the report.

Talk to us