HCP-as-Pilot™ · Operational AI Governance · Version 4.0 Français ↗ Download PDF ↓
PatientCentricCare.AI — Helping every patient feel known
HCP-as-Pilot™ · Version 4.0 · July 2026

Operational AI Governance for AI-enabled healthcare.

AI is beginning to coordinate care between clinical encounters — scheduling follow-ups, monitoring recovery, supporting discharge. The question hospitals now face is not whether AI is capable, but whether every AI-mediated action is authorised, consented, risk-tiered, escalated and evidenced — at the point of use.

The thesis. Operational AI Governance is becoming as essential to AI-enabled healthcare as cybersecurity became to digital healthcare. It is the discipline that lets hospitals adopt AI safely — and it exists, ultimately, to protect one thing: continuity of care.
Business category
Operational AI Governance
▲ powered by
Architecture / IP
Runtime Governance Infrastructure (RGI)
▲ implemented as
Software platform
PCC-SafetyOS™
▲ deployed as
Product environment
The Patient Recognition Platform · Home Companion™ · MyHealthCanvas® · Trusted Health Memory™
1
Why PatientCentricCare.AI

We began with a continuity problem — not a language model.

Andy Squire, Founder

“We did not start by asking how to build another AI assistant. We started with a different question: why do patients spend 99% of their lives outside healthcare, yet every clinical encounter begins as though their story has been forgotten?”

— Andy Squire, Founder, PatientCentricCare.AI

That gap — between the continuous life of a patient and the episodic memory of the system — is where care breaks down: at discharge, across handovers, between the hospital and the home, between one multidisciplinary team and the next. Information is lost, questions are re-asked, and the patient carries the burden of remembering.

Operational AI Governance — and the Runtime Governance Infrastructure behind it — emerged from solving that continuity problem. Once AI begins acting between encounters, continuity can only be safe if every action is governed: who authorised it, whether consent held, what risk it carried, when it should escalate, and what evidence it left behind.

Every governance decision ultimately exists to improve continuity of care.

Helping every patient feel known.

Continuity of care · continuity of knowledge · continuity of each person's health context. Our hypothesis is simple: continuity compounds.

2
The adoption problem

Why AI healthcare projects stall.

Every hospital now has access to the same frontier models. Capability is no longer the differentiator — yet AI projects keep stalling before they touch a care transition. They stall on the same wall.

What teams reach for

  • A better model
  • Better prompts
  • A bigger context window
  • More agents
  • Another pilot

What actually blocks adoption

  • Unclear authority
  • Fragmented care workflows
  • Missing accountability
  • No runtime evidence
  • Fragile patient & clinician trust

None of the items on the left solve a single item on the right.

The agentic shift removed the technical ceiling and exposed the organisational one. A capable agent dropped into an ungoverned care workflow does not improve continuity — it accelerates whatever was already broken: unclear authority becomes faster unclear authority; assumed consent becomes automated assumed consent. Operational AI Governance is the missing layer that lets the 70% — people, authority and how care actually moves — finally have infrastructure beneath it.

1 The 10/20/70 framing is drawn from AI-implementation practitioner Andreas Horn's publicly shared 2026 lessons, cited as independent validation of a direction PatientCentricCare.AI reached through healthcare deployment — not as its intellectual source.

3
People first

Care is a workflow between people.

Everyone understands a care pathway; few understand a governance diagram. So we start where care actually happens — with the path a real interaction travels, from the patient to the evidence and back. Governance is the mechanism. Continuity is the outcome.

Patient
The person at the centre — at home, between appointments, across a discharge boundary.
Home Companion™
Engages before, during & between care — check-ins, reminders, wellbeing, everyday conversation.
Governance
Every action is checked before it happens — authority, consent, risk, escalation, evidence.
Care Team
Caregivers & nurses receive governed alerts and coordinate — never surprised, always in control.
Hospital
Clinicians & institution hold authority for clinical decisions, with a defensible record across every handover.
Evidence
Every governed decision is recorded — reconstructable and audit-ready, without surveillance.

The Patient Recognition Platform — four pillars, one continuity

Engage
Home Companion™
Engages people before, during & between care
Capture
MyHealthCanvas®
Captures what matters from every encounter
Remember
Trusted Health Memory™
Preserves the person's story across time
Govern
PCC-SafetyOS™
Operational AI Governance — humans in control
4
The adoption path

