Synthesis of existing local research

Local research synthesis

The user's existing local knowledge bases provided a substantial starting taxonomy and several useful evidence distinctions. Their conclusions were treated as research leads. A local page is not a new NHS requirement, and its original source IDs are not interchangeable with this pack's IDs. The companion provenance manifest records exact files, hashes and repository revisions inspected on 28 October 2026.

The local InterSystems notes identified diagnostic Epic E00431. The current C8 page does not contain it. This pack therefore uses the current inspected E00432/E00433 and conditional E00434 instead of carrying forward the older identifier. This is why local synthesis includes source reconciliation, not just text aggregation. ⁰⁶⁴

The most useful additional questions are operational: who owns an outstanding result; what happens after a document is received; who accepts a transferred supplier control; and whether an imported record is complete enough for its stated use. They become explicit review controls or proposed hazard causes, not assertions that a defect exists.

Local research contributions: ^{091, 092, 093, 094}.

Local safety knowledge synthesis

Checked: 28 October 2026, Europe/London. Sibling repositories were read only. Existing local research was used as a discovery and synthesis source, with current primary-source checks for material statutory and clinical-safety points. A local wiki's conclusion is not itself legislation, supplier assurance or deployment evidence.

Retrieval record

In UK Digital Health compliance (the trailing space is part of the directory name), the Graphify query DCB0129 DCB0160 applicability equivalent baseline non-NHS Defence returned 184 nodes, truncated to 50. It surfaced the two intended concepts, their source register and applicability decision tree. Canonical concept files and relevant source-register rows were then read; the graph was navigation only.

In DShCR, the Graphify query GP Connect clinical safety DCB0129 DCB0160 evidence assurance deployment returned 15 nodes about Standard proposal records, with no useful clinical subject recall. This was recorded as poor retrieval. Scoped canonical fallback read GP Connect capabilities, onboarding and internal Defence implementation, then source-register and evidence-matrix rows. No rendered page or generated graph was promoted to evidence.

Findings incorporated into the DSIC synthesis

Primary sources rechecked from these local leads

• ⁰⁸³ — SI 2025/807: Regulation 3 preserves the pre-amendment 2012 Act framework for standards in effect immediately before 7 July 2025. The explanatory note specifically identifies continued section 250(6) have-regard duties. Read the actual notice and contract before deciding a particular organisation's obligation. Official PDF.
• ⁰⁸⁴ — SI 2025/950: Regulation 6 requires published standards to state publication/effective dates, comply-or-have-regard status, consequences and other specified information. This is a reason to inspect the applicable notice, not a finding that every current standard creates an identical duty. Official PDF.
• ⁰⁷⁹ — NHS applicability guide: Existing guidance distinguishes public funding/commissioning, direct-care use, wholly private use and device/infrastructure circumstances. It strongly recommends DCB practice outside some mandatory routes. Its 2022 date and saved statutory context should stay visible. Step-by-step guide.
• GP Connect safety principles (local DShCR SRC-234; this pack ⁰⁸⁵): Direct page review confirms separate supplier/deployment responsibilities and patient-demographic discrepancy checking, while displaying active-review and release-TBC qualifications. Official NHS Connect guide. Proposed new source alias only; ⁰⁸⁵ remains available for root allocation.

The legislation HTML endpoints returned unsupported-content errors; the official PDFs were inspected instead. This is a targeted source check, not a legal opinion on an identified product/deployment.

Local provenance snapshots

These hashes identify the local research bytes used for scoped synthesis. They do not establish primary-source truth or product assurance. No sibling research was changed.