Healthcare and the NHS · Playbook 13

I've worked in this sector

Appointment no-show prediction

Fewer empty clinic slots, because the patients most likely to miss an appointment get help to attend or rebook in good time. Prediction leads to support, never to penalties, and people make every decision about a patient's care.

  • Predictive ML
  • Agents with tools
  • Human in the loop
  • Event-driven integration
  • UK GDPR special category data
  • Caldicott principles
  • National data opt-out
  • Equality Act 2010
  • DSPT
  • DCB0129 / DCB0160

At a glance

The problem
Thousands of outpatient slots are wasted each month, and the patients who miss them are often the ones who most need care
Typical volume
Around 900,000 outpatient appointments a year across 40 specialties
Who's involved
Outpatients and booking teams, clinical leads, the patient access and health inequalities leads, information governance, the Caldicott Guardian, digital and BI teams
Pilot
10–12 weeks in three or four specialties, after a 3–4 week discovery
Platforms
AWS, Azure, or a sovereign or on-prem stack

An illustrative scenario. The numbers are typical examples, not a client case study. The cloud services and UK rules were checked on 9 November 2026.

The business problem

Missed appointments are one of the most expensive quiet problems in outpatients. Government figures put missed elective appointments at about 8 million in 2023/24. Every empty slot is clinical time lost while the waiting list grows. NHS England's own guidance is clear that people often miss appointments for reasons outside their control: a letter that never arrived, no way to get there, caring responsibilities, a shift they couldn't swap, or a reminder in a language they don't read.

In a typical trust, the response is the same for everyone. One letter, perhaps one text, and a booking team that only finds out about a missed slot when the clinic list shows a gap. Patients who miss twice can be discharged back to their GP under local access policy, which can push the people with the greatest need furthest from care. For children, a missed appointment is recorded as 'was not brought', because the child depends on an adult to get there, and it can be a sign that something is wrong at home.

The pressure to fix this is real. The 2026/27 planning framework asks every trust for at least a 7% improvement in 18-week performance, or at least 65%, whichever is greater, and calls for a reset of outpatient care. It also names better communication through the NHS App as a way to reduce 'did not attend' rates. But a no-show model is easy to build badly. Missing appointments is closely linked to deprivation, so a model can easily learn to label poorer patients as 'unreliable'. The design has to make sure that a high risk score only ever brings more help.

What AI changes

  • Each week, every booked appointment gets a likelihood of being missed, with the main reasons in plain English, such as two recent missed appointments, a letter returned undelivered, or a long journey with no transport booked.
  • Patients most likely to miss get more help, not less: an extra reminder through the NHS App, an easy way to rebook, travel and transport information, a check that their contact details are right, and for some, a phone call from the booking team.
  • Patients who can't come are helped to cancel early, so the slot goes to someone else on the waiting list instead of sitting empty.
  • Clinic leads can add carefully limited extra bookings to sessions where several missed appointments are expected, within rules they set for each clinic. Booking staff decide, and the model never double-books onto a named patient's slot.
  • Missed-appointment rates and the help offered are tracked by deprivation, ethnicity, age and disability, so the trust can show that the gap is narrowing and no group is worse off.
  • Nobody is discharged, deprioritised or moved down a list by the model. A clinician reviews every missed appointment before any decision, and a child who was not brought is always considered for safeguarding.

How success is measured

Agree these, and measure the baseline, before anything is built. Example targets are typical, not promises.

Missed-appointment rate

Share of booked outpatient appointments missed without notice, by specialty and first or follow-up.

ExampleDown by a fifth in pilot specialties

Gap between most and least deprived

Missed-appointment rate for patients in the most deprived 20% of areas compared with the least deprived. This is the measure that shows whether the help is reaching the right people.

ExampleNarrowing, reported quarterly

Slots reused

Cancelled slots that were offered to another patient and used, because the cancellation came early enough.

ExampleUp, measured against last year

Help reached

Share of high-likelihood patients who received the extra reminder, rebooking offer or call before the appointment.

ExampleAbove 90% in pilot specialties

