Confirm current product availability, licensing, named hosting regions, customer-specific managed-service boundaries, support commitments, and security/compliance controls for IRIS for Health, FHIR Services, FHIR Server, Bulk FHIR Coordinator, OMOP, HealthShare components, HealthShare Unified Care Record, HealthShare Clinical Viewer, EMPI, Provider Directory, and Health Connect; current public docs now support cloud FHIR, OAuth/security, Network Connect, Health Connect Cloud, Cloud Services Portal, UCR product positioning, Clinical Viewer presentation/access positioning, Care Community / Personal Community patient-contribution integration mechanics, and general cloud-hosted-service boundaries, but not customer-specific commitments. The 2026-06-20 Health Connect, IRIS for Health, FHIR Services, UCR, Clinical Viewer, and HealthShare / PRSB CIS audits plus the 2026-06-21 Care Community and EMPI / Provider Directory passes still need current NHS/customer conformance, onboarding, validation-scope, managed-service assurance, SSO/RBAC/audit configuration, AI-adjacent governance where enabled, and customer deployment evidence before using product capability or conformance facts as implementation proof. For EMPI / Provider Directory, PDS/ODS evidence now defines the national-service requirements, and PDS integrated-products evidence names Intersystems HealthConnect 2020.1; still seek EMPI / Provider Directory product/version, PDS FHIR onboarding, ODS/SDS mapping, matching/stewardship, synchronisation, audit, safety ownership, and deployment artefacts.
For DSIC, locate public catalogue/supplier records naming InterSystems, HealthShare, Health Connect, IRIS for Health, or partner products by capability and standards scope. Current DSIC analysis supports component relevance but not a full DSIC GP foundation-system claim.
Track remaining Data (Use and Access) Act 2025 non-data-protection commencement points and final ICO guidance for Right of Access in brief, SARs Q&A, research, automated decision-making/profiling, IDTA/Addendum transfers, and enforcement/code processes; current ICO guidance now replaces GOV.UK factsheet-only treatment for complaints, lawful basis / recognised legitimate interests / purpose limitation, storage/access technologies, the main subject-access guide, and parts of international transfers. Treat this as a trigger-based queue item rather than the default next pass.
Keep the new structured DSIC capability-to-standard crosswalk current, especially for Patient Information Maintenance, Appointments, Consultation, Prescribing, Referral, Document, Task, Reporting, Scanning, patient-facing services, Personal Health Record, and Unified Care Record.
Track the Digital Primary Care replacement framework and Buying Catalogue changes, because DSIC procurement routes are versioned inputs rather than static facts.
Extend source/evidence domain pages only where they reduce repeated traversal of sources.md and evidence-matrix.md; NHS England Digital Primary Care, HealthShare Components, and Standards and Interoperability are now split. UK NHS examples were reassessed and do not yet need a separate evidence-domain page because the overview plus independent example pages remain navigable. The 2026-06-20 devolved-nations traversal-cost check does not justify another page now; create one only if future passes repeatedly traverse the parent comparison, three connectivity pages, three InterSystems-by-nation pages, and canonical registers for the same cross-nation question.
Validate the structurally parsed NHS GP Connect supplier-progress InterSystems rows against the GP Connect evidence request pack, product documentation, assurance artefacts, and customer deployment evidence; the table now maps IRIS for Health (Middleware) to Send Document (Send) v2.0.1 and HealthShare to Access Record: Structured Medications, Allergies, Immunisations, and Uncategorised cells, but it does not prove live local use.
Validate InterSystems GP Connect support using GP Connect-specific InterSystems documentation and implementation-specific evidence, keeping service definition, capability taxonomy, mirrored due-diligence checklists, architecture pattern, Update Record pharmacy write-back scope, MESH/ITK3 adjacency, and InterSystems evidence boundaries separate.
Keep NHS England GP Connect, Spine, and DSIC evidence separate from Scotland, Wales, and Northern Ireland functional equivalents. The latest pass added comparison pages for ECS/KIS/CHI/NDP/SCI/ePharmacy/MyCare.scot in Scotland, WGPR/WCP/WCCG/NDR/WDS/NHS Wales App in Wales, and NIECR/encompass/EpicCare Link/HCN/DIS/ePharmacy in Northern Ireland. Future passes should add deeper architecture/API sources before treating any of those routes as more than functional equivalents.
Add official NHS/customer/procurement sources for North West London ICS and West Midlands Cancer Alliance / UHB cancer registry claims. North West London now has vendor, Digital Health/AWS/6B, and acute-trust Health Connect / TIE recruitment evidence, but still no public ICB/customer programme, contract-award, or procurement source for the ICS-level Health Connect Cloud operating model. West Midlands cancer/eMDT evidence remains vendor plus Digital Health/local eMDT context, not UHB or West Midlands Cancer Alliance confirmation of the InterSystems component.
Add current Huma/eConsult/NHS/customer architecture evidence to confirm the live eConsult/eTriage / Digital Front Door InterSystems role. Current evidence now supports historic IRIS for Health selection, current InterSystems/Huma HCC vendor positioning, and public Digital Front Door signals, but not product-version, HCC-versus-IRIS role split, clinical-safety ownership, interface specifications, or site-by-site deployment artefacts.
Add formal North Tees and Hartlepool NHS Foundation Trust procurement or outcome-evaluation evidence beyond trust news, quality-account, board, and award narratives.
Confirm current operating status and post-2026 continuity for MERIT and the Birmingham / West Midlands shared-care-record programme, and use the Evidence Validation Queue FOI/source-target pack to extend the Birmingham / West Midlands DUAA worked evidence pack with final DSA/DPIA, DCB0129/DCB0160, supplier-responsibility, GP Connect/MESH/ITK3 onboarding, Medicus integration architecture, and current live-status artefacts. Official NHS sources now support national Medicus GP Connect status, but not the local West Midlands HealthShare route. Hold further deepening until a request is drafted/submitted, a response arrives, or a new official/customer source appears.
Track The Royal Orthopaedic Hospital TrakCare EPR implementation milestones, go-live date, clinical-safety approval, and outcomes after the selection, contract signature, Contracts Finder award, and medicines-strategy planning evidence.
Verify the current status of NHS Interoperability Toolkit accreditation or related UK interoperability certifications outside the InterSystems website. Rechecked 2026-06-20: current IRIS for Health docs, the NHS ITK conformance process, and the NHS ITK conformance-catalogue route were found, but no current public InterSystems, HealthShare, Health Connect, or IRIS for Health catalogue row/certificate was exposed in the rendered catalogue or targeted public search; the Solution Assurance compliance catalogue excludes ITK Accreditation. 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.
Monitor contemporary NHS roadmap sources for GP Connect supplier progress, Update Record releases, NCRS Access Document pilots, NHS App patient-facing API work, and Single Patient Record / Connecting Care Records dependencies.
Validate Clinical Viewer, Navigation Application, HealthShare component configuration, and HealthShare AI Assistant SSO, embedded-workflow use, version differences, RBAC, audit, prompt, and clinical-safety controls using current product documentation, the Clinical Viewer high-risk audit on InterSystems Standards Product Map, the reusable standards-conformance request pattern, and the HealthShare Components Evidence Domain; public HealthShare 2026.1 documentation is account-gated and the AI Assistant sample repository is useful but incomplete for governance detail.
Continue validating international TrakCare PHC/community-health evidence: find a formal Gateway Health go-live publication, a Victorian Government or provider-level TrakCare scope source, named El Bosque / SSMS APS live-status evidence, and a DHAMAN primary source naming TrakCare. Treat Qatar as historical-only unless a current PHCC or Ministry of Public Health source names TrakCare.
Treat Programme CORTISONE / UK Defence healthcare as a contained evidence area except where the Executive Summary exam question requires DMICP / CORTISONE interface proof. Do not use Defence as the default breadth target, but keep the specific proof gap visible: DMICP interface catalogue, CORTISONE architecture, Health Connect / SDA / FHIR / HL7 / CDA mediation route, HealthShare component/version scope, national-service adapters, DSA/DPIA, DCB0129/DCB0160, and operational runbook evidence.