The Gap in Healthcare Integration Tooling
After working with Mirth Connect in production healthcare environments, I noticed a recurring pain point: the tooling gap between integration engineers and operations teams.
Mirth Connect's Administrator is a Java desktop application. It's powerful for building and debugging channels, but it's not designed for operations monitoring. When a channel goes down at 2 AM, the on-call engineer needs to:
- Launch the Mirth Administrator desktop app
- Connect to the server
- Navigate to the channel list
- Find the failing channel
- Drill into the message history
That's too many steps for an incident response workflow.
What Operations Teams Actually Need
From my experience, healthcare operations teams need:
- A browser-based dashboard they can access from any device
- At-a-glance status of all channels — running, stopped, errored
- Quick message inspection — see recent messages, errors, and processing times
- FHIR resource visibility — browse resources on connected FHIR servers
- Proper authentication — enterprise SSO, not shared credentials
Why Build From Scratch?
There are commercial monitoring solutions for Mirth Connect, but they tend to be:
- Expensive — enterprise licensing that doesn't fit smaller teams
- Opinionated — tightly coupled to specific workflows
- Closed-source — no ability to customize or extend
I wanted something that was:
- Open and extensible — React frontend I can customize for any workflow
- Modern — responsive, fast, built with current tools
- Self-hosted — runs alongside existing infrastructure
- Secure — real enterprise auth, not basic auth or API keys
The Design Philosophy
InteropNimbus follows a read-first philosophy. It's primarily a monitoring and inspection tool, not a management tool. It doesn't start/stop channels or modify FHIR resources (yet). This constraint simplifies security and reduces the blast radius of any potential vulnerability.
The frontend is intentionally decoupled from any specific backend. It consumes standard Mirth Connect and HAPI FHIR APIs, which means it can point at any compatible server without custom adapters.