Overbooking overruns

Sessions that ran over because more patients attended than expected. Clinic staff feel this first.

ExampleRare, and reviewed every month

Model calibration

Whether predicted likelihoods match what actually happens, checked separately for each patient group.

ExampleWithin agreed limits for every group

UK regulation and controls

Cross-sector rules are on the UK regulation map.

  • ICOUK GDPR special category data and the Data Protection Act 2018

    Appointment histories show which services someone uses, so they are health data. That means a DPIA before the pilot, a clear lawful basis and condition for processing, processing in UK regions or the trust's own data centre, a defined retention period, and a contract that stops providers training their models on the trust's data. Patients are told, through the privacy notice and the reminder itself, how their information is used to offer help.

  • ICOAutomated decisions (UK GDPR, as amended by the Data (Use and Access) Act 2025)

    Since 5 February 2026, the strict limit on solely automated significant decisions applies mainly where special category data is involved, and here it is. The design keeps every significant decision with a person: the model only triggers extra reminders and support, and discharge, priority and overbooking decisions are made by staff.

  • National Data GuardianThe Caldicott principles

    Use only the data the model needs, give access only to those who need it, and inform patients' expectations about how their data is used. The Caldicott Guardian signs off the data used and the purposes, and is consulted on any change to either.

  • NHS EnglandThe national data opt-out

    The opt-out does not apply when a provider uses its own patients' data to support their individual care, which covers offering a patient help to attend. It can apply if data is used for wider planning or research, or shared under section 251 support. Agree the position with information governance in discovery, and apply the opt-out wherever it is needed.

  • NHS England and EHRCHealth inequalities duties, Core20PLUS5 and the Equality Act 2010

    The planning framework asks ICBs to show how they will reduce health inequalities, and trusts are bound by the public sector equality duty. NHS England's Core20PLUS5 approach focuses on the most deprived 20% of the population and other groups with poorer access. The model's results are monitored for each of these groups, and the trust's equality impact assessment is updated before go-live.

  • NHS EnglandDCB0129 and DCB0160 clinical safety, and the DSPT

    Missed appointments can cause harm, so the clinical safety officer decides how the standards apply. If the trust builds the model, it is the manufacturer under DCB0129 as well as the deploying organisation under DCB0160. The standards are under review, so watch for revised versions. The new system is covered in the trust's Data Security and Protection Toolkit submission.

The solution

Showing AWSAzuresovereign / on-prem services. Switch with the toggle; every diagram and table on this page follows it.

Appointment no-show prediction: reference architecture
  1. 01Channels

    • NHS App
    • Text message and letter
    • Phone call from the booking team
  2. 02Intake

    • API GatewayAPI ManagementKong, or your existing API gatewayAppointment events
    • Amazon S3Azure Data Lake StorageCeph, or IONOS S3 Object StorageAppointment history
  3. 03Intelligence

    • SageMaker AIAzure Machine LearningMLflow and Kubeflow on KubernetesNo-show model
    • SageMaker AI PipelinesAzure Machine LearningMLflow and Kubeflow on KubernetesFairness and drift checks
    • Agent
      Bedrock AgentCoreFoundry Agent ServiceLangGraph on Kubernetes, with open-weight models via vLLMOutreach assistant
  4. 04Orchestration

    • Step FunctionsLogic Apps / Durable FunctionsTemporal, or n8nOutreach workflow
    • EventBridge + SQSEvent Grid + Service BusApache Kafka or RabbitMQEvents and queues
  5. 05Systems of record

    • PAS / EPR
    • NHS Notify
    • Personal Demographics Service
  6. 06People

    • Person
      Booking team: calls and rebooking
    • Person
      Clinic lead: overbooking rules
    • Person
      Clinician: missed appointment review
  • Cloud or platform service (AWSAzuresovereign / on-prem)
  • AI agent
  • A person decides
  • Your existing systems
  • Outside your organisation

Components, side by side

