Skip to content

England Spine and National Services

England's healthcare connectivity combines networks, national identity and directory services, clinical APIs, messaging, record access and local systems. Spine is a major part of this landscape; it is not a single database containing every clinical record. Baseline public-source review: 15 September 2026; urgent-care routing extension: 29 September 2026. Start with the UK Healthcare Connectivity Landscape for the four-nation view.

Services by Function

Function Service What it does and how it connects
Network connectivity Health and Social Care Network (HSCN) Network connectivity for health and care organisations, replacing N3. Suppliers provide connectivity; national-service permissions are a separate matter.
National infrastructure Spine Supports national information exchange and services including PDS, EPS and record access. The official scope includes England, Wales and the Isle of Man.
Patient identity Personal Demographics Service (PDS) NHS number, demographics, registered GP and related information. The PDS FHIR API has defined access modes and onboarding; patient identity is not a full clinical record.
Staff identity Care Identity Service / CIS2 Authentication Staff single sign-on and applicable role-based controls. CIS2 uses OpenID Connect and supports internet access and multiple authenticators. It identifies the professional, not the patient.
Organisation directory Organisation Data Service (ODS) Organisation codes and reference data, including relationships and change/succession information.
System and endpoint directory Spine Directory Service (SDS) Accredited systems, service endpoints and addressing information; FHIR API access is available. ODS identifies an organisation; SDS helps locate its system/service.
Asynchronous delivery Message Exchange for Social Care and Health (MESH) Store-and-forward file/message delivery through API, filesystem client or web interface, over internet or HSCN. Used across the UK; not an England-only clinical repository.
GP information exchange GP Connect and Spine Secure Proxy (SSP) Specific APIs for record access and other approved capabilities. SSP brokers access to provider FHIR APIs, using SDS endpoint lookup, mutual TLS and traceable system identities. Document sending uses a separate MESH route.
National professional access application National Care Records Service (NCRS) Brings multiple national sources and functions into one application: SCR, demographics, care-plan documents, patient flags and administrative workflows. See the feature breakdown below; availability and permissions differ by feature.
GP-derived summary record Summary Care Record (SCR) One of the records available through NCRS, containing medicines, allergies/reactions and, where included, additional information. SCR is a source record, not the collective name for NCRS's other functions.
Locate records National Record Locator (NRL) Finds pointers to records held by connected providers; discovery and retrieval from the source are separate steps. See NRL evidence.
Electronic prescribing Electronic Prescription Service (EPS) Prescription exchange between prescribing and dispensing systems. Wales also uses Spine/PDS for its EPS implementation.
Referrals NHS e-Referral Service (e-RS) Referral workflows and APIs for the supported services; this is distinct from generic messaging or record access.
GP registration and record transfer NHAIS/GP Links and GP2GP GP software integration includes registration and practice-to-practice transfer routes. GP2GP differs from GP Connect record access. NI's NHAIS replacement is a separate national programme.
Documents and wider records/data National Document Repository, shared care records and related programmes Use the national record/data platform page to distinguish GP documents, local/regional records, proposed Single Patient Record and the Federated Data Platform.
Patient access NHS App and NHS login Patient-facing access and authentication, distinct from CIS2 staff identity and the APIs used by clinical systems.
Diagnostic exchange Pathology and Laboratory Medicine Reporting; National Imaging Registry FHIR pathology is in pilot, and NIR has limited beta use. See Diagnostic Results and Image Exchange for exact programme, interface and rollout boundaries.

For primary-care system implementers, NHS England's national-service integration guide links APIs and adaptors for these functions. Its legacy laboratory-results adaptor is not the new FHIR pathology implementation guide.

Urgent-Care Routing

England's urgent-care flow has distinct stages. The four-nation comparison compares the functions; common telephone numbers or supplier brands do not establish shared national endpoints.

