Skip to content
IntuCloud is built on the open-source intu-dev engine — star it on GitHub

Solutions

Using Mirth? Move in minutes.

Your channels are not the problem — the engine underneath them is. Import the channel XML you already have, keep the integration logic, and leave behind the JVM, the ES5 scripting, and the commercial license on clustering.

Get started free Talk to sales

The situation

Why teams start looking.

Channels locked in a GUI

Configuration lives in a GUI backed by a database. Reviewing a change means clicking through it, and there is no meaningful diff.

ES5 Rhino JavaScript

Transformers are written against an old JavaScript runtime with no type checking and no modern tooling.

Clustering costs money

Running more than one node for availability requires a commercial license.

Uncertain direction

Licensing direction has been uncertain enough that a lot of interface teams are building a contingency plan.

Migration

Four steps, in this order.

Nothing here requires a big-bang cutover. Channels move one at a time, at whatever pace your change window allows.

  1. 1 Import

    Upload your channel XML

    The in-app import wizard reads Mirth Connect channel XML and rebuilds each channel as an editable visual pipeline — sources, destinations, filters and transformers land as nodes on the canvas, not as a read-only document. The engine CLI equivalent is intu import mirth when you want to script a bulk migration.

  2. 2 Modernize

    Rhino ES5 becomes TypeScript

    Transformer logic moves from ES5 Rhino JavaScript to real TypeScript with npm type packages and a Monaco editor that tells you when a mapping is wrong before you deploy it. Channel configuration moves from a GUI backed by a database into YAML and files you can review in a pull request.

  3. 3 Test before cutover

    Prove it in the sandbox

    Run the imported channel in an isolated sandbox against captured sample messages. Live traces show the payload at every stage, so you can compare behaviour against the channel still running in Mirth before anything changes hands.

  4. 4 Run anywhere

    Promote, or take it with you

    Promote the channel to IntuCloud staging and production behind deployment gates — or export the project and run it yourself on the open-source intu-dev engine, where Redis-based clustering is included at no cost.

Side by side

Mirth Connect and intu-dev, factually.

Both are capable interface engines. These are the differences that tend to decide the question.

  • Authoring model
    Mirth Connect
    GUI plus a configuration database
    intu-dev / IntuCloud
    Git-native YAML plus TypeScript files
  • Transformer language
    Mirth Connect
    Rhino ES5 JavaScript
    intu-dev / IntuCloud
    TypeScript with npm types
  • Clustering
    Mirth Connect
    Requires a commercial license
    intu-dev / IntuCloud
    Included, Redis-based, in the open-source engine
  • Install footprint
    Mirth Connect
    JVM-based, 500 MB and up
    intu-dev / IntuCloud
    Single Go binary of roughly 20 MB
  • First-party cloud
    Mirth Connect
    None
    intu-dev / IntuCloud
    IntuCloud managed platform
  • Migration path
    Mirth Connect
    —
    intu-dev / IntuCloud
    Channel XML import wizard and intu import mirth
  • License
    Mirth Connect
    Commercial editions available
    intu-dev / IntuCloud
    MPL-2.0 open source

Mirth Connect is a good product that a lot of hospitals have run well for years. The point of this table is not that it is bad — it is that the constraints that came with it in 2010 are no longer constraints you have to accept.

After the move

What you land on.

The connectors you already depend on

HL7 v2 over MLLP, FHIR R4, database readers and writers, SFTP, file drops, SOAP and IHE — 27 connector types across sources and destinations.

Connector catalog

Change control the auditors will accept

Promotion gates with connector preflight, soak windows and named approvals, all recorded in the audit event stream.

Environments & deployments

Operations after cutover

Monitor queue depth, browse messages with an HL7 segment viewer, and reprocess a batch when a downstream system comes back.

Observability

No second lock-in

The engine is MPL-2.0. Export the project and run it on your own infrastructure whenever you want to.

The intu-dev engine

Other solutions

Hospitals & Health Systems Replace an aging interface engine without a rip-and-replace project. HIE Networks IHE profiles, Direct messaging and high fan-out at network scale. Digital Health Vendors Standardize one integration surface across every hospital customer.

Import your first Mirth channel today.

Upload a channel XML on the free plan and see it as an editable pipeline in a few minutes.

Get started free Talk to sales