NHS England
NHS England (which absorbed NHS Digital in 2023) is the national body that runs England's public health and social care API platform at digital.nhs.uk and api.service.nhs.uk. It publishes a large catalogue of internet-facing APIs - most of them HL7 FHIR R4 built to the FHIR UK Core profile - covering the national spine services: the Personal Demographics Service (PDS), GP Connect, the e-Referral Service (e-RS), the Electronic Prescription Service (EPS), the Organisation Data Service (ODS), Booking and Referral Standard (BaRS), immunisation history, the NHS App, NHS Notify, and the Directory of Healthcare Services. Access is governed centrally: applications onboard through the NHS API platform and authenticate with OAuth 2.0 bearer tokens - application-restricted (signed-JWT client credentials / API key) or user-restricted via NHS login (OIDC) and NHS CIS2 - with production access gated behind registration, assurance, and connection agreements. Home market is the United Kingdom (England). Positioning: a single national health system operating public, standards-based (FHIR UK Core) interoperability APIs rather than a commercial API vendor.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles NHS England the way a machine reads it — 16 machine-readable artifacts across 10 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — NHS England scores 45.2/100 (developing), with a separate agent-readiness read of 78/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile NHS England
Each block below is one kind of artifact we hold for NHS England. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 10
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Personal Demographics Service (PDS) - FHIR API
National electronic database of NHS patient demographic details - name, address, date of birth, related people, registered GP, nominated pharmacy and NHS number - exposed as an ...
GP Connect Access Record - Structured - FHIR API
Lets authorised health and social care staff retrieve a patient's GP practice record as structured HL7 FHIR resources (medications, allergies, problems, immunisations, and more)...
Electronic Prescription Service (EPS) - FHIR API
National service for sending electronic prescriptions from prescribers to dispensers (pharmacies), exposed as an HL7 FHIR R4 API. Sandbox FHIR endpoint confirmed live (returns a...
e-Referral Service (e-RS) - FHIR API
Create paperless referrals from primary to secondary care and receive referrals, Clinical Referral Information (CRI) and attachments from the NHS e-Referral Service, as an HL7 F...
Booking and Referral Standard (BaRS) - FHIR API
Sends booking and referral information between NHS service providers using the Booking and Referral Standard as an HL7 FHIR R4 API. OpenAPI harvested verbatim (8 paths).
Immunisation History - FHIR API
Access a patient's immunisation record (including coronavirus, influenza and HPV immunisations) as an HL7 FHIR R4 API. OpenAPI harvested verbatim.
Organisation Data Service (ODS) - FHIR API
Reference data on NHS and healthcare organisations, roles and terminology (the Organisation Data Service), exposed as an HL7 FHIR R4 API. OpenAPI harvested verbatim (8 paths).
NHS App API
Integrate with the NHS App to deliver messages and content to citizens and to link into NHS App journeys. OpenAPI harvested verbatim (4 paths).
NHS Notify (Communications Manager) API
National service for sending messages to people about their health and care across channels (NHS App, SMS, email, letter). OpenAPI harvested verbatim (7 paths).
Service Search (Directory of Healthcare Services) API
Search the national Directory of Healthcare Services for NHS organisations, services and their attributes. OpenAPI harvested verbatim.
Scroll within the panel for all 10 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
nhs-england-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Nhs England Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for NHS England — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/nhs-england · machine-readable index on apis.io