Healthcare

Patient Escalation

An illustrative healthcare scenario showing governed clinical evidence, observations, pathway policy and explainability without replacing clinical decision makers.

Illustrative Architecture Diagram

Governed understanding before an Action Proposal

The diagram names the architectural identities, evidence categories and authority checkpoints involved in the scenario. Operational systems remain the owners of operational records.

  1. Patient
  2. Referral
  3. Observations
  4. Care Pathway
  5. Policy
  6. Explanation
  7. Clinical Review

Scenario Structure

Constitutional scenario review

1. Operational Trigger

A patient referral or clinical escalation requires review against care pathway criteria.

2. Fragmented Current State

Patient identity, observations, referral notes, pathway rules, care-team responsibilities and prior decisions may be held across disconnected clinical and administrative systems.

The issue is not that operational systems are wrong. The issue is that each system may hold a partial view of identity, evidence, policy, events or authority.

3. Governed Evidence Required

Enterprise Reality governs representation rather than replacing source systems. Evidence categories include:

  • Patient identity
  • Clinical observations
  • Referral event
  • Care pathway
  • Clinical policy
  • Responsible authority
  • Prior decisions

4. Enterprise Reality Reasoning

Governed reasoning evaluates the relationship between clinical observations, the care pathway and policy criteria, producing an explainable Satisfied, Not Satisfied or Indeterminate outcome.

Satisfied

Governed evidence and policy support the condition.

Not Satisfied

Governed evidence or policy does not support the condition.

Indeterminate

Evidence is insufficient, unresolved or contradictory.

This is deterministic reasoning over governed relationships, evidence and policy. It is not AI inference and does not make AI a constitutional authority.

5. Governed Action Proposal

A governed proposal may recommend escalation review, evidence request, referral routing or scheduling for clinical consideration.

  • Escalate
  • Approve
  • Reject
  • Investigate
  • Refer
  • Schedule inspection

A proposal is not automatic execution. Triggering a workflow requires explicit authority and remains subject to the organisation's governed controls.

Reasoning, decision, Action Proposal, approval or pre-authorisation, execution authority and execution remain separate.

6. Human Accountability

Clinical judgement remains with accountable clinicians and care governance. Enterprise Reality does not diagnose, prescribe or replace clinical decision making.

Human review remains essential where required. Regulated judgement is preserved, and Enterprise Reality supports rather than replaces accountable decision makers.

7. Organisational Value

The scenario supports more traceable pathway handling, clearer evidence gaps and reviewable escalation rationale.

Expected value is described qualitatively: consistency, traceability, explainability, governed automation, cross-system understanding and improved auditability. No quantified return or deployment outcome is claimed.

Constitutional Summary

Enterprise Reality does not replace the operational systems used within this industry. It establishes a governed constitutional layer that enables consistent representation, explainable reasoning, justified decisions and authorised action across those systems.

Understand before change.