NHS England Digital Primary Care

This page is the parent for NHS England digital primary-care material in this wiki. It brings DSIC, GP Connect, GP foundation capabilities, national-service dependencies, procurement/migration, and InterSystems HealthShare compliance analysis into one England-specific structure.

Use this page for England. Use the devolved-nation pages for Scotland, Wales, and Northern Ireland. DSIC, GP Connect, and Spine are not treated as UK-wide labels unless a nation-specific source explicitly adopts them.

Scope

Area	What it covers	Main pages
DSIC operating model	NHS England digital primary-care procurement, frameworks, Buying Catalogue, capability model, standards, assurance, and migration.	DSIC Digital Services for Integrated Care, DSIC Procurement, Assurance, and Migration
GP foundation capability model	The GP system/service component set for patient records, appointments, consultation, prescribing, referrals, documents, tasks, reporting, scanning, patient-facing services, and shared/integrated care.	DSIC GP Foundation Capabilities, DSIC Capability-to-Standard Crosswalk
Standards and national services	PDS, NHAIS, GP2GP, SCR, National Document Repository, GP Connect, GPAD, GPES, MESH/MNS, eMED3, Yellow Card, EPS, e-RS, NHS login, ITK, NDO, NEMS, and adjacent NHS England service routes.	DSIC Standards and National Services, NHS National Record and Data Platforms, GP2GP Record Transfer, NHS Standards Directory and DHSC Standards Direction, NHS Standards Directory GP Connect, MESH, and ITK3
Statutory data and standards layer	Data (Use and Access) Act 2025 context for staged data protection/privacy reforms, the 19 June 2026 ICO data-protection-provision status, and the England health/adult social care information-standard powers affecting IT and IT-service providers.	Data (Use and Access) Act 2025, NHS Standards Directory and DHSC Standards Direction
GP Connect deep dive	GP Connect service context, capabilities, architecture, due diligence, roadmap, and InterSystems supplier-progress evidence.	GP Connect Deep Dive, GP Connect Capability Map, GP Connect Due Diligence
InterSystems compliance mapping	How HealthShare, Health Connect, IRIS for Health, FHIR Server, and related components can support DSIC-aligned solutions.	DSIC HealthShare Compliance Map, InterSystems GP Connect Evidence Boundary

Working Model

NHS England digital primary care has four nested levels:

DSIC defines the buying, capability, standards, assurance, migration, and operating frame for digital primary-care services in England.
GP Connect and other NHS services provide specific national interfaces, APIs, message routes, and service dependencies inside that wider frame.
DUAA provides a wider statutory data and information-standard layer, including an England-specific health/adult social care standards point that can reach IT and IT-service providers. ICO guidance now says all DUAA data-protection provisions are in force as of 19 June 2026. The main subject-access guide is updated, while Right of Access in brief, SARs Q&A, research, automated decision-making/profiling, and IDTA/Addendum updates remain tracked where final guidance or companion products are pending.
Supplier products and local solutions must be mapped capability-by-capability, standard-by-standard, role-by-role, and commencement-by-commencement before any compliance claim is safe.

For Executive Summary use, DUAA should be read as a standards-governance test: identify the named NHS England information standard, supplier role, component, and deployment first, then ask whether DUAA section 121 / Schedule 15 changes the standards-applicability analysis. Do not treat DUAA as a DSIC, GP Connect, PRSB, clinical-safety, or InterSystems product compliance label.

For InterSystems, the strongest current reading is component-based:

HealthShare UCR, Clinical Viewer, EMPI, Provider Directory, Health Insight, and related HealthShare components align with shared-care, record-viewing, identity, provider-data, analytics, and patient-facing patterns.
Health Connect and IRIS for Health align with integration, middleware, FHIR, HL7, CDA, document, MESH/ITK, and national-service adapter patterns.
InterSystems FHIR Server and FHIR Services align with managed FHIR repository/API infrastructure.
NHS supplier-progress evidence maps IRIS for Health (Middleware) to GP Connect Send Document (Send) v2.0.1 and HealthShare to specific Access Record: Structured sections; customer deployment proof is still required.
Current public DSIC pages distinguish S99 structured read, S101 document send, and S102 structured write-back, with separate mandatory roles and dependencies. Their effective status does not prove a DMICP/CORTISONE use case or InterSystems implementation.
NHS service/DPIA evidence supports Medicus nationally in GP Connect context, including Patient Facing APIs live with Medicus and Medicus as a new NHS market entrant for GPs, but that does not prove the West Midlands HealthShare route or local artefact pack.
GP2GP is a separate GP-practice record-transfer route. Current public evidence does not prove InterSystems GP2GP provider, requesting, sending, or complete GP foundation-system capability.
SCR, the National Document Repository, FDP, and SPR should be kept separate: SCR is a direct-care summary record, NDR may mean NHS England National Document Repository or Wales National Data Resource depending on source, FDP is an operational/data platform, and SPR is a current programme direction rather than live implementation proof.
Current public evidence does not prove HealthShare alone as a complete DSIC GP foundation clinical system.