Appointment no-show prediction: components on AWS, Azure and a sovereign or on-prem stack
LayerAWSAzureSovereign / on-prem
Intake: appointment events and historyStart from the trust's data warehouse if it already holds clean appointment history. Don't build a second one.API Gateway, Amazon S3, AWS GlueAPI Management, Azure Data Lake Storage, Azure Data FactoryKong or your existing API gateway; Ceph or IONOS S3 Object Storage; PostgreSQL
Prediction modelA simple, explainable model (for example gradient-boosted trees) usually does as well as anything more complex here, and is easier to explain to a clinic lead.Amazon SageMaker AIAzure Machine LearningMLflow and Kubeflow on Kubernetes
Fairness and drift monitoringSageMaker Model Monitor and SageMaker Clarify closed to new customers on 30 July 2026, so new AWS builds run these checks in their own pipeline.Custom checks in SageMaker AI Pipelines, using open-source libraries (e.g. Fairlearn)Azure Machine Learning Responsible AI dashboard and model monitoringOpen-source fairness and drift checks (e.g. Fairlearn) in MLflow and Kubeflow pipelines
Call briefs for the booking teamThe only generative step. It turns the reasons and the patient's contact history into a short brief for the person making the call.Amazon BedrockMicrosoft FoundryOpen-weight models served with vLLM on your own GPUs, or IONOS AI Model Hub
Agent runtimeThe original Bedrock Agents closed to new customers on 30 July 2026; new builds use AgentCore.Amazon Bedrock AgentCoreFoundry Agent ServiceAn open-source agent framework (e.g. LangGraph) on Kubernetes
WorkflowRuns the reminder schedule, the call tasks and the cancellation offers.AWS Step FunctionsLogic Apps or Durable FunctionsTemporal, or n8n
Middleware and eventsAmazon EventBridge, SQSEvent Grid, Service BusApache Kafka or RabbitMQ
Link to the PAS or EPRRead appointments; write only call tasks and notes. Agree in discovery what the supplier allows.Through your EPR supplier's published API or integration engineThrough your EPR supplier's published API or integration engineThrough your EPR supplier's published API or integration engine
Patient messagingThe 2026/27 planning framework asks providers to move direct-to-patient messaging to NHS Notify. Don't sign a new local messaging contract for this.NHS Notify (NHS App first, then text, then letter)NHS Notify (NHS App first, then text, then letter)NHS Notify (NHS App first, then text, then letter)
Human reviewCalls and overbooking decisions happen where staff already work, not in a new screen.In the booking team's existing PAS worklistsIn the booking team's existing PAS worklistsIn the booking team's existing PAS worklists
Identity, keys, data protectionAccess to the scores follows the same role-based access as the PAS.IAM Identity Center, KMS, MacieEntra ID, Key Vault, PurviewKeycloak or your existing Active Directory; OpenBao or HashiCorp Vault; an HSM
Monitoring and auditLog every score, every message sent and every action a person took, with the model version.CloudWatch, CloudTrailAzure Monitor, Log AnalyticsPrometheus, Grafana, OpenTelemetry
UK data residencyThis is NHS patient data. Trust IG policy will usually require UK residency, so an EU-hosted option such as IONOS AI Model Hub (Germany) may not fit.eu-west-2 (London)UK South / UK WestYour own UK data centre, or a UK or EU provider

On a phone, the table shows the platform you pick. Sovereign / on-prem means open, portable components you can run in your own data centre or with a UK or European provider; IONOS is shown as one example, and others exist. What sovereign cloud means →

Hybrid and on-prem

Many organisations keep core systems and sensitive data on their own servers. This is how the same design works across both.

Stays on-prem

The PAS or EPR, the integration engine and the trust's data warehouse stay where they are. Appointment booking, discharge and access policy decisions all stay in the PAS, as now.

Uses cloud AI

Model training, weekly scoring, fairness checks and the call briefs run in a UK cloud region, or on the trust's own Kubernetes platform for the sovereign option. Only pseudonymised features are used for training, and scores are linked back to patients inside the trust.

How they connect

Through the integration engine and an API gateway, over a private link such as AWS Direct Connect or Azure ExpressRoute, or the HSCN where the trust already uses it. Scores return as events onto a queue, and messages go out through NHS Notify.

