DSIC GP Foundation Capabilities
This page explains the DSIC capability model as it applies to GP system and software/service components in England. DSIC capability pages describe business requirements, epics, acceptance criteria, additional implementation detail, standards links, supplementary-care variants, and interoperability relationships. A supplier can therefore be assessed for specific capabilities and standards rather than being treated as generically "NHS compliant".
Use DSIC Capability-to-Standard Crosswalk for the structured capability-to-standard map.
Foundation System Reading
The NHS England primary-care operating model describes a GP IT foundation solution as the core GP digital service that supports essential general-practice operations. DSIC then exposes the capability and standards detail used to assess supplier products and service components.
For analysis, a full GP foundation system should be treated as a bundle of capabilities:
| Capability area | Role in a GP system | Why it matters for DSIC compliance |
|---|---|---|
| Patient information maintenance | Patient demographics, registration status, record maintenance, identifiers, access permissions, record transfer, and links to national demographics and record services. | It is the patient-record anchor for PDS, GP2GP, NHAIS, SCR, GP Connect, patient-facing APIs, GPES, and related national services. |
| Appointments management | Appointment books, slot types, booking/cancellation/viewing, internal and external appointment flows, and appointment reporting. | It connects foundation GP workflows to GP Connect appointment management, GP Appointment Data, and patient-facing access where in scope. |
| Consultation management | Capturing and managing consultation activity, clinical notes, problems, coded entries, documents, forms, and workflow outcomes. | It feeds clinical record quality, reporting, eMED3, Yellow Card reporting, GP Connect consumer/provider use, and wider clinical-safety obligations. |
| Prescribing | Medication selection, issue, repeat prescribing, clinical checks, prescriptions, and dispensing-related workflows. | It is central to EPS, dm+d, medication safety, patient-facing prescription visibility, GP record quality, and connected-care medicines workflows. |
| Referral management | Referrals, advice and guidance, service selection, referral letters, attachments, referral status, and onward communication. | It connects GP workflow to e-RS, Directory of Services, document messaging, clinical documents, and transfer-of-care standards where in scope. |
| Document management | Incoming and outgoing clinical documents, attachments, filing, coding, workflow distribution, scanning linkage, and audit. | It connects to MESH, ITK, GP Connect Send Document, Access Document, transfer-of-care FHIR, and local record quality. |
| Task and workflow management | Administrative and clinical tasks, work queues, delegation, review, completion, and audit. | DSIC compliance is operational as well as technical. A GP supplier must support safe work routing, service management, and user accountability. |
| Reporting | Contractual, operational, clinical, prescribing, appointments, extraction, audit, and population reporting. | Reporting links GP workflows to GPAD, GPES, terminology usage reporting, medicines safety, PCN/ICB oversight, and secondary-use extraction boundaries. |
| Scanning | Document capture, classification, linkage to patient records, filing workflow, and audit. | Scanning matters because legacy and external clinical documents still enter GP systems outside purely structured APIs. |
| Citizen and patient-facing services | Online record access, appointments, prescriptions, messaging, personal health record, questionnaires, and NHS App / NHS login related access. | Patient-facing services may depend on GP Connect Patient Facing APIs, NHS login, NHS App direction, proxy access, and user-permission controls. |
| Shared and integrated care | Unified care record, shared-care workflow, interoperability, cross-setting visibility, and record access. | DSIC includes capabilities beyond a single GP practice system. This is where HealthShare and connected-care platforms become relevant, but only at the capabilities they actually provide. |
Capability Detail Pattern
The public DSIC capability pages follow a repeated pattern:
- A stated capability description.
- Epics and acceptance criteria.
- Additional implementation details.
- Mapped standards and interface dependencies.
- Where applicable, supplementary-care standard relationships.
- Release notes or DSIC portal links.
This pattern matters because "supporting appointments" or "supporting prescribing" is not enough. DSIC compliance requires the assessed product to satisfy the capability and standards detail that NHS England attaches to that capability.
Core GP Workflow Shape
The core GP workflow implied by the DSIC foundation capability set is:
- Register and identify the patient.
- Maintain the patient demographic and clinical record.
- Book, manage, and report appointments.
- Conduct consultations and capture coded/uncoded clinical content.
- Prescribe safely and send prescriptions through the relevant national route.
- Refer, message, and exchange documents with other services.
- Receive, file, scan, and act on inbound documents and messages.
- Manage tasks, reminders, workflow queues, and audit trails.
- Report activity, quality, appointments, extracts, and contractual data.
- Expose appropriate record access and patient-facing functions.
The interoperability page for DSIC capabilities links this core workflow to national services. For example, patient information maintenance carries dependencies around PDS, GP2GP, NHAIS, SCR, GP Connect Access Record, GP Connect Send Document receiving, Update Record receiving, patient-facing APIs, GPES, National Data Opt-Out, NEMS, Message Exchange, and related national services. Appointments management links to GP Connect appointment management and GPAD. Consultation management links to Yellow Card and eMED3, and prescribing links to the national prescribing and medicines standards context.
Foundation Versus Modular Components
DSIC analysis should separate three supplier patterns:
| Supplier pattern | Example role | DSIC interpretation |
|---|---|---|
| Foundation GP clinical system | The system of record used by a practice for registration, clinical record, appointments, prescribing, referrals, documents, tasks, reporting, and national-service connectivity. | Must satisfy a broad foundation capability set and its mapped standards. |
| Modular GP service | Online consultation, patient messaging, advanced telephony, care navigation, remote monitoring, referral support, reporting, or specialist workflow. | Can be DSIC-relevant for a narrower capability, but does not become a foundation system unless assessed as one. |
| Shared-care or integration platform | Unified care record, clinical viewer, integration engine, FHIR repository, identity service, provider directory, analytics, or middleware. | Can support DSIC and NHS connectivity, but needs explicit capability mapping and often depends on a foundation system or national-service adapters. |
InterSystems Reading
HealthShare and related InterSystems products are strongest against the shared-care and integration side of the DSIC model:
- HealthShare Unified Care Record aligns conceptually with DSIC shared/unified care-record needs because it aggregates, normalises, and deduplicates records into a longitudinal view.
- HealthShare Clinical Viewer aligns with direct-care presentation needs, but it is a viewer, not a full GP foundation transaction system by itself.
- Health Connect and IRIS for Health align with integration, transformation, API, and middleware patterns needed around DSIC standards and national services.
- HealthShare PRSB Core Information Standard conformance strengthens a shared-care-record content reading, but it does not prove DSIC foundation-system compliance.
The cautious conclusion is that InterSystems can plausibly contribute major DSIC solution components, especially for shared care, interoperability, GP Connect consumption, and national-service integration. A complete DSIC GP foundation-system claim would still require explicit assessment evidence for the GP capabilities above.
Follow-up Evidence
- Find public DSIC capability entries or catalogue records naming InterSystems products or partner services.
- Confirm which DSIC capabilities, if any, are directly covered by HealthShare, Health Connect, IRIS for Health, TrakCare, or a partner application.
- Pair each capability claim with the exact DSIC standard, interface, onboarding, clinical-safety, and information-governance evidence.