NHS API Platform
The NHS API Platform is the route for NHS APIs and developer access. It is relevant to patient-facing API patterns, including GP Connect Patient Facing APIs and other NHS App-adjacent integrations.
GP Connect architecture material distinguishes API Platform patient-facing routes from Spine Secure Proxy (SSP) professional routes and Message Exchange for Social Care and Health (MESH) messaging routes. Interface Mechanism 1 (IM1) is separate again: it is a supplier-specific GP-system interface and pairing route rather than the NHS API Platform itself.
Role in NHS App Architecture
The NHS API Platform is an access route for NHS APIs. In this wiki it matters where patient-facing or provider-facing data moves through an NHS API route rather than direct web integration, MESH, Spine Secure Proxy, or supplier-specific IM1 pairing.
Route Placement
| Route | Placement |
|---|---|
| GP Connect Patient Facing APIs | NHS API Platform route in the reviewed GP Connect architecture. |
| NHS App API / integration routes | API and developer route evidence where a service integrates with the NHS App. |
| Personal Demographics Service (PDS) / Organisation Data Service (ODS) / other APIs | May support identity, registration, organisation, or onboarding flows. |
DPHC Relevance
For Programme Cortisone or any Defence Primary Healthcare (DPHC) integration, record the exact API route:
- NHS API Platform API.
- Spine Secure Proxy API.
- MESH messaging route.
- NHS App integration route.
- Supplier-specific GP system route.
- Interface Mechanism 1 pairing route.
- NHS England partner onboarding / assurance route.
Dependencies
| Dependency | Why it matters |
|---|---|
| API catalogue status | Determines whether a route is current, deprecated, in development, or a mirror / secondary listing. |
| Authentication / authorisation pattern | Determines patient, provider, or system access assumptions. |
| Partner onboarding | Determines whether the API can be used in a live service. |
| Supplier / practice enablement | Determines whether a documented API is available for the relevant provider. |
What This Does Not Prove
NHS API Platform evidence does not prove DPHC onboarding, NHS App publication, GP-provider role, supplier enablement, or patient cohort availability.
Evidence Needed
- Exact API route for each proposed DPHC / CORTISONE feature.
- API status and assurance route.
- Patient, provider, or system authentication model.
- DPHC / supplier onboarding and live-service evidence.
Related Routes
- Architecture Index
- GP Connect Patient Facing APIs
- Interface and Assurance Layer
- NHS App Integration Route
Current Source Confidence
High for API Platform role. Not evidenced for DPHC or CORTISONE live use.