Stage England route Boundary
Patient entry and triage NHS 111 telephone, 111 online and NHS App entry; NHS Pathways clinical decision support Pathways assesses clinical need and urgency. It is a licensed clinical tool, separate from the directory and referral transport. Online symptom assessment is generally for ages 5 and over.
Find an appropriate service Urgent and Emergency Care Directory of Services (UEC DoS) Clinical search uses profiled services and eligibility/routing rules. NHS developer guidance selects the SOAP API for 111 service discovery; its basic REST counterpart is not suitable for that particular 111 referral use case.
Book and refer BaRS for supported urgent-care journeys; GP Connect Appointment Management for GP slots through existing assured systems A slot booking and the clinical referral are separate operations. BaRS application support does not establish that every local sender and receiver is live.
Send the 111 report to the GP/other receiver NHS 111 API standard: synchronous ITK SOAP with CDA; NHS 111 Report adaptor can convert received reports to FHIR The adaptor's output format does not make the incoming exchange BaRS or MESH. The active 111 reporting route remains distinct from newer BaRS applications.

Three directories must stay distinct: UEC DoS supports urgent-care service selection; e-RS's own Directory of Services supports its referral workflow; Directory of Healthcare Services (DoHS / Service Search) supplies public service listings. The shared word “directory” does not make their data, selection rules or APIs interchangeable.

DoS modernisation is staged. The newer DoS Search API is production/beta, but its checked specification establishes organisation/endpoint lookup now and explicitly withholds HealthcareService and triage-code searches from UAT and production. Those published operations support transparency/onboarding; wider replacement functionality is planned across 2026–27. Existing UEC SOAP/REST APIs remain listed in production and under review for deprecation. DoHS v3 is a separate service, and its overview's conflicting legacy v1/v2 retirement/status text does not establish completed retirement.

BaRS is live, with application-specific adoption. Current evidence covers 111/CAS to ED/UTC, 111 online and streaming/redirection, 999/CAS referral or validation, and GP-to-pharmacy journeys. Ambulance trust-to-trust remains in development. The supplier register distinguishes technical assurance from active use: NHS 111 Online App 2 is live; Nervecentre's App 1/2 receiver is supplier-assured. No InterSystems-named entry was found in the checked register; middleware standards support alone does not establish a BaRS-assured product or deployment.

GP Connect Appointment Management remains a documented GP-slot route, but the current service page closes new-developer onboarding for it while allowing existing consumer suppliers to onboard end users. Older API onboarding instructions must be read with that restriction. See the DSIC urgent-care requirements for receiver, sender and capability obligations.

National Care Records Service (NCRS)

NCRS is the professional application that brings several national services into one view; SCR is one of its sources. NHS England's service overview describes both viewing and selected updating functions. It is broader than an SCR viewer, while access to each feature remains dependent on the user's role and the service's availability.

Features and Underlying Services

The following are documented NCRS functions, checked 15 September 2026. The table distinguishes clinical sources, patient flags and administrative workflows rather than treating them all as parts of SCR.

NCRS feature Underlying service or information What an authorised user can do / scope
Patient search and demographics Personal Demographics Service (PDS) Find a patient and view identity, contact, GP/provider and demographic-history information. NCRS onboarding also lists demographic editing; the public sources do not establish that every field is editable by every user.
Summary Care Record SCR derived from GP records View medicines, allergies and adverse reactions, with additional information where included. Record availability and permitted access depend on the patient's SCR preferences and the user's permissions.
Care plans and documents National Record Locator (NRL) Discover pointers to information shared by other organisations, such as crisis and end-of-life plans. Permission to see a pointer is distinct from permission to open its document.
Patient flags: child protection Child Protection – Information Sharing (CP-IS) View safeguarding information under the appropriate role. Access with the relevant activity triggers an Access to Service Notification; this is not an NCRS facility for editing the underlying protection plan.
Patient flags: FGM Female Genital Mutilation – Information Sharing (FGM-IS) View an indicator; appropriately authorised users can add or remove it. This is a separate safeguarding function, not SCR content.
Patient flags: reasonable adjustments Reasonable Adjustment Digital Flag View adjustments and, with appropriate permission, create or delete supported entries; changing a specific adjustment uses deletion and re-addition. NCRS cannot add or delete the underlying conditions.
Birth notifications PDS birth-notification process Authorised midwives and health-records managers can create a birth notification, registering the baby on PDS and notifying linked services. Standalone NHS-number allocation is a different function and does not perform the birth-notification workflow.
Chargeable status and overseas-visitor records Home Office information and Overseas Visitor Manager (OVM) records View status information. Separate permissions govern creating/editing OVM records and editing chargeable status; NCRS is presenting or recording information, not replacing the applicable eligibility assessment.
Dedicated COVID-19 vaccination view COVID-19 vaccination history Retirement announced. Guidance updated 13 August 2026 says the dedicated view will retire, with vaccination status remaining available in SCR. It gives no retirement date or confirmation of completed withdrawal.

