NHS National Record and Data Platforms
This page distinguishes the National Care Records Service, its Summary Care Record source, NDR, Single Patient Record, and Federated Data Platform evidence so they are not collapsed into one architecture claim.
Use the UK Healthcare Connectivity Landscape for the whole-UK service map, country drill-downs and diagnostic-exchange transitions.
Current Reading
| Term | Current official reading | Main use | Boundary for this wiki |
|---|---|---|---|
| National Care Records Service (NCRS) | NHS England web application bringing several national services into one professional view. SCR is one component alongside demographics, NRL documents, patient flags, vaccinations and selected administrative workflows. See the NCRS feature breakdown. | Authorised access to multiple national information sources and role-specific actions from desktop or mobile devices. | NCRS is the access application; SCR is a source record. Features have separate permissions and availability: GP Connect information remains pilot-only, and shared-care-record shortcuts are planned/piloted rather than universally live. |
| Summary Care Record (SCR) | NHS England direct-care summary record derived from GP records, usually including medicines, allergies, and adverse reactions, with additional information where recorded and consented / governed. SCR is one of the records viewed through NCRS and can also be accessed through other approved point-of-care routes. | Urgent and direct care access to a limited GP-derived summary. | SCR is not GP Connect, not a full GP record, not a shared-care-record platform, and not evidence of InterSystems implementation by itself. |
| NDR | Use the acronym only after disambiguation. In NHS England current public sources, NDR commonly appears as the National Document Repository for GP scanned documents and digital patient documents. NHS England also describes data-services work that uses centralised national data repository language for commissioning flows. In Wales, NDR means National Data Resource, a DHCW / NHS Wales data platform around reusable data, FHIR, and the Care Data Repository. | Document storage, commissioning data-flow processing, or Welsh national data-platform work depending on source. | Do not treat "NDR" as a single UK platform. State whether the source means NHS England National Document Repository, NHS England commissioning/data repository work, or Wales National Data Resource. |
| Single Patient Record (SPR) | NHS England describes SPR as a programme to give patients and healthcare professionals a single place to access relevant patient information. It is a policy and delivery programme with Health Bill, standards, business-case, and supplier-prototype work; the public page says prototype testing included InterSystems, Oracle Health, and Orion Health shared-care-record suppliers. | Future England record-access and data-sharing direction. | SPR is not yet proof of a live InterSystems national deployment, DSIC conformance, or HealthShare implementation. Treat InterSystems prototype participation as a signal, not an award or assured operating model. |
| Federated Data Platform (FDP) | NHS England's FDP is a federated operational/data platform with local and national components, including the National Data Integration Tenant (NDIT), privacy/security controls, public uptake/benefits reporting, and NHS England programme governance. | Operational planning, waiting-list, discharge, pathway, population-health, and national data-integration use cases. | FDP is not a direct-care summary record like SCR, not the same as SPR, and not evidence that InterSystems is the FDP supplier or participant. |
Direct Care Versus Data Platform
The safest axis is purpose:
| Purpose | Better evidence label | Why it matters |
|---|---|---|
| Access national information through one application | NCRS, combining distinct source services and role-specific functions | Source coverage, feature permissions and pilot enrolment differ; NCRS does not make every source a complete or universally accessible record. |
| Direct-care record or summary content | SCR, GP Connect Access Record, local shared-care record | Needs direct-care access controls, RBAC, audit, patient transparency, provenance, and clinical-safety evidence. |
| GP-practice document storage | NHS England National Document Repository | Needs document lifecycle, indexing, retrieval, migration, and GP-system role evidence. |
| Operational / planning analytics | FDP / NDIT, commissioning-flow repositories, Welsh NDR where relevant | Needs controller/processor model, data-flow, lawful-basis, minimisation, pseudonymisation where applicable, opt-out / confidentiality handling, DPIA, and access governance. |
| Future single view of record | SPR | Needs programme, legislation, standards, supplier-role, business-case, safety, IG, and deployment evidence before being treated as live implementation proof. |
InterSystems Implication
For the Executive Summary architecture, these sources strengthen the national-service and target-architecture vocabulary but do not close the implementation proof gap.
| Architecture question | What the current sources support | Evidence still needed |
|---|---|---|
| Could Health Connect mediate record/data routes? | Product capability remains plausible for integration routes, and SCR / NDR / SPR / FDP sources identify route families that may need adapters. | Named product/version, approved route, endpoint/API, supplier responsibility, onboarding, monitoring, DSA/DPIA, DCB0129/DCB0160, and customer deployment artefacts. |
| Could HealthShare support SPR-style shared-care access? | HealthShare shared-care / UCR / Clinical Viewer / EMPI relevance remains plausible, and NHS England says SPR prototypes tested shared-care-record suppliers including InterSystems. | The SPR full business case, procurement or supplier award, architecture, standard set, product/version, access model, safety case, IG pack, and deployment plan. |
| Does FDP prove an InterSystems analytics or data-platform role? | No. FDP sources define an NHS England / NDIT platform and public benefit/governance route. | Any InterSystems role would need an official NHS, procurement, customer, supplier-approved, or technical architecture source naming the role. |
| Does Welsh NDR prove InterSystems Wales involvement? | No. Welsh NDR/CDR/FHIR sources support Welsh national data-platform context. InterSystems evidence covers LIMS 2.0 / TrakCare Lab Enterprise and documented laboratory interfaces with WCP for test booking and WRRS for results, not NDR/CDR operation. | Evidence for any InterSystems-to-NDR/CDR data flow and completed TrakCare Lab Enterprise interface migration. Existing WCP/WRRS laboratory connections do not establish InterSystems ownership of those national services. |
Evidence Request Checklist
Use this checklist only when one of these labels becomes decision-critical:
- Which label is being used: SCR source record, NCRS access application, National Document Repository, National Data Resource, central commissioning data repository, SPR, FDP, or NDIT?
- Which administration is in scope: England or Wales?
- Is the route direct care, document storage, operational analytics, population health, research, or policy/programme design?
- Which system supplies, stores, transforms, displays, or analyses the data?
- Which organisation is controller, joint controller, processor, subprocessor, manufacturer, deployer, service owner, and clinical-safety owner?
- Which service-access requirements and standards apply: GP Connect, FHIR/UK Core, SCR creation/access, NCRS application access, PDS, ODS/SDS, MESH/ITK3, DCB0129/DCB0160, Welsh FHIR/NDR standards, or SPR programme standards?
- Which artefacts prove the claim: product/version, API route, onboarding approval, DPIA, DSA, safety case, access-control model, audit model, contract, live-status evidence, and operational runbook?