If the link drops

Standard reminders carry on exactly as before, because they don't depend on the model. Extra help simply pauses, and the last week's scores remain available to the booking team until the link returns.

The agents

What each agent may do through its tools, what it may not, and where a person signs off. The limits are enforced by the platform, not the prompt.

Outreach assistant

May do

  • Read upcoming appointments, the likelihood score and its reasons
  • Send approved reminder templates through NHS Notify, within the patient's contact preferences
  • Add travel, parking, transport eligibility and Healthcare Travel Costs Scheme information to the message
  • Offer a link to confirm, cancel or rebook, so the patient chooses
  • Check contact details against the Personal Demographics Service and flag mismatches
  • Create a call task with a short brief for the booking team

May not do

  • Cancel, move or double-book an appointment
  • Discharge a patient or change their place on a waiting list
  • Write free-text messages to patients, or change approved templates
  • Mention the likelihood score or its reasons to the patient
  • Contact a patient by a channel they have opted out of

Where a person signs offBooking staff make every call and every rebooking a patient asks for. Clinic leads set the overbooking rules, and clinicians review every missed appointment. The agent's permissions are enforced by the platform's identity and policy controls, not by instructions in a prompt.

Middleware and integration

The PAS stays the record of every appointment. The model reads appointment events through the integration engine and writes back nothing except call tasks and notes. If the trust already runs an integration engine, the AI uses it like any other system does.

Patient messages go through NHS Notify, which sends to the NHS App first and falls back to text and then letter. Templates and translations are approved once by the patient access team and the clinical lead, not generated on the fly. Delivery and read receipts feed back into the model, so 'never received the reminder' is visible and not blamed on the patient.

Events keep the AI decoupled. Each booking, change or cancellation becomes a message on a queue. If the model or the cloud service is unavailable, standard reminders continue from the PAS as today, nothing is lost or sent twice, and every message carries an ID so a retry never duplicates a reminder.

Process and people

  • A clear rule, written into the access policy: a likelihood score can only bring extra help. It is never used to discharge, deprioritise or offer worse slots.
  • Every missed appointment is reviewed by a clinician before any discharge. A child who was not brought is always considered under the trust's safeguarding policy.
  • Overbooking rules owned by each clinic lead, with caps, excluded clinic types (for example urgent suspected cancer and paediatric clinics), and a monthly review of overruns.
  • A quarterly fairness review, chaired by the health inequalities lead, of missed-appointment rates, help offered and outcomes by deprivation, ethnicity, age and disability.
  • A named owner for the model, the templates and the call scripts, with change control like any other system.
  • Booking staff trained before go-live in what the score means, what it doesn't, and how to talk to patients about getting to their appointment.

Delivery plan

  1. 3–4 weeks

    Discovery

    Measure missed-appointment rates by specialty and patient group, check data quality and contact details, agree the national data opt-out position and the supplier route, and pick the pilot specialties.

  2. Gate · must be true to passBaseline by patient group agreed, Caldicott Guardian and IG support, DPIA and equality impact assessment started, clinical safety officer named.

  3. 10–12 weeks

    Pilot

    Score appointments in shadow mode first, then switch on extra help for half the high-likelihood patients and compare. No overbooking yet.

  4. Gate · must be true to passMissed appointments down, no group worse off, calibration within limits for every group, and clinical safety and IG sign-off.

  5. 4–6 weeks

    Production

    Extra help goes live in the pilot specialties, then overbooking is switched on for clinics whose leads opt in.

  6. Gate · must be true to passMonitoring, fairness reporting, support model, rollback plan and booking team training in place.

  7. Ongoing

    Scale

    Add specialties in waves, then reuse the pattern for diagnostics and community appointments.

  8. Gate · must be true to passEach new specialty passes the same pilot gate, including the fairness check.

Roles and RACI