Pilot and Planned Features

Feature What it adds Published availability
GP Connect information and Access Document Access to GP information and clinical documents held by the registered GP practice. This is separate from both SCR and NRL documents. Pilot users only on the August 2026 service page. The July roadmap reports Access Document pilots with two ambulance services and GP practices across selected ICBs; this is not universal NCRS access.
Shortcut to Shared Care Records Open the same patient's record in a connected shared-care-record application without another search or login; Greater Manchester is the service page's example. Upcoming pilot / development, not an established national feature for every shared record. A contextual launch is distinct from importing every shared-record item into NCRS.

Access and Interface Structure

NCRS uses CIS2 authentication and works on internet or HSCN connections. The service overview sets a baseline access requirement; the feature-specific user guidance then defines the permissions for each task. Logging in does not grant all clinical, safeguarding or administrative capabilities.

The documented interface has Overview, Patient details and Clinical tabs, with a Documents tab for eligible roles. For example, NRL activity B0268 permits pointer viewing, while B0269 also permits document access. OVM record editing and chargeable-status editing likewise have different permissions. Use the relevant guidance before assigning a role or designing an integration.

NHS England also supports launching NCRS from a local patient system in patient context, through supplier integration and onboarding. This opens NCRS with its applicable role controls; it is distinct from the planned shortcut in the other direction, from NCRS into a Shared Care Record.

Permissions by Feature

The service access requirements include a Care Identity profile, authenticator and a role with at least activity B0264, plus organisational onboarding. The table gives the additional feature distinctions published in NHS guidance, checked 15 September 2026. B codes are activities assigned to a role; a job title alone does not establish access. Birth notifications explicitly require a role and activity combination (SRC-045, SRC-401 to SRC-403).

Feature Published role/activity Permitted action and limit
SCR B0257, B0082, B0168, B0085 or B0030 View with patient consent. Guidance specifies separate legal, emergency or legitimate-relationship access routes; these codes are not an unrestricted permission to browse records. No SCR editing function is documented here.
NRL B0268 / B0269 B0268: see document pointers. B0269: also open documents. Organisational onboarding is required.
Child protection B0107 / B0170 Both view alerts. B0107 also sends an Access to Service Notification to the local authority; B0170 does not. Neither is described as editing protection plans.
FGM indicator B0370 / B0380 B0370: view. B0380: view, add or remove the indicator.
Reasonable Adjustment Flag B0264 / B0257 / B0380 See existence / view details / manage the flag, respectively. Changes to adjustments require deletion and re-addition; underlying conditions cannot be added or deleted in NCRS.
Birth notifications R8013 + B1610, or R8016 + B1610 Health Records Manager or Midwife: create and view birth notifications. The Midwife combination also permits standalone NHS-number allocation, a separate process.
Chargeable status Patient-record access / B0259 / B0266 Record viewers can see the status banner. B0259 and B0266 can inspect Home Office/OVM details and create/edit OVM records; only B0266 also edits chargeable status.
Demographic editing, dedicated vaccination view and pilot features No complete feature-permission mapping verified in the reviewed guidance Retain the documented feature and availability limits above; do not infer an edit permission or pilot entitlement from basic access.