The AI care maturity model.

Every hospital sits somewhere on this ladder. The value is not in reaching the top fastest — it is in never letting autonomy outrun governance, so continuity never depends on an unaccountable action.

1Level
Chatbot
Answers questions. Stateless, no authority, no memory of the person.
2Level
Assistant
Helps with tasks and retrieves context. Still fully human-driven, one step at a time.
3Level
Agent
Executes real multi-step work on its own. Capability arrives — and risk becomes structural.
4Level
Governed Agent OPERATIONAL AI GOVERNANCE OPERATES HERE
The agent acts inside an enforced authority envelope — consent, risk tier, escalation and evidence checked before every action.
5Level
Evidence-Earned Adaptive Autonomy
Autonomy expands only for specifically inventoried decisions whose risk, evidence and institutional policy permit it. Human authority is not an immature stage — in many clinical contexts it is the correct operating model.
Operational AI Governance operates between Level 3 and Level 4 — turning a capable agent into a governed one. That is where safe adoption lives.
5
The category

What hospitals are really buying.

Hospitals do not buy governance. They buy outcomes — the results that keep patients safe and staff confident as care moves between people and settings.

Continuity of care
Safer AI adoption
Better, safer discharge
Fewer information gaps
Stronger multidisciplinary communication
Improved patient experience
Greater staff confidence
A defensible audit trail

Governance is the mechanism. Continuity is the outcome. Operational AI Governance is the discipline of ensuring every AI-mediated action in care is authorised, consented, risk-tiered, escalated and evidenced — at the point of use — so that a follow-up, an escalation or a handover can be trusted across every care transition.

As essential as cybersecurity became to digital healthcare

A decade ago, few hospital boards discussed cybersecurity as core infrastructure. Today none would deploy a clinical system without it. Operational AI Governance is following the same curve for AI-enabled care: first a differentiator, soon an expectation, ultimately a precondition for deployment.

And it answers the five questions no ungoverned AI can: Who authorised this action? Was consent valid at this moment? Who holds authority now? Is escalation required? And when something goes wrong — why was execution permitted?

6
How it works — for people, not engineers

Five principles of Operational AI Governance.

A hospital executive needs these five principles — not the software beneath them. Together they keep continuity safe as care moves between people, teams and settings.

01
Authority
Who decides
A named human always holds authority for each decision. AI acts only within a clinician-defined envelope.
02
Consent
The patient agrees
Consent is checked at the moment of every action. No consent, no action — the patient stays in control of their story.
03
Risk
Scaled to stakes
Tier A routine → AI acts. Tier B safety signal → human confirms. Tier C clinical → clinician decides.
04
Escalation
Reaches the right person
Concerns route to caregiver or clinician by urgency — predefined, not improvised, so nothing falls through a handover.
05
Evidence
Recorded & defensible
Every decision records what was permitted and why — audit-ready, without surveilling the conversation.

Authority flows through the care team

Patient
Consent & wellbeing; in control of their story
Caregiver
First-line coordination & support
Nurse
Reviews exceptions; triages escalation
Physician
Authority over clinical intervention
Institution
Accountable owner; policy & oversight
Authority · Consent · Risk · Escalation · Evidence — five principles in service of continuity of care.
7
The architecture beneath

Powered by Runtime Governance Infrastructure.

Operational AI Governance is made possible by Runtime Governance Infrastructure (RGI) — a domain-agnostic architecture that evaluates the five principles at the point of execution, in milliseconds, before an AI-mediated action reaches a patient.

Governance before action

Traditional AI execution

AI generates output
Action occurs
Audit later

Runtime Governance

AI proposes action
Governance evaluatesauthority · consent · risk · escalation · evidence
Patient-safe action occurs → evidence recorded

HCP-as-Pilot™ is the healthcare framework built on RGI, following the principle proven in aviation: autopilot may execute, but authority remains with the pilot. AI may assist, recommend and coordinate; authority over patient-impacting actions remains human. RGI is a new infrastructure category — healthcare is its first implementation.

8
Why now, alignment & early proof

A narrow window — and evidence already accruing.

Regulatory inevitability creates a window for first movers: hospitals that build Operational AI Governance today will hold the evidence and institutional trust required when it becomes mandatory.

Indicative market-development scenario — projection, not sourced regulatory fact

