Evidence Validation Queue
Use What Next: Suggestions and Decisions to choose and reconcile follow-up suggestions. This queue remains the canonical home for missing evidence, blockers, source targets and the detailed editorial passes below; suggestion status does not replace evidence status.
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 |
|---|---|---|---|
| Product interface illustrations | Current TrakCare Lab Enterprise screen and current Provider Directory Data Steward screen. | Needed | The 2026-09-15 review found no verified public Lab Enterprise UI and only a small 2019 Provider Directory Master Viewer example. Keep the historical caption; do not substitute legacy TrakCare Lab, stock photography or architecture diagrams. Reopen when a current official manual, demonstration or customer-approved training screen becomes available. No new screenshot page or request pack is needed. |
| 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-08-11 public-source refresh confirmed the current catalogue model and effective S99/S101/S102 GP Connect standard pages, but found no supplier listing there naming InterSystems, HealthShare, Health Connect, IRIS for Health, or a DMICP/CORTISONE 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. |
| Terminology and code management | Deployment proof for Read / CTV3 migration, SNOMED CT UK Edition, dm+d, NHS Terminology Server or local terminology-service integration, and local-code / extension mapping. | Boundary | New standards sources support the model: Read Version 2 and CTV3 are retired or deprecated, TRUD provides static Read / CTV3 to SNOMED CT migration artefacts, SNOMED CT UK Edition and dm+d are the current national coded-clinical / medicines standards, NHS England Terminology Server provides FHIR terminology services, and local codes should be governed through CodeSystem / ValueSet / ConceptMap resources. Still need deployment-specific source packages, release versions, map versions, terminology-service architecture, local-code ownership, mapping equivalence and review, inactive-code handling, original-code provenance, clinical validation, DCB0129/DCB0160 where workflow is affected, and customer deployment proof before using any InterSystems terminology claim. |
| 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 now support DMICP as the Armed Forces electronic patient record / Defence primary-healthcare source baseline, CORTISONE's 2025 stabilisation position followed by the January 2026 TPP EHR award, InterSystems HealthShare / IRIS licence evidence, Health Connect / HealthShare product relevance, DSIC / DUAA England governance boundaries, current effective S99 structured-read / S101 document-send / S102 structured-update standards, and devolved-nation functional-equivalence context. Current GP Connect supplier-entry restrictions must be resolved independently of effective S101/S102 catalogue standards. The standard pages do not approve a DMICP use case or prove InterSystems implementation; the 2025 Primary Dental Care notice is a dental replacement signal only. This row is the single holding item for missing implementation artefacts: DMICP interface catalogue/source data model; coding/free-text/scanned-record handling; workflow-specific S99/S101/S102 route decision and provider/consumer/sender/receiver role; CORTISONE architecture; Health Connect mediation design; IRIS/SDA/FHIR/HL7/CDA mapping rules; HealthShare component/version/configuration scope; replacement migration/decommissioning plan; 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, dental, or devolved trails unless a new source, assurance decision, or user instruction requires it. The 1 September GP Connect policy closes new-developer onboarding for Update Record, Send Document and Appointment Management; establish the current supplier-entry route before interpreting effective DSIC standards as implementation feasibility. |
| 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. The Care Community customer-confirmation trail remains parked; July 2026 support alerts provide a new, separate trigger for permission/build/correction checks. 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. The 2026-06-28 Provider Directory pass adds stronger public product-feature, API, data-stewardship, managed-service, and version-boundary evidence, plus a legacy Coordinate My Care usage signal; it still does not prove current Provider Directory ODS/SDS mapping, customer architecture, or live assurance. The current UCP breadth check points to Better / Valida / London Care Record / UCP web portal / National Record Locator routes and does not name InterSystems or Provider Directory as the live platform or ODS/SDS owner. Need current 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 | Current InterSystems supplier status and implementation proof. | Boundary | The 2026-09-08 HTML recheck retains HealthShare’s four populated structured-consumer cells. The IRIS middleware Send Document row from June is absent in the page edited 3 September; current IRIS status is unconfirmed, not proven withdrawn. Use the existing supplier-progress request pattern to resolve status, product/build, capability and validation scope, then obtain route-specific onboarding, safety and customer proof. |
| GP Connect | Current InterSystems product-specific GP Connect support by capability. | Boundary | Current NHS API and DSIC pages confirm effective S99 Access Record Structured, S101 Send Document, and S102 Update Record standards, their mandatory supplier roles, dependencies, and service context. Health Connect Cloud documentation supports broad standards capability, not current InterSystems GP Connect conformance; no current source makes DMICP/CORTISONE an approved provider, consumer, sender, or receiver. Still need GP Connect-specific InterSystems docs, NHS assurance material, approved use-case evidence, and customer implementation artefacts. Keep Update Record separate from Send Document, Access Record, MESH API, and generic MESH/ITK3 evidence, and keep its broader catalogue applicability separate from the narrower publicly assured pharmacy workflows. |
| GP2GP | InterSystems GP2GP implementation, adaptor, or GP foundation-system proof. | Boundary | Current official evidence supports GP2GP / GP record-transfer routes in England, Wales, Scotland, and Northern Ireland, but no public source found in this pass proves InterSystems GP2GP sending, requesting, receiving, adaptor, middleware, or DSIC GP foundation-provider capability. Need product/version evidence, supplier role split, GP2GP HL7 V3 / Spine / FHIR-adaptor scope, conformance/onboarding evidence, customer deployment proof, migration/cutover pack, clinical-safety case, DSA/DPIA, and operating RACI before using any InterSystems GP2GP claim. To Do: reopen this only when a supplier or customer source appears, then update the GP2GP Record Transfer page and this queue row with the product/version, role, onboarding, safety, DSA/DPIA, and deployment proof. The 25 September adapter research is complete within public evidence; implementation ambiguities are parked for a real implementation decision or authoritative response. |
| Spine equivalents | Nation-specific access, interface/version and deployment scope beyond the service map. | Boundary | The UK landscape now covers networks, identity, records, messaging and diagnostics, with country drill-downs and direct source records. Shared Spine/PDS infrastructure in Wales is evidenced; no single UK API or universal supplier role is inferred. Keep implementation-specific gaps in the country and diagnostic queue items. |
| UK nations connectivity | Keep GP Connect as NHS England evidence unless Scotland, Wales, or Northern Ireland official sources explicitly say otherwise; retain GP2GP as a distinct transfer workflow, with England GP Connect migration dependencies assessed separately. | Boundary | Current evidence supports GP2GP / GP record-transfer routes in England, Wales, Scotland, and Northern Ireland, but no nation-specific GP Connect evidence outside England and no InterSystems GP2GP proof. Recheck national roadmaps before using GP Connect language outside England, and require supplier/product evidence before linking any devolved GP2GP route to InterSystems. |
| Scotland connectivity | Current NHS Scotland InterSystems connectivity status beyond the Public Health Scotland and NHS Shetland evidence. | Moderate | PHS, NHS Shetland and Golden Jubilee support official local TrakCare / Ensemble facts, including a board-reported version-2024 upgrade. SRC-352 adds an Ayrshire and Arran software-support award; hosted-migration completion remains separate. SRC-328 confirms initial national MyCare.scot availability; later feature delivery and service-specific interfaces remain distinct. Still need NHS Scotland, NSS, procurement, or board-side sources for current national InterSystems integration-platform, hosted TrakCare, integrated-care-record, GP2GP involvement, and board-by-board operating status. To Do: validate any current Scotland GP2GP supplier or implementation detail against NSS, NHS Scotland, procurement, and board sources before linking it to InterSystems. SRC-375 to SRC-382 add SWAN/SCI Store/NDP detail and direct NHS Lothian TrakCare document-viewing evidence. SWAN2 and PACS completion remain unverified: the Government March 2026 target is estate-specific. Retain actual interface/version and board acceptance as the remaining gate; do not infer all-NDP FHIR or universal SCI Store APIs. |
| 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. DHCW primary-care evidence supports GP2GP as a Welsh primary-care service, not InterSystems involvement. SRC-329 adds first LIMS cellular-pathology go-live and revised tranche forecasts; SRC-330 adds a named CDR feed, and SRC-334/SRC-335 establish Welsh EPS Spine/PDS reuse and dated partial rollout. Obtain completed clinical-tranche and current EPS rollout evidence. SRC-383 to SRC-386 and SRC-392 add PSBA, operational WDS/WCCG, Philips RISP scope and named early-2026 imaging milestones. Keep final RISP rollout, LIMS discipline acceptance and WCP/WRRS migration separate; March draft milestones are targets only. |
| 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, a separate encompass/Epic/Rhapsody/DIS/ePharmacy context, and a BSO / HSCNI GP2GP objective that does not name InterSystems. Recheck DHCNI roadmap, BSO/eTendersNI procurement, GP IT Modernisation, and GP/primary-care integration material for any future scope change. To Do: validate any current Northern Ireland GP2GP supplier or implementation detail against BSO, HSCNI, GP IT Modernisation, eTendersNI, and procurement sources before linking it to InterSystems. SRC-387/SRC-388 establish live NIDIS Phase 1 and separate NHAIS GP-registration/screening replacement boundaries; Phase 2 acceptance and residual NHAIS functions remain unverified. SRC-389/SRC-391 name Sectra NIPACS+ and Clinisys CoreLIMS; June imaging closure reporting announces July operations handover prospectively. Resolve post-encompass NIECR role and any actual retirement/handover claim from a current service record rather than transferring legacy Caché attribution. |
| 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, and the September review adds a historical London North West NHS Jobs Health Connect signal, but no stronger current ICB/cloud procurement or operating-model evidence. 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 | Current national pages disagree on Medicus Access Document: the 1 September service page says FoT ready and the 3 September supplier table says development. Preserve both source-specific statuses; the FOI/source-target pack below remains the local evidence route. SRC-336 adds Medicus supplier-side regional integration confirmation, without naming HealthShare or the transport. 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 MERIT-specific post-contract continuity source. The later collaborative Shared Care Record FOIs confirm wider HealthShare contract facts to April 2029 but do not establish MERIT-specific continuity. Use a MERIT service/contract source to close this gap. |
| 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; additional public procurement, implementation, or customer-side records where current scope matters. |
| TrakCare PHC/community-health international | Current live-scope validation for Gateway Health, Nexus, Victoria, Chile APS, and DHAMAN evidence. | Moderate | Gateway CEO social corroboration, Nexus provider-level historical evidence, VHA Victoria status, newer SSMS workflow material, current SSMS-network hospital/procurement/municipal-health context, direct InterSystems Chile procurement signals, and DHAMAN network-scope source now exist; current Qatar PHCC sources do not support a present TrakCare claim. SRC-331 now limits Acacia to delivered FG0/FG1 with later phases deferred; government response and subsequent delivery evidence remain open. Still need formal Gateway publication, named current El Bosque APS live status, official Mercado Publico detail-link validation for the mirror-reported 2026 SSMS direct award, current Nexus status, 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. |
| Product support alerts | Applicability and correction evidence for the July 2026 HealthShare / IRIS for Health / Health Connect notices. | Boundary | SRC-295 to SRC-298 and SRC-300 supply concrete version/configuration questions for permissions, FHIR audit/access, SSO, consent, upgrades, fetch operations, Clinical Viewer patient context, NRL pointer labels and UCR ODS caching. Match a named deployment inventory to the full vendor notices and WRC correction records, then obtain local test, patch and safety evidence. No public notice proves a named customer is affected or remediated. Keep this within the existing HealthShare and product assurance pages. |
| IntelliCare / TrakCare | Deployment detail, AI-workflow controls and independent outcome evidence. | Boundary | SRC-345 strengthens all-hospital EMC implementation reporting; it does not close the independent-benefit gap. Use the IntelliCare workflow/outcome tables for attribution (SRC-341 to SRC-347). Parked following the user's 9 September direction to resume broader review. If specifically reopened, the EMC/EMTEK pilot evidence needed is: site and release, enabled features, participant/task denominators, comparator, time including review/correction, clinically significant errors, observation period and evaluator independence. Medcare/King's go-live, RedSalud rollout and certificate/intended-use scope retain their earlier boundaries (SRC-299, SRC-337 to SRC-340). No further open-ended search is scheduled by this row; reopen for a targeted methods/evaluation question, new evidence or user instruction. |
| England diagnostic exchange | Revised DAPB4101 conformance date and final pathology acknowledgement route. | Boundary | SRC-393 to SRC-396 establish the pilot, April 2027 assurance target and API/PDM/MNS route, but not a replacement compliance date or complete acknowledgement closure. Keep these gaps here; update the diagnostic-results page when NHS England publishes the revised milestone or final specification. No request pack is needed. |
| England imaging exchange | NIR rollout footprint, future FHIR/WADO-RS release and any IEP retirement. | Boundary | SRC-397 to SRC-400 support limited production beta and current SOAP/XCA interfaces, with mixed status/roadmap wording. Use dated NHS England rollout/release notices to advance status. Do not infer IEP shutdown from reduced-reliance objectives or procurement activity; no such national date was verified. |
| NCRS feature availability | GP Connect/shared-record pilot scope, dedicated COVID-view withdrawal date and any required field-level PDS editing permissions. | Boundary | The NCRS feature map, published activity/role table and source/launch diagrams now close the application-composition and public-permission mapping gaps. Field-level demographic edits remain unverified. SRC-045/SRC-046 retain pilot restrictions; SRC-403 announces vaccination-view retirement without a date, with COVID vaccination status retained in the Summary Care Record. Seek a dated feature release/retirement notice or specific permission specification only when that claim is needed; no new page or request pack is justified. |
| UK professional and patient portals | Local professional entitlements, staged patient-app features and NI legacy-record transition. | Boundary | The portal comparison and SRC-404 to SRC-415 establish public feature/access boundaries. Scotland board permissions are dated and MyCare cohort features differ from national coverage; Wales caregiver access and timeline expansion remain staged; NI archive/portal transition and individual record-release rules need dated operational evidence for any stronger claim. Obtain local access/workflow specifications only for an actual connection or role decision. These are bounded gaps, not grounds for another page or request pack. |
GP2GP Requesting Adapter Validation
The adapter synthesis closes the public-documentation research pass on 25 September 2026. Keep these issues in this queue; no new request pack or evidence-domain layer is justified. They reopen for an actual supplier/build selection, NHS clarification, changed source or customer artefact, rather than repeated broad searches.
| Evidence gap | Existing evidence and decision needed |
|---|---|
| Supported implementation baseline | Reconcile the requesting catalogue's maturity label with component assurance and release history. Obtain supported tag/image digests, upgrade dependencies, assurance scope and operational support owner. |
| Contract discrepancy | S94 and README reverse the practice roles assigned to TO/FROM headers; examples also differ in parameter spelling. Confirm the selected build's authoritative contract and evidence an end-to-end transfer. |
| Clinical timing and retention | Obtain an interpretation of attachment-retrieval versus integration clocks and the inconsistent retention interval. Do not silently repair source wording or invent a deployment policy. |
| Operations and failure recovery | Full operating/failure/redaction documents were not retrievable. Require configuration-specific storage expiry/deletion, retry/dead-letter recovery, logging and restricted-data test evidence. |
| ORC, Defence and deployment scope | ORC's live service does not prove this adapter's routing; a missing-ASID example does not survey DMS; Medicus functionality does not identify its adapter build or InterSystems participation. Require route-specific architecture and acceptance evidence. |
National-Service Matrix Gaps
The UK Core Services Matrix now separates delivery scope from missing evidence. The 16 September follow-up replaces bare gaps with trust/laboratory, imaging-provider and Scottish health-board routes. ECS/KIS through NIECR and NI hospital-to-GP EDT are documented functions; their earlier unnamed-counterpart gaps are closed.
Remaining limits concern current NIECR GP-summary feed completeness, NI national electronic prescription transfer and live GP2GP scope, and SCI Store's complete current coverage. SCI Store's national adoption is historical; local and supplier evidence does not settle every board/discipline. Reopen these for a current coverage/transition notice or an actual interface decision. A provider-level route does not itself require more research: request local configuration only for a concrete connection. Existing pathology/NIR, NIDIS/NHAIS and portal rollout rows retain their own triggers; no additional request pack is justified.
DSIC-Lens Comparison Limits — 29 September 2026
The expanded matrix retains meaningful single-nation services and marks unverified counterparts, not absent clinical care. These are bounded implementation/source gaps; they do not justify new pages or request packs. Existing NIDIS/NHAIS and national-rollout rows still own their transition questions.
| Gap | Evidence boundary and next concrete validation | Existing destination |
|---|---|---|
| Devolved full-GP read/write, cross-organisation booking and bulk interfaces | Public summary/portal functions do not establish a general GP API or bulk route. For a chosen use case, compare the national/supplier interface contract, approved requester role and record coverage with the specific England capability; do not infer IM1 from a shared supplier. | UK Core Services Matrix and country modules |
| Welsh identity and registration reuse versus current DSIC versions | NHS login and PCRM reuse are evidenced; September 2026 S125/VRS/patient-facing API adoption and exact GP registration endpoints are not. Retrieve the Welsh service's current interface/authorisation specification before asserting those features. | Wales Connectivity Equivalents |
| Prevention-system transitions and current extraction products | Scottish CHS replacement is explicit, but exact interface cutovers are not; Welsh Audit+ later replacement and NI child-health operational migration are unverified. Use dated acceptance/interface evidence, not programme forecasts or statistical source labels. | Scotland, Wales, Northern Ireland |
| National flags, endpoint directories and notification equivalents | No general devolved counterpart established for England SDS, NRL, adjustment/FGM flags or NEMS/MNS/NHS Notify APIs. Local registers, plans and feeds remain evidenced routes. GIRFEC provides Scotland’s wider framework; its child’s plans and local child-protection registers do not establish NHS CP-IS or FGM-IS API equivalence. England's flag APIs are documented, but generic retirement wording does not establish a completed Patient Flags migration; confirm the selected production route when onboarding (SRC-653 to SRC-655). Request the named national-service/interface specification only when its absence blocks a real connection decision. | Matrix safety and prevention; England flag interfaces |
| FPPS and payment-interface scope | NI BSO → Wales FPPS provision is evidenced; the audit does not establish every current NI payment workflow. Verify current nation-specific payment module, input/output contract and rules for any proposed reuse. | Matrix coding/reporting/payments |
Urgent-Care Routing Limits
Reviewed 29 September 2026. The urgent-care comparison is a functional baseline, not a national endpoint inventory. Keep these gaps here; no separate request pack or new page is justified.
| Gap | Evidence boundary and concrete next validation | Existing destination |
|---|---|---|
| England DoS operation/lifecycle mismatch | DoS Search has organisation lookup but not its published clinical service-search operations in UAT/production. Existing SOAP/REST remain production under review; public DoHS legacy version/retirement text conflicts. Compare the operation-specific OAS, release notice and applicable onboarding route before changing an interface. | England urgent routing |
| BaRS supplier assurance versus actual receiving service | Supplier-assured Nervecentre is not evidence that a chosen hospital receives that application live; no InterSystems entry was found. Match the named sender/receiver application and product version to the current supplier register and customer implementation. Do not infer a live endpoint from an EPR estate row. | England urgent routing |
| Devolved handoff, booking and notification interfaces | Public service descriptions and dated Adastra/CCG evidence do not establish current payloads, endpoint access, acknowledgements or appointment ownership. For one named NHS 24/FNC, Welsh 111/OOH or NI Phone First route, identify the receiving service and obtain its interface specification before claiming BaRS/GP Connect/DoS compatibility. | Urgent-care adapter boundary |
| NI directory scope conflicts | SPPG says Belfast adults-only while the Trust's current ED page includes children; Southern current contacts extend beyond old pilot FAQ hours. Reconcile direct Trust operating guidance with the central listing before publishing a patient-facing directory or encoding eligibility rules. | NI urgent routing |
| New national routing proposals | Scottish navigation centres/hubs, wider Welsh directory/booking work and NI HSC 111 proposals are not completed rollouts. Current interface/acceptance evidence is required before advancing their status. Park launch assertions until a dated implementation source or a concrete integration decision warrants reopening them. | Country urgent-care sections |
Future Content and Narrative Work
Status: To Do — recorded 16 September 2026. The content review is complete; the editorial and presentation changes below are future work. The review sampled entry points, anchor and detail pages, and the locally rendered Home and Executive Summary. It was not a fresh validation of every external source.
The main gap is reader progression: introductory explanations sometimes give way to dense assurance tables, repeated caveats and research chronology before the reader understands the system. Preserve four connected reading arcs:
- Product understanding: product roles → components → documented uses.
- Healthcare connectivity: connectivity layers → national services → clinical workflows.
- Evidence and assurance: capability → conformance → deployment → outcomes.
- Defence application: DMICP/CORTISONE question → proposed architecture → outstanding proof.
Planned Passes
- Clarify entry points and shorten the executive route. Review Home, Knowledge Base and Executive Summary. Consider the label “Defence Connectivity: Executive Summary” while retaining the existing URL. Put a brief answer, the proposed architecture and main decision constraints before detailed assurance tables. Complete when a new reader can distinguish the broad introduction from the Defence application, with existing evidence and deep links still accessible.
- Pilot a workflow-led HealthShare explanation. Build on the clinical-data synthesis gap in HealthShare, Products and Services and Comparative Analysis. Explain an illustrative sequence from source systems through integration and identity matching to the shared record and clinician view. Keep the detailed component inventory owned by the HealthShare page and shorten duplication in the portfolio. Complete when each component's job is clear and illustrative steps cannot be mistaken for a verified customer architecture.
- Separate current explanations from research chronology. Use the question-led model and medicines example in Standards and Interoperability as the template. Consolidate repeated role descriptions in product/component pages; retain dated research decisions in the existing Research Log. Complete when unique claims, source links, dates and material limitations remain in the current linked content, while each overview explains the resulting model before its research history.
- Improve scanning and visible evidence access. Review long table cells, repeated highlighted links and source-ID suppression in the rendered Executive Summary and standards overview. Prototype concise comparison cells and compact evidence links while preserving Markdown source IDs. Apply the existing design contract, keeping
DESIGN.mdanddocs/assets/theme.cssaligned for any styling change. Complete after desktop/mobile review shows readable tables, working source links and preserved evidence boundaries; naming or navigation changes must also preserve aliases and anchors. - Resolve reader-visible history and source-preservation needs. Use the page-history boundary to assess last-substantively-reviewed metadata, page-history access and selective dated captures of changeable external evidence. Record a concrete implement/defer decision for each. GitHub history links must account for the private repository; an edit timestamp must not imply a fresh evidence review. Do not duplicate every wiki page or treat JJ recovery as an external-source archive.
- Test a separate national-service reading journey. Starting from the UK Connectivity Landscape, follow one comparable task across the existing country pages: identify the portal, its information sources, permitted actions and availability. Record confusing handoffs and fix them in place. Complete when the route distinguishes application, source record, permissions, rollout and supplier evidence without a new routing page.
Non-destructive implementation preserves unique evidence, qualifications and working links in the current wiki, with earlier wording recoverable through committed history. Apply the structure stop/go rule before adding structure; these passes fit existing pages. Use small JJ commits, regenerate the no-API index and Graphify, run the repository checks, and verify clean pushed Git state. Mark individual passes complete only after their changes and checks are done.
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 Shared Care Record 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 8 September check updates subject-access, research and automated-decision planning statuses below; other tracker topics retain their earlier verification dates. Planned or draft guidance is not final implementation authority.
| Topic | Current wiki position | Replacement trigger | Affected pages |
|---|---|---|---|
| Subject access and reasonable/proportionate searches | Rechecked 2026-09-08. The main guide covers one-month response, justified extensions, identity verification, reasonable and proportionate search, clarification stop-clock, secure accessible supply and an alternative when a requester cannot or does not want to use a portal. Right of Access in brief is now published, closing that publication gap; SARs Q&A remains drafting with an autumn 2026 target. Other companion products retain their earlier check dates. | 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-09-08. The ADM/profiling consultation is closed and guidance remains drafting with a winter 2026 final target. Current organisation guidance retains tighter significant solely automated decision restrictions for special-category data, including health data. HealthShare AI Assistant, IntelliCare, triage, risk scoring and workflow automation still need deployment-specific safety and governance evidence. | 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-09-08. General Research, Archiving and Statistics guidance remains redrafting despite the tracker’s elapsed summer 2026 target. Research anonymisation/pseudonymisation consultation is now open, with final guidance targeted for winter 2026. These targets do not establish publication. Secondary-use and analytics deployments still need lawful-basis, approval, 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 |
UK Clinical Platform Estate
The UK-wide baseline is complete as a dated research baseline, not a full provider/site census. Keep gaps here rather than creating individual trust pages or a new evidence domain.
| Evidence gap | Current boundary | Concrete next evidence action |
|---|---|---|
| Current shared-record suppliers and migrations | Lancashire supplier unverified; four Scottish board assignments unknown. Dorset/Nottinghamshire/Gloucestershire/Cheshire retain historical and transition observations. | Retrieve the primary Lancashire continuity award FTS 046130-2026 and current commissioner supplier statement; obtain dated local go-live/decommission notices for the four transitions, then update the existing dataset rows. |
| Successor ICB programme footprints | All 36 current ICBs have programme associations, but Central East, Essex, Norfolk/Suffolk, Surrey/Sussex and Thames Valley contain legacy programmes or cross-boundary services. | Build a provider-participation crosswalk from current programme lists for the merged ICBs; qualify overlapping access/publication roles rather than assigning a single supplier to a polygon. |
| Hospital estate denominator and exceptions | England is selected coverage. Scotland D&G/Western Isles and Wales Cardiff/Vale have unknown alternative core EPR/PAS rows. Scottish PMS and Welsh WPAS do not prove complete clinical EPR scope. | Reconcile the baseline with a current official trust/board roster; source the three named alternative estates and missing English priority-supplier deployments. |
| EpicCare Link scope | Eleven distinct observations; ESNEFT pilot. Roles, patient cohorts and enabled referral/order/result functions differ. | Compare current provider onboarding guides for NI, Devon and ESNEFT; record read/view versus order/referral permissions and catalogue limits in the existing portal observations. |
| Diagnostic phase/site/discipline coverage | Welsh LIMS/RISP, Scottish PACS, Highland order comms and Kent/Medway WinPath have phased or unconfirmed completion. ABUHB transfusion WinPath is a concrete exception. | Retrieve site/discipline acceptance and current operational guidance, then link each backend to its evidenced GP and hospital front ends. |
| Dated or unavailable diagnostic instructions | UHL handbook direct URL returned 404; NCL guidance is overdue; Stockport tQuest guidance is old despite new WinPath evidence. | Find replacement provider handbooks or dated system lists; update the existing observations and mark superseded guidance historical. |
| Exact collaborative contract boundary | SRC-443/SRC-444 confirm HealthShare, three areas and April 2029; BCHC gives 31 March 2029. | Resolve the precise contract end and signed service/hosting schedules when a procurement or architecture decision requires them. Do not infer MERIT-specific continuity from the wider contract. |