Who is responsible, accountable, consulted and informed, by activity
ActivityDirector of operationsOutpatients product ownerSolutions architectI can fill thisTechnical PMI can fill thisData scientists and engineersI can fill thisClinical safety officerIG, DPO and Caldicott GuardianHealth inequalities lead
Business case and benefitsAccountableResponsibleConsultedConsultedInformedInformedInformedConsulted
Target architecture and PAS integrationInformedConsultedAccountable and ResponsibleConsultedConsultedConsultedConsultedInformed
DPIA, opt-out position and Caldicott sign-offConsultedConsultedConsultedInformedInformedConsultedAccountable and ResponsibleConsulted
Clinical safety case and hazard logConsultedConsultedConsultedInformedConsultedAccountable and ResponsibleInformedInformed
Model build and fairness testingInformedConsultedAccountableResponsibleResponsibleConsultedConsultedConsulted
Overbooking rules for each clinicAccountableResponsibleConsultedInformedConsultedConsultedInformedConsulted
Go-live decisionAccountableResponsibleConsultedResponsibleInformedConsultedConsultedConsulted
Run, monitor and fairness reviewInformedAccountableConsultedConsultedResponsibleConsultedConsultedResponsible

Business case and benefits

Director of operations
A · Accountable
Outpatients product owner
R · Responsible
Solutions architect
C · Consulted
Technical PM
C · Consulted
Data scientists and engineers
I · Informed
Clinical safety officer
I · Informed
IG, DPO and Caldicott Guardian
I · Informed
Health inequalities lead
C · Consulted

Target architecture and PAS integration

Director of operations
I · Informed
Outpatients product owner
C · Consulted
Solutions architect
A/R · Accountable and Responsible
Technical PM
C · Consulted
Data scientists and engineers
C · Consulted
Clinical safety officer
C · Consulted
IG, DPO and Caldicott Guardian
C · Consulted
Health inequalities lead
I · Informed

DPIA, opt-out position and Caldicott sign-off

Director of operations
C · Consulted
Outpatients product owner
C · Consulted
Solutions architect
C · Consulted
Technical PM
I · Informed
Data scientists and engineers
I · Informed
Clinical safety officer
C · Consulted
IG, DPO and Caldicott Guardian
A/R · Accountable and Responsible
Health inequalities lead
C · Consulted

Clinical safety case and hazard log

Director of operations
C · Consulted
Outpatients product owner
C · Consulted
Solutions architect
C · Consulted
Technical PM
I · Informed
Data scientists and engineers
C · Consulted
Clinical safety officer
A/R · Accountable and Responsible
IG, DPO and Caldicott Guardian
I · Informed
Health inequalities lead
I · Informed

Model build and fairness testing

Director of operations
I · Informed
Outpatients product owner
C · Consulted
Solutions architect
A · Accountable
Technical PM
R · Responsible
Data scientists and engineers
R · Responsible
Clinical safety officer
C · Consulted
IG, DPO and Caldicott Guardian
C · Consulted
Health inequalities lead
C · Consulted

Overbooking rules for each clinic

Director of operations
A · Accountable
Outpatients product owner
R · Responsible
Solutions architect
C · Consulted
Technical PM
I · Informed
Data scientists and engineers
C · Consulted
Clinical safety officer
C · Consulted
IG, DPO and Caldicott Guardian
I · Informed
Health inequalities lead
C · Consulted

Go-live decision

Director of operations
A · Accountable
Outpatients product owner
R · Responsible
Solutions architect
C · Consulted
Technical PM
R · Responsible
Data scientists and engineers
I · Informed
Clinical safety officer
C · Consulted
IG, DPO and Caldicott Guardian
C · Consulted
Health inequalities lead
C · Consulted

Run, monitor and fairness review

Director of operations
I · Informed
Outpatients product owner
A · Accountable
Solutions architect
C · Consulted
Technical PM
C · Consulted
Data scientists and engineers
R · Responsible
Clinical safety officer
C · Consulted
IG, DPO and Caldicott Guardian
C · Consulted
Health inequalities lead
R · Responsible

R ResponsibleA AccountableC ConsultedI Informed· not involved

Where I'd fit

Option A

Lead the architecture

