Connect Hub
Check Mirth Connect compatibility before pairing with Connect Hub
Prepare a Mirth Connect pairing with Connect Hub by checking the exact engine build, plugin, permissions, and recovery process.
By Globalesm
Connect Hub gives teams a browser workspace for supported integration engines. If you run Mirth Connect, begin with the installed version and environment rather than assuming a connection package will work across releases. The same preparation applies to Open Integration Engine and BridgeLink.
Inventory the engine
Record the engine name, exact version, deployment environment, and installed extensions. Identify the person who can install and remove a connection plugin. Check the current Connect Hub compatibility list and confirm the package with Globalesm before installing.
Choose the access you need
Write down whether the pilot needs status visibility, channel administration, or access to messages. Start with the minimum level needed for the agreed workflow. Review network access and ownership with the engine administrator, then document who can change the setup.
Verify pairing and recovery
Use a designated test engine where possible. Confirm the expected engine and channel status appear, and test how your team recognizes a disconnected engine. Record the version and approved configuration, along with how to disconnect or update the integration if required.
Put the plan into practice
Tell us about the workflow, environment, and product capabilities you want to evaluate.