GLOBALESM / CONNECT HUB

Early access

Your interfaces.
In view.
In control.

See which channels need attention. Understand what happened. Give your team the tools to take the next step in a workspace connected to ONE.

Request a pilot Explore plansDownloads

Start with monitoring. Add management when your team is ready.

G
Connect HubIntegration operations
Illustrative data
OVERVIEW

A clear place to start.

Connected
Engines2
Channels24
Needs attention1
Message activityLast hour
Admissions · HL7Receiving and processing
Started
Laboratory resultsQueue threshold reached
Review queue
Your assigned engines. Your permitted actions.
Works withOpen Integration Engine 4.6.0Mirth Connect 4.5.2 · 4.7.0BridgeLink 26.6.1Connect Hub 4.7.0

FROM SIGNAL TO ACTION

See the issue.
Stay with the work.

A channel warning is the beginning of an investigation. Keep the context and the tools close together.

01

Watch your interfaces

Bring engine status, channel activity, queued messages and incidents into a single operational view.

02

Inspect and improve

Work with channel definitions, transformer steps, reference snippets and message templates in the browser.

03

Act with clear access

Use individual or bulk channel controls. Keep engine administration and message access restricted to authorized users.

THE WORKSPACE TODAY

A look inside
Connect Hub.

These screens come from our demo workspace. The engines, channels and numbers in them are made up.

Connect Hub dashboard with a health row for each of two demo engines, messages per hour for each on the same scale, and the channel status table grouped by engine.
DashboardDemo workspace with made-up data
Connect Hub Channel Studio on the Summary tab of a demo channel, laid out like Mirth Edit Channel, with channel tasks and Hub tasks in the left pane.
Channel StudioDemo workspace with made-up data
Connect Hub Test and Debug after a run on a made-up HL7 result message: two transformer steps passed and the destination would send, with the message at the selected step on the right.
Test & DebugDemo workspace with made-up data
Connect Hub Message Browser with a demo ADT message open in the Readable HL7 view: field names next to values and the message structure beside them.
Message BrowserDemo workspace with made-up data
Connect Hub Monitors list with queue, error, stopped-channel and engine-offline rules for two demo engines, two of them breached.
MonitorsDemo workspace with made-up data

ON YOUR ENGINE

The Globalesm Hub
extension.

Connect Hub reaches each engine through a small extension installed on it. Your engine’s administrator decides what our Hub may do there. ONE can give a person less than that, never more.

The engine connects out to our Hub over HTTPS, through your proxy if you use one. No inbound port, no VPN.

See all our products
  • Monitor onlyDefault

    Status and health. No changes.

  • Monitor and manage channels

    Also start, stop, edit and deploy channels, and work with code templates. No messages. Anyone who can edit a channel can change where its messages go.

  • Full access, including messages

    Also read, send and reprocess messages. Messages can hold patient data.

Works with
EngineVersionHow you get the extension
Open Integration Engine4.6.0We send it with your pairing key
Mirth Connect4.5.2, 4.7.0We send it with your pairing key
BridgeLink26.6.1We send it with your pairing key
Connect Hub4.7.0Included in the engine download

Trying Connect Hub 4.7.0? Engine packages for Windows, macOS and Linux, with the Hub extension included, are on our downloads page.

Go to downloads
  • Outbound only. The engine connects out to our Hub over HTTPS. No inbound port is opened for it.
  • Checked and logged on the engine. Each request from our Hub is checked against the level you picked. Requests made by people, and every refusal, go to the engine’s Event log.
  • Backups are opt-in. A daily configuration backup stays off until the engine’s administrator turns it on. It holds channels, code templates, scripts and settings. It never holds messages. Connector passwords inside channel settings are included.
  • One engine user. Our Hub works on the engine as its own user, globalesm-connect. Disconnecting retires that user.

PLANS PER ENGINE

Visibility first.
Room to do more.

Each engine has its own plan, and each plan includes the one before it. The engine’s access level and ONE still decide what each person can do.

Connect

Know each engine is up.

For every engine you connect: whether it is online, and the state of its channels.

FreePer engine
Connect an engine
  • Engine online or offline
  • Channel states
  • Sign-in through ONE

