Legacy engine → MedHook

Leave your interface engine one interface at a time.

There is no big-bang cutover. We use the strangler fig pattern: the new system grows around the old one and takes over piece by piece until the old one can be removed.

Plan a migrationSee your engine
  1. 01

    Front door

    MedHook sits in front of your legacy engine and forwards every message unchanged over MLLP. Senders re-point to MedHook once and get their ACKs from MedHook.

  2. 02

    Strangle

    Move interfaces one at a time. Each new workflow runs alongside the legacy engine against a test destination, so production never gets a message twice, and is replay-tested on real traffic before it goes live. Any interface can be routed back to the legacy engine from MedHook, without re-pointing senders.

  3. 03

    Retire

    When the last interface has moved, the legacy engine is switched off. For Mirth, workflows can be exported back as Mirth channels for rollback.

From your engine

Every engine below speaks MLLP, so every one can sit behind the MedHook front door. If yours listens on a port per interface, each port gets its own passthrough. Only Mirth has an automated importer today.

Mirth Connect / Open Integration EngineAutomated, read-only importer: connect to the server or upload a channel export, and channels become draft workflows. Replay compares output with what Mirth sent. Workflows export back as Mirth channels.Importer
RhapsodyMLLP front door and strangle. No automated importer: workflows are rebuilt from your interface exports and specs with AI assistance, then dry-run against real messages.No importer
Infor CloverleafMLLP front door and strangle. No automated importer: workflows are rebuilt from your interface exports and specs with AI assistance, then dry-run against real messages.No importer
CorepointMLLP front door and strangle. No automated importer: workflows are rebuilt from your interface exports and specs with AI assistance, then dry-run against real messages.No importer
InterSystems HealthShare Health Connect (Ensemble)MLLP front door and strangle. No automated importer: workflows are rebuilt from your interface exports and specs with AI assistance, then dry-run against real messages.No importer
iNTERFACEWARE IguanaMLLP front door and strangle. No automated importer: workflows are rebuilt from your interface exports and specs with AI assistance, then dry-run against real messages.No importer

Why it's safe

  • Per interface

    Interfaces move one at a time, never all at once.

  • Reversible

    An interface can go back to the legacy engine without re-pointing senders.

  • Replay-tested

    Each interface is replay-tested on real messages before it moves. For Mirth, MedHook compares its output with what Mirth sent, field by field.

  • The legacy engine stays up

    It keeps running until the last interface has moved.

  • Your own cloud project

    MedHook runs in a cloud project you own.

Send us your interface list.

We'll map each interface to a stage and walk you through the plan.

Talk to us