What is InteropNimbus?
InteropNimbus is a healthcare interoperability monitoring dashboard that provides a browser-based, real-time operations view into integration engines and FHIR servers. It's designed for healthcare integration teams who manage Mirth Connect channels and HAPI FHIR resources.
The name combines "Interop" (interoperability) with "Nimbus" (a type of cloud) — representing a cloud-native approach to healthcare data exchange monitoring.
The Problem It Solves
Healthcare organizations running Mirth Connect and HAPI FHIR servers need visibility into their integration pipelines. Mirth's built-in administrator UI is a desktop Java application — functional but dated, and not ideal for operations teams who need quick, browser-based access to channel status, message flow, and error monitoring.
InteropNimbus provides:
- Real-time channel monitoring — see which Mirth channels are running, stopped, or erroring at a glance
- Message flow visualization — track HL7, FHIR, and other healthcare messages through integration pipelines
- FHIR resource browsing — query and inspect FHIR resources from connected HAPI FHIR servers
- Role-based access — enterprise SSO via Keycloak with granular permissions
- Operations-first design — built for healthcare IT teams who need fast answers, not admin-level configuration
Series Overview
This series covers the full architecture and implementation of InteropNimbus across 8 posts:
- Post 1 (this post) — Introduction and overview
- Post 2 — Why I built it: the motivation and problem space
- Post 3 — Tech stack deep-dive: React 19, Zustand, Feature-Sliced Design
- Post 4 — Keycloak integration: enterprise SSO with PKCE
- Post 5 — Infrastructure: Docker, Traefik, and Nginx
- Post 6 — Security architecture
- Post 7 — Roadmap: production hardening and scaling plans
- Post 8 — What's next for InteropNimbus
Let's get started.