<!-- Derived Markdown alternate of project/status.md; canonical repository sources and registered evidence retain authority. -->


# Project status

## Agreed purpose and scope

The wiki explains what healthcare and social care organisations must legally send digitally or make digitally available across England, Wales, Scotland and Northern Ireland. Publicly funded healthcare organisations are central; private healthcare is compared. Suppliers appear where needed to explain those organisations' duties. Individual care is primary, with planning, research and public health also covered.

The user clarified this through sequential questions and expressly authorised the structure and rewrite on 3 November 2026. The [home answer](https://uk-digital-healthcare-legal-requirements.pages.dev/index.md) leads the account, followed by comparison, examples and national/legal detail. The [core catalogue](https://uk-digital-healthcare-legal-requirements.pages.dev/digital-requirements/index.md) and [protection catalogue](https://uk-digital-healthcare-legal-requirements.pages.dev/protection-requirements/index.md) provide exact reference records. It records the information, responsible organisation, recipient, method or standard, timing, legal force and national/provider scope. Statutory requirements and contractual obligations are distinct. Unseen local terms remain unknown.

## Current content and evidence

The corpus contains **268 source identities**, **108 bounded evidence claims** and **16 portable concepts**. The core catalogue has **56 assessed rows**: 22 identified digital obligations, 14 qualified standards/access conditions/national mandates, 10 information duties without an independently prescribed digital-only method, and ten operational routes or recommendations. The companion protection catalogue adds **40 assessed exchanges and contexts**, with permissions and operational evidence labelled separately. Conditions within each row remain material; these counts are not universal legal mandates.

The three core worked examples cover [SCR or equivalent exchange](https://uk-digital-healthcare-legal-requirements.pages.dev/examples/summary-care-records/index.md), [blood tests and results](https://uk-digital-healthcare-legal-requirements.pages.dev/examples/blood-tests-results/index.md) and [hospital discharge](https://uk-digital-healthcare-legal-requirements.pages.dev/examples/hospital-discharge/index.md). The linked [capacity, children's care and representative-authority map](https://uk-digital-healthcare-legal-requirements.pages.dev/examples/capacity-and-representation/index.md) compares one hospital-to-community-healthcare/social-care transition across all four nations. That bounded map is complete; it does not validate a particular appointment or disputed case. Child/adult protection concerns can arise at any point in care. The [protection examples](https://uk-digital-healthcare-legal-requirements.pages.dev/examples/protection-sharing/index.md) use hospital discharge as one worked setting involving relevant police and education services, digital routes and controlled representative access.

The [local research review](https://uk-digital-healthcare-legal-requirements.pages.dev/local-research/index.md) records screening of 3,193 text files across 52 project folders and selected deeper review. Primary-source checks support imported legal findings. The table and worked examples received independent source-fidelity reviews, including the English discharge recipient qualifier and the England/Wales age-18 LPA donor requirement.

Maturity remains a source-backed explanatory baseline, rather than an exhaustive audit of every national return, unpublished contract or actual implementation. A digital service's existence is not proof of a legal upload duty. The [validation queue](https://uk-digital-healthcare-legal-requirements.pages.dev/validation-queue/index.md) records the remaining boundaries. Earlier Scottish and NI implementation checks remain resolved dated findings, with event-triggered rechecks.

The [national service-report comparison](https://uk-digital-healthcare-legal-requirements.pages.dev/national-service-reports/index.md) now covers one selected example per nation. It defines “return” in plain language, preserves claim/extraction triggers, and marks the unresolved NI collection-specific digital linkage and SMR target. VAL-014 is complete for this bounded comparison.

## Presentation and technical boundary

The reader title is **UK Digital Healthcare Legal Requirements**. The Standard remains pinned to v0.1.0-rc.9 at `8800e139d73fd58ee1bd756d3e5497f62ed678e4`. The Parliament-purple theme, portcullis-only header icon, source favicon and independent-publication identification remain in place. The owner explicitly confirmed public-use permission for the marks. The managed service remains `uk-digital-health-legal-basis-wiki` on port 8035. Publication is authorised for a private GitHub source repository and the public Cloudflare Pages website at the selected canonical URL. The release process checks the exact pushed commit, public-content review, verification and live response. Runtime deployment evidence is recorded separately; no recurring automation is scheduled.

Technical verification is evidenced separately by the generated receipt and conformance report. Research review does not replace those checks.

## Current research priorities

The child/adult protection examples complete the bounded sensitive-disclosure priority. They distinguish necessary agency disclosure from patient/representative access and compare national restrictions. No further grounded content update is available.

Parked work below needs its recorded new evidence or a concrete case before reopening. Address a failed or unrun required technical check before optional research.

## Parked and evidence-blocked work

| Item | blocked_by | reopen_when | last_checked |
|---|---|---|---|
| Assess a particular provider/pathway contract | No named organisation, executed terms, local directions or access agreement supplied | A concrete pathway and supporting documents are available | 2026-11-03 |
| Reopen Scottish/NI reform implementation status | Current dated positions already resolved; no new implementing evidence | New official law, instrument or implementation evidence, or explicit user instruction | 2026-11-03 |
| DAPB4101 replacement full-conformance deadline | Later implementation update announces an extension but publishes no replacement date | New Information Standards Notice or official dated replacement timetable | 2026-11-03 |
| Establish the legal route for particular Welsh administrative mandates | Published circular/DSCN does not identify an applicable statutory-direction or executed-contract chain | Specific direction, delegation, adoption or contractual evidence is available | 2026-11-03 |
| Assess an overseas recipient or supplier access path | No concrete overseas flow identified | Recipient, location, purpose and roles supplied | 2026-11-03 |
| NI KH03a digital legal linkage | Collection instructions do not expressly invoke the general statutory Trust duty; email timetable uses should | New collection-specific legal instruction or official clarification is available | 2026-11-03 |
| Scottish SMR01 binding digital authority | Verified electronic collection and target, but no named binding direction/request/contract located | New authoritative collection instrument or applicable provider contract is available | 2026-11-03 |
| Protection local implementation and current protected forms | No named adopted local protocol, deployment/access evidence or authorised protected-form review | A named partnership/provider supplies the actual instrument and implementation evidence | 2026-11-03 |
| English education designation and future protection laws | Current status is bounded; future designation/commencement cannot be assumed | New official designation, commencement or applicable published standard | 2026-11-03 |
| Resolve a disputed capacity/proxy decision | No individual instrument, facts or dispute supplied | Defined case and relevant grant/order/authority evidence are available | 2026-11-03 |

[Validation queue](https://uk-digital-healthcare-legal-requirements.pages.dev/validation-queue/index.md) · [Evidence matrix](https://uk-digital-healthcare-legal-requirements.pages.dev/evidence-matrix/index.md) · [Research log](https://uk-digital-healthcare-legal-requirements.pages.dev/log/index.md) · [Home](https://uk-digital-healthcare-legal-requirements.pages.dev/index.md)
