Pathscription logoPathscription
Pathscription platform

One orchestration architecture. Different clinically governed workflows.

Pathscription is a clinical workflow and safety layer designed to reduce the cognitive and administrative burden surrounding clinical decisions. It helps healthcare teams understand what needs to happen next, identify what is missing, track whether important actions are completed, and escalate when necessary.

Pathscription — Clinical pathway intelligence.

HEARKNOWOWNACTTELLCHECK

Pathscription helps healthcare teams carry important signals, context and actions through to completion.

Nothing missed. Nothing unheard. Tell us once. Close the loop.

Healthcare does not only have a knowledge problem.
It has a completion problem.

Pathscription helps turn important clinical signals and decisions into completed, owned and auditable workflows.

Hear. Know. Own. Act. Tell. Check.

The Pathscription loop

Hear · Know · Own · Act · Tell · Check

HEAR1/6

Has the important signal been captured?

Capture what matters.

  • · patient concern
  • · clinician observation
  • · result
  • · request
  • · preference
  • · referral
  • · task
  • · decision
KNOW2/6

Does the right person have the context?

Bring the right context forward.

  • · history
  • · current plan
  • · relevant patient preferences
  • · previous decisions
  • · outstanding concerns
  • · previous team handover
OWN3/6

Does somebody know they are responsible?

Make responsibility clear.

  • · named owner
  • · responsible clinical team
  • · acknowledged task
  • · escalation owner
  • · follow-up owner
ACT4/6

Did the required next action happen?

Make the next action visible.

  • · review
  • · discussion
  • · referral
  • · calculation
  • · prescription
  • · reassessment
  • · documentation
TELL5/6

Does the patient and/or next team know what happened?

Close the communication gap.

  • · patient updated
  • · next step explained
  • · care plan updated
  • · receiving team informed
  • · instructions provided
CHECK6/6

Did the action actually resolve the workflow?

Confirm what happened next.

  • · concern resolved?
  • · referral confirmed?
  • · reassessment completed?
  • · patient understands?
  • · follow-up arranged?
  • · next team acknowledged?
Workflow issue categories

  • HEAR GAP

    Important information has not been captured or acknowledged.

  • KNOW GAP

    Relevant context is unavailable, fragmented or not reviewed.

  • OWN GAP

    No responsible owner or team has acknowledged the next action.

  • ACT GAP

    Required action remains outstanding.

  • TELL GAP

    Relevant patient/team communication remains incomplete.

  • CHECK GAP

    The action happened, but completion or resolution has not been confirmed.

Common workflow failure examples — fictional

  • HEAR failure

    Patient raises concern but it is not captured.

  • KNOW failure

    Concern is documented but new team does not see relevant context.

  • OWN failure

    Review is required but nobody owns it.

  • ACT failure

    Review is assigned but does not happen.

  • TELL failure

    Decision is made but patient is not told.

  • CHECK failure

    Referral is sent but nobody confirms the next step.

Closed loop — fictional example

Patient: “I don’t feel right.”

  1. HEARConcern recorded
  2. KNOWRelevant context surfaced
  3. OWNResponsible team assigned
  4. ACTClinical review completed
  5. TELLPatient updated
  6. CHECKPatient says concern addressed / appropriate next step confirmed
LOOP COMPLETE

Illustrative only. Pathscription does not determine clinical urgency, diagnosis or treatment.

What this feels like for the clinician
  • HEARImportant information arrives in one place.
  • KNOWRelevant context is available.
  • OWNResponsibility is clear.
  • ACTNext work is visible.
  • TELLCommunication is not forgotten.
  • CHECKUnfinished follow-up stays visible.

Pathscription is designed to reduce the amount clinicians must hold in memory.

One engine. Multiple clinical pathways.

Hear → Know → Own → Act → Tell → Check

Prescribe

  • HEARPatient/context
  • KNOWGuidance/context
  • OWNClinician
  • ACTPrescribing workflow
  • TELLInstructions
  • CHECKApproval/completion

