# Validation queue The subject is legally required digital sending and availability of healthcare information across all four nations. Individual care is primary, with planning, research and public-health flows included. The [requirements table](https://uk-digital-healthcare-legal-requirements.pages.dev/digital-requirements/index.md) distinguishes verified obligations from qualified standards, medium-neutral duties and operational evidence. Completed bounded findings remain closed unless their stated trigger arises. | ID | Gap | State | Next action | blocked_by | reopen_when | last_checked | |---|---|---|---|---|---|---| | VAL-001 | Scottish Care Reform sections 2–7 | Resolved dated status; parked implementation trail | Retain section 1 ministerial duty and prospective sections 2–7; inspect a new official instrument/status change if one appears | No current status gap; no operative provider scheme inferred | New official implementation evidence or explicit user instruction | 2026-11-03 | | VAL-002 | NI 2016 Act secondary-use machinery | Resolved current-status finding; parked implementation trail | Preserve commenced Act versus pending machinery distinction in the implementation record | Published record supports pending machinery; no project approval or universal digital return supplied | New official instrument/status evidence, due recheck or explicit user instruction | 2026-11-03 | | VAL-003 | Standards transitions and proposed record reforms | Current dated position recorded; event-triggered | Read any new notice, enacted text and commencement before attributing a new digital duty | Future law/notice cannot be assumed; old information standards have statutory saving qualifications | New law/notice or a specific operational reliance | 2026-11-03 | | VAL-004 | Actual local, private-provider and service contracts/directions | Unverified arrangements; evidence-blocked | Inspect one named provider’s adopted contract, service categories, local protocol, direction and recipient-specific digital clause | No executed local/private contract or complete Trust/Board instruction set supplied | A named flow and actual governing documents become available | 2026-11-03 | | VAL-005 | Current Welsh Control Standard version | Resolved bounded source check | Use version 5.0 and its access conditions; retain recorded front-date/effective-footer difference | Version identification resolved; actual organisational signing/adoption belongs to VAL-004 | Replacement standard or evidence changing the current version/status | 2026-11-03 | | VAL-006 | Four-nation capacity, children and representation map at discharge | Resolved bounded baseline | Use the completed source-linked map and keep care, disclosure and representative access separate | No current baseline-map gap; individual authority documents, disputes and separate liberty regimes are not decided | New national law/status evidence or a specific question outside the completed map | 2026-11-03 | | VAL-007 | Wider public-accountability instruments | Parked context | Review an exact language, equality, public-record or accountability provision only where it changes an identified digital-information duty | No complete FOI/procurement/government-accountability survey commissioned by the central question | A direct digital-duty relevance or explicit scope extension is identified | 2026-11-03 | | VAL-008 | Overseas recipients and supplier access | Evidence-blocked; no general transfer conclusion | Identify recipient, location, controller and purpose for one actual access/transfer path | No overseas flow supplied; supplier hosting does not itself establish authority | A concrete overseas recipient/access path is identified | 2026-11-03 | | VAL-009 | Specialist ICO guidance retrieval | Bounded source-access limit | Resolve a specific guidance-dependent question using the current primary law already retrieved | Earlier direct retrieval failures do not invalidate the separately verified statutory digital-copy/portability rows | Direct source access or a specific unresolved guidance question | 2026-11-03 | | VAL-010 | Wider remedies and clinical-negligence case law | Parked context | Research one defined digital-information decision or dispute | No bounded dispute supplied; a general liability survey is not the main register | A specific remedy or care-information failure question is identified | 2026-11-03 | | VAL-011 | Sensitive protection information and controlled access | Resolved bounded child/adult examples; wider regimes remain scoped | Use the four-nation protection examples and current DPA health/social-work/child-abuse restrictions; assess each live decision separately | No actual case, complete specialist restrictions survey or local portal/access configuration supplied | New law, a defined different sensitive flow or actual access/authority evidence | 2026-11-03 | | VAL-012 | DAPB4101 replacement conformance timetable | Unresolved; awaiting authoritative new ISN/date | Compare the new notice with the implementation page and record the replacement date when published | Original ISN says 30 April 2025; later implementation material anticipates extension; April 2027 pilot assurance is not a replacement deadline | NHS England publishes an authoritative replacement notice/conformance date | 2026-11-03 | | VAL-013 | Full WASPI source availability and particular adoption | Bounded source/arrangement gap | Obtain the full relevant framework and adopted agreement only for an identified Welsh flow | Earlier full-source availability intermittent; no actual local agreement supplied | Reliable full source or a specific arrangement requiring inspection | 2026-11-03 | | VAL-014 | Four national service-report examples | Resolved bounded comparison; qualifications retained | Use the completed comparison for England CDS, Welsh GP extraction, Scottish CGS claims and NI KH03a; SMR01 remains an operational contrast | No current four-example gap; NI collection-specific digital invocation and the SMR binding instrument remain unverified | New authoritative collection/legal evidence or a specified provider/report outside this comparison | 2026-11-03 | | VAL-015 | Protection system adoption, forms and future duties | Bounded dated findings; local implementation evidence-blocked | Verify a named provider's CP-IS, eIRD/register, CJSM or regulator route against its actual current instruments | No executed local terms, deployment proof or authorised current protected-form inspection | Actual instruments/access evidence, new designation/standard/commencement or official replacement guidance | 2026-11-03 | Version 5 identification is supported by [SRC-200](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-200). The completed [capacity and representative-authority map](https://uk-digital-healthcare-legal-requirements.pages.dev/examples/capacity-and-representation/index.md) uses [SRC-241](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-241)–[SRC-259](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-259) and [SRC-263](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-263), with its explicit limits. DAPB4101’s timetable conflict is documented by [SRC-187](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-187)–[SRC-189](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-189). The completed [national service-report comparison](https://uk-digital-healthcare-legal-requirements.pages.dev/national-service-reports/index.md) defines “return” as a report and retains the different legal/evidence classes. Its completion does not turn the qualified NI route or SMR target into an unqualified statutory digital duty. The completed [protection explanation](https://uk-digital-healthcare-legal-requirements.pages.dev/topics/protection-and-safeguarding/index.md), [catalogue](https://uk-digital-healthcare-legal-requirements.pages.dev/protection-requirements/index.md) and [worked examples](https://uk-digital-healthcare-legal-requirements.pages.dev/examples/protection-sharing/index.md) distinguish duty, channel, handover and access. They do not establish every specialist protection regime or a universal EPR interface. No automated monitoring is scheduled. [Current law and changes](https://uk-digital-healthcare-legal-requirements.pages.dev/changes/index.md), [retained implementation findings](https://uk-digital-healthcare-legal-requirements.pages.dev/context/secondary-use-status/index.md) and the [evidence matrix](https://uk-digital-healthcare-legal-requirements.pages.dev/evidence-matrix/index.md) preserve the dated conclusions. These rows do not authorise repeated searches without a trigger or a live disclosure. Required technical verification remains the integration owner’s responsibility. [Project status](https://uk-digital-healthcare-legal-requirements.pages.dev/project/status/index.md) · [Digital requirements](https://uk-digital-healthcare-legal-requirements.pages.dev/digital-requirements/index.md) · [Home](https://uk-digital-healthcare-legal-requirements.pages.dev/index.md)