If there's no architect on the programme, I'd own the design end to end: the data from your PAS, the model and its fairness checks, the link to NHS Notify, and the gates. I'd work closely with your Caldicott Guardian, clinical safety officer and health inequalities lead, and report to your programme board.

Option B

Support your architect

If your partner, your EPR supplier or your own team already has an architect, I'd take on the model pipeline, the fairness monitoring and the outreach workflow under their lead, and give them a second senior opinion on integration, information governance and the clinical safety evidence.

Where this goes wrong

  1. Goes wrong

    The model learns that deprivation predicts missed appointments, and the score gets used to give poorer patients worse slots or fewer chances.

    How the design avoids it

    A written rule that the score only brings extra help, enforced in the workflow, plus fairness monitoring by group from the first week of the pilot.

  2. Goes wrong

    Patients are blamed for missing appointments they were never told about.

    How the design avoids it

    Contact details checked against the Personal Demographics Service, delivery receipts from NHS Notify, and 'never received' treated as a system failure, not a patient one.

  3. Goes wrong

    Overbooking turns into overrun clinics and frustrated staff.

    How the design avoids it

    Clinic leads set caps per session, high-risk clinic types are excluded, and overruns are reviewed every month.

  4. Goes wrong

    A missed paediatric appointment is treated like any other, and a safeguarding signal is lost.

    How the design avoids it

    'Was not brought' is recorded separately, never triggers automatic discharge, and always goes to a clinician.

  5. Goes wrong

    The model quietly goes stale after a change, such as more virtual clinics or patient-initiated follow-up.

    How the design avoids it

    Monthly drift checks, retraining with change control, and a named owner who is told when pathways change.

On the horizon

Changes already announced or under way that affect this design. More in the UK horizon scan.

  1. 2026/27 to 2028/29
    The planning framework asks providers to move all direct-to-patient messaging to NHS Notify, with NHS App notifications as the preferred channel. Migration starts in 2026/27 and should be complete by the end of 2028/29.

    Send every reminder through NHS Notify from the start, and design templates for the app first, with text and letter as fallbacks.

  2. 2026/27
    An outpatient reset: fewer routine follow-ups, more Advice and Guidance, and digital patient-initiated follow-up to be in place by the end of 2028/29. Every trust must improve 18-week performance by at least 7% or reach 65%.

    Expect the mix of appointments to change. Patients on patient-initiated follow-up have no fixed booking, so retrain the model as pathways change and don't compare this year's rate with last year's without adjusting.

  3. 2026–2027
    The ICO's code of practice on AI and automated decision-making, required by regulations in force since May 2026.

    Keep the decision log, the reasons shown to staff and the records of human review in a form you could show the ICO.

  4. Late 2026 and 2027
    Revised DCB0129 and DCB0160 clinical safety standards are expected after the review that closed on 11 September 2026.

    Keep the hazard log and safety case structured and current, so moving to the new versions is an update, not a rewrite.

  5. By December 2028
    The Health Bill, introduced in May 2026 and now in the Lords, would give the legal basis for a Single Patient Record and move NHS England's functions into DHSC. The government's target is to launch the Single Patient Record in the NHS App by December 2028.

    Build on national services such as NHS Notify and the Personal Demographics Service, not one-off integrations, so the design keeps working as national systems change.

Questions to ask your partner or vendor

Good answers are specific. Vague answers to any of these are worth following up.

Copy them into your next supplier meeting

  1. How will we know the model isn't disadvantaging patients from deprived areas, and who looks at that every quarter?
  2. What exactly can a high likelihood score change about a patient's care, and where is that enforced?
  3. Does the national data opt-out apply to our use, and who has agreed that?
  4. How are children who were not brought handled differently from adults who did not attend?
  5. Which clinics are excluded from overbooking, and who sets the caps?
  6. What does it cost to run per thousand appointments, at our volume?

Planning something like this?

Whether you need someone to lead the design or to support the architect you already have, let's talk it through.

Sam Naseem
Sam NaseemBirmingham, UK · UK & Europe
Available now