Perspective
The next era of care is continuous
Why the most important healthcare experience is no longer a visit, but the connected days between visits.
What a healthcare operating system must connect
Healthcare does not need one database to replace every database. It needs a coordination layer that can turn many authoritative systems into one accountable flow of work around a person. Calling that layer an operating system is useful only if we are precise about what it operates.
An operating system is not a system of record
The EHR remains authoritative for much of the clinical record. Claims platforms govern financial transactions. Device clouds manage telemetry. A care operating system should not create a competing truth. Its job is to maintain identity, context, permission, state, and accountability while work moves across those systems.
The architectural test is simple: can the platform explain where information came from, whether it is current, who may use it, what action it triggered, and whether that action was completed? If not, it is an integration layer with a better name.
Interoperability begins after transmission
FHIR and modern APIs make structured exchange more practical. But successful transmission is not the same as shared meaning. Two systems can exchange a field while disagreeing about identity, units, timing, provenance, or what the recipient is expected to do.
An operational connection therefore includes a contract: which system is authoritative, how records are matched, what consent permits, how errors are reconciled, where the item is routed, when it expires, and how completion returns to the source. Data exchange becomes care only when it closes a workflow.
Home signals require an evidence boundary
A measurement taken at home arrives with missingness, device error, behavioral context, and population-specific uncertainty. A platform must distinguish raw observation from derived signal, and derived signal from clinically validated inference. Those categories should never collapse into one confident number.
The system must preserve device provenance, units, collection conditions, confidence, and gaps. It should expose thresholds and make them adjustable by program and population. Most importantly, it must state what the signal cannot establish. Connected is a transport property, not a clinical conclusion.
Context should be shared selectively
Patients, clinicians, family caregivers, coordinators, and payers may participate in one journey without having the same rights or responsibilities. The goal is not universal visibility. It is minimum necessary context delivered to the person who can act.
That requires purpose-based access, explicit consent where appropriate, revocation, audit trails, and interfaces that explain why information is being shown. Privacy is not a wall around data. It is the disciplined control of data across a changing network of relationships.
AI needs a control plane
AI should not enter through a hundred isolated product features, each with its own hidden assumptions. A care operating system can provide a common control plane: approved use cases, permitted data, model identity, evaluation results, escalation policy, human review, and change history.
This is where an operating system earns the name. It does not merely connect applications. It establishes the rules under which information and intelligence become action—and makes those rules observable enough to govern.