| 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 Glue | API Management, Azure Data Lake Storage, Azure Data Factory | Kong 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 AI | Azure Machine Learning | MLflow 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 monitoring | Open-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 Bedrock | Microsoft Foundry | Open-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 AgentCore | Foundry Agent Service | An open-source agent framework (e.g. LangGraph) on Kubernetes |
|---|
| WorkflowRuns the reminder schedule, the call tasks and the cancellation offers. | AWS Step Functions | Logic Apps or Durable Functions | Temporal, or n8n |
|---|
| Middleware and events | Amazon EventBridge, SQS | Event Grid, Service Bus | Apache 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 engine | Through your EPR supplier's published API or integration engine | Through 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 worklists | In the booking team's existing PAS worklists | In 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, Macie | Entra ID, Key Vault, Purview | Keycloak 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, CloudTrail | Azure Monitor, Log Analytics | Prometheus, 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 West | Your own UK data centre, or a UK or EU provider |
|---|