Source IDs: SRC-002, SRC-003, SRC-004, SRC-005, SRC-008, SRC-020, SRC-021, SRC-034, SRC-035, SRC-041, SRC-050, SRC-051, SRC-057, SRC-095, SRC-099, SRC-202, SRC-203, SRC-204, SRC-205, SRC-206, SRC-207, SRC-208, SRC-209, SRC-213, SRC-214, SRC-217, SRC-219, SRC-220, SRC-221, SRC-222, SRC-223, SRC-224, SRC-225, SRC-226, SRC-227, SRC-228, SRC-229, SRC-263, SRC-267, SRC-268, SRC-269, SRC-270, SRC-291, SRC-292.

England Adapter Landing

In the Executive Summary diagram, England adapters means the NHS England route set that a Health Connect mediation layer would need to connect to or support where the deployment requires it. It is not a single adapter product.

The safest landing model is:

Adapter group	Main evidence page	Proof boundary
DSIC capability, procurement, standards, assurance, and migration	DSIC Digital Services for Integrated Care, DSIC Standards and National Services, DSIC Procurement, Assurance, and Migration	DSIC compliance remains solution-level and capability-specific. Product relevance is not catalogue, supplier, or deployment proof.
GP Connect and national GP-system routes	GP Connect Deep Dive, GP2GP Record Transfer, NHS Connectivity and GP Connect, NHS Standards Directory GP Connect, MESH, and ITK3	Select S99 structured read, S101 document send, S102 structured update, or another route by workflow. GP Connect, GP2GP, MESH, ITK3, dependencies, supplier roles, supplier-progress rows, and onboarding artefacts must be proven separately; GP2GP record transfer and DMICP/CORTISONE approval are not inferred from GP Connect standard status.
National record and data platforms	NHS National Record and Data Platforms	SCR, NDR, SPR, and FDP have different purposes and proof routes. Disambiguate direct care, document storage, operational/data-platform work, and future single-record programme evidence before assigning an InterSystems role.
Identity, demographics, organisation, and provider data	DSIC Standards and National Services, DSIC HealthShare Compliance Map	PDS, ODS, SDS, EMPI, and Provider Directory claims need product/version, onboarding, synchronisation, stewardship, audit, and clinical-safety evidence.
Shared-care, viewer, FHIR, and integration components	DSIC HealthShare Compliance Map, Health Connect, HealthShare, FHIR Services, SDA and CDA Transformation	Health Connect/HealthShare/IRIS/FHIR capability supports an architecture, but each national-service or customer route needs its own assurance pack.
DUAA standards-governance test	Data (Use and Access) Act 2025, NHS Standards Directory and DHSC Standards Direction, DSIC HealthShare Compliance Map	Use DUAA to ask whether a named NHS England information standard applies to a supplier role in the route. Do not use it as a compliance label or replacement for DSIC, GP Connect, PRSB, DCB0129/DCB0160, IG, or deployment evidence.

Evidence Boundary

Claim type	Current status
DSIC is NHS England-specific digital primary-care operating/procurement/capability evidence.	High.
GP Connect is one NHS England service/API family within the wider digital primary-care environment.	High.
GP2GP is a separate GP-practice record-transfer route and a GP foundation-system concern.	High for NHS England service/standards relevance; no current public InterSystems GP2GP implementation proof.
HealthShare can support DSIC-aligned shared-care/integration architecture.	High for component relevance.
HealthShare is a complete DSIC GP foundation clinical system.	Not proven in current public evidence.
InterSystems products are listed in current DSIC/Buying Catalogue capability entries.	Open evidence gap.
DUAA proves InterSystems DSIC, GP Connect, or NHS Standards Directory conformance.	Not proven; DUAA and ICO guidance are statutory/regulator context, not supplier assurance evidence.

Follow-up

Confirm public DSIC/Buying Catalogue supplier entries naming InterSystems products or partner services.
Map DUAA section 121 / Schedule 15 to NHS England information standards, DSIC standards, and InterSystems supplier roles only where a named standard or deployment requires it; use the GP Connect / MESH / ITK3 child page for that standards cluster.
Confirm any local West Midlands Medicus / HealthShare deployment route with official customer-side architecture, onboarding, IG, and clinical-safety artefacts.
Keep the DSIC capability-to-standard crosswalk current as public DSIC pages change.
Keep England DSIC and GP Connect evidence separate from Scotland, Wales, Northern Ireland, and UK Defence evidence.