This view shows the current HealthCloud reference cluster in a landscape layout: horizontal service bands,
clearly separated runtime containers, and the current node footprint on freeos.
It is intended to be intuitive at a glance for CIOs, architects and hosting partners.
Cluster Architecture
HealthCloud Cluster
Application & BI Layer
Healthcare-facing workloads and analytical services
Standards-based clinical API and data access boundary for structured healthcare data.
Dedicated healthcare business intelligence application in its own container, separate from the clinical API layer.
Future Clinical Apps
Examples
Patient portals, virtual care services, EHR adapters and other domain-specific application containers.
Clinical Data Layer
Persistent healthcare data services
Clinical Data Services
Data Core
Persistent structured data, FHIR resources, and controlled access patterns for compliant health workloads.
Integration Layer
Messaging, transformation and streaming
Event backbone for clinical streams, operational feeds and asynchronous data exchange.
Healthcare interface engine for message transformation, routing and interoperability.
Lightweight message queue for service orchestration and operational workloads.
Cloud-native integration runtime for routes, connectors and message choreography.
Platform Services
Identity, GitOps, registry, observability and protection
Node Footprint
Physical or virtual hosts under the HealthCloud cluster
Current reference node hosting the active control plane and worker footprint for the live cluster.
Reserved scale-out node for a broader production topology and higher resilience.