Monitor

Know where to look first.

For teams that need a shared view of channel health and a clear response to incidents.

Per engineAsk for pricing
Discuss monitoring
  • Everything in Connect
  • Dashboard and health signals
  • Monitors, incidents and maintenance windows
  • Alerts by email, Teams or Slack
  • Events: who did what, and why

Pro

Monitoring + changes

Go from finding to fixing.

For integration teams that also change, test and deploy channels from the browser.

Per engineAsk for pricing
Discuss Pro
  • Everything in Monitor
  • Channel Studio and Test & Debug
  • Deploy, start, stop and roll back
  • Messages, with readable HL7
  • Daily configuration backups
  • Add-ons: Channel History, FHIR, DICOM SR

Enterprise

Your security rules on every engine.

For organizations that also need the engine itself locked down to their own standards.

Per engineAsk for pricing
Discuss Enterprise
  • Everything in Pro
  • Add-ons: MFA, user roles, directory sign-in
  • Add-ons: certificates and secrets

Add-ons are in early access. A lapsed plan never stops messages or weakens security; every engine gets 60 days’ grace. Need people too? Managed support adds an integration team, runbooks and agreed response times on top of any plan. No automatic signup or payment is required to inquire.

Compare the plans
IncludedConnectMonitorProEnterprise
Engine online or offline, channel statesIncludedIncludedIncludedIncluded
Dashboard, monitors, incidents and alertsNot includedIncludedIncludedIncluded
Channel Studio, Test & Debug and deploysNot includedNot includedIncludedIncluded
Messages in the Hub and configuration backupsNot includedNot includedIncludedIncluded
Add-ons: Channel History, FHIR, DICOM SRNot includedNot includedEarly accessEarly access
Add-ons: MFA, user roles, directory sign-in, certificates, secretsNot includedNot includedNot includedEarly access

PART OF YOUR ONE WORKDAY

One place to sign in.
The right engines in reach.

Open Connect Hub through ONE’s Interface Monitoring module. Assign viewer, operator or engine-admin access to the specific engines each person needs.

Explore Globalesm ONE
  1. 1

    Sign in through ONE

    Your identity and current permissions are verified.

  2. 2

    Open your workspace

    Only explicitly assigned engines are visible.

  3. 3

    Start with observation

    Enable management after your environment and access have been validated.

BEFORE YOU CONNECT

A few useful
answers.

Your engine keeps running your interfaces. We help you put the right visibility and access around it.

Which engines can I use?

Open Integration Engine 4.6.0, Mirth Connect 4.5.2 and 4.7.0, BridgeLink 26.6.1, and our own Connect Hub 4.7.0. Each extension package is built for one exact engine version. If yours isn’t on the list, tell us the version and we’ll check it before you install anything.

Is Connect Hub generally available?

Connect Hub is in early access. We pair your first engine with you and agree what the Hub may do on it before switching anything on. Connect Hub 4.7.0 engine packages are on our downloads page; during early access they’re signed with a development certificate.

Does monitoring require access to message content?

Routine monitoring uses channel status and counters; it does not automatically collect message payloads. Authorized administration can retrieve messages, attachments and logs on demand. Those views can contain sensitive information, so we agree on access and data handling before enabling them.

Can our engine stay behind a firewall?

Yes. The extension opens one outbound HTTPS connection to our Hub, through your proxy if you use one. You don’t open an inbound port or set up a VPN. Keep the engine’s own management port off the public internet.

How does it work with Globalesm ONE?

The prepared integration opens Connect Hub from ONE’s Interface Monitoring module and uses ONE to verify identity and permissions. Your workspace also has explicit user-to-engine assignments. Activation is part of setup; a ONE account alone does not grant engine access.

Will this replace the integration engine?

No. Your engine continues receiving, transforming and routing messages. Connect Hub provides monitoring and supported browser administration. Existing channel traffic can continue if the management connection is interrupted.

LET’S START WITH YOUR ENVIRONMENT

Make your next incident
easier to understand.

Tell us which engine you use, how many interfaces you run and what your team needs to see.

Request a Connect Hub pilot Please do not include patient information, message payloads or credentials in your inquiry.
Schedule a discovery call