Evidence Validation Queue
Use this queue for unresolved evidence work that cuts across product, customer, standards, and regional pages.
Status Convention
| Status | Meaning |
|---|---|
| High | Primary, official, or customer-side source currently supports the claim boundary. |
| Moderate | Useful support exists, but source type, age, or specificity limits the claim. |
| Vendor | Vendor-published evidence only; external validation needed before outcome or deployment claims. |
| Boundary | Evidence exists for adjacent facts, but not the precise claim. |
| Needed | Source required before the claim should be used. |
Queue Use Discipline
Queue entries are backlog and trigger records, not automatic next-step defaults. West Midlands Medicus / HealthShare, DUAA / ICO guidance, and other active trails should be revisited when a new source appears, an FOI or supplier response arrives, a regulator publishes final guidance, or the user explicitly asks for that trail. Otherwise, next passes should rotate through anchor synthesis and adjacent source/evidence domains as recorded in the Context Map and Source and Evidence Domain Map.
Use the Executive Summary architecture-boundary row as the single holding item for missing DMICP / CORTISONE, Health Connect, HealthShare, NHS England, and four-nation adapter implementation artefacts. Do not duplicate the same proof gap into separate Defence, DUAA, identity-directory, devolved-nation, or supplier rows unless a new source, assurance decision, or user instruction changes the scope.
This queue is source-ID-first and backlog-oriented. Link source-layer labels only where the queue row itself is a reusable routing boundary; otherwise leave DSA/DPIA, DCB0129/DCB0160, Caldicott, records-management, and standards labels to be explained by the synthesis page that uses the queue item.
Queue
| Domain | Validation item | Current status | Next source targets |
|---|---|---|---|
| DUAA | Commencement and ICO guidance tracking for Data (Use and Access) Act 2025 provisions. | High | ICO organisation guidance now says all DUAA data-protection provisions are in force as of 19 June 2026. Keep provision-level checks for non-data-protection DUAA provisions and use the DUAA / ICO Guidance Tracker below because some topic guidance is final/updated while research, automated decision-making/profiling, and IDTA/Addendum transfer updates still need final ICO guidance before implementation-level conclusions. Revisit on publication or scheduled recheck rather than as the default next pass. |
| DUAA / NHS standards | Mapping section 121 / Schedule 15 to named NHS England information standards and suppliers. | Boundary | Explanatory notes support the England health/adult social care IT / IT-service provider standards interpretation. Need NHS England / DHSC interpretation, Standards Directory applicability notes, DSIC standards, product/version mappings, supplier-responsibility matrices, and customer artefacts before claiming any specific InterSystems obligation or compliance status. |
| DUAA / InterSystems | Product and deployment readiness evidence for DUAA-adjacent obligations. | Boundary | Birmingham / West Midlands public evidence now gives a partial worked pack for HealthShare shared-care-record scope, DPIA/supplier role, BCHC retention/contract-end wording, NRL InterSystems references, HL7 UK OIDs, DSA-sensitive-information statements, GP Connect supplier-progress rows, WMCA DSCR/GP Connect onboarding support, current Medicus integration signalling, and national NHS GP Connect/Medicus status evidence. Still need customer-specific final DSA, current local DPIA, DCB0129/DCB0160, data-subject-rights procedure, complaint-handling workflow, AI/ADM governance if applicable, research/secondary-use approvals, cloud/subprocessor/transfer terms, PECR/cookie controls, digital-identity route, and audit/export evidence. |
| DSIC | Public catalogue/supplier evidence for InterSystems products or partner services. | Boundary | Current DSIC sources support the England-only operating model, capability taxonomy, standards relationships, the capability-to-standard crosswalk, ODS/SDS treatment, and HealthShare component relevance. The 2026-06-21 current-source check found DSIC and Digital Primary Care framework/procurement evidence but no public indexed DSIC/Buying Catalogue or Find a Tender listing naming InterSystems, HealthShare, Health Connect, IRIS for Health, or a partner capability scope. Reopen when a supplier listing, award, catalogue row, customer architecture, or procurement artefact appears. |
| DSIC | HealthShare as DSIC GP foundation system versus shared-care/integration component. | Boundary | Current evidence supports HealthShare/UCR/Clinical Viewer/Health Connect relevance for shared care, interoperability, and GP Connect consumption. It does not prove full foundation capability coverage for patient information maintenance, appointments, consultation, prescribing, referrals, documents, tasks, reporting, scanning, migration, and GP national-service provider obligations. |
| DSIC / HealthShare | Solution role split for a HealthShare-backed DSIC architecture. | Boundary | Anchor-page audit keeps four roles separate: HealthShare shared-care record/viewer, Health Connect or IRIS national-service middleware, partnered GP foundation supplier, and bespoke application on InterSystems platforms. Need a supplier-responsibility matrix, component architecture, national-service ownership, DCB0129/DCB0160 hazard ownership, data-controller/processor model, and catalogue/capability evidence before claiming DSIC compliance. |
| DSIC | Digital Primary Care replacement framework and Buying Catalogue changes. | Moderate | The Find a Tender notice signals a replacement framework for Digital Care Services catalogue frameworks. Track procurement documents, awards, catalogue guidance, and any changed DSIC terminology before using commercial conclusions. |
| Source and evidence domains | Domain split coverage beyond NHS England Digital Primary Care, HealthShare Components, and Standards / Interoperability. | Boundary | Source/evidence domain pages now split the largest England primary-care cluster, the HealthShare component cluster, and the standards/governance cluster. The 2026-06-21 traversal-friction check keeps the GP Connect supplier-progress conformance request inside the existing standards and GP Connect pages, records sibling-project reuse in LLM maintenance/starter guidance, keeps UK NHS examples as overview plus independent pages, keeps international PHC in its module page, and treats UK Defence as contained unless a new primary source appears or the user explicitly reopens it. The devolved-nations traversal-cost check still does not justify a new domain page: the parent comparison, three connectivity-equivalent pages, and three InterSystems-by-nation pages remain navigable. Create a devolved domain only if future passes repeatedly traverse all of those pages plus the canonical registers for the same class of cross-nation question. |
| Standards and interoperability | Standards-surface-to-implementation proof boundary for NHS Standards Directory, PRSB, GP Connect, MESH, ITK3, DCB0129/DCB0160, DUAA, and InterSystems product roles. | Boundary | The Standards and Interoperability Evidence Domain now routes standards families, supplier-role questions, Update Record separation, implementation-proof boundaries, and the canonical reusable standards-conformance evidence request pattern. The selected narrow implementation-proof slice is NHS ITK, rechecked on 2026-06-20 with no current public InterSystems row found; the ITK page now has a focused checklist plus a supplier/customer request template. GP Connect InterSystems Supplier Progress applies the reusable request pattern only where supplier-progress rows are being relied on for assurance. Health Connect, IRIS for Health, FHIR Services, HealthShare Unified Care Record, HealthShare Clinical Viewer, and HealthShare / PRSB CIS are the high-risk product-map rows audited for capability/conformance/presentation/access-versus-deployment separation. Remaining evidence need is product/version documentation, validation-scope detail, current non-vendor conformance/certificate records, SSO/RBAC/audit detail where access claims are used, customer deployment packs, and rechecks when standards pages change. |
| UK healthcare recording | Deployment proof pack for recording healthcare information and healthcare delivery. | Boundary | The legal/professional model is now source-backed: UK GDPR, DPA 2018, PECR, common law confidentiality, Caldicott, section 251, professional record duties, provider governance, candour, records-management codes, SNOMED CT, PRSB/provenance, DCB0129/DCB0160, Health and Care Act 2022, and DUAA. For any named HealthShare, Health Connect, DMICP/CORTISONE, portal, analytics, AI, or shared-care deployment, still need local legal basis, Article 9 condition, confidentiality route, PECR controls where applicable, controller/processor/RACI, DSA/DPIA, retention/disposal schedule, amendment/export/search procedure, RBAC/SSO/audit/provenance design, clinical-safety case, incident/candour workflow, and professional workflow evidence. |
| Executive Summary architecture boundary | Single bounded proof gap for the recommended DMICP / CORTISONE to Health Connect to HealthShare target architecture and its NHS England / four-nation adapter extensions. | Boundary | Direct sources support DMICP / CORTISONE source context, InterSystems HealthShare / IRIS licence evidence, Health Connect / HealthShare product relevance, DSIC / DUAA England governance boundaries, and devolved-nation functional-equivalence context. This row is the single holding item for missing implementation artefacts: DMICP interface catalogue/source data model; CORTISONE architecture; Health Connect mediation design; IRIS/SDA/FHIR/HL7/CDA mapping rules; HealthShare component/version/configuration scope; NHS England GP Connect, MESH, ITK3, PDS, ODS/SDS, NDSA/DSA/DPIA, DCB0129/DCB0160, supplier RACI, endpoint/certificate/monitoring/runbook evidence; and nation-specific adapter/onboarding/approval packs for Wales, Scotland, and Northern Ireland. Do not reopen as separate Defence, DUAA, identity-directory, or devolved trails unless a new source, assurance decision, or user instruction requires it. |
| PRSB CIS / HealthShare | Validation-scope evidence behind the InterSystems Healthshare Core Information Standard listing. | Boundary | The Standards and Interoperability Evidence Domain hosts the canonical reusable request pattern; the PRSB page now keeps only PRSB-specific assurance scope instead of repeating that generic table. Need PRSB, InterSystems, NHS standards-owner, or customer-approved evidence for certificate reference, product/version/build, CIS version, assessed sections, exclusions, component scope, GP Connect/FHIR/HL7/DICOM/IHE/MESH/ITK/DSIC adjacency, DSA/DPIA, DCB0129/DCB0160 responsibility split, role/view configuration, and live deployment status before using the PRSB fact as implementation proof. Keep single-source or unresolved PRSB scope gaps in this queue until a concrete assurance decision needs them. |
| HealthShare components | Component licensing, configuration, and customer deployment scope. | Boundary | The HealthShare Components Evidence Domain supports taxonomy and source routing, but it does not prove which components are licensed, configured, integrated, safety-assessed, or live in a named customer environment. Care Community is complete for now unless Lincolnshire/customer confirmation is explicitly required. The 2026-06-21 identity-directory pass strengthened PDS/ODS national-service dependency evidence and found an official PDS integrated-products row for Intersystems HealthConnect 2020.1, but not HealthShare EMPI or Provider Directory implementation proof. Need EMPI / Provider Directory product/version evidence, PDS FHIR onboarding, ODS/SDS mapping, matching/stewardship, synchronisation, local back-office process, audit, safety ownership, DSA/DPIA, DCB0129/DCB0160, and customer deployment artefacts before treating those components as implementation assurance. |
| GP Connect | InterSystems supplier-progress cell mapping and implementation proof. | High | The 5 June 2026 NHS page has been structurally parsed. InterSystems IRIS for Health (Middleware) maps to Send Document (Send) v2.0.1; source-spelled InterSytems Healthshare maps to Access Record: Structured Medications v1.2.6, Allergies v1.2.6, Immunisations v1.5.0, and Uncategorised v1.5.0, with other structured cells blank. GP Connect InterSystems Supplier Progress now applies the reusable conformance-request pattern to this non-Defence assurance claim. Remaining evidence need is supplier-progress/current-status confirmation, product/version scope, validation/test scope, exclusions, component coverage, adjacent MESH/ITK3/FHIR/NDSA/safety/onboarding artefacts, customer deployment proof, and rechecks after any NHS page edit later than 5 June 2026. |
| GP Connect | Current InterSystems product-specific GP Connect support by capability. | Boundary | Current NHS API pages confirm Access Record Structured, Send Document, and Update Record service context, and Health Connect Cloud documentation supports broad standards capability, not current InterSystems GP Connect conformance; still need GP Connect-specific InterSystems docs, NHS assurance material, and customer implementation evidence. Keep Update Record separate from Send Document, Access Record, MESH API, and generic MESH/ITK3 evidence. |
| Spine equivalents | Keep England Spine services separate from devolved-nation functional equivalents. | Boundary | New comparison pages map functions across Spine/PDS/SCR/EPS/e-RS/SDS, Scotland CHI/ECS/KIS/NDP/SCI/ePharmacy/MyCare.scot, Wales WGPR/WCP/WCCG/NDR/WDS, and Northern Ireland NIECR/encompass/EpicCare Link/HCN/DIS/ePharmacy. Need deeper technical architecture and API sources for the devolved services. |
| UK nations connectivity | Keep GP Connect as NHS England evidence unless Scotland, Wales, or Northern Ireland official sources explicitly say otherwise. | Boundary | Current pass added official Scotland TrakCare Patient Management System and NHS Shetland TrakCare ED / Ensemble evidence, Wales board/procurement LIMS evidence, and Northern Ireland NHAIS Caché plus encompass/Epic evidence, but no nation-specific GP Connect evidence outside England. Recheck national roadmaps before using GP Connect language outside England. |
| Scotland connectivity | Current NHS Scotland InterSystems connectivity status beyond the Public Health Scotland and NHS Shetland evidence. | Moderate | PHS 2026 data-quality material and NHS Shetland support stronger official TrakCare / Ensemble facts; Scotland NDP/MyCare/ePharmacy/SCI sources support national-service comparison. Still need NHS Scotland, NSS, or board-side sources for current national InterSystems integration-platform, hosted TrakCare, integrated-care-record, and board-by-board operating status. |
| Wales connectivity | Relationship between DHCW FHIR, Care Data Repository, Welsh Clinical Portal, Welsh Clinical Communications Gateway, GP2GP, and LIMS 2.0. | Moderate | Board/procurement sources now support the InterSystems LIMS 2.0 / TCLE route, including Welsh Clinical Portal and WRRS interface references. Need richer DHCW technical/programme sources and post-deployment implementation status. |
| Northern Ireland connectivity | Future primary-care scope and any InterSystems involvement in HSCNI beyond NHAIS Caché licensing. | Boundary | Current evidence supports InterSystems Caché licensing for NHAIS and a separate encompass/Epic/Rhapsody/DIS/ePharmacy context. Recheck DHCNI roadmap, BSO/eTendersNI procurement, and GP/primary-care integration material for any future scope change. |
| North West London ICS | Official NHS/customer/procurement confirmation for Health Connect Cloud / HealthShare Health Connect. | Boundary | Rechecked 2026-06-21. The pass found North West London acute-trust recruitment evidence supporting Health Connect / TIE technical context, but no stronger public ICB, board, contract-award, procurement, or customer programme source naming a North West London ICS Health Connect Cloud operating model. Continue only with official ICB/trust board, procurement, customer programme, or contract-award targets. |
| eConsult / UK NHS triage | Current Huma/eConsult/NHS/customer architecture proof for IRIS for Health and/or Health Connect Cloud role. | Boundary | Rechecked 2026-06-21. Current InterSystems material says eConsult, part of Huma, chose HCC for NHS integration, HSJ and public Digital Front Door posts name InterSystems & eConsult in urgent and emergency care, and procurement notices support eConsult Digital Front Door / eTriage scope. Still need Huma, NHS, or customer-approved architecture evidence for product versions, HCC versus IRIS role split, interfaces, clinical-safety artefacts, service levels, and site-by-site deployment scope. |
| West Midlands cancer/eMDT | Official UHB or West Midlands Cancer Alliance source naming InterSystems HealthShare. | Boundary | Search pass found no stronger official UHB or WMCA source naming HealthShare. Continue with UHB programme pages, WMCA publications, board papers, and procurement records. |
| West Midlands Medicus / HealthShare | Official NHS/customer confirmation of the Medicus integration route into the West Midlands Shared Care Record. | Boundary | Recheck found stronger official national Medicus evidence in NHS GP Connect status/DPIA material and an FOI/source-target pack is now listed below. No official local West Midlands source yet confirms the Medicus-to-HealthShare route, local GP Connect/MESH/ITK3 onboarding, final DSA/NDSA adoption, current local DPIA, DCB0129/DCB0160, endpoint/certificates, MESH mailbox, or supplier-responsibility matrix. Hold this trail until a targeted request is drafted/submitted, a response arrives, or a new source appears; then continue with ICB/programme pages, board papers, FOI, procurement, practice/PCN notices, and supplier/customer artefact packs. |
| MERIT | Post-31 March 2026 continuity and supplier status. | Needed | Search pass found no post-contract continuity source. Continue with BSMHFT, Black Country, CWPT, Midlands Partnership, FOI, and contract updates. |
| Royal Orthopaedic Hospital | TrakCare EPR implementation milestones after contract signature and award. | Moderate | Contracts Finder OCDS supports supplier, value, and term for the EPR award. The 2026-06-21 breadth recheck added ROH medicines-strategy planning evidence for integrated EPR, DMS/EPS, reporting, and patient-facing navigation context, but found no public go-live, implementation outcome, or clinical-safety update. Continue with ROH programme updates, go-live news, and clinical safety material. |
| HealthShare AI Assistant | Clinical safety, model, prompt, audit, RBAC, runtime-service, and UK availability controls. | Vendor | Public sample deployment artefacts, HealthShare AI Model Services product-term boundary, and a US Healthix governance pattern now exist; still need UK product documentation detail, safety case material, model/prompt governance, and customer deployment evidence. |
| FHIR Services / OMOP / Bulk FHIR | Customer-specific hosting, tenancy, commercial, security, service-level, UK-region, NHS profile, and deployment-governance boundaries. | Boundary | Public FHIR Server cloud, supported-operations, packages/profiles, OAuth/security, Network Connect, Health Connect Cloud, Cloud Services Portal, and cloud-hosted services overview docs now exist; the FHIR Services high-risk audit keeps managed-service mechanics separate from NHS profile conformance and customer assurance. Still need customer-specific trust/security documentation, UK-region commitments, commercial terms, profile/validation configuration, safety/governance artefacts, and architecture evidence. |
| TrakCare PHC international | Current PHC/community-health deployment evidence beyond vendor stories. | Moderate | Formal Gateway Health go-live publication; Chile SSMS / El Bosque named live-status update; Qatar PHCC or Ministry of Public Health material; public procurement or implementation records. |
| TrakCare PHC/community-health international | Current live-scope validation for Gateway Health, Victoria, Chile APS, and DHAMAN evidence. | Moderate | Gateway CEO social corroboration, VHA Victoria status, newer SSMS workflow material, and DHAMAN network-scope source now exist; current Qatar PHCC sources do not support a present TrakCare claim. Still need formal Gateway publication, Victorian Government or provider-level operational scope, and DHAMAN primary source naming TrakCare. |
| NHS ITK | Current official non-vendor accreditation status and implementation-proof pack. | Boundary | Rechecked 2026-06-20. Current IRIS for Health ITK documentation, NHS ITK conformance process, and NHS ITK conformance-catalogue route were found, but no current public NHS or standards-body row/certificate naming InterSystems, HealthShare, Health Connect, or IRIS for Health was exposed in the rendered catalogue or targeted public search. The Solution Assurance compliance catalogue explicitly excludes ITK Accreditation and its Healthshare-named rows are not ITK proof. Use the focused ITK evidence request checklist and supplier/customer request template for product/version, certificate/register status, message bundle/profile, scope, test pack, current status, and local deployment artefacts. |
| Clinical Viewer | Presentation, access, SSO/RBAC/audit, AI Assistant adjacency, version differences, configuration, and deployment-specific evidence. | Boundary | HealthShare 2026.1 documentation availability is confirmed but account-gated, and the high-risk product-map audit now separates Clinical Viewer product/access evidence from deployment assurance. Still need accessible Clinical Viewer documentation, identity/SSO/RBAC/audit configuration, role/view templates, Navigation Application and AI Assistant governance evidence if enabled, DSA/DPIA, DCB0129/DCB0160, implementation guides, customer deployment descriptions, and current live-status proof. |
West Midlands Medicus / HealthShare FOI and Source-Target Pack
Use this pack to seek recorded evidence for the specific Medicus GP system connection into the West Midlands Shared Care Record. FOI targets are public authorities only; InterSystems and Medicus are supplier/source targets, not FOI bodies. Do not request patient-identifiable records. Ask for architecture, governance, safety, service-management, and assurance artefacts at deployment or programme level.
| Target | Evidence question | Ask for these artefacts | Best route | Why this target matters |
|---|---|---|---|---|
| NHS Birmingham and Solihull ICB / Shared Care Record programme | Does the Birmingham and Solihull Shared Care Record include a live Medicus route into HealthShare, and what is its scope? | Deployment note, practice/PCN cohort or ODS-code list if publishable, go-live date, route architecture, data-source list, HealthShare component/tenant, supplier RACI, DSA/NDSA adoption note, DPIA addendum, DCB0160 evidence, and board/programme approval. | FOI / information request and public programme pages. | The ICB is the primary local source for the Birmingham and Solihull SCR footprint and local governance gap. |
| NHS Coventry and Warwickshire ICB | Does the Medicus route affect the Coventry and Warwickshire Integrated Care Record or shared regional HealthShare instance? | Current ICR architecture, local DSA/DPIA addendum, controller/joint-controller matrix, approved data flows, route-specific use-case approval, safety responsibilities, and go-live/current-status evidence. | FOI / information request and ICR programme pages. | The historic regional DPIA describes a shared regional instance, so Coventry/Warks may hold common-model and cross-area governance records. |
| NHS Herefordshire and Worcestershire ICB | Does the shared HealthShare / ICWR route include Medicus-derived GP data or shared national-service components? | Current Connecting Care Record architecture, UHB-hosting confirmation, InterSystems processor/subprocessor terms, local DSA/DPIA status, interface catalogue, DCB0160 artefacts, and operating model. | FOI / information request and shared-care-record programme pages. | The H&W DPIA previously identified UHB hosting and the shared HealthShare instance. |
| University Hospitals Birmingham NHS Foundation Trust | What does UHB hold as host, processor-support participant, or major provider for the shared HealthShare environment? | Hosting/service-management role, current InterSystems contract or service schedule if disclosable, data-flow diagram, incident/support model, endpoint/certificate ownership, DCB0160 or clinical-safety participation, and DPIA/DSA annexes. | UHB FOI route and board/procurement records. | Historic DPIA evidence points to UHB hosting; UHB may hold infrastructure and operational records that ICB pages do not expose. |
| Participating provider trusts: BCHC, ROH, BSMHFT, and other directly affected trusts | How does the Medicus / HealthShare route affect local direct-care viewing, clinical workflow, and safety obligations? | Local deployment notice, user-role model, Clinical Viewer use, GP Connect view availability, local DPIA/safety addendum, audit/access procedure, downtime/fallback workflow, SAR handling, and complaint route. | Trust FOI routes, privacy notices, board papers, and digital programme records. | Provider-level records may reveal actual use, clinical-safety ownership, and workflow controls absent from system-wide pages. |
| NHS England GP Connect / national-service owners | Is there recorded national onboarding evidence for the specific West Midlands HealthShare or Medicus route? | Approved-use-case evidence, supplier onboarding status, NDSA scope, GP Connect consumer/provider role split, SSP/HSCN/RBAC/JWT/TLS MA evidence where disclosable, and MESH/ITK3 route confirmation if Send Document is used. | NHS service pages, supplier-progress material, and national-service enquiry/FOI routes. | NHS pages prove national Medicus status but not local onboarding; national-service owners may confirm whether a named use case exists. |
| Medicus and InterSystems UKI | What supplier-side evidence can be provided voluntarily for the reported integration? | Product/version statement, integration architecture, HealthShare/Medicus role split, GP Connect capability used, MESH/ITK3 involvement, safety-case ownership, information-governance pack, support model, and customer-approved case study or deployment note. | Supplier/customer evidence request, not FOI. | Supplier material can close technical gaps only if it is specific, dated, and ideally customer-approved or matched to NHS/customer evidence. |
DUAA / ICO Guidance Tracker
Use this tracker to replace GOV.UK DUAA factsheet summaries with ICO topic guidance as it becomes final. The ICO organisation page was updated on 19 June 2026 to say all DUAA data-protection provisions are now in force and to link new or updated ICO topic guidance. The wiki should still not treat planned or draft guidance as final implementation authority.
| Topic | Current wiki position | Replacement trigger | Affected pages |
|---|---|---|---|
| Subject access and reasonable/proportionate searches | Rechecked 2026-06-19 second pass. Partially replaced. ICO organisation guidance says updated right-of-access guidance reflects DUAA subject access request changes, and the guide now covers one-month response, clarification pause, identity verification, reasonable efforts, and no unreasonable or disproportionate searches. No final companion replacement was found for Right of Access in brief or SARs Q&A; ICO planning still lists both for summer 2026 and Handling subject access requests generated by AI for winter 2026. | Local controller/processor subject-access workflow for a named deployment, plus final ICO companion guidance products when published. | Data (Use and Access) Act 2025, DSIC HealthShare Compliance Map |
| Complaints handling | ICO complaint-handling guidance is now available and says the DUAA complaints process requirement comes into force on 19 June 2026. Use it over GOV.UK factsheet-only treatment. | Local controller/processor complaint workflow, acknowledgement, investigation/update, outcome, escalation, and audit evidence for a named deployment. | Data (Use and Access) Act 2025, Evidence Matrix |
| Automated decision-making and AI | Rechecked 2026-06-19 second pass. Still queued. The ADM/profiling consultation page says the consultation closed on 29 May 2026; the technology planning page still lists ADM/profiling as drafting with final guidance due winter 2026. No final DUAA-updated ADM/profiling guidance was found. HealthShare AI Assistant, IntelliCare, triage, risk scoring, and workflow automation still need safety/governance proof. | Final ICO automated decision-making/profiling guidance updated for DUAA. | Data (Use and Access) Act 2025, HealthShare AI Assistant, DSIC HealthShare Compliance Map |
| Research and statistical purposes | Rechecked 2026-06-19 second pass. Still queued. Existing ICO research provisions guidance remains under review for DUAA, while planning material shows Research, Archiving and Statistics Provisions guidance in redrafting after consultation with final guidance due in summer 2026; anonymisation/pseudonymisation for research is drafting with consultation due July 2026 and final guidance due winter 2026. Secondary-use and analytics deployments still need lawful-basis, approvals, minimisation, pseudonymisation, retention, and access-control evidence. | Final ICO research provisions guidance updated for DUAA and any final anonymisation/pseudonymisation research guidance where relevant. | Data (Use and Access) Act 2025, HealthShare Health Insight, InterSystems OMOP |
| Recognised legitimate interests, legitimate interests, and further processing | ICO lawful-basis, recognised legitimate-interest, legitimate-interest, and purpose-limitation guidance is now available or updated for DUAA. Do not use recognised legitimate interest as a generic patient-data lawful basis. | Deployment-specific lawful-basis, special-category, purpose, controller-role, and transparency analysis. | Data (Use and Access) Act 2025, NHS Standards Directory and DHSC Standards Direction |
| International transfers | Rechecked 2026-06-19 second pass. ICO adequacy, safeguards, and transfer-risk/data-protection-test guidance has been updated for DUAA terminology. Cloud, support, external AI, subprocessor, disaster-recovery, and managed-service claims remain customer-specific. ICO still says it plans to update the IDTA and Addendum in the course of 2026 and to continue using current versions meanwhile; no final IDTA/Addendum replacement was found. | Customer terms, DPA, subprocessor list, support-access controls, transfer mechanism, technical safeguards, and final IDTA/Addendum guidance updates when published. | Data (Use and Access) Act 2025, FHIR Services, Health Connect, DSIC HealthShare Compliance Map |
| PECR, cookies, storage access, and electronic communications | ICO storage/access technologies guidance was finalised after DUAA PECR changes. Patient portals, analytics, reminders, surveys, and messaging still need local direct-care/marketing and consent analysis. | Local cookie/storage classification, consent or exception analysis, communications purpose split, and patient-facing service configuration. | Data (Use and Access) Act 2025, HealthShare Personal Community, DSIC HealthShare Compliance Map |
| ICO governance, codes, and enforcement | ICO organisation guidance reflects the post-19 June 2026 data-protection-provision status and links current topic guidance, but code/enforcement-process detail still needs tracking. | Commenced Information Commission governance changes and final ICO code/enforcement process updates. | Data (Use and Access) Act 2025, Standards and Interoperability |