These are published application permissions, not a recommended access profile for every clinician. The linked SCR guidance explains the exceptional-access conditions; local role assignment and the patient's record preferences remain relevant.

Source Services and Launch Directions

Where the information comes from. This diagram shows the services presented through NCRS. Arrows mean information is available to the application; they do not specify an API, copied database or permission to update the source. The feature table above describes the supported updates (SRC-045, SRC-401 to SRC-403).

flowchart LR
    PDS["PDS<br/>Patient demographics"] --> NCRS["NCRS<br/>Professional application"]
    SCR["SCR<br/>GP-derived summary"] --> NCRS
    NRL["NRL<br/>Document pointers"] --> NCRS
    DOC["Provider-held documents"] -->|"NRL link"| NCRS
    FLAGS["Patient Flags<br/>CP-IS / FGM-IS / adjustments"] --> NCRS
    HO["Home Office status"] --> NCRS
    VAX["Dedicated COVID view<br/>Retirement announced"] --> NCRS

NRL locates documents; opening a document requires the separate document-access permission. NCRS also provides the birth-notification and OVM-record workflows described in the feature table. GP Connect pilot access adds a separate route to GP-held information/documents, and is not shown as a generally available source. Vaccination status remains available through SCR when the dedicated view retires.

Which application opens which. The two directions have different published statuses. CIS2 and feature permissions still apply when NCRS is launched in patient context.

flowchart TB
    LOCAL["Local patient application<br/>Approved supplier integration"] -->|"Existing contextual launch<br/>Opens the selected patient"| NCRS["NCRS in the browser"]
    CIS["CIS2 staff authentication<br/>Assigned role and activities"] --> NCRS
    NCRS -.->|"Planned / upcoming pilot shortcut<br/>Same patient, no new search or login"| SHCR["Connected Shared Care Record<br/>Greater Manchester cited as an example"]

The solid launch is documented supplier integration. The dashed launch remains a prospective Shared Care Record feature in the reviewed service/roadmap pages; it does not establish national availability or import the shared record into NCRS. This distinction comes from the supplier integration guide and NCRS roadmap.

This is NHS national-service functionality. The presence of SCR, NRL or GP Connect in NCRS does not by itself establish an InterSystems implementation or approval for a particular supplier interface. See national record and data platforms for the distinction between the NCRS application, its source records and wider programmes.

Patient Flag System-to-System Interfaces

CP-IS, FGM-IS and reasonable adjustments have documented software interfaces as well as NCRS access. An S2S indicator identifies the exchange; it does not imply that every interface is generally available or that the caller can change every flag. Interface status checked: 30 September 2026.

Interface Supported exchange and current boundary
CP-IS healthcare API The catalogue lists the HL7 V3 interface as production. Healthcare applications query protection information; unscheduled-care access triggers a local-authority notification, while scheduled-care access does not. HSCN, user authentication, local authorisation and supplier onboarding apply. This is not a healthcare-system facility for editing protection plans.
CP-IS local-authority MESH integration Production asynchronous exchange: authorities upload protection information and receive access or inactive-NHS-number notifications. This distinct sending/receiving role uses MESH and approved software.
Legacy FGM-IS FHIR API Production but deprecated, with no agreed retirement date stated. Its current route queries an under-18 patient's indicator; the read-and-update version is retired. HSCN and application authentication apply, with the caller enforcing end-user permissions.
Patient Flags FHIR API The published specification, v4.1.109, describes reasonable-adjustment/FGM read and write, and scheduled-care CP-IS read. It remains internal/beta: reasonable adjustments are used by NCRS with external integration at first-of-type; all three flag routes have sandbox/integration testing. CP-IS unscheduled encounter sharing and MNS integration remain in development. Each integration requires onboarding.

Migration completion is unresolved. The supplier-interest form uses broad retirement/merger wording, while the specific CP-IS catalogues still show production and the FGM catalogue shows deprecated production. The newer API's test endpoints and supported operations do not establish completed replacement. Confirm the chosen flag, operation, care setting and production route during onboarding (SRC-653 to SRC-655).