Maternity

  • HEARConcern / care signal
  • KNOWHistory / plan / context
  • OWNResponsible team
  • ACTReview / care action
  • TELLWoman updated
  • CHECKResolved / follow-up confirmed
Future conceptsDischargeReferralResultsMedication reviewFollow-up

Across care settings — maternity, neonatal, paediatric

Continuous care pathway

One pathway can cross multiple care settings

PREGNANCYBIRTHNEWBORNINFANTCHILD

Pathscription is designed to carry important context, actions and open loops across a clinical pathway — including transitions between maternity, neonatal and paediatric care.

Prototype concept only. Pathscription does not integrate with NHS or any other clinical systems.

Module
Research / future

Pathscription Neonatal

Workflow orchestration for the transition from birth through neonatal treatment, discharge and follow-up.

Illustrative workflow areas

  • Newborn observations
  • Investigations
  • Results requiring review
  • Medication workflows
  • Parent communication
  • Discharge actions
  • Follow-up
  • Transfer of care

Illustrative workflow areas only. Fictional — no clinical recommendations or medication doses.

Transition — fictional example

Mother & baby care transition

  1. Maternity

    Birth completed

  2. Newborn

    Newborn care pathway begins

  3. Neonatal / paediatric workflow

    Relevant actions and context continue

Maternal context
✓ Available where relevant and appropriate
Baby context
✓ Separate patient record / workflow
Open actions
2
Responsible team
Neonatal team — fictional
Parent communication
1 item outstanding
  • Mother and baby are represented as separate patients with separate clinical records and workflows.
  • Sensitive maternal information is never automatically transferred into the baby's record.
Fictional workflow
CHECK GAP

Newborn medication workflow

  • HEAR✓Clinical need recorded
  • KNOW✓Relevant fictional newborn context available
  • OWN✓Responsible clinician identified
  • ACT✓Fictional medication workflow reviewed
  • TELL✓Parent / carer instructions provided
  • CHECK—Follow-up confirmation outstanding

A medication being prescribed is not necessarily the end of the workflow.

Entirely fictional example. No real medicine, dose or clinical recommendation is shown.

Parent / carer communication

  • What has happened?

    A newborn care workflow was started after birth — fictional example.

  • What happens next?

    The neonatal team completes the outstanding review actions.

  • What are we waiting for?

    One investigation result requiring clinician review.

  • Who is responsible?

    Neonatal team — fictional named clinician.

  • Is follow-up required?

    Yes — follow-up not yet confirmed.

  • Has the parent / carer been updated?

    Last update given; one item still outstanding.

Communication status only. Pathscription does not provide clinical advice to parents or carers.

Continuity

From newborn care to paediatric prescribing

NEWBORNINFANTCHILD

As the child moves through healthcare, Pathscription's underlying workflow architecture remains the same.

  • HEARCapture the clinical signal.
  • KNOWBring forward the relevant context.
  • OWNMake responsibility clear.
  • ACTComplete the appropriate clinician-led workflow.
  • TELLGive parents / carers clear information.
  • CHECKConfirm the required next step or follow-up.

Different stage of care. Same Pathscription engine.

Platform journey

  1. Pathscription Maternity

    Prototype demonstration

    Pregnancy → Birth

  2. Pathscription Neonatal

    Research / future

    Newborn → Discharge → Follow-up

  3. Pathscription Prescribe

    Prototype demonstration

    Infant / child → Clinical decision → Prescription → Parent instructions → Follow-up

None of these products is clinically deployed. Maternity and Prescribe are prototype demonstrations; Neonatal is research / future.

Care doesn't start and stop with departments.

  • A maternity pathway can become a neonatal pathway.
  • A neonatal pathway can become a paediatric pathway.
  • Pathscription is designed around the journey of care rather than the boundaries between individual systems.
Core architecture language

Pathscription models healthcare as connected completion loops rather than isolated records or alerts.

  • An alert is not a workflow.
  • A note is not a workflow.
  • A referral is not a completed workflow.
  • A conversation is not necessarily a resolved workflow.
  • Pathscription follows the next responsible action until the completion condition is known.
