NHS API
NHS England's API management platform provides FHIR R4 and REST APIs for healthcare interoperability across the NHS. The platform covers GP Connect (appointment management and access record), Personal Demographics Service, Electronic Prescription Service, Summary Care Records, NHS login (OpenID Connect for citizens), Booking and Referral, Organisation Data Service, and content syndication. APIs are managed via NHS England's Apigee-based API platform and are targeted at system suppliers, NHS organisations, and accredited third-party healthcare application developers.
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 API the way a machine reads it — 24 machine-readable artifacts across 13 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 API scores 45.8/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile NHS API
Each block below is one kind of artifact we hold for NHS API. 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 13
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.
GP Connect Access Document - FHIR API
Retrieve documents held at a patient's registered GP practice, such as letters, discharge summaries, and other clinical documents stored in GP systems. Used alongside the Access...
EPS Prescription Tracker - FHIR API
Real-time tracking of prescriptions within the Electronic Prescription Service. Enables authorised users to retrieve details about prescription status and dispensation progress ...
Booking and Referral - FHIR API
Send booking and referral information between NHS service providers using the NHS Booking and Referral Standard (BaRS). Enables sharing of clinical and administrative data to su...
NHS Website Content API
Retrieve NHS-approved health information content (conditions, medicines, treatments, live well articles) for syndication into third-party apps and services. Returns structured c...
Elective Waiting List API
Access data from the NHS Waiting List Minimum Data Set (WLMDS), the national electronic database of NHS patient waiting list records. Supports performance monitoring and patient...
NHS API CodeSystem API
The CodeSystem API from NHS API — 2 operation(s) for codesystem.
NHS API List{id} API
The List{id} API from NHS API — 1 operation(s) for list{id}.
NHS API Metadata API
The Metadata API from NHS API — 1 operation(s) for metadata.
NHS API Organization API
The Organization API from NHS API — 2 operation(s) for organization.
NHS API OrganizationAffiliation API
The OrganizationAffiliation API from NHS API — 2 operation(s) for organizationaffiliation.
NHS API R4 API
The R4 API from NHS API — 6 operation(s) for r4.
NHS API STU3 API
The STU3 API from NHS API — 32 operation(s) for stu3.
NHS API ValueSet API
The ValueSet API from NHS API — 2 operation(s) for valueset.
Scroll within the panel for all 13 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Nhs Api Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
NHS API API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
NHS Organisation (ODS FHIR R4)
JSON SCHEMANHS Patient Demographics (PDS FHIR R4)
JSON SCHEMAExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
E Referral Worklist Response
EXAMPLEOrganisation Search Response
EXAMPLESecurity 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 API — 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 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/nhs-api · machine-readable index on apis.io