NHS App: Patient Access

The NHS App is the patient-facing application; NHS login authenticates the person. It does not give patients an NCRS staff role. The eligibility guidance specifies age 13+ and registration with an NHS GP practice in England or the Isle of Man, with practice arrangements needed at ages 13–15. It explicitly excludes people while registered with Defence Medical Services.

Feature group Source or service route Access and availability
Personal health information GP-system information, including results and records made available through connected services Identity verification is needed for full access. GP settings, source-system support and sensitive-information controls affect what appears; hospital information may be absent.
Prescriptions and appointments Requests and bookings with the relevant GP/provider service Request repeats and use available appointment services. A practice can disable a service; an app login does not guarantee every booking or hospital connection.
Messages and documents Connected NHS services and GP documents The help catalogue describes separate inbox and document functions. Their presence is not evidence of a complete cross-provider record.
Family and carer access A separate, practice-authorised linked profile The published route requires both people at the same practice. The practice determines the permitted actions; applying within the app is being tested at some practices.

Sources: full-access guidance, feature help and family/carer access. These patient functions should be compared with MyCare.scot, NHS Wales App and NI My Care separately from the professional portals in the UK landscape.

Network and Access Changes

Spine's August 2026 service page encourages transition from HSCN to internet-based access and retains HSCN support during that transition. Check the chosen API's network, authentication and onboarding requirements before changing a route; the general announcement does not replace service-level instructions. Official Spine service page.

CIS2 works over the internet and supports a wider range of authenticators than CIS1. NHS England schedules CIS1 retirement for the end of February 2027, with new integrations required to use CIS2. This is a staff-authentication migration, separate from patient identifiers and the lifecycle of the clinical APIs. CIS2 Authentication.

HSCN is therefore one network route in the architecture, not a synonym for Spine or a guarantee of access to a record. Wales' evidenced use of Spine also does not imply use of every England service or applicability of England's DSIC procurement framework.

A Connection in Practice

For a supported GP Connect read, the public architecture describes a consuming application finding the provider endpoint and system identity through SDS, then making the request through SSP to the GP system. SSP provides the security proxy and logs the transaction; the GP system provides the supported record response. Endpoint lookup, application identity, user permissions and the clinical capability all need to agree.

For MESH, the sending system uploads a file to a mailbox route and the receiving system retrieves it. A workflow identifier describes the exchange purpose; the payload can be a FHIR document or another agreed format. Delivery acknowledgements establish a transport event. They do not, by themselves, establish that a clinician has reviewed a result or that a receiving application has correctly filed it—that is the workflow implication, not an extra MESH guarantee.

Use the GP Connect architecture pages and MESH/ITK3 standards page for implementation detail. Current restrictions on new GP Connect developer onboarding must be checked separately from the publication or effective date of a DSIC standard.

National Data Opt-Out Checking

Setting a patient's preference and applying it to a proposed data use are separate operations. The Check for National Data Opt-outs service uses MESH: an organisation submits NHS numbers and receives a list with opted-out patients removed. This is the documented system-to-system checking route; it does not create or change the person's choice. The organisation must first determine whether the intended use or disclosure is in scope. The national preference concerns specified uses of data about care in England and does not govern individual-care sharing. Technical route checked: 30 September 2026.

InterSystems Evidence

The NHS integrated-products list names Intersystems HealthConnect 2020.1, North West Anglia NHS Foundation Trust, application-restricted PDS access, with approval dated 25 August 2021. The register includes approved products whether or not currently active. This is a specific PDS integration record; it does not establish every current Health Connect version, HealthShare EMPI or Provider Directory as approved for all PDS access modes. PDS integrated products.

The wiki separately records NHS-published HealthShare GP Connect supplier progress and NRL activity. Capability-specific supplier rows, dated roadmap milestones and a named live deployment are different forms of evidence. No public evidence reviewed here establishes InterSystems as the operator of Spine or the supplier of England's new pathology or NIR programme.