Interfaces and data journeys
Conditional interface applicability inventory
The following inventory is derived from the visible DSIC non-overarching index and capability-relationship guidance. It is a routing list, not a complete transcription of each interface standard. For each applicable family, obtain the selected provider/consumer or sender/receiver specification and assurance evidence 024, 025.
| Family / listed standards | Activate review when | Principal safety questions to investigate (original review prompts) |
|---|---|---|
| NHS CIS2 Authentication; NHS login service/provisioning; Validated Relationship Service | Staff or citizen identity/proxy integration | Can an incorrect identity or expired authority access/act on a record? |
| PDS; Spine Mini Services; NHAIS HA/GP Links; Register with a GP Surgery | Demographics/registration integration | What prevents misidentification, duplicate registration and incorrect record ownership? |
| GP2GP; Requesting/Sending Adaptors | Patient registration transfer | Are missing attachments, degraded facts and incomplete integration visible? |
| GP Connect HTML; Structured; Send Document; Update Record; Appointment Management | Relevant supplier role and operational route | What is read-only, locally filed, changed or merely presented? |
| GP Connect Patient Facing Access Record, Prescriptions, User Permissions; NHS App | Citizen access/transactions | Are proxy scope, redaction, data currency and transaction status correct? |
| EPS – Prescribing; Digital Medicines and Pharmacy FHIR Payload | Electronic prescribing or pharmacy exchange | Can cancellation, duplicate issue or ambiguous medication state cause harm? |
| Digital Diagnostics & Pathology Messaging | Results exchange | Are amended/late/mismatched results reviewed and acted on? |
| e-RS; BaRS; DoS – Urgent and Emergency Care; 111 | Referral/booking/urgent-care integration | Who owns rejected referrals or booking failures and clinical escalation? |
| SCR; NCRS | National clinical summary access/update | Is completeness/currentness clear and is authoritative data distinguished? |
| MESH; ITK; Generic FHIR Receiver; CDA; Transfer of Care FHIR Payload | Transport, document or clinical payload exchange | Are receipt, validation, filing and action separately confirmed? |
| IM1 | Provider/consumer integration or bulk extraction | Are permissions, schema meaning, failure handling and version changes controlled? |
| NEMS; MNS | Event/notification subscriptions | Can lost/repeated/out-of-order events leave stale care information? |
| GPES; GP appointments reporting; primary-care terminology usage reporting | Reporting/extraction role | Can incorrect extraction damage source data or drive unsafe care decisions? |
| National Data Opt-Out | In-scope secondary-use disclosures | Is purpose/exemption handling correct without suppressing direct-care access? |
| NHSBSA claims/reporting; Vaccination Extract | Payment/claims or vaccination reporting | Are clinical facts distinguished from claims status and duplicate events? |
| Electronic Yellow Card; eMED3 | ADR reporting/fit notes | Are identity, authorisation and submission failures handled? |
| Email; NHS Notify | Patient/professional communications | Is the recipient verified and delivery failure actionable? |
| Screening Messaging; SEFT; online consultation/video reporting | Relevant service integration | Are omissions, timing, reconciliation and confidentiality analysed? |
Dependency rule: An available API or standards listing is not evidence that the deployment is onboarded, authorised or connected. A closed network may require approved gateways, local alternatives or explicit exclusions. Do not presume HSCN, internet connectivity, Spine access or an NHS Smartcard alone supplies all identity, authorisation and service permissions. Document the actual architecture and approved interface dependencies.
Security/medical-device standards: Identify contractually or regulatorily adopted ISO/IEC 27001, ISO 22301/27031, ISO/IEC/IEEE 29119, ISO 14971, IEC 62304, IEC 62366-1 and IEC 80001-1 editions where relevant. They are related assurance frameworks, not automatically universal DSIC requirements or interchangeable certificates. This file does not reproduce or verify their licensed clauses. Obtain locally authorised copies and applicability decisions before making clause-level findings. S69 explicitly uses the testing standard as a reference point rather than mandating certification 008, 009, 011, 046.