Explore the Pathscription loop →

Tell us once.

Important patient context should travel with the patient — across appointments, wards, clinicians and procedures.

Pathscription is designed so the next professional starts with context, not a blank page.

A concern should survive the appointment.

A preference should survive the handover.

A care plan should survive the change of team.

Important context should reach the clinician before the conversation.

See care context continuity
Orchestration loop
  1. Clinical context
  2. What needs to happen?
  3. What is missing?
  4. Prioritise
  5. Assign / surface
  6. Acknowledge
  7. Complete
  8. Document
  9. Escalate if required
  10. Audit

Traditional clinical systems primarily record what happened. Pathscription is designed to help teams manage what needs to happen next.

Nothing important gets lost in the workflow. No concern without a response. No task without an owner.

Reusable engine modules

  • Context Engine

    Structures available clinical information into workflow fields.

    Prescribe · Maternity

  • Guidance Layer

    Surfaces authoritative guidance with source, version and date.

    Prescribe

  • Deterministic Rules Engine

    Applies clinically governed rules with inspectable working.

    Prescribe

  • Workflow Orchestrator

    Sequences what needs to happen next and tracks completion.

    Prescribe · Maternity

  • Safety Engine

    Runs configured checks before a workflow can be closed.

    Prescribe · Maternity

  • Task & Ownership Engine

    Gives every outstanding action a named owner and a state.

    Maternity

  • Escalation Engine

    Keeps unacknowledged work visible and escalates by local pathway.

    Maternity

  • Patient / Family Input Layer

    Brings concerns and requests into the clinical workflow as events.

    Maternity

  • Documentation Engine

    Prepares record entries and patient-facing communication.

    Prescribe · Maternity

  • Audit Trail

    Timestamps who knew what, who owned it and what happened next.

    Prescribe · Maternity

  • Integration Layer

    Future connections to source clinical systems.

    Future concept

Different clinical workflows use different combinations of these modules.

Workflow modules

PRESCRIBEDEMONSTRATOR

Turn prescribing decisions into completed prescribing workflows.

Patient context → relevant guidance → safety checks → deterministic calculation where required → clinician review → documentation → patient instructions.

Open demo
MATERNITY SAFETYRESEARCH / FUTURE WORKFLOW

Help prevent safety-critical actions and patient concerns from being lost when maternity services are under pressure.

Clinical context → maternal concerns → required actions → ownership → deadlines → escalation → completion → audit trail.

Explore concept
MEDICATION REVIEWFUTURE

Structured review of a patient's current medicines, with actions and owners.

DISCHARGEFUTURE

Everything agreed on the ward reaching the patient and their GP.

REFERRALFUTURE

Referrals tracked to acceptance, not just to sending.

FOLLOW-UPFUTURE

Results and planned reviews with a named owner and a deadline.

Platform architecture — concept
  1. EPR / maternity record / other clinical systems
  2. Pathscription context layer
  3. AI structuring + workflow orchestration
  4. Authoritative guidance / clinically governed rules
  5. Task + ownership engine
  6. Escalation engine
  7. Clinician review
  8. Documentation / source systems
Separate lane — patient / family
  1. Patient / family concern
  2. Pathscription
  3. Clinical workflow
Future integration concept
NHS EPR systems — future integration conceptMaternity record systems — future integration conceptFHIR — future integration conceptClinical observations — future integration conceptLab results — future integration conceptStaffing / acuity systems — future integration conceptNHS App / patient interfaces — future integration concept

No integration exists in this prototype and no NHS approval, regulatory approval or clinical validation is claimed. Any deployed system would require appropriate clinical safety, information governance, regulatory and interoperability assessment.

Pathscription

Clinical pathway intelligence

Pregnancy. Birth. Newborn. Child.

Different stages. Different clinical workflows.

The same problem: important context, actions and communication need to reach the right person and be carried through to completion.

Hear. Know. Own. Act. Tell. Check.

Nothing missed. Nothing unheard. Tell us once. Close the loop.

Prototype — not for clinical use. All data fictional.