2026 WE ARE HERE
EU AI Act enforcement begins; runtime evidence supporting conformity assessment becomes a differentiator.
2027 →
Projected: first enforcement precedents; ungoverned systems face scrutiny.
2028 →
Projected: payer requirements emerge; governance evidence trends toward table stakes.
2029+ →
Projected: clinical expansion favours systems with a proven governance history.

Regulatory alignment — evidence by design, not compliance by assertion

FrameworkReferenceAlignment
EU AI ActArt. 12, 14, 16Generates runtime evidence for human-oversight, record-keeping and post-market monitoring obligations.
Singapore AIHGle 2.0MOH/HSA 2026Independent convergence: mandates human oversight for clinical AI; flags home-care AI as needing added governance.
UK MHRASaMD RoadmapPhased architecture aligns with the MHRA's progressive AI-oversight framework for software as a medical device.
FDA SaMD / PCCP2019 / 2023Phase III maps to Predetermined Change Control Plan requirements for adaptive AI medical devices.

Early field evidence — governed AI in real homes

Phase I (Home Companion™) is an early-access usability deployment with senior users across Switzerland and the UK — non-medical, non-SaMD, governed end to end.

4,600+
Governed runtime events — each evaluated before execution
Controls applied to every event; nothing acts outside authorised bounds
12 · 3 · 2
Seniors · care professionals · months of continuous use

A governed runtime event is a single AI-mediated action evaluated for consent, authority, risk and escalation before it executes. Figures describe a usability deployment, not a clinical study; hospital-pilot recruitment is now underway.

9
The bottom line & your next step

Operational AI Governance is the new precondition for AI in care.

Every hospital now has access to intelligence. The differentiator is the capability to govern it — to trust, scale, audit, improve and certify AI acting between clinical encounters. Hospitals that can do this will adopt AI faster, protect continuity of care, and earn greater confidence from patients, clinicians and regulators.

“She made me laugh speaking in Luzern Swiss German dialect from my childhood.”

— Senior & cancer survivor, 86, Basel

“I love that I can suggest personalised memories for my mum to discuss. It makes her smile.”

— Caregiver, 62, Allschwil

“I care for multiple seniors, and Home Companion keeps the status of each organised for me.”

— Care-home assistant, 42, Basel
Your next step

Pilot the governance layer before clinical autonomy.

Start where the risk is bounded — one care transition, one virtual ward, one discharge pathway. Prove Operational AI Governance there, then expand autonomy only where the evidence earns it.

1Select one bounded care workflow
2Inventory its decisions
3Define authority & escalation
4Generate 90 days of runtime evidence

The question is not whether AI can participate in care.
It is how AI is governed — at the point of use, in service of continuity.

10
Appendix · Technical implementation

PCC-SafetyOS™ — the software beneath the principles.

Hospital readers can stop at the five principles. This appendix is for technical evaluation and procurement due diligence: the components of PCC-SafetyOS™ that implement Operational AI Governance using Runtime Governance Infrastructure — each stated as one function and one governance consequence.

Decision Inventory FOUNDATION

Inventories every AI-involved decision and assigns one named human owner.

→ A decision not inventoried cannot be automated. · Authority

Human Authority Envelope

Defines the boundaries AI may act within — and who holds authority when it cannot.

→ AI never operates outside authorised boundaries. · Authority

Consent Engine

Validates consent at the moment of every AI-mediated action.

→ No consent, no action; ambiguity defaults conservatively. · Consent

Risk-Adaptive Stratification

Classifies every action into a risk tier in real time.

→ Higher risk demands human confirmation or authority. · Risk

Escalation Engine

Routes to caregiver or clinician by urgency and availability.

→ Escalation is governed, not improvised. · Escalation

Flight Recorder

Records why each action was permitted — not just what happened.

→ Every governed decision is reconstructable; append-only. · Evidence

Runtime Evidence Ledger

Structures governance artefacts for internal review, quality assurance and regulatory assessment.

→ Everyday operation becomes defensible evidence. · Evidence

Operational AI Governance, powered by Runtime Governance Infrastructure — in service of continuity of care.
11
From Autopilot to Agentic AI: The Pilot Never Left the Cockpit — the aviation ecosystem (Pilot, Autopilot, Copilot, flight-management systems, Black Box) mapped to the healthcare ecosystem (HCP-as-Pilot, PCC-SafetyOS RGI layer, Agent Swarm, healthcare systems, Flight Recorder), showing that accountability evolves but never disappears.
12