Solution & Multi-Tenant Architecture
Component map, tenancy model, deployment and country-configuration approach.
Blue Care Health OS is built as a multi-tenant SaaS with a FHIR R4-native core. Each organisation and facility is a tenant that controls its own operations — users, roles, local scheduling — while a shared patient-identity and longitudinal-record layer spans every tenant, which is what makes connected care possible instead of isolated systems. An interoperability layer isolates all external integrations behind configurable adapters, so a new system (a national registry, a lab, an insurer) is connected without changing the core.
Tenancy model
Two levels: Organisation (the legal/administrative entity — a hospital group or health district) contains one or more Facilities (a physical hospital or clinic). Users, roles and local scheduling are scoped to a facility within an organisation. The patient-identity layer is the one thing that is never tenant-scoped — a Blue Care Health ID resolves the same way everywhere.
Country configuration
Botswana is the first implementation. A new country is onboarded by configuring terminology packs, identifier formats (the Omang pattern is one such configuration) and regulatory profiles — not by rebuilding the core. This is what the Ongoing · Configurability roadmap line means in practice.
Deployment
Containerised (Docker), cloud-agnostic — deployable to the client's chosen dedicated, private-cloud, or sovereign environment. Hosting and any component licences (e.g. the FHIR server) are provisioned in the client's own cloud accounts and billed at cost (SOW §11), so ownership and control stay with Blue Care.