DSIC Capability-to-Standard Crosswalk
This page turns the DSIC capability-to-standard relationship into a structured crosswalk for analysis. It is not a replacement for the public DSIC pages; it is the wiki's working map for asking what a supplier or product must prove before a DSIC capability claim is safe.
The crosswalk uses existing source IDs and should be read with DSIC GP Foundation Capabilities, DSIC Standards and National Services, and DSIC HealthShare Compliance Map.
Crosswalk
| Capability or service component | Main DSIC / NHS standards and services to check | InterSystems relevance | Proof needed for compliance claims |
|---|---|---|---|
| Patient Information Maintenance - GP | PDS, NHS number handling, ODS/SDS registered-practice and organisation context, NHAIS, GP2GP, SCR, GP Connect Access Record, GP Connect Send Document receiving, GP Connect Update Record receiving, patient-facing APIs, GPES, National Data Opt-Out, NEMS, MESH/MNS, registration and record-transfer controls. | HealthShare EMPI can support identity matching; HealthShare Provider Directory can support provider/organisation data; Health Connect/IRIS can support integration; HealthShare UCR can consume and present patient-record data. | DSIC capability listing, PDS onboarding, ODS/SDS mapping, GP2GP/provider obligations if acting as foundation system, GP Connect role, demographic governance, NHS number policy, organisation-code governance, audit, clinical safety. |
| Appointments Management - GP | GP Connect Appointment Management, GP Appointment Data, patient-facing appointment access, local appointment book workflow, audit and reporting. | HealthShare can present integrated context; Health Connect/IRIS can integrate appointment data where approved. | Foundation appointments UI/service, GP Connect appointment status where claimed, GPAD reporting, patient-facing access controls, local booking/cancellation workflow evidence. |
| Consultation Management - GP | GP clinical record content, coded/uncoded entry, eMED3, Yellow Card, GP Connect record exposure, reporting/extraction, clinical-safety controls. | HealthShare can consume/present consultation data; Health Connect/IRIS can route and transform; FHIR Server can expose FHIR resources where governed. | Foundation consultation workflow, coding/terminology controls, clinical-safety case, GP Connect provider/consumer role evidence, record-amendment and audit rules. |
| Prescribing | EPS, dm+d, medicines standards, patient-facing prescription visibility, medication-safety workflows, repeat prescribing, audit, downstream record-sharing. | HealthShare can aggregate medicines views; Health Connect/IRIS can integrate medication messages/data. | GP prescribing module, EPS assurance, dm+d integration, decision-support/safety controls, repeat workflow, audit, clinical-safety case. |
| Referral Management - GP | e-RS, Directory of Services, referral letters, attachments, document exchange, advice and guidance, status workflow. | Health Connect/IRIS can integrate referral messages/documents; HealthShare can show referral context. | e-RS onboarding, referral workflow UI, document/attachment handling, status reconciliation, audit, clinical-safety evidence. |
| Document Management - GP | GP Connect Send Document, GP Connect Access Document, MESH, ITK3, ODS/SDS sender/receiver and endpoint context, transfer-of-care FHIR, document filing, coding, attachment handling, workflow queues. | Health Connect/IRIS are strongly relevant as message/document integration layers; Provider Directory may support local organisation/provider context where configured; HealthShare can show filed documents in context. | MESH mailbox and certificates, payload conformance, workflow IDs, ODS/SDS mapping, filing rules, exception handling, audit, supplier-progress/customer evidence. |
| Task and Workflow Management | Work queues, delegation, reminders, review, completion, audit, clinical-safety and service-management standards. | HealthShare Care Community may support care-management workflows; HealthShare viewer can support direct-care action context. | Role model, queue ownership, escalation, audit, safety case, local operating procedure, service-management evidence. |
| Reporting and Extraction | GPAD, GPES, local reporting, contractual reporting, data-quality controls, extracts, secondary-use governance. | Health Insight, IRIS, FHIR Server, OMOP, and UCR data can support analytics and reporting patterns. | Reporting specification, extraction approval, pseudonymisation or identifiable-data basis, data-quality controls, governance, customer reporting evidence. |
| Scanning and Filing | Document scanning, classification, patient-record linkage, workflow distribution, audit, retention. | Health Connect/IRIS can integrate scanned-document flows; HealthShare can present documents once indexed and governed. | Scanning workflow, indexing and matching rules, retention, audit, exception handling, local operational evidence. |
| Patient-facing services | NHS login, NHS App, GP Connect Patient Facing APIs, appointments, prescriptions, record access, messaging, proxy access, safeguarding controls. | Personal Community may support digital-front-door patterns; HealthShare can supply record data where governed. | NHS login integration, patient-facing API assurance, proxy/access policy, content controls, accessibility, clinical-safety and safeguarding evidence. |
| Personal Health Record | Patient record presentation, patient-contributed data, messaging, questionnaires, access/proxy controls, NHS login or patient identity route. | Personal Community and HealthShare can support record access and patient engagement patterns. | DSIC capability listing, identity proofing, consent/proxy rules, data provenance, write-back boundaries, safety and IG evidence. |
| Unified Care Record | PRSB Core Information Standard, GP Connect consumer access, PDS/identity, ODS/SDS provider and organisation identity, NRL/events where applicable, shared-care governance, viewer access, consent/RBAC/audit. | HealthShare UCR, Clinical Viewer, EMPI, Provider Directory, Health Insight, and Health Connect are directly relevant. | DSIC capability scope, PRSB/CIS evidence, source-system mappings, GP Connect onboarding, PDS FHIR onboarding where used, ODS/SDS mapping, data-sharing agreement, DPIA, RBAC, audit, local go-live evidence. |
| Online consultation, video consultation, advanced telephony, and digital pathways | DSIC non-foundation service frameworks, Tech Innovation Framework, patient messaging, NHS 111/pathway dependencies where applicable, clinical triage and routing. | HealthShare can provide record context; Health Connect/IRIS can integrate pathway outputs; partner products may provide the front-end workflow. | Framework/catalogue listing, triage model, clinical-safety case, integration contract, record update/document route, operational support evidence. |
Source IDs: SRC-020, SRC-021, SRC-026, SRC-027, SRC-038, SRC-039, SRC-040, SRC-041, SRC-047, SRC-057, SRC-061, SRC-062, SRC-063, SRC-064, SRC-065, SRC-095, SRC-099, SRC-132, SRC-184, SRC-185, SRC-186, SRC-194, SRC-202, SRC-203, SRC-204, SRC-205, SRC-206, SRC-207, SRC-208, SRC-209, SRC-210, SRC-211, SRC-234, SRC-235.
How to Use This Crosswalk
For any supplier or product claim:
- Identify the exact DSIC capability.
- Identify whether the product is acting as a foundation provider system, consumer system, shared-care platform, integration middleware, patient-facing service, analytics service, or workflow adjunct.
- Check the standards and national services in the row.
- Require supplier/catalogue evidence for the capability and implementation evidence for the national-service role.
- Record any gap in the Evidence Validation Queue.
InterSystems Boundary
This crosswalk strengthens the component interpretation:
- HealthShare maps most strongly to Unified Care Record, clinical-viewer, identity, provider-directory, shared-care, and analytics roles.
- Health Connect and IRIS map most strongly to integration and middleware roles.
- FHIR Server maps to FHIR repository/API infrastructure roles.
- ODS/SDS is explicit in this crosswalk after the PDS/ODS identity-directory pass, but it remains national-service dependency evidence. It does not prove Provider Directory implementation unless a source names product/version, mapping, synchronisation, stewardship, audit, and deployment scope.
- None of those roles automatically proves foundation GP clinical-system compliance.
Follow-up
- Capture exact DSIC page references for each capability if a procurement-grade crosswalk is needed.
- Add supplier-specific rows if InterSystems or a partner appears in DSIC/Buying Catalogue evidence.
- Keep this page aligned with DSIC public-page changes and Digital Primary Care replacement-framework updates.