DSIC Digital Services for Integrated Care
Digital Services for Integrated Care (DSIC) is NHS England's digital primary-care procurement, capability, standards, and assurance environment for general practice and related digital services in England. NHS England Digital says the products and services developed by the GP IT Futures programme have evolved into the DSIC model, and DSIC is explicitly England-specific in this wiki. Scotland, Wales, and Northern Ireland have separate national digital-health stacks and should not be described as DSIC-compliant unless a future official source says so.
Use NHS England Digital Primary Care as the parent for DSIC and GP Connect together. Use this page as the DSIC router, then use the child pages for GP foundation capabilities, capability-to-standard mapping, standards and national-service dependencies, procurement and migration, and the InterSystems HealthShare compliance interpretation.
For adjacent statutory data and information-standard context, use Data (Use and Access) Act 2025. DUAA is not DSIC, but its England health/adult social care information-standard provision is relevant when assessing whether a named NHS information standard applies to an IT supplier or IT service provider.
For the HealthShare side of that interpretation, use the HealthShare Components Evidence Domain to keep HealthShare component taxonomy, deployment evidence, standards relevance, AI Assistant evidence, and DSIC adjacency separate from DSIC foundation-system claims.
What DSIC Is
DSIC is not a single system, API, or product. It is the NHS England environment that combines:
| DSIC layer | What it governs | Practical meaning |
|---|---|---|
| Procurement route | Frameworks and catalogues for digital services used by GP practices, PCNs, ICBs, and other care settings. | Buyers use DSIC routes and the Buying Catalogue to identify and buy assured capabilities rather than treating GP software as an ordinary commodity purchase. |
| Capability model | Business capabilities such as patient information maintenance, appointments, consultation, prescribing, referrals, reporting, scanning, document handling, messaging, online consultation, patient messaging, personal health record, and unified care record. | Supplier offers are assessed at capability level, and a product can be in scope for one capability set without being a full GP foundation system. |
| Standards model | Overarching and non-overarching standards, including clinical safety, information governance, hosting, service management, data migration, training, interoperability, GP Connect, GP2GP, PDS, ODS/SDS, EPS, MESH, e-RS, NHS login, ITK, NHAIS, GPAD, GPES, SCR, NEMS, and other national services. | Compliance is not only functional. It also depends on standards, APIs, workflows, assurance, testing, onboarding, and operating controls. |
| GP operating model | The operating model for GP IT and digital services, including core GP IT foundation solutions and ICB/practice responsibilities. | A full GP clinical system must cover the foundation capability set and must fit the primary-care operating model, not just expose interfaces. |
| Migration and lifecycle | Migration guidance, data migration, training, catalogue agreement, supplier responsibilities, order changes, mergers/splits, and service transition. | Moving GP practices between systems is treated as a planned clinical, operational, data, and supplier-transition event. |
| Innovation route | Tech Innovation Framework and other DSIC frameworks for modular, cloud-hosted, API-enabled digital tools. | DSIC can also cover non-foundation services that integrate with GP foundation systems and national services. |
England-Only Boundary
DSIC is part of the NHS England primary-care digital environment. It is connected to GP Connect, Spine, PDS, ODS/SDS, GP2GP, SCR, EPS, e-RS, NHS login, MESH, ITK, and other England service-stack components. The wiki already treats Scotland, Wales, and Northern Ireland separately because their digital-health equivalents are functionally similar in places but do not use the same DSIC operating model.
This matters for InterSystems analysis:
- A product can be relevant to NHS England connectivity without being a DSIC foundation GP clinical system.
- GP Connect evidence is not the same as DSIC evidence, although DSIC standards can require GP Connect capability.
- HealthShare evidence in Scotland, Wales, Northern Ireland, or UK Defence should not be re-labelled as DSIC evidence.
- A DSIC-compliant deployment is a supplier, service, capability, standards, assurance, and local operating-model claim. It is not proven by product-brand positioning alone.
DSIC Relationship to GP Connect
GP Connect is one standards/service family inside the wider DSIC and NHS England digital primary-care environment. GP Connect provides approved routes for GP record access, document messaging, appointments, update-record workflows, and patient-facing routes. DSIC uses capability and standards assessment to decide which products and suppliers can offer these and adjacent functions through the catalogue model.
The distinction should stay explicit:
| Question | DSIC answer | GP Connect answer |
|---|---|---|
| What is being assessed? | Supplier services, business capabilities, standards, hosting, service management, data migration, training, and interoperability obligations. | Specific NHS APIs or messaging patterns for GP record, document, appointment, update-record, or patient-facing access. |
| Who uses it? | GP practices, PCNs, ICBs, NHS England, suppliers, and buyers of primary-care digital services. | Approved provider and consumer systems in defined direct-care or patient-facing use cases. |
| Does InterSystems evidence prove it? | Only where InterSystems or a specific InterSystems-backed service is assessed and listed for a DSIC capability/standard or customer deployment. | Only where NHS supplier progress, InterSystems documentation, or customer implementation evidence proves a specific GP Connect role. |
DSIC Pages in This Wiki
- DSIC GP Foundation Capabilities
- DSIC Capability-to-Standard Crosswalk
- DSIC Standards and National Services
- DSIC Procurement, Assurance, and Migration
- DSIC HealthShare Compliance Map
Current Evidence Reading
The current public source set supports DSIC as a thorough capability and standards framework for English digital primary care, with visible public Confluence pages for capabilities, standards, supplier-facing guidance, and interoperability relationships. The strongest official sources are NHS England Digital pages, DSIC Confluence pages, the Buying Catalogue buyer guidance, the primary-care GP digital-services operating-model page, and the Digital Primary Care replacement-framework procurement notice.
The current source set does not prove that InterSystems HealthShare is a complete DSIC GP foundation system. It supports a more careful conclusion: HealthShare, Health Connect, IRIS for Health, and related InterSystems components can satisfy or support important DSIC-adjacent shared-record, interoperability, identity, FHIR, integration, analytics, and clinical-viewer requirements, but a full DSIC GP solution would need capability-specific assessment, national-service adapters, clinical-safety and information-governance evidence, migration and training artefacts, and possibly a separate GP EPR or workflow application layer.
Anchor Audit Notes
The current DSIC anchor model remains valid after the HealthShare cross-check. DSIC is solution-level, capability-level, standards-level, and England-specific. HealthShare relevance should be mapped to one or more explicit roles:
- Shared-care record, clinical viewer, identity, provider directory, analytics, or patient-facing component.
- Health Connect or IRIS for Health integration/middleware route for national-service connectivity.
- Partnered service beside a DSIC GP foundation supplier.
- Bespoke application built on InterSystems platforms that would still need full DSIC assessment.
The unresolved model gaps are now explicit in the Evidence Validation Queue: catalogue/supplier evidence, GP foundation completeness, national-service ownership, clinical-safety ownership, data-controller/processor roles, migration/training responsibility, and customer deployment artefacts.
Remaining Evidence Gaps
- Confirm any public DSIC catalogue entries naming InterSystems, HealthShare, Health Connect, IRIS for Health, or an InterSystems-backed customer service by capability.
- Structurally parse the DSIC capabilities and standards pages into a stable local reference if the public Confluence structure changes.
- Pair DSIC capability claims with implementation-specific evidence: supplier listing, assessed capability scope, national-service onboarding, clinical-safety case, information-governance pack, and local deployment design.
- Keep England DSIC evidence separate from the already covered Scotland, Wales, Northern Ireland, and UK Defence evidence sets.