DSIC Procurement, Assurance, and Migration
DSIC is also a commercial and operating route. It defines how NHS England, ICBs, GP practices, PCNs, and suppliers buy, change, migrate, and assure GP digital services in England.
Procurement Context
The NHS England DSIC page frames DSIC as the route for digital tools supporting integrated care and general practice, including frameworks for GP IT foundation systems, non-foundation services, patient online consultation and video consultation, advanced telephony, and the Tech Innovation Framework.
The public procurement record for Digital Primary Care says NHS England intends a new framework to replace the current Digital Care Services catalogue frameworks and that the procurement is intended to cover core and non-core digital primary-care capability. This reinforces the need to treat DSIC frameworks as versioned procurement infrastructure rather than permanent static lists.
Buyer Route
The Buying Catalogue buyer guidance is the practical buyer-facing route for DSIC-style services. It explains that buyers use the catalogue to identify solutions, review capabilities, compare services, run competitions where needed, place orders, and manage changes such as contract extensions, practice mergers/splits, and supplier moves.
| Buyer question | DSIC answer | Evidence boundary |
|---|---|---|
| Where does a buyer start? | With the Buying Catalogue and the relevant framework or capability set. | Catalogue presence supports procurement eligibility, not implementation success. |
| Is direct award possible? | The buyer guidance describes direct-award and competition patterns depending on route and circumstances. | Buyers still need local procurement governance and value-for-money assessment. |
| Are all services foundation GP systems? | No. DSIC includes foundation and non-foundation services. | A modular service should not be described as a full GP clinical system without foundation capability evidence. |
| Can a service be changed after purchase? | The buyer guidance covers order changes, extensions, mergers/splits, and related catalogue processes. | Local contract and service obligations still govern exact change handling. |
Supplier Assurance Pattern
DSIC supplier assurance is capability and standards based. A supplier must show that its service meets the requirements for the capability being offered and the attached standards. For GP Connect specifically, NHS supplier-progress material shows that capability status depends on development, assurance, testing, and first-of-type deployment, with provider and consumer status tracked by supplier and version.
The practical assurance evidence pack for a DSIC-relevant service should include:
- Catalogue agreement and service listing evidence.
- Capability scope and standards scope.
- Clinical safety case and DCB0129 manufacturer evidence.
- Information-governance and data-protection evidence.
- Hosting, resilience, business continuity, disaster recovery, service management, and support evidence.
- NHS national-service onboarding evidence for PDS, GP Connect, GP2GP, EPS, e-RS, MESH, ITK, NHS login, or other routes in scope.
- Test evidence, conformance evidence, endpoint/mailbox/certificate setup, first-of-type or rollout evidence where required.
- Data migration, cutover, rollback, training, and service-transition artefacts.
- Customer-side deployment evidence for local configuration and live use.
Source IDs: SRC-041, SRC-176, SRC-182, SRC-184, SRC-185, SRC-193, SRC-203, SRC-204, SRC-206, SRC-208.
Clinical System Migration
NHS England's clinical system migration guide is aimed at helping commissioners and practices prepare for and complete migration between established GP foundation suppliers. It is relevant because DSIC compliance is not only about the target software. The migration work affects patient-record completeness, coding quality, attachment handling, workflow continuity, downtime planning, user training, and clinical safety.
For DSIC analysis, migration evidence should be requested whenever a product is proposed as a replacement or core system:
| Migration area | What to verify |
|---|---|
| Scope | Which practices, PCNs, services, registers, attachments, documents, tasks, appointment books, prescriptions, templates, and reporting artefacts are in scope. |
| Data extraction and mapping | Source-system exports, mapping specification, structured and unstructured record handling, coding/terminology mapping, validation checks, and exception handling. |
| National services | PDS, GP2GP, EPS, SCR, e-RS, MESH, NHS login, GP Connect, GPAD, GPES, and other national routes before, during, and after cutover. |
| Clinical safety | Hazard log, safety case, cutover risks, degraded-mode workflows, recovery plan, sign-off, and post-migration monitoring. |
| User readiness | Role-specific training, super-user support, workflow rehearsal, go-live command structure, and service desk arrangements. |
| Assurance | Test results, reconciliation evidence, issue log, residual risks, and business acceptance. |
Tech Innovation and Modular Services
The Tech Innovation Framework is part of the DSIC service family and is positioned around introducing innovative, cloud-hosted, browser-based, open-API digital tools into primary-care workflows. It supports a modular model where services can integrate with GP foundation systems instead of replacing them.
Digital pathways, online consultation, video consultation, messaging, advanced telephony, remote patient monitoring, and other workflow services therefore need a different evidence reading from foundation GP clinical systems:
- They may be DSIC-compliant for a narrow capability.
- They may depend on a foundation GP system for the legal patient record.
- They may need IM1, GP Connect, NHS login, MESH, or other national routes for integration.
- They may introduce new clinical-safety, triage, prioritisation, routing, notification, and audit obligations.
- They may depend on local practice/PCN/ICB configuration and workflow governance.
InterSystems Procurement Interpretation
For InterSystems, DSIC procurement and assurance should be read at solution level:
| InterSystems product/service | Likely procurement role | Assurance implication |
|---|---|---|
| HealthShare Unified Care Record | Shared-care-record, integrated-care, longitudinal-record, and data-unification component. | Strong fit for UCR/shared-record analysis, but not a full GP foundation-system claim. |
| HealthShare Clinical Viewer | Clinical presentation layer for direct-care users. | Needs SSO, RBAC, audit, user access, clinical-view template, and local deployment evidence. |
| Health Connect | Integration engine or managed integration service. | Needs interface-specific evidence for PDS, MESH, ITK, GP Connect, EPS, e-RS, HL7, FHIR, CDA, DICOM, and other routes used. |
| IRIS for Health | Healthcare data/application platform and possible middleware/application layer. | Needs DSIC capability and national-service evidence for any GP system role. |
| FHIR Services / FHIR Server | Managed FHIR repository/API infrastructure. | Needs profile/package, validation, OAuth, hosting, tenancy, UK-region, service-level, and DSIC standard evidence. |
| TrakCare or IntelliCare | EHR context. | Current wiki evidence does not prove DSIC foundation-system accreditation. Use only if a DSIC or NHS source names the product and capability. |
Follow-up Evidence
- Locate current public DSIC catalogue listings for any InterSystems product, partner product, or HealthShare-backed service.
- Track the Digital Primary Care replacement framework as procurement documents move from notice to award.
- For any InterSystems DSIC proposal, request the capability matrix, standards matrix, clinical-safety case, data-migration pack, national-service onboarding pack, and catalogue listing evidence.