Pathscription · Clinical pathway intelligence
Turn clinical decisions
into completed care.
Pathscription identifies the open loops between patients, clinical teams, decisions and actions — and helps carry them through to completion.
Prototype · not for clinical use
Check·The loop only closes when the completion condition is known. Otherwise it stays visible, owned and reopenable.
The problem
Care breaks at the joins.
A note is not an action. An alert is not a completed workflow. A referral being sent does not mean care happened. The gaps appear between people, shifts and systems.
Patient
Concern not carried forward
Clinician
No owner
Team
Waiting for review
Shift
Plan changed
System
Patient not updated
Care setting
Referral sent — outcome unknown
Pathscription closes the gaps.
Product
See an open loop close.
“I am frightened about the anaesthetic.”
One sentence, spoken once. Pathscription treats it as an open loop with an owner, a next action and a completion condition — and keeps it visible until somebody confirms what happened.
Fictional illustration · prototype
Hear
Concern recorded
Know
Important care context surfaced
Own
Anaesthetic team owns response
Act
Discussion completed
Tell
Patient updated
Check
“Did that address what you were worried about?”
- PartlyLoop remains open
Responded is not the same as resolved. The loop stays owned, and a further action is created until the patient confirms the concern was addressed.
Heard & Held
Being recorded is not the same as being heard.
- “I don’t feel heard.”
- “I am frightened.”
- “I don’t understand what is happening.”
- “I was told somebody would come back.”
- “I don’t want to explain this again.”
Responded ≠ resolved.
A concern remains open until the patient has been updated and the completion condition is known.
See Heard & Held →Tell us once
The next clinician should start with context — not make the patient start again.
Booking
Context transferred ✓
Antenatal
Context transferred ✓
Triage
Context transferred ✓
Admission
Context transferred ✓
Labour
Context transferred ✓
Theatre
Context transferred ✓
Recovery
Context transferred ✓
Postnatal
Context transferred ✓
Conceptual research only. No current NHS system integration is implied.
One engine
Pathscription Maternity
Concerns, context and unfinished actions that must survive handover.
Pathscription Neonatal
Newborn care, treatment and discharge actions. Research / future.
Pathscription Prescribe
Prescribing decisions carried through to a confirmed outcome.
Different stage. Different workflow.
Same Pathscription engine.
Platform architecture
Built around the real clinical workflow.
- EPR / maternity systemFuture / proposed
- Patient context + clinical signals
- Pathscription
- Workflow orchestration
- Owner + next action + escalation
- Clinical team
- Patient / family
- Audit + assurance
Pathscription is designed to sit alongside the clinical record rather than replace it. Integrations are proposed, not live. No NHS endorsement is implied and no NHS identity is used.
Evidence
Designed to be measured.
Proposed research metrics · no outcome improvements are claimed
The questions Pathscription asks
- What is still unfinished?
- Who owns the next action?
- Did the patient hear back?
- Did the referral actually lead somewhere?
- Does the next clinician have the context?
Pathscription
Clinical pathway intelligence.
Nothing missed.
Nothing unheard.
Tell us once.
Close the loop.
Prototype — not for clinical use. All patients, medicines, doses, guidance and maternity scenarios are fictional demonstration data. Pathscription does not diagnose, recommend treatment or make autonomous clinical decisions.