One architecture. From a single clinic to a sovereign nation.

A single-facility deployment runs HealthOS for one hospital, specialty institution, or clinic on a single-tenant architecture. The full four-layer environment — Clinical, Nursing, Operations, Financial — plus the Patient Platform and Clinical Reasoning Layer operate at the smallest institutional unit. Operational go-live in one to two weeks; clinical cutover phased thereafter.

A hospital-network deployment runs HealthOS across a chain of facilities operating under one institutional governance — multi-site hospital groups, academic health systems, private hospital chains. Federated identity, shared records across facilities, network-level operations and financial visibility. Deployment timeline six to ten weeks per facility wave.

A regional deployment runs HealthOS across hospitals, clinics, and community providers within a defined geographic region — a state, province, or sub-national jurisdiction — typically anchored by a public-health authority or large institutional group. Three to six months phased rollout; population-scale records; regional operational and clinical visibility.

A sovereign national deployment runs HealthOS as the substrate for a country's healthcare delivery — population-scale records, national operational visibility, ministry-level governance. Architecture is sovereign by design: data residency, identity, governance, and accountability are structurally owned by the jurisdiction. Deployment is domain-led, twelve to twenty-four months across a national rollout.