NHS England Digital Primary Care Evidence Domain
This domain page groups the DSIC, GP Connect, NHS England standards, GP software integration, Buying Catalogue, migration, and InterSystems component evidence. It is a working slice of Sources and Evidence Matrix, not a replacement for them.
Domain Boundary
NHS England Digital Primary Care includes DSIC, GP Connect, NHS England primary-care digital procurement, GP software national-service integration, and standards needed for GP and integrated-care digital services in England.
It excludes:
- Scotland, Wales, and Northern Ireland national-service equivalents unless used as contrast.
- UK Defence healthcare unless an NHS England route is explicitly involved.
- Generic InterSystems product positioning unless the claim maps to a DSIC/GP Connect/NHS England service role.
Source Clusters
| Cluster | What they support |
|---|---|
| GP Connect service and API model | GP Connect service definition, capabilities, architecture, supplier progress, utilisation, roadmap, NCRS, NHS App, Single Patient Record, current API/status context, National Data Sharing Arrangement context, and official national Medicus service/DPIA evidence. |
| NHS standards, statutory data layer, and national-service surface | Information standards, DAPB/DAB governance, Standards Directory, DUAA staged commencement, health/adult social care IT standards power, FHIR/UK Core, GP Connect, MESH/ITK3, PDS/events, ODS organisation data, terminology, medicines, clinical safety, transfer of care, shared-record/life-stage, imaging, diagnostics, ITK conformance route, ICO data-protection-provision status, topic guidance, subject-access guidance, and guidance pipeline. |
| DSIC operating model and capability standards | DSIC overview, GP digital-services operating model, capability and standards pages, capability-to-standard relationships, GP software national services, Buying Catalogue, clinical migration, Tech Innovation, digital tools, advanced telephony, and Digital Primary Care replacement-framework procurement. |
| InterSystems component relevance | HealthShare, UCR, Clinical Viewer, Health Connect, IRIS for Health, FHIR Server, EMPI, Provider Directory, Health Insight, Personal Community, PRSB CIS conformance, InterSystems GP Connect supplier-progress boundaries, PDS integrated-products evidence for Intersystems HealthConnect 2020.1, PDS/ODS identity-directory dependency boundaries, Birmingham / West Midlands artefact-pack context, current Medicus integration signalling, and official national Medicus GP Connect context. |
Evidence Claims
| Claim | Evidence status | Canonical detail |
|---|---|---|
| DSIC is an NHS England digital primary-care procurement, capability, standards, assurance, migration, and Buying Catalogue environment. | High. | DSIC Digital Services for Integrated Care |
| DSIC is wider than GP Connect. GP Connect is one service/API family inside the wider NHS England digital primary-care environment. | High. | NHS England Digital Primary Care, GP Connect Deep Dive |
| DSIC GP foundation capabilities need capability-by-capability and standard-by-standard analysis. | High for visible DSIC model; supplier-specific claims still need evidence. | DSIC GP Foundation Capabilities, DSIC Capability-to-Standard Crosswalk |
| DUAA adds a statutory data and information-standard layer to England health/adult social care, including potential applicability to IT and IT-service providers, but it is not DSIC/GP Connect supplier assurance by itself. ICO now says all DUAA data-protection provisions are in force as of 19 June 2026. | High for statutory and regulator-context reading; supplier-specific claims still need evidence. | Data (Use and Access) Act 2025, NHS Standards Directory and DHSC Standards Direction, NHS Standards Directory GP Connect, MESH, and ITK3 |
| GP Connect / MESH / ITK3 dependency mapping now needs a child-page level role split covering GP foundation provider, consumer, document sender, middleware, viewer, and patient-facing routes. | High as wiki structure; implementation claims still need supplier/customer evidence. | NHS Standards Directory GP Connect, MESH, and ITK3 |
| NHS England material supports Medicus in the national GP Connect context, including supplier-progress rows, Patient Facing APIs live with Medicus, Access Document FoT-ready status for Medicus, and the GP Connect DPIA naming Medicus as a new NHS market entrant for GPs. | High for national Medicus GP Connect status; boundary for any named local HealthShare deployment route. | GP Connect InterSystems Supplier Progress, Birmingham and West Midlands Validation |
| HealthShare can support DSIC-aligned shared-care and integration architecture. | High for component relevance. | DSIC HealthShare Compliance Map |
| EMPI / Provider Directory evidence now has stronger PDS/ODS dependency definition, but no direct public implementation proof for those components. | High for national-service requirements; boundary for InterSystems component implementation. | HealthShare EMPI, HealthShare Provider Directory, DSIC HealthShare Compliance Map |
| HealthShare alone is a complete DSIC GP foundation clinical system. | Not proven. | Evidence Validation Queue |
InterSystems IRIS for Health (Middleware) has an NHS supplier-progress row for GP Connect Send Document (Send) v2.0.1. |
High for NHS table mapping; implementation proof still required. | GP Connect InterSystems Supplier Progress |
| InterSystems HealthShare has NHS supplier-progress row evidence for specific Access Record: Structured sections. | High for parsed NHS table mapping; customer deployment proof still required. | InterSystems GP Connect Evidence Boundary |
Open Evidence Work
- Public DSIC/Buying Catalogue listings naming InterSystems products or partner services.
- Current-source check on 2026-06-21 found DSIC and Digital Primary Care framework/procurement evidence but no public indexed DSIC/Buying Catalogue or Find a Tender listing naming InterSystems, HealthShare, Health Connect, IRIS for Health, or a partner capability scope. Reopen when a supplier listing, award, catalogue row, or customer/procurement artefact appears.
- DUAA commencement and ICO guidance tracking for remaining non-data-protection staged provisions, Right of Access in brief, SARs Q&A, research, automated decision-making/profiling, IDTA/Addendum transfer material, and enforcement/code process updates. Complaints, recognised legitimate interests / lawful basis / purpose limitation, storage/access technologies, the main subject-access guide, and parts of international transfers now have ICO guidance rows.
- DUAA section 121 / Schedule 15 mapping to NHS England information standards and supplier applicability for named products, IT services, or deployments.
- Structured capture of DSIC capability-to-standard relationships from public Confluence pages.
- Product/customer validation of the parsed GP Connect supplier-progress cell mapping for InterSystems rows.
- Official customer-side confirmation of the West Midlands Medicus / HealthShare integration route, including local GP Connect, MESH, ITK3, DSA/NDSA, DPIA, DCB0129/DCB0160, and supplier-responsibility artefacts.
- Product-specific InterSystems implementation documentation for PDS, ODS/SDS, GP Connect, MESH, ITK3, EPS, e-RS, NHS login, GP2GP, and other DSIC national services.
- Deployment artefacts for any HealthShare-backed DSIC solution: DPIA, DSA, clinical-safety case, architecture, onboarding, certificates, migration, training, and go-live evidence.