Research Log

2026-10-01 - Separate Summary Ordering and Viewing Rows

Split the executive summary’s combined pathology/imaging ordering row into Order pathology and Order imaging, placing each directly above its corresponding results/reports row. Split Professional / patient viewing into Professional viewing and Patient viewing, with separate service links and the relevant permission, feature and rollout limits for each nation. The detailed matrix already separates these functions.

The summary now has 38 grouped rows, covering the same 43 detailed functions. Existing Access styles, six paired Current Med IS markers and their date/scope are unchanged. This is a presentation and wording correction using the existing country evidence, not new service research. Updated the maintenance rule and WN-007 editorial progress; the existing WN-008/002/006 options remain unselected.

2026-10-01 - Synchronise Current Med IS Summary Highlights

Repeated the six existing user-reported England Current Med IS service markers from the matrix in the executive summary, using the existing light-teal cell highlight and accessible ticks. PDS, ODS, EDIFACT pathology over MESH, e-RS, MESH document exchange and HSCN retain the same 21 September 2026 reporting date and scope. The combined Referrals and documents summary cell has two separately keyed ticks; six markers therefore occupy five summary service cells. Access columns remain neutral.

Added a Healthcare network summary row for HSCN, SWAN, PSBA and HSC WAN, bringing the summary to 36 grouped rows while the matrix stays at 43 unique functions. Network Access is Other because the row describes transport rather than clinical APIs. The pathology tick still applies only to EDIFACT over MESH; the separate FHIR reporting pilot is excluded. No new current-service availability, external-source verification or supplier-assurance claim is introduced.

Added stable data-med-is keys and a shared dated legend for paired validation. The review guard checks all six keys, their expected England service cells and valid matching ISO legend dates, recorded here as data-med-is-date="2026-09-21"; a mismatch blocks review recording. Updated the operational contract and WN-007 partial editorial progress; WN-008, WN-002 and WN-006 remain unselected. Existing source-review dates, reading order and regular Service/Access headings are preserved. Validation and publication follow the established lint, strict build, no-API index/Graphify, verification, JJ/main clean-push and Cloudflare workflow.

2026-10-01 - Core Services Reading Order and Reconciliation

Addressed the user’s navigation and synchronisation comments by making the national-service reading order UK Core Services Executive Summary → UK Core Services Matrix → UK Healthcare Connectivity Landscape, followed by country detail. The summary remains independent and immediately before the matrix; section entry links and page introductions now distinguish quick comparison, detailed functions and architectural/programme context. Existing paths and source-review dates are preserved.

Reconciled existing safeguarding/flag, authentication and opt-out interface qualifications and gave the summary its own DSIC comparison section. The matrix retains 43 unique functions and six user-reported Med IS markers; the summary retains 35 grouped comparison rows. The repeated child-protection and FGM rows remain identical to their respective originals in each page. Existing Access columns, regular Service/Access subheadings and standard table separators are retained. This is an editorial reconciliation of documented evidence, not a new nationwide service or supplier validation.

Strengthened the explicit review gate to fingerprint the summary body (excluding its own marker) plus 11 source pages, now including the landscape. Structural checks require five topic tables, a separate DSIC explanation, cross-border list/table entries and exact safeguarding repeats within each comparison page. These checks cannot establish semantic correctness; manual review and an explicit --record-review remain required. Updated the operating rules and concise operational notes; no new wiki page, evidence domain or dependency is introduced.

Reconciled WN-007 as partial editorial progress. WN-008, WN-002 and WN-006 remain unselected, actionable closure/synthesis/breadth suggestions. Validation and publication follow the existing design lint, strict build, no-API index/Graphify, verification, JJ/main clean-push and Cloudflare workflow.

2026-09-30 - Safeguarding Views in Both Core Services Pages

Added a Safeguarding subsection under Safety, Prevention and Care Planning in the executive summary and detailed matrix. Each repeats its existing child-protection and FGM rows exactly, with reciprocal links and a scope note. GIRFEC remains within the Scottish child-protection entry; general care planning, child-health and accessibility functions are not reclassified. The matrix still describes 43 unique functions, and its six Med IS markers are unchanged.

Rechecked the existing NHS CP-IS/FGM guidance, legacy FGM API scope and Scottish GIRFEC evidence; no new service claim or source ID was needed. Updated operational guidance and reconciled the paired review marker. The country and service anchors retain the detail; WN-008, WN-002 and WN-006 remain unselected follow-up suggestions.

2026-09-30 - Regular-Weight Service and Access Subheadings

Made the Service and Access subheadings regular weight across the UK Core Services Executive Summary, as requested. The CSS targets only those table headers. Updated DESIGN and maintenance guidance; table content and the evidence review marker are unchanged.

2026-09-30 - Restore Consistent Summary Table Borders

Removed the added Access-cell borders from the UK Core Services Executive Summary, following the user’s styling correction. The grouped Service/Access columns now inherit the standard wiki table separators. Updated DESIGN and the maintenance contract; the summary’s content, detailed matrix and evidence review marker are unchanged.

2026-09-30 - Executive Topic Coverage and Separate Access Boxes

Addressed all six browser comments on the Core Services Executive Summary. Access/registration/GP transactions, urgent-care routing, safety/prevention/care planning, coding/reporting/payments and actual cross-border reuse now each have an explicit executive section. Thirty-five concise function rows group the detailed matrix’s 43 functions without copying its technical discussion; child protection and FGM remain independent. The original matrix file is unchanged in this pass.

Each nation now has service text and a separate Access cell on its right. Following the user’s final clarification, System replaces S2S; Portal, Local, Files, Other, Planned and Unverified describe other routes. Mixed values identify the distinct exchanges described in a cell, such as the NI EDT feed and EpicCare Link portal. Added a narrowly triggered presentation transform for grouped nation headers, explicit accessible header associations and preserved authored access values, with neutral existing design tokens and horizontal scrolling. DESIGN and the operational maintenance contract document the authoring pattern. No dependency upgrade or new wiki page was needed.

Parallel evidence checks supported existing devolved distinctions and identified specific England flag interfaces. Registered SRC-653–655 and added an England interface-status table: CP-IS HL7v3/MESH production routes, deprecated legacy FGM read, and Patient Flags internal/beta operations remain distinct, with conflicting migration language recorded in the existing queue. SRC-656 supports ScotAccount OIDC authentication onboarding; SRC-657 supports National Data Opt-Out MESH list checking, separate from preference-setting and direct care. Refreshed SRC-420 with the ODS API distribution scope for named NI organisation classes. Country pages and canonical claims hold the new evidence; markers do not establish general availability or supplier implementation.

Expanded the paired review dependency set to include terminology, making ten canonical source pages. Checked matrix, country, diagnostic, DSIC and terminology anchors, preserved existing rollout/onboarding and Med IS limits, and reconciled WN-007’s partial editorial coverage. WN-008, WN-002 and WN-006 remain unselected follow-up options. Validation follows the existing presentation tests, design lint, strict build, no-API index/Graphify, JJ/main clean-push and publication workflow.

2026-09-30 - Core Services Executive Summary and Integration Indicators

Created the requested independent UK Core Services Executive Summary immediately before the matrix in navigation, with reciprocal links and a landscape entry. The structure gate approves a distinct reader level over 43 detailed functions; it does not create another evidence domain. The matrix’s substantive content, row count, source dates and six user-reported Med IS markers remain unchanged.

Reconciled existing England/Scotland and Wales/NI evidence in parallel. The summary distinguishes documented S2S APIs/messages/feeds from portals, local configurations, unverified external interfaces and planned or restricted services. In particular, EpicCare Link orders/referrals remain portal workflows, NI EDT is a separate hospital-to-GP feed, Scottish NDP interfaces retain access limits, and GIRFEC remains a framework. This is an editorial synthesis pass, not a new nationwide external-source or supplier validation; no new source IDs are required.

Added an explicit nine-source-page review digest check and targeted Node tests, included in repository/CI verification. Source changes require semantic review and a deliberate --record-review; normal builds and kb:update cannot silently acknowledge them. Updated operational guidance, navigation design, context and suggestion dispositions. Existing WN-008, WN-002 and WN-006 remain unselected closure/synthesis/breadth options. Validation and publication use the established lint, strict build, no-API index/Graphify, JJ/main clean-push and Cloudflare workflow.

2026-09-29 - Separate Safeguarding Rows and Explain GIRFEC

Addressed both browser comments: split the combined child-protection/FGM matrix row into two independent functions and added GIRFEC to Scotland’s child-protection cell. The matrix now has 43 functional rows, with all six Med IS markers unchanged. A focused Scottish Government review and parallel scope check established the distinction between the GIRFEC framework, child’s plan, Child Protection Plan, local-authority register and digital alert. Added a subsection within the existing Scotland page and three glossary entries; no new page, navigation change or evidence-domain layer was needed under the structure gate.

Registered the GIRFEC policy/practice sources as SRC-652, reused and clarified SRC-608, and rechecked England’s CP-IS/FGM-IS guidance under SRC-402. Updated the evidence claim, existing interface-limit queue and operational context. The 2023 Police Scotland flag reference is explicitly scoped and dated; no national NHS API, absence of Scottish digital safeguarding systems or InterSystems implementation is inferred. Existing WN-008, WN-002 and WN-006 remain unselected follow-up options in the suggestion register; this clarification does not start those tasks.

Use the existing no-API index/Graphify regeneration, verification, JJ/main clean-push and Cloudflare publication workflow for the edited pages.

2026-09-29 - What Next Suggestion Reconciliation

The user questioned the relevance of the GP API and identity/registration follow-ups and requested a wiki working base of unpursued suggestions. Added one suggestion register after applying the structure gate: repeated traversal across chat recommendations, priorities, the queue and completed work justified a selection layer, not another evidence register. Seeded eleven stable WN entries from the available conversation and existing wiki priorities; explicitly did not claim an exhaustive historical-chat import.

Parked the broad devolved GP API item pending a named connection decision. Retained registration/identity as a partly covered explanation task. Marked the urgent-care comparison complete and merged the 111-report and urgent-handoff examples. Indexed the six existing editorial passes without copying their detailed criteria. Narrowed the stale four-nation research priority and acknowledged the platform estate baseline in the deployment priority. A parallel read-only audit corroborated the relevance and duplication decisions. No new supplier-interface research, external correspondence or implementation was performed.

Added navigation and Home links using the existing presentation contract, and updated AGENTS plus the LLM maintenance/context/starter guidance so future response suggestions are recorded, reconciled and linked before presentation. Existing evidence and source registers retain their roles. Verification follows the established design lint, strict MkDocs, no-API index/Graphify, repository gate, JJ/main clean-push and Pages publication workflow.

2026-09-29 - Four-Nation Urgent-Care Routing

Followed the user's annotated request for BaRS/DoS, NHS 24, NHS 111 Wales and NI pathways. Added five functional rows to the existing matrix (42 total): access, triage, discovery, referral/GP notification and appointment arrangements. Three parallel primary-source reviews supplied the four country sections. Registered SRC-630–651 and refreshed SRC-169, SRC-206 and SRC-380 rather than duplicating existing source URLs. No new page, map, dependency or evidence-domain layer was required.

Confirmed role-specific S33/S93/S107 requirements and separated England's three directory services, staged DoS Search operations, BaRS assurance/live application status and existing SOAP/CDA 111 reporting. Scotland's NHS Pathways assurance learning is not software adoption; NHS 24/FNC handoff contracts remain unverified. Wales has CPSS/ECNS, dated booking/handoff evidence and actual England/Wales border referral routing. NI's ministerial 111 status, local Phone First scope differences and historical Adastra/CCG evidence remain distinct from universal deployment or encompass integration.

Updated PRSB referral-versus-notification detail, DSIC crosswalk, existing adapter model, glossary, evidence claims, queue and operational context. Final rendered-source validation found and removed inherited blank lines that had split the source-register table before SRC-443, SRC-592 and SRC-593; recent evidence rows now remain in the canonical table. Peer reviews checked matrix country cells, terminology and source reuse; source conflicts and proposals retain explicit limits. Use the established index/Graphify, strict verification, JJ/main, clean-push and Pages publication workflow.

2026-09-29 - Four-Nation GP Functions Through the DSIC Lens

Expanded the existing UK Core Services Matrix from 15 to 37 functional rows after the user's browser comment, retaining all six user-reported Med IS markers and their 21 September date. Added access/registration/GP transactions, prevention/safety, coding/reporting/payment comparisons; significant single-nation services remain visible with unverified counterparts distinguished from absent care. The original 16 September core-service review date remains separate from this extension.

Three parallel primary-source reviews covered England DSIC, Scotland, and Wales/NI. Registered SRC-593–SRC-629, preserving older source IDs. Current DSIC catalogue evidence includes September identity/provisioning/relationship/patient-facing changes and vaccination FHIR-versus-MESH obligations, with onboarding limits separate from effective standards. Strong corrections include Scottish CHS replacing CHSP/SIRS, PCIS after SPIRE, NI GPIP/QOF after PCAS, and Welsh PCRM/WDS after NHAIS. Cross-nation reuse is evidenced for Welsh NHS login/Spine/PCRM, NI BSO supplying Welsh FPPS, Scottish NHSCR administrative exchanges, shared terminology and joint UK Core work. None establishes universal GP APIs or InterSystems conformance.

Applied the structure gate: extend the existing matrix, DSIC crosswalk and country anchors; no new page, evidence domain, map, dependency or request pack. Updated canonical claims/queue, glossary and LLM context. Independent nation reviews checked role and coverage limits; corrected an implied devolved supplier/bulk-access claim to unverified. Regenerate discovery assets and use the established verification, JJ/main, clean-push and Pages publication workflow.

2026-09-25 - UK Clinical Platform Estate Baseline

The user requested a new shared-record/EHR/diagnostics topic and selected a UK-wide baseline first. Applied the structure gate: five reader-facing pages and one shared dataset reduce repeated supplier/country/provider traversal, without another evidence-domain register. Three parallel research slices supplied 193 scoped observations (40 shared-care; 98 EPR/PAS; 11 portal; 44 diagnostics), 168 public source URLs and all 36 current English ICB associations. Registered 150 new sources SRC-443–SRC-592 and reused 18 existing IDs.

Inspected sibling projects read-only using Graphify where present. DShCR supplied the current ICB-crosswalk lead; dmsGIS supplied public-derived devolved boundary geometry; veloGIS informed the lightweight map choice; X-Lab supplied a public NHSBT procurement lead. Fresh ONS April 2026 England geometry replaces older derived ICB shapes. No private source content or operational/facility metadata was copied. Pinned Leaflet 1.9.4 from the official stable release, installed with lifecycle scripts disabled; no heavyweight GIS dependency needed.

New evidence separates HealthShare in six current ICB associations from successor-wide coverage; Oracle London HIE from InterSystems integration; Epic/EpicCare Link from departmental products; Scottish TrakCare PMS and Welsh WPAS from full clinical EPRs. Retained historical/transition/unknown observations, including Dorset/Gloucestershire and site/discipline-specific diagnostics. Independent audit strengthened MKUH via its 23 September 2025 trust response and downgraded UHL handbook currency because direct retrieval returns 404. BSMHFT FOIs close collaborative supplier/contract identification while preserving March/April 2029 and MERIT-specific boundaries.

Updated affected anchors, source/evidence/queue/LLM controls, navigation and design contract. Generated article tables, accessible local map and CSV/JSON from the same validated dataset; use the existing strict build, Graphify, JJ/main, clean-push and Pages-publication workflow for completion.

2026-09-25 - GP2GP Sender Registration Check

The user's technical follow-up prompted a focused check of S94 Step 10 and the adapter API contract. Made the sender's mandatory PDS current-GP check and NACK 19 explicit in the adapter FAQ, architecture, Evidence Matrix and LLM context. The earlier answer described the supported workflow but omitted this material technical enforcement point. Distinguished an adapter accepting a request from the sender releasing the EHR, and an existing registered-requester retry/resend from third-party viewing. Rechecked SRC-428 online; direct current repository/API access returned 404, so no new executed-code or live-supplier claim is made. Existing source and validation trails suffice; no new page or queue item. Regenerate discovery assets and run the established verification, JJ/main clean-push and publication workflow.

2026-09-25 - Read-only Access and Registration Clarification

Made the user's read-only/full-record and “pull registration” questions explicit in GP2GP Requesting Adapter, with reciprocal HTML-view and architecture links. Distinguished the adapter's transfer contract from the receiving system's permanent registration/PDS update and from PDS registered-GP lookup. Preserved resend, mapping and missing-attachment limits. Rechecked the existing HTML catalogue source; this is a clarification of SRC-028, SRC-036, SRC-037, SRC-428, SRC-432, SRC-433 and SRC-435, with no new page, evidence gap or implementation claim. Checked affected context-map anchors and added the concise operational boundary. Validation follows generated-index/Graphify regeneration, the full repository gate, rendered checks, JJ/main clean push and Cloudflare publication.

CI exposed a pre-existing Graphify publication edge case: the source-less HTMLParser node retained a raw community number in its group key/label, so equivalent local and Linux graphs produced different browser assets. Changed external-node grouping to stable node identity and labels, with a focused regression check; retained the full freshness gate and dependency versions.

2026-09-25 - GP2GP Requesting Adapter Research

Researched the NHS Requesting/Receiving Adaptor and Patient Switching implementation across current NHS catalogue/service pages, full S94 requirements, S43, R9 onboarding, GP Connect dependencies, repository setup/mapping/change history and adjacent workflow evidence. Added SRC-427 to SRC-442 and GP2GP Requesting Adapter, with architecture, interface, clinical receiving responsibilities, operations and assurance boundaries. Corrected the parent/anchor model: GP2GP is a distinct transfer workflow whose FHIR implementation reuses GP Connect migration operations. InterSystems and Defence implementation remain unproven.

Read the full S94 body through the public Confluence REST API because the indexed page stopped at requirement 47; checked its incorporated historical degrade PDF, including visual review of pp. 2–3. Kept current requirements separate from historical exceptions. Preserved source conflicts about catalogue maturity, header roles, timing and retention; exact current repository HEAD/image digests and complete operating documents were unavailable. No NHS integration or patient-data test was performed. ORC and Medicus evidence remain adjacent to adapter deployment proof.

The structure gate supports one synthesis page to reduce source traversal. Updated canonical registers, existing queue, glossary, relevant anchors, navigation/design contract and concise LLM notes; no new evidence domain or request pack. The remaining gaps are trigger-bound as recorded in the queue. Validation uses design lint, strict MkDocs, no-API/Graphify regeneration, full repository checks, rendered review, JJ/main clean-push and existing Cloudflare publication workflow.

2026-09-21 - Current Med IS Matrix Highlights

The user identified six England entries as available with the current Med IS: PDS/NHS number, ODS, pathology results over EDIFACT/MESH, e-RS, MESH document/message exchange and HSCN. Added very light accent cell backgrounds, visible accessible check marks and a dated legend to the existing UK Core Services Matrix. The pathology mark applies to EDIFACT over MESH only; the separate FHIR reporting API retains its pilot status. Unmarked cells are not an absence finding.

This is a user-reported operational annotation, not a new public-source validation or supplier-assurance claim. The service-source review date remains 16 September. Updated the design contract and Context Map; no new page, source register entry or evidence-domain structure is needed. Validation follows design lint, strict MkDocs, generated-index/Graphify checks, rendered cell/link review, JJ/main commit and clean push, and Cloudflare publication.

2026-09-21 - UK NHS Section Terminology

Renamed the section and overview to UK NHS Digital Connectivity and Interoperability Evidence at the user's request. Updated current entry-page links, content-map references and operational notes. The overview now introduces the four-nation service matrix, connectivity landscape and standards route before its InterSystems examples, keeping national-service evidence distinct from supplier deployment claims.

The existing page path and legacy heading fragment are preserved. Historical log wording and source titles remain intact; build-time and browser auto-link aliases retain the old title's destination. Existing sidebar wrapping handles the longer label. This editorial pass adds no pages or evidence claims. Validation uses design lint, strict MkDocs, no-API index and Graphify regeneration, rendered navigation/link review, and the JJ/main clean-push and Cloudflare publication workflow.

2026-09-16 - Clarify Matrix Delivery Levels

The user clarified that “Gap” must explain whether a function is delivered regionally, through a trust/laboratory, or through another route. Updated the existing UK Core Services Matrix to distinguish delivery scope from unverified evidence. England requesting is labelled by receiving trust/laboratory or imaging provider; Scottish requesting, report return and professional portals use health-board/provider descriptions. Local product examples remain in the linked detail pages.

Added SRC-423 to SRC-426 and corrected/rechecked SRC-142. The sources also identify NI ECS/KIS through NIECR and hospital-to-GP EDT, replacing two overly broad gaps while retaining current feed and transition limits. Clinician-to-laboratory requests are separated from NPEx laboratory-to-laboratory exchange. Existing anchors, evidence controls and the table contract were aligned without adding pages or changing CSS. Validation follows the generated-index/Graphify checks, strict build, rendered/link review, JJ commit, clean Git push and Cloudflare production publication.

2026-09-16 - Core UK National Services Matrix

The user requested a dedicated, simple function-by-nation matrix and chose national services only, with gaps explicitly marked. Added UK Core Services Matrix, linked immediately after the landscape in navigation and from the landscape, Content Map and detailed comparison. It separates requesting, reports and images, and includes demographics, organisation codes, referrals, prescribing, summaries/viewers, patient portals, messaging, GP transfer and networks. Local hospital products do not fill national gaps.

Checked the landscape, country and diagnostic anchors and used primary-source checks to clarify national organisation reference services, Scottish PACS/SCI Store scope, Welsh test requesting and NI imaging reports. Added SRC-416 to SRC-422, extended the existing DHCW source notes, recorded claim boundaries in the Evidence Matrix and added bounded national-service gaps to the existing queue. Scottish SCI Store combines dated government national-adoption evidence with supplier mechanics; it is not presented as one current national endpoint. NI imaging scope comes from a June 2024 privacy notice checked visually at pp.3, 6 and 11, with deployment evidence kept separate.

The explicit user need meets the repeated-traversal gate for one matrix, not another evidence domain. Existing URLs and evidence trails remain available; DESIGN.md records the navigation/table contract using unchanged theme styling. The earlier general editorial backlog remains To Do. Validation uses design lint, strict MkDocs, no-API/Graphify regeneration, repository checks, rendered page and link review and the JJ/main clean-push workflow.

2026-09-16 - Narrative Review Recorded as Future Work

Reviewed the main entry routes, representative product/component and standards pages, the UK connectivity anchor and locally rendered Home/Executive Summary. The review found four useful narrative arcs and identified audience mixing, repeated assurance text, research chronology and dense table/link presentation as improvement targets. This was a sampled editorial review, not an external-source refresh or an audit of every page.

At the user's request, recorded six scoped To Do passes with completion criteria in the existing queue, with a summary link from Further Research Priorities. Recorded the Git/JJ preservation boundary in Maintenance and linked the backlog from the Context Map. The preceding read-only review recovered an earlier homepage revision and verified clean local Git/JJ state matching remote main at d27244f.

The proposed title, page rewrites, navigation/styling changes, history interface and source-capture mechanism remain future work. The existing pages satisfy the structure stop/go rule; no new wiki page, source record, evidence claim or assurance queue is needed. This recording pass uses the existing no-API index, Graphify, repository verification and JJ/main commit-and-push workflow.

2026-09-15 - Older-Page SCR and NCRS Terminology Audit

Searched all 132 authored Markdown pages; reviewed the 31 containing SCR/NCRS terms, with independent checks of older modules and the source/evidence controls. Corrected one combined SCR/NCRS checklist label and three regional uses of SCR that meant Shared Care Record. Added the missing Summary Care Record glossary definition, clarified its separation from regional records, and linked the four-nation summary-access comparison to NCRS as a viewing application. Vaccination-retirement wording now explicitly identifies the COVID vaccination status retained in SCR.

Rechecked the existing NHS SCR and NCRS sources; SCR has no user interface of its own and is accessed through NCRS or approved local applications. Accurate SCR-specific GP obligations, official source titles and historical research-log entries remain intact. No further conflation was found in the reviewed current prose. No new source ID, wiki page or evidence-queue trail is needed. Updated the Context Map naming rule and regenerated the no-API index and Graphify; validation uses the existing repository checks, rendered-link checks and clean JJ/main publication workflow.

2026-09-15 - NCRS Permissions and UK Portal Features

Completed the selected follow-ups within the existing national-service and country pages. The NCRS section now has a compact activity/role table and two diagrams: source services presented in the application, and the existing local-system-to-NCRS launch versus the prospective reverse shortcut to a Shared Care Record. Rechecked the NHS feature guidance and retained separate pointer/document access, flag existence/details/management, CP-IS notification behaviour, birth-notification role combinations and OVM record/status editing.

The UK landscape now routes to professional and patient portal breakdowns for all four nations. England adds NHS App identity, provider-feature and family/carer access limits. Scotland separates board portals, ECS/KIS, SCI Store/TrakCare, SCI Gateway and MyCare.scot; dated Lanarkshire cohort evidence corrects the earlier overly broad treatment of appointment/letter viewing as entirely future. Wales distinguishes WCP, WGPR and WCCG, with current patient-app feature limits: GP-record results are not the same as timeline results, hospital display varies, and caregiver Authorised access remains in development. Northern Ireland separates encompass, EpicCare Link, My Care and NIECR's transition, including patient proxy permissions and the difference between professional record viewing and supported actions.

Added SRC-404 to SRC-415 and expanded existing source notes where the same evidence now supports a more precise claim. Local permissions and staged features remain bounded in the existing queue. No new page, checklist, navigation hierarchy or evidence-domain layer was needed. The Context Map and operational architecture retain professional applications, patient applications, source records and contextual launch as separate concepts. This pass is a portal expansion, not a new whole-wiki source audit.

Verification covers existing presentation tests, strict MkDocs, no-API index and Graphify regeneration/freshness, source/table/link checks, rendered diagrams and responsive layout. Publication follows the repository's JJ/main clean-push, CI and existing Cloudflare Pages workflow.

2026-09-15 - NCRS Service and Feature Breakdown

The user identified that the combined SCR/NCRS entry understated NCRS. The England service catalogue now has separate NCRS application and SCR source-record rows, plus a dedicated feature section within the existing page. It describes PDS, SCR, NRL documents, the three patient-flag functions, birth notifications, OVM/chargeable status and the dedicated vaccination view, with specific actions and permission boundaries. GP Connect and Shared Care Record shortcuts have a separate pilot/planned table.

Rechecked the official service/roadmap and feature guidance. Added SRC-401 to SRC-403, retaining existing source IDs for the umbrella service. The specific vaccination guidance announces retirement of the dedicated COVID view, with status retained in SCR, but gives no completed withdrawal/date. The NCRS interest form explicitly offers demographic editing; it was read only, not submitted. Permissions to view, edit, notify and open a document are not interchangeable.

The national-records page, UK landscape, glossary, evidence matrix, queue and Context Map now preserve NCRS as the collective professional application and SCR as one source. Existing sections meet the structure stop/go rule; no new page, navigation change or request pack was needed. Verification covers strict MkDocs, generated-index/Graphify freshness, rendered links/table and feature checks, JJ/main commit, clean push, CI and existing Cloudflare publication.

2026-09-15 - UK Healthcare Connectivity Landscape

The user requested a master page for the whole UK landscape, explicitly choosing national infrastructure with InterSystems evidence marked. Graphify and the Context Map were checked first. Existing coverage centred on GP Connect/Spine functional comparisons and the Defence Executive Summary; SWAN, SCI Store, NIDIS phases and diagnostic transitions were missing or too dispersed.

Added three reader-facing modules: UK Healthcare Connectivity Landscape, England Spine and National Services, and Diagnostic Results and Image Exchange. Expanded the three existing country pages with network, identity, clinical exchange, record and diagnostic layers. Home, Knowledge Base, Content Map, Executive Summary and affected standards/supplier anchors now lead into the new routes. The recorded stop/go decision permits these synthesis pages because they reduce repeated traversal; no extra evidence-domain register or request pack was created.

Added 30 primary-source records, SRC-371 to SRC-400, and updated existing Spine, SDS, GP national-service and PDS source notes. The dated source review establishes:

• England's HSCN/internet, identity, directory and messaging distinctions, including CIS2 migration and the difference between PDS approval and current usage.
• Scotland's SWAN/SCI Store/SCI Gateway roles, current NDP component detail and a direct Lothian SCI Store-to-TrakCare viewing workflow. Estate-specific SWAN targets and PACS procurement milestones do not prove completed national cutover.
• Welsh PSBA, WDS/WCCG and diagnostic milestones, with InterSystems LIMS separated from Philips RISP.
• NI's live NIDIS Phase 1, separate GP-registration replacement phase and NHAIS screening continuity. BSO identifies Clinisys CoreLIMS and Sectra NIPACS+; the June imaging closure event announced July operations transfer, rather than retrospectively confirming it.
• England's pathology pilot/API/PDM/MNS route and July 2026 FHIR IG; EDIFACT/MESH remains operational without a verified retirement date. NIR has limited beta use and current SOAP/XCA interfaces; FHIR/MHD and wider rollout remain planned, and no national IEP shutdown was established.

This is a focused connectivity review, not a fresh audit of every wiki source. Canonical source, claim, gap and operational-note layers remain separate. Existing valid anchors and published paths were retained. Peer checks reconciled programme names, pilot wording, dated announcements and supplier boundaries. Rendered review also caught country-name auto-links pointing to supplier pages; full supplier navigation labels now prevent that ambiguity. Publication gates are source/link checks, design lint, strict MkDocs, no-API/Graphify regeneration, repository verification, rendered desktop/mobile checks, JJ/main commit, clean push, CI and deployment to the existing Cloudflare Pages wiki.

2026-09-15 - Product Interface Screenshots

Added IntelliCare to the Knowledge Base's opening product summary, as requested in the browser comment. Added 17 sourced UI images across 19 existing product/component pages, with a screenshot navigation table in Products and Services. Clinical Viewer is reused as the explicitly named access surface on the HealthShare and UCR pages. The SDA/CDA page uses the shared DTL editor and labels its generic example.

Sources include public InterSystems manuals and product material, first-hand developer tutorials, a Gloucestershire Hospitals TrakCare T2022.4 training guide and a 2023 InterSystems care/patient-community presentation. IntelliCare uses a full-frame capture at 9:39.924 in InterSystems France's SantExpo 2025 video: it shows mobile recording controls projected at the event, with limited fine detail and a link to the timed video. Brochure imagery, stock photographs, unrelated products and unverified legacy Lab screens were excluded. No private system or account was accessed.

Added SRC-355 to SRC-370 and a local asset provenance manifest with source URLs, dates, versions, dimensions, extraction details and SHA-256 hashes. Original image downloads and native PDF screenshot content were retained; the IntelliCare browser capture was not retouched. Each page supplies descriptive alt text, a workflow caption and a full-size image link. The Source Register records provenance; the Evidence Matrix limits what the UI examples establish.

Provider Directory has only a small historical 2019 Master Viewer example. A verified public TrakCare Lab Enterprise screenshot was not found; that section states the gap instead of reusing the EHR bed-search screen. These limits remain in the existing Evidence Validation Queue. The IntelliCare/EMC outcome trail remains parked.

Checked the Context Map and product, HealthShare and FHIR anchors before and after work. Existing pages satisfy the structure stop/go rule; no new wiki page or request pack was needed. DESIGN.md and the theme now specify bounded, uncropped product images with keyboard focus and full-size access. Publication checks cover rendered desktop/mobile layout, image links and provenance, design lint, strict MkDocs, no-API index and Graphify regeneration, repository verification, JJ/main commit, clean push and the existing Cloudflare Pages deployment.

2026-09-09 - Broader Content Review and Synthesis

The user redirected the work away from the IntelliCare/EMC trail toward broader content review. That trail remains in the existing page and queue; no pilot request or further AI outcome search was performed.

This pass built on the 8 September review of all 129 Markdown pages. It re-reviewed 21 product/technical pages, 20 UK/nation/deployment modules, standards/glossary anchors and shared overview/control pages. These groups overlap and are not a second full external-source audit. Graphify and the Context Map were checked before work; affected product, standards, UK, country and executive anchors were reconciled afterwards.

Broader Changes

• Corrected product taxonomy and added practical TrakCare functions and laboratory scope to existing pages. Reconciled Health Connect deployment wording across the product, portfolio, family overview and glossary.
• Corrected surviving historical IRIS supplier-row wording, CIS standard/software-version ambiguity and the CORTISONE route-entry discussion using existing NHS evidence.
• Added current Scottish procurement evidence and corrected Welsh laboratory-interface boundaries. Existing board evidence already documented WCP/WRRS connections; national-service ownership and completed migration remain separate.
• Replaced the placeholder comparison page with product-role distinctions and sourced FHIR delivery-model examples. Microsoft service lifecycle wording distinguishes a scheduled future retirement from the current service.
• Added a plain-language standards explanation and foundational glossary terms. Rewrote the Knowledge Base overview to make the portfolio, use, standards and governance understandable before directing readers to detailed evidence.
• Broadened Home entry routes and research priorities. The Executive Summary remains a specific application of the wider knowledge and no longer claims an unevaluated best fit.

Added seven primary-source records, SRC-348 to SRC-354. Sources include product documentation, an NHS contract notice, official HAPI/Microsoft material and published HL7/IHE definitions. Comparator evidence is descriptive; no common benchmark or independent clinical-outcome comparison was found or claimed. The HAPI landing page includes old release-news content, so it was not used to establish a current software version. The FHIR foundations reference is explicitly published R4, not a latest-version assertion.

Structure and Validation

The existing pages satisfy the source-domain stop/go rule. No new page, request pack, domain, dependency or styling change was needed. Canonical Source Register and Evidence Matrix entries remain separate from reader-facing synthesis; historical Research Log entries are preserved. Review QA checked the changed local links and anchors and found no material loss of evidence from its canonical page.

Publication gates are the no-API index, Graphify regeneration, repository verification, rendered-content checks, JJ commit/main bookmark, clean Git push and deployment to the existing Cloudflare Pages wiki. Remaining supplier-response and deployment-assurance gaps stay in the queue rather than defining the next broad pass.

2026-09-09 - IntelliCare Workflow and EMC Outcome Review

The user requested both annotated follow-ups: map IntelliCare AI to TrakCare workflows and test EMC's implementation claims against independent outcome evidence. Checked Graphify, the Context Map and existing product/source anchors. The source-domain stop/go rule supports two tables in the existing IntelliCare page; no new wiki page, checklist or request pack was created.

Added SRC-341 to SRC-347. Product descriptions support a functional workflow correspondence and human review, not an internal implementation map. Dated brochure regulatory footers were kept separate from later EU evidence. The EMC pass strengthened implementation reporting, corrected benefit attribution and retained the independent-evaluation gap. Earlier dated log entries remain historical.

Research covered English/Indonesian combinations of IntelliCare, InterSystems and EMC with outcome, evaluation, study, trial, penelitian and jurnal; targeted PubMed/PMC, Indonesian Ministry of Health and indexed research; customer and parent-group reports; original interviews, vendor publicity and HIMSS reporting. PubMed ESearch returned zero records for IntelliCare AND InterSystems, IntelliCare AND "EMC Healthcare", and TrakCare AND "EMC". Unrelated mental-health applications and the Philippine insurer were excluded. No qualifying independent EMC IntelliCare evaluation was found within this scope; absence from these searches is not proof that none exists.

The outcome-provenance table keeps earlier TrakCare transformation, narrow IntelliCare usability, reported adoption, study activity and digital maturity distinct. Customer financial, satisfaction or safety trends were not attributed to IntelliCare without an evaluation design. Press republications and partner awards were not counted as independent confirmation. Pilot methods/results remain a concrete target in the existing queue; no external message was sent.

InterSystems brochure text was available through web extraction, while direct downloads failed. Customer reports and the trade-interview reprint were extracted and relevant evidence pages visually checked. Selected global product pages exposed navigation only; indexed primary text and readable UK pages supported the functional mapping. No new inference depended on an unreadable diagram.

Updated the IntelliCare and TrakCare pages, portfolio routing, source/evidence registers, queue and operational context. Standard publication gates: no-API index and Graphify regeneration, repository checks, rendered-table/link verification, JJ commit/bookmark, clean Git push and the existing Cloudflare Pages deployment.

2026-09-08 - IntelliCare Deployment and Middle East Follow-Up

The user's IntelliCare/Middle East question triggered a focused primary-source pass after the full-wiki review. The earlier EMC-only vendor signal was incomplete: customer implementation evidence and further adoption announcements were located. Added SRC-337 to SRC-340 and updated the existing IntelliCare page, source/evidence registers, queue, portfolio routing and Context Map.

• Medcare UAE: adoption agreement and customer corroboration; completed rollout unconfirmed.
• King's Jeddah: customer and vendor announcements on 7/8 September, with future-tense go-live qualification.
• EMC: March 2026 customer presentation confirms implementation during 2025, beyond the prior pilot/transition evidence.
• RedSalud: June vendor announcement supports adoption intent, not completed deployment.

Public social-post timestamps were verified from JSON-LD. EMC's presentation was downloaded and extracted, with its implementation slide visually checked. Medcare's linked magazine could not be opened; only the customer post was used. Current product descriptions and the May MDR statement were checked for capability/regulatory context. No independent clinical-outcome claim, all-site AI activation, Middle East completed go-live or named UK deployment was inferred.

The source-domain stop/go rule supports one deployment-status table inside the existing IntelliCare page; no new page or request pack is justified. Outstanding completion, feature and certificate gaps remain in the existing queue. The standard pass gates are index/Graphify regeneration, repository verification, JJ commit/bookmark, clean Git push and publication to the existing wiki.

2026-09-08 - Full Wiki Review and Public-Source Refresh

Scope and Method

Reviewed all 129 Markdown pages under docs/, including unchanged pages, canonical registers, synthesis, glossary, operational notes and hidden revision scaffolds. The historical Research Log was read in full: 2,040 lines and 96 dated entries before this addition. Existing dated findings remain historical records rather than being rewritten to imply later information was already known.

Review area	Pages covered	Review boundary
Product/technical modules and HealthShare evidence domain	22	Full text and relevant source/evidence rows; public release, documentation and advisory checks.
England primary care, standards and legal modules/domains	52	Full text and relevant source/evidence rows; volatile service, supplier, standards and regulator checks.
Deployment, UK nations, Defence and international modules	23	Full text and relevant source/evidence rows; government, customer, programme and procurement checks.
Shared controls, synthesis, operational pages and remaining module routers	32	Full content, cross-page reconciliation, source-ID/local-link checks and deployment-workflow comparison.

“Open source information” in this pass means publicly available evidence. This was a full local-content review with targeted current primary-source verification, not a claim that every historical external URL was re-fetched or every public record exhaustively searched. Graphify and the Context Map were checked before domain work; affected product, England, legal, country and executive anchors were reconciled afterwards.

Material Findings

• The September GP Connect service policy changes supplier-entry feasibility. The current supplier table retains HealthShare's structured-consumer row but no longer shows the IRIS middleware row recorded in June. Historical supplier evidence, current table contents and actual assurance/withdrawal status remain separate.
• Current NHS/standards evidence adds the medical-examiner use case, reported April–June NCRS pilot activity and CIS v2.01 release/safety context; these do not establish local InterSystems approval or adoption (SRC-308, SRC-309 and refreshed existing NHS sources).
• IRIS for Health / Health Connect 2026.2 release and FHIR documentation add version-specific mechanics. July support notices supply concrete permission, audit, access, SSO, consent, upgrade, patient-context, NRL pointer and data-store checks; they do not prove a named customer is affected or corrected (SRC-293 to SRC-298, SRC-300, SRC-301).
• IntelliCare's TrakCare/IRIS foundation, vendor-hosted EMC transition signal and vendor EU MDR statement refine previously generic positioning. Certificate scope, jurisdiction and customer deployment assurance remain separate.
• Welsh EPS explicitly reuses NHS Spine/PDS. Scotland's MyCare.scot has initial national availability; Golden Jubilee reports a TrakCare upgrade. Welsh LIMS has phased delivery and revised forecasts, and Cardiff and Vale supplies a named CDR data-flow example (SRC-127, SRC-328 to SRC-330, SRC-332, SRC-334, SRC-335).
• The August Acacia inquiry constrains claims of completed remote/primary-care deployment. Its findings and recommendations are separate from later government action or delivered functionality.
• The January TPP EHR award was already registered but not consistently reflected in CORTISONE synthesis. The architecture now explicitly requires reconciliation of TPP, InterSystems and DMICP responsibilities rather than treating the proposed InterSystems diagram as the full contracted programme.
• Medicus's integration catalogue adds first-party supplier corroboration of regional Shared Care Record connectivity. It does not identify HealthShare or the transport or supply local NHS/customer assurance. London North West recruitment evidence adds historical trust technical context without closing ICS cloud-procurement gaps.
• ICO guidance status and special-category automated-decision boundaries were refreshed. Northern Ireland's published Being Open framework replaces consultation-only treatment; its FAQ distinguishes policy implementation from a new statutory duty. The DUAA England health-standard provision is now consistently separated from UK-wide data-protection changes (SRC-310 and refreshed existing ICO sources).
• Deployment documentation incorrectly described the current GitHub workflow as a GitHub Pages publisher. It now matches the repository: GitHub verifies; the existing Cloudflare Pages project publishes.

Added / Changed

Added public-source records SRC-293 to SRC-301, SRC-308 to SRC-310 and SRC-328 to SRC-336, retaining all earlier IDs and their historical access context. Updated corresponding Evidence Matrix claims, existing queue entries, the Executive Summary, country/product/service anchors, glossary and LLM operational context. Research priorities now identify decision-relevant evidence gaps rather than repeat general maintenance or completed guidance.

The structure stop/go check found the existing modules and three evidence domains sufficient. No new wiki page, domain, checklist or request pack was created. The prior source-number gap at 086 remains unallocated; stable IDs were not renumbered. Historical log ordering was retained.

Unchanged Boundaries and Access Limits

No current public evidence in the targeted checks closed full InterSystems DSIC foundation coverage, DMICP/CORTISONE live adapter architecture, current ITK certificate scope, customer-specific cloud/patch/safety assurance, MERIT post-contract continuity, eConsult formal current architecture, North West London ICS cloud procurement, or West Midlands Medicus transport/local safety. International gaps remain for formal Gateway/Nexus status, current named El Bosque APS scope, official SSMS award detail and a DHAMAN primary source naming TrakCare. These are scoped evidence gaps, not proof of absence or non-compliance.

Several InterSystems and DHCW article bodies were available through the publishers' indexed text while direct page rendering exposed navigation only. HealthShare detailed manuals/WRC correction artefacts remain gated. The former Update Record service page returns 404; current policy and API material are recorded separately. The Northern Ireland framework publication and FAQ were accessible while the linked framework PDF was unavailable. Acacia inquiry text was readable, but its screenshot/download attempts failed; no finding depends on interpreting a visual chart. Welsh LIMS source pages were visually checked. No supplier message, FOI or other external request was sent.

Validation and Publication Gates

The pass uses npm run kb:update to regenerate the no-API index and rebuild Graphify after removing previous publication artifacts, followed by npm run verify for design lint, presentation tests, index freshness, strict MkDocs and Graphify freshness. Source-table continuity, source IDs, local links and rendered changed-page content are checked separately. Deployment follows a JJ commit, main bookmark update and verified Git push, using the existing Cloudflare project and the previously documented Wrangler 4.105.0 runtime. No dependencies, runtime configuration or styling were changed.

2026-08-11 - DSIC Catalogue and DMICP GP-record Route Cross-Check

Searched

• Public NHS England DSIC Capabilities & Standards overview and introduction pages.
• Current DSIC GP Connect Access Record Structured, Send Document, and Update Record standard pages.
• Local Graphify relationships for DSIC, NHS Standards Directory, GP Connect / MESH / ITK3, Programme CORTISONE, Evidence Matrix, Evidence Validation Queue, Source Register, and Context Map.

Found

• The public DSIC model separates business Capabilities from Standards that define technical or operating conditions required for Catalogue Compliance.
• S99 Access Record Structured v1.0.4 is the effective structured-read standard, with provider/consumer MUST roles and PDS or Spine Mini Services dependency.
• S101 Send Document v1.0.3 is the effective document route, with sender/receiver MUST roles and ITK3/MESH dependencies plus Generic FHIR Receiver for receiver solutions.
• S102 Update Record v1.0.3 is the effective structured-write standard, with sender/receiver MUST roles and ITK3/MESH/PDS or Spine Mini Services dependencies. It is listed across four contracting vehicles, while current service-facing public assurance remains the named community-pharmacy workflows.

Added / Changed

• Added source IDs SRC-291 and SRC-292.
• Updated the DSIC overview, standards and national-services map, capability crosswalk, NHS Standards Directory parent and GP Connect/MESH/ITK3 child pages.
• Updated GP Connect Update Record synthesis and due diligence to separate catalogue applicability from assured clinical use.
• Added the S99/S101/S102 route decision and DMICP proof boundary to Programme CORTISONE and the Executive Summary.
• Updated the Evidence Matrix, Evidence Validation Queue, Source and Evidence Domain Map, further research priorities, and LLM Context Map.
• Converted the legacy GitHub Pages deployment workflow into the repository's wiki verification workflow because production is hosted on the existing Cloudflare Pages project and GitHub Pages is not enabled. The workflow now installs the pinned Graphify CLI from requirements-tools.txt, keys the pip cache from both Python manifests, and runs the full npm run verify gate without attempting to create a second public wiki.
• Published the verified wiki build to the production Cloudflare Pages project and checked the stable public route, DMICP synthesis, and source-register entries.

Boundary

• Current DSIC standard status does not prove that DMICP/CORTISONE is an approved provider, consumer, sender, or receiver, and it does not prove InterSystems implementation. A route still needs an approved use case, named supplier role, onboarding/conformance, dependencies, DSA/DPIA, DCB0129/DCB0160, payload tests, operating RACI, and customer deployment evidence.

2026-07-04 - DMICP Definition and CORTISONE Replacement Context

Searched

• GOV.UK / MOD DMICP statistics background material.
• UK Parliament written answers for DMICP record-system definition, rollout, deployed-use, replacement, medical deployability sourcing, and CORTISONE rollout status.
• Find a Tender procurement notice for a Primary Dental Care system to replace DMICP in the dentistry slice.
• CGI vendor case-study material for historical DMICP implementation context.
• Local Graphify relationships for Programme CORTISONE, DMICP, NHS Standards Directory cross-checks, Evidence Matrix, Evidence Validation Queue, Source Register, and Context Map.

Found

• DMICP is best defined as the MOD / Armed Forces electronic patient record system and Defence primary-healthcare source baseline, with an integrated primary Health Record plus pseudo-anonymised / coded data warehouse.
• DMICP first went live at Chicksands on 16 February 2007 and had fixed and deployed-use context by the 2018 MOD answer, but that answer is point-in-time operational context rather than current live-service sizing.
• CORTISONE is currently evidenced as stabilising current Medical Information Services / DMICP while introducing new capabilities; the 2025 MOD answer says procurement for the new electronic healthcare information management system was ongoing with rollout planned over the next two years.
• A 2025 Find a Tender notice supports a Primary Dental Care system replacement signal for the DMS dentistry slice only.
• CGI material adds historical supplier/product context around EMIS PCS, JPA linkage, deployed synchronisation, and data-warehouse use, but remains vendor evidence.

Added / Changed

• Added source IDs SRC-286 through SRC-290.
• Added a What DMICP Is section to Programme CORTISONE / UK Defence Healthcare.
• Updated the Executive Summary, NHS Standards Directory map, Evidence Matrix, Evidence Validation Queue, Source and Evidence Domain Map, Glossary, and Context Map.

Boundary

• The new sources strengthen the DMICP definition and replacement context. They still do not prove the current DMICP interface catalogue, source data model, Health Connect mediation route, HealthShare configuration, CORTISONE migration/decommissioning plan, clinical-safety/IG artefacts, or NHS England / four-nation adapter onboarding.

2026-07-03 - Terminology Code Management and Read-to-SNOMED Mapping

Searched

• NHS England Digital Read Codes, SNOMED CT, clinical-coding developer guidance, Standards Directory, NHS Terminology Server, Terminology Server FHIR API, access, syndication, and system-to-system guidance.
• NHS TRUD data-migration, Data Migration Workbench, PBCL Read Code to SNOMED translation, and SNOMED CT UK Clinical Edition release listings.
• NHSBSA dm+d and NHS England UK Medicines Terminology Futures pages.
• HL7 FHIR R4 terminology module / binding examples and SNOMED International mapping, extension, and national terminology-server guidance.
• Local and federated terminology-service examples including NHS England local Ontoserver route, OneLondon, NHS Scotland terminology tooling, CSIRO / Dedalus partnership material, Australia NCTS, OpenSAFELY, and OpenCodelists.

Found

• Read Version 2 and CTV3 are retired or deprecated for active NHS England content management; new clinical content routes through SNOMED CT and medicines content through dm+d where medicines information is transferred electronically.
• TRUD provides official Read / CTV3 to SNOMED CT migration artefacts, but the generic Read Version 2 to SNOMED CT mapping tables are static after the final April 2020 release.
• SNOMED CT UK Edition and dm+d are versioned national terminology assets, while the NHS England Terminology Server exposes FHIR CodeSystem, ValueSet, and ConceptMap resources plus terminology operations and syndication.
• Local or extension codes should be governed through a terminology-service model: local CodeSystems, ValueSets, ConceptMaps, versioned source packages, mapping purpose/equivalence, clinical review, inactive-code handling, provenance, and safety governance.

Added / Changed

• Added Terminology Code Management and Read-to-SNOMED Mapping.
• Added source IDs SRC-278 through SRC-285.
• Updated Standards and Interoperability, NHS Standards Directory map, DSIC Standards and National Services, FHIR Services, UK Healthcare Recording Legal and Professional Position, DSIC HealthShare Compliance Map, Healthcare Record Source Layers, glossary, Evidence Matrix, Evidence Validation Queue, Source and Evidence Domain Map, Context Map, MkDocs navigation, and module index.

Boundary

• Mapping artefacts, terminology-server availability, and implementation examples are standards/model evidence. They do not prove any InterSystems product or deployment has loaded specific terminology releases, implemented NHS Terminology Server, preserved historical Read-coded provenance, validated local maps, or completed clinical-safety / information-governance assurance.

2026-06-28 - Executive Summary GP2GP Row and Queue To Dos

Changed

• Added a compact GP2GP record-transfer / practice-move row to the Executive Summary interface-strategy table, linked to the GP2GP Record Transfer page.
• Recorded the remaining GP2GP follow-ups as Evidence Validation Queue To Dos instead of creating a new checklist or evidence-domain layer: reopen the InterSystems GP2GP proof gap only when a supplier or customer source appears; validate Scotland and Northern Ireland GP2GP supplier / implementation detail against NSS, BSO, HSCNI, GP IT Modernisation, and procurement sources before linking either route to InterSystems.
• Updated the Context Map to record that the Executive Summary carries the compact GP2GP row while the unresolved proof work remains parked in the queue.

Boundary

• This was a synthesis and backlog-routing update. It did not add new source evidence or change the GP2GP conclusion: current public evidence still does not prove InterSystems GP2GP implementation, adaptor, middleware, or GP foundation-system capability.

2026-06-28 - Provider Directory Evidence Request and UCP Current Boundary

Searched

• Graphify and wiki relationships for HealthShare Provider Directory, Coordinate My Care, Universal Care Plan, DSIC HealthShare Compliance Map, Evidence Matrix, Evidence Validation Queue, Source Register, Source and Evidence Domain Map, UK NHS Evidence, and Context Map.
• Current UCP / OneLondon pages and guidance for UCP launch, go-live/support, care-home access, release notes, London Care Record, web portal, National Record Locator, Better / Valida routes, and supplier/integration signals.
• Targeted public searches for current UCP architecture with InterSystems, HealthShare Provider Directory, Better, Valida, London Care Record, and ReStart/Qvera.

Found

• The historical Coordinate My Care signal remains useful only as legacy component evidence: the J2 source named Provider Directory, but current UCP public evidence does not carry that forward as a live claim.
• Current public UCP / ICB / supplier evidence points to UCP web portal, London Care Record, local EPR routes, Better / Valida guidance, National Record Locator integration, and Better / ReStart/Qvera integration signals.
• No current public UCP source found in this pass names InterSystems or HealthShare Provider Directory as the live UCP platform, directory, ODS/SDS owner, or current customer architecture component.
• Because no current named Provider Directory deployment is evidenced, the DSIC HealthShare Compliance Map should stay bounded rather than gaining a named UCP / Provider Directory deployment pack.

Added / Changed

• Added SRC-266 for current UCP platform/access and InterSystems-boundary evidence.
• Added a Provider Directory evidence-request block covering product/version, ODS/SDS mapping, data stewardship, governance/safety, and deployment proof.
• Updated HealthShare Provider Directory, UK NHS Evidence, Evidence Matrix, Evidence Validation Queue, DSIC HealthShare Compliance Map, HealthShare Components Evidence Domain, Source and Evidence Domain Map, and Context Map.

Boundary

• Use the Provider Directory evidence-request block only when a current implementation claim is being made. Keep UCP as a current successor-service boundary unless a customer/supplier architecture explicitly names InterSystems or Provider Directory.

2026-06-28 - GP2GP Record Transfer and InterSystems Boundary

Searched

• Graphify and wiki relationships for GP2GP, DSIC standards, NHS Standards Directory, GP Connect, devolved connectivity pages, InterSystems-by-nation pages, Evidence Matrix, Evidence Validation Queue, Source Register, Source and Evidence Domain Map, and Context Map.
• NHS England GP2GP service, API catalogue, FHIR adaptor, and Standards Directory material.
• DHCW primary-care GP2GP evidence.
• NHS Scotland / NHS inform / NSS / SCIMP GP record-transfer and GP2GP material.
• BSO / HSCNI GP IT Modernisation and GP2GP material.
• Targeted public searches for InterSystems GP2GP, HealthShare GP2GP, Health Connect GP2GP, and IRIS for Health GP2GP.

Found

• GP2GP is a GP-practice record-transfer route when a patient changes GP practice. It is not GP Connect Access Record, Send Document, Update Record, or patient-facing API evidence.
• England has official NHS England service/API/Standards Directory evidence for GP2GP, including the HL7 V3 / Spine / adaptor context.
• Wales has DHCW primary-care evidence listing GP2GP as a Welsh primary-care service.
• Scotland has NHS Scotland / NSS evidence for electronic GP health-record transfer within Scotland and printed-record handling for moves between Scotland and other UK administrations.
• Northern Ireland GP IT Modernisation material identifies GP2GP as an electronic transfer route for patient notes / records between practices or clinical systems.
• Targeted public search found no public InterSystems GP2GP implementation, adaptor, sending/requesting/receiving GP clinical-system role, or complete DSIC GP foundation-provider proof.

Added / Changed

• Added GP2GP Record Transfer.
• Added SRC-263, SRC-264, and SRC-265 to Source Register.
• Updated NHS England Digital Primary Care, DSIC Standards and National Services, NHS Standards Directory and DHSC Standards Direction, NHS Connectivity and GP Connect, DSIC HealthShare Compliance Map, GP Connect and Spine Equivalents by Nation, Scotland / Wales / Northern Ireland connectivity pages, and InterSystems-by-nation pages.
• Updated Evidence Matrix, Evidence Validation Queue, NHS England Digital Primary Care Evidence Domain, Standards and Interoperability Evidence Domain, Source and Evidence Domain Map, Context Map, MkDocs navigation, and module index.

Boundary

• GP2GP would add foundation GP record-transfer capability and stronger migration / practice-move continuity if implemented in a named architecture. It would not add shared-care record access, GP Connect, a patient portal, or proof that HealthShare is a full GP foundation clinical system.
• Health Connect / IRIS may be plausible middleware only with product/version, supplier-role, onboarding, conformance, safety, governance, and customer-deployment evidence.

2026-06-28 - HealthShare Provider Directory Evidence Update

Searched

• Graphify relationships for HealthShare Provider Directory, HealthShare Components Evidence Domain, DSIC HealthShare Compliance Map, Evidence Matrix, Evidence Validation Queue, Source Register, Source and Evidence Domain Map, and Context Map.
• Current InterSystems Provider Directory product page, fact sheet, and product advisories.
• Targeted public search for HealthShare Provider Directory with ODS, SDS, NHS, Coordinate My Care, Royal Marsden, and procurement terms.
• Coordinate My Care / Universal Care Plan transition sources to separate historical deployment signal from current live assurance.

Found

• InterSystems' public Provider Directory fact sheet gives stronger feature evidence than the product page alone: data stewardship, source trust / survivorship rules, change-source tracking, FHIR Plan Net and REST APIs, on-premises deployment, and managed-service deployment.
• A 26 February 2026 InterSystems advisory provides a concrete product/version boundary for Provider Directory versions up to and including 2025.2 and fix HSPD-11325 in 2026.1 and future releases.
• J2 Interactive reports a historical Coordinate My Care implementation using Provider Directory for a searchable clinician registry, with NHS Smartcard access and PDS via Spine Mini Services. UCP / OneLondon sources show CMC later ceased / rebranded around 31 March or 1 April 2022 and was replaced by Universal Care Plan, so this is a legacy signal rather than current Provider Directory assurance.
• No public source found in this pass proves current Provider Directory ODS/SDS mapping, directory stewardship, audit, safety ownership, DSA/DPIA, or live customer deployment assurance.

Added / Changed

• Added SRC-261 for Provider Directory fact sheet and 2026 product advisory evidence.
• Added SRC-262 for historical Coordinate My Care Provider Directory implementation signal and UCP transition / legacy boundary evidence.
• Updated HealthShare Provider Directory, HealthShare, DSIC HealthShare Compliance Map, Standards Product Map, Products and Services, HealthShare Components Evidence Domain, Evidence Matrix, Evidence Validation Queue, Source and Evidence Domain Map, and Context Map.

Open Questions

• Which current customer or supplier artefact proves Provider Directory product/version, licensed scope, ODS/SDS mapping, data-source authority, stewardship rules, synchronisation, audit, DSA/DPIA, and DCB0129/DCB0160 ownership?
• Is any current UCP / London architecture still using InterSystems Provider Directory, or should Coordinate My Care remain only a historical implementation signal?

2026-06-25 - OKF Compatibility Boundary

Changed

• Added an Open Knowledge Format (OKF) compatibility boundary to Maintenance, including the default sidecar-export approach, the in-place conversion risks, and local page-role-to-OKF type guidance.
• Updated Architecture, App Flow, Source and Evidence Domain Map, Context Map, Starter Instruction, and the LLM Wiki index so future agents treat OKF as an optional portability layer over canonical docs/ content.

Boundary

• OKF can add typed metadata, portable concept IDs, traversal hints, validation checks, and a sibling-project export surface. It does not add evidence, improve source reliability, replace Graphify, replace sources.md or evidence-matrix.md, or change the source/evidence model without a separate stop/go decision.

2026-06-25 - DSIC and Executive Source-Layer Link Audit

Changed

• Added Clinical Safety DCB0129 and DCB0160 as the canonical source-layer page for clinical-safety standard labels.
• Extended Data Protection and Health-Record Rights with a DSA/DPIA source-layer section.
• Updated Healthcare Record Source Layers so DSA/DPIA and DCB0129/DCB0160 now route to maintained canonical pages.
• Linked repeated decision-facing source-layer labels in DSIC HealthShare Compliance Map and Executive Summary, including DSA/DPIA, DCB0129/DCB0160, Caldicott/confidentiality, records management, information standards, and clinical safety where they appear as proof requirements.
• Updated Evidence Matrix, Evidence Validation Queue, Standards and Interoperability Evidence Domain, Source and Evidence Domain Map, Context Map, Maintenance, Glossary, MkDocs navigation, and module indexes.

Boundary

• The audit keeps Evidence Matrix and Evidence Validation Queue source-ID-first. Reader-facing source-layer links belong in synthesis/proof tables and route-setting claim rows, not in every dense register occurrence.

2026-06-25 - Healthcare Record Source-Layer Pages and Links

Changed

• Added Healthcare Record Source Layers as the canonical routing map for repeated source-layer acronyms and shorthand labels in healthcare-recording synthesis tables.
• Added source-layer pages for Data Protection and Health-Record Rights, GMC Record Keeping and Professional Duties, NMC Record Keeping and Professional Duties, HCPC Record Keeping and Professional Duties, GPhC Record Keeping and Pharmacy Duties, CQC Provider Governance, Candour Source Layer, NICE Shared Decision Making and Medicines Safety, and Records Management and Amendment Practice.
• Linked the What Must Be Recorded table's source-layer labels to canonical pages or sections.
• Updated Standards and Interoperability Evidence Domain, Source and Evidence Domain Map, Evidence Matrix, Glossary, Context Map, Maintenance, MkDocs navigation, and the module index so the source-layer linking convention is project-wide.

Boundary

• Source-layer pages explain reusable evidence layers and route readers to source families. They do not replace docs/sources.md, source IDs, implementation evidence, legal advice, or supplier/customer artefacts.

2026-06-25 - Public Records and Health-Record Access Routes

Searched

• Official primary legislation and public-records / archival sources for the Public Records Act 1958, Welsh public-records context, Public Records (Scotland) Act 2011, Public Records Act (Northern Ireland) 1923, The National Archives, National Records of Scotland, and PRONI.
• Official legislation and regulator/code sources for Access to Health Records Act 1990, Access to Health Records (Northern Ireland) Order 1993, Freedom of Information Act 2000 section 40 and section 46, the FOIA section 46 records-management code, ICO FOI/EIR guidance, and Access to Medical Reports Act 1988.

Found

• Public-records law is a preservation, management, transfer, archival, and public-accountability layer; it does not define clinical content or prove disclosure, product, DSIC, or deployment compliance.
• Living-patient access remains a UK GDPR / Data Protection Act 2018 subject-access route, while deceased-patient access follows Access to Health Records Act 1990 in Great Britain or the Northern Ireland Order in Northern Ireland.
• FOI/EIR and medical-report access are adjacent public-information / report-specific routes, not substitutes for confidentiality, subject access, deceased-record access, or clinical-record workflow evidence.

Changed

• Added a public-records and health-record access route section to UK Healthcare Recording Legal and Professional Position.
• Added SRC-259 and SRC-260 to Source Register for public-records frameworks and related access-route boundaries.
• Updated Evidence Matrix, Glossary, and Context Map so public-records, AHRA, NI deceased-record access, FOIA section 46, and AMRA are handled as distinct evidence layers.

2026-06-25 - What Must Be Recorded Legal Source Column

Changed

• Added a legal/statutory source-layer column to the What Must Be Recorded table in UK Healthcare Recording Legal and Professional Position.
• Kept the existing professional/source layer separate from legal sources so record content, professional expectations, and legal/statutory duties can be read together without duplicating the Source Register.

2026-06-25 - Legal Alignment Matrix and Cross-Nation Note

Changed

• Added a dedicated Evidence Matrix claim row for the healthcare-recording legal alignment model as its own synthesis.
• Trimmed duplicated legal wording in DSIC HealthShare Compliance Map so the page points to the general legal model and keeps only the DSIC / HealthShare translation.
• Added a cross-nation legal-record alignment note to GP Connect and Spine Equivalents by Nation, keeping legal-record structure UK-wide while records-management, candour, national-service, and deployment proof remain nation-specific.
• Updated Context Map so future passes treat the cross-nation legal-record note as part of the devolved connectivity boundary.

2026-06-25 - Legal Alignment Application Heading Correction

Changed

• Renamed the implementation-facing section on UK Healthcare Recording Legal and Professional Position from a Health Connect / HealthShare / DMICP / DSIC-specific heading to a general digital-health workflow application heading.
• Reworded the table introduction and column labels so DSIC is treated as one application route for the legal alignment model, not the frame for the whole legal page.

2026-06-25 - Healthcare Records Legal Alignment Section

Changed

• Added a dedicated legal alignment section to UK Healthcare Recording Legal and Professional Position, focused on healthcare-record creation, maintenance, sharing, correction, retention, provenance, audit, and disposal in general.
• Added a separate Healthcare Records Legal Alignment section to DSIC HealthShare Compliance Map and removed the legal chain from the England implementation artefact table so legal/professional alignment is not treated as just another technical artefact.
• Updated Executive Summary and Context Map so the legal alignment model is recorded as a controlling anchor for healthcare-record creation and maintenance evidence.

2026-06-25 - Statutory Chain Proof Alignment

Changed

• Added a compact UK healthcare-recording statutory-chain proof row to DSIC HealthShare Compliance Map, covering NHS Act 2006 section 251, Health and Social Care Act 2012 section 250, Health and Care Act 2022, DUAA 2025, and Health and Social Care (National Data Guardian) Act 2018 as separate assurance roles.
• Tightened Executive Summary so the short answer points decision readers to UK Healthcare Recording Legal and Professional Position.
• Updated Evidence Matrix so the healthcare-recording assurance row explicitly names Health and Social Care (National Data Guardian) Act 2018 and its governance-context boundary.

2026-06-25 - NHS Statutory Label Clarification

Changed

• Corrected UK Healthcare Recording Legal and Professional Position to remove the residual incorrect shorthand NHS Act label.
• Clarified the intended statutory chain as National Health Service Act 2006 section 251, Health and Social Care Act 2012 section 250, Health and Care Act 2022, and Data (Use and Access) Act 2025.
• Removed the open-validation row for the incorrect shorthand NHS Act label because the user clarified the intended Acts.

2026-06-25 - UK Healthcare Recording Legal and Professional Position

Searched

• Official UK, NHS, regulator, professional-body, and devolved sources for the legal and professional position on recording healthcare information and healthcare delivery.
• UK GDPR / Data Protection Act 2018, PECR, NHS Act 2006 section 251, Health and Social Care Act 2012 section 250, Health and Social Care (National Data Guardian) Act 2018, Health and Care Act 2022, and Data (Use and Access) Act 2025 evidence.
• GMC, NMC, HCPC, GPhC, CQC, NHS England, ICO, HRA, PRSB, NICE, Scottish Government, Welsh Government, and Department of Health Northern Ireland sources.

Found

• The legal/professional position is layered and should not be collapsed into a generic "NHS Act" or "data protection" label.
• UK GDPR and Data Protection Act 2018 are the baseline for personal and special-category health data; PECR is a separate electronic-communications and storage/access layer for portals, apps, cookies, reminders, surveys, and direct-marketing boundaries.
• NHS Act 2006 section 251 is the relevant confidentiality gateway where confidential patient information is used without consent for specified medical purposes; it does not remove UK GDPR/DPA duties.
• Health and Social Care Act 2012 section 250 is the England information-standard base; Health and Care Act 2022 strengthens mandatory compliance and monitoring/enforcement; DUAA 2025 extends information-standard analysis to IT, IT services, and information-processing service providers in England health/adult social care.
• Professional duties converge on clear, accurate, timely, attributable, secure records of clinical findings, treatment, information shared, consent/decision making, risk, actions, review, incidents, and candour.

Added / Changed

• Added UK Healthcare Recording Legal and Professional Position.
• Added source rows SRC-241 to SRC-258 in Sources.
• Added claim rows to Evidence Matrix for the UK healthcare-recording assurance model and England information-standard statutory chain.
• Updated Standards and Interoperability, Standards and Interoperability Evidence Domain, Source and Evidence Domain Map, Evidence Validation Queue, Context Map, Glossary, and MkDocs navigation.

2026-06-23 - Architecture Boundary Queue and England Artefact Map

Changed

• Consolidated the DMICP / CORTISONE interface proof gap into a single Executive Summary architecture-boundary row in Evidence Validation Queue so missing implementation artefacts are tracked once.
• Added an England implementation artefact map to DSIC HealthShare Compliance Map covering GP Connect, MESH, ITK3, PDS, ODS/SDS, DSA/DPIA, and DCB0129/DCB0160.
• Updated Context Map so future passes treat the architecture boundary as a consolidated proof gap rather than reopening separate Defence, DUAA, identity-directory, or devolved trails by default.

2026-06-22 - Executive Summary Proof Links and Matrix Row

Changed

• Added direct proof-table links to Executive Summary for the England adapter landing, DMICP interface-proof table, and Health Connect / HealthShare four-nation adapter logic.
• Ran a terminology consistency pass over Executive Summary, NHS England Digital Primary Care, and GP Connect and Spine Equivalents by Nation, keeping DSIC and DUAA labels England-bounded.
• Added a consolidated Executive Summary architecture-boundary row to Evidence Matrix.
• Updated Context Map to record the proof-link and matrix-row model.

2026-06-22 - England and Four-Nation Adapter Alignment

Changed

• Aligned NHS England Digital Primary Care with the DUAA decision-boundary wording by adding a standards-governance test to the working model and England adapter landing.
• Added a compact DMICP interface-proof table to Programme CORTISONE / UK Defence Healthcare without opening a wider Defence research trail.
• Added Health Connect / HealthShare adapter logic to GP Connect and Spine Equivalents by Nation so DSIC and DUAA labels remain confined to England unless direct nation-specific evidence changes that boundary.
• Updated Context Map to record the aligned anchor model.

2026-06-22 - DUAA Executive Decision Boundary

Changed

• Added a DUAA decision-boundary box to Executive Summary so decision readers see DUAA as an England statutory data and information-standard layer, not a DSIC or InterSystems compliance label.
• Tightened DSIC HealthShare Compliance Map with a DUAA England standards-governance boundary covering DMICP / CORTISONE, Health Connect, HealthShare, and DSIC claim handling.
• Added a DMICP / Health Connect / HealthShare cross-check to NHS Standards Directory and DHSC Standards Direction so DUAA supplier-role analysis is tied to named standards surfaces.
• Updated Context Map to keep the Executive Summary and DSIC anchor model aligned with this DUAA boundary.

2026-06-22 - Executive Summary Mermaid Node Links

Changed

• Added Mermaid click links to the Executive Summary Reference Architecture nodes so DMICP, Health Connect, IRIS / SDA / FHIR, England, Scotland, Wales, Northern Ireland, regional/hospital, HealthShare, UCR, EMPI, Clinical Viewer, and Provider Directory all route to relevant wiki pages.
• Added an England adapter landing section to NHS England Digital Primary Care.
• Added an IRIS / SDA / FHIR landing section to SDA and CDA Transformation.
• Switched Mermaid initialisation to securityLevel: "loose" because Mermaid click links are disabled under strict; documented the controlled local-content convention in LLM Wiki Maintenance.

2026-06-22 - Mermaid Accent Colour Restoration

Changed

• Restored Executive Summary Mermaid diagram accent colouring by wiring Mermaid theme variables to the wiki design tokens in docs/assets/mermaid-init.js.
• Updated DESIGN.md so Mermaid diagrams are explicitly covered by the project accent-colour contract.

2026-06-22 - Executive Summary HealthShare Diagram Rank

Changed

• Adjusted the Executive Summary Mermaid reference architecture so HealthShare sits below the Health Connect adapter row, with UCR, EMPI, Clinical Viewer, and Provider Directory beneath HealthShare.
• Preserved the compact Mermaid diagram and the existing Health Connect to HealthShare relationship; the change is only a layout/rank correction for readability.

2026-06-22 - SDA Definition Link Pass

Changed

• Added explicit Executive Summary links from Summary Document Architecture (SDA), CDA, FHIR, Health Connect, HealthShare, and IRIS for Health to their local wiki definition or product pages.
• Expanded SDA and CDA Transformation with a fuller SDA definition and related InterSystems transformation-route table for SDA, CDA/C-CDA, FHIR, HL7, DTL, and XSLT/XSL.
• Made Summary Document Architecture and Clinical Document Architecture terms explicit links so the generic Architecture page-title linker does not hijack the definition text.
• Updated the glossary SDA entry so readers land on the full definition rather than an incidental phrase highlight.

2026-06-22 - Executive Summary Mermaid Restoration

Changed

• Restored the Executive Summary Reference Architecture as a Mermaid flowchart TB at user direction.
• Kept the diagram labels compact to avoid the earlier overlap problem; detailed interface names and proof requirements remain in the adjacent tables.
• Added a pinned Mermaid browser runtime (mermaid@11.15.0) and local initializer so MkDocs Mermaid fences render as diagrams.
• Updated Context Map so the current anchor model says the Executive Summary uses compact Mermaid, not a static text diagram.
• Broadened Graphify freshness normalization for volatile GRAPH_REPORT.md prose sections while retaining generated graph-asset checks.

2026-06-22 - Executive Summary Alignment Pass

Searched

• Graphify relationships for Executive Summary, DSIC HealthShare Compliance Map, and GP Connect and Spine Equivalents by Nation.
• Rendered Executive Summary HTML at http://127.0.0.1:8002/executive-summary/.
• Existing DSIC, devolved connectivity, and context-map anchor wording.

Found

• The Executive Summary static text diagram is sufficient for now: the served page contains the static architecture block and no Mermaid block.
• The detailed interface names and proof requirements belong in the DSIC and four-nation evidence tables, not in a long diagram label set.
• DSIC alignment needed a clear split between Health Connect as mediation/adapter layer, HealthShare as shared-care/identity/viewer layer, and DSIC as an England solution-level proof question.

Added / Changed

• Added an Executive Summary interface-alignment table to DSIC HealthShare Compliance Map.
• Added a compact four-nation adapter proof table to GP Connect and Spine Equivalents by Nation.
• Updated Context Map to record the static-diagram decision and the DSIC/devolved anchor alignment.

2026-06-22 - Executive Summary Diagram Rendering Fix

Changed

• Replaced the Executive Summary Reference Architecture Mermaid block with a compact static text diagram after the rendered page showed diagram text overlap / instability in the in-app browser.
• Kept the detailed route names, standards, onboarding artefacts, and governance dependencies in the surrounding strategy and four-nation tables rather than forcing them into the diagram labels.
• Tightened the Graphify freshness checker so non-semantic GRAPH_REPORT.md community-count/list variance is normalized consistently with the existing community-section normalization.

Verification

• Ran npm run kb:update.
• Ran npm run verify.
• Checked the rendered Executive Summary at http://127.0.0.1:8002/executive-summary/ and confirmed there are no Mermaid elements left in the Reference Architecture section.

2026-06-22 - Executive Summary Home Section

Searched

• Graphify relationships for Home, Programme CORTISONE / UK Defence Healthcare, DSIC HealthShare Compliance Map, NHS England Digital Primary Care, GP Connect Deep Dive, GP Connect and Spine Equivalents by Nation, Standards and Interoperability Evidence Domain, Evidence Matrix, Source and Evidence Domain Map, and Context Map.
• Current wiki evidence for Health Connect, HealthShare, SDA/CDA transformation, DSIC national-service dependencies, GP Connect supplier-progress evidence, CORTISONE, and devolved-nation connectivity equivalents.
• Official GOV.UK evidence for the Defence Medical Information Capability Programme (DMICP) baseline.

Found

• Executive Summary should sit under the Home navigation group above Knowledge Base, not replace the Home page.
• The ES needs to answer the exam question directly: Health Connect as mediation layer; HealthShare as shared-care/identity/viewer layer; DSIC as England-only; devolved nations as functional connectivity equivalents rather than DSIC routes.
• GOV.UK supports DMICP as an integrated Defence primary health record and central data warehouse source, but does not expose the current interface catalogue, extract/API design, migration status, or CORTISONE-mediated implementation.
• CORTISONE and InterSystems evidence supports programme intent and supplier/licence facts, but still does not prove live DMICP-to-Health Connect-to-HealthShare routing, national-service adapters, clinical safety, information governance, or operational runbooks.

Added / Changed

• Added a new Home-section Executive Summary page before Knowledge Base in navigation.
• Updated Home to point readers to the Executive Summary first.
• Added SRC-240 for the DMICP baseline source.
• Updated Programme CORTISONE / UK Defence Healthcare, Evidence Matrix, Evidence Validation Queue, Source and Evidence Domain Map, Further Research Priorities, and Context Map to record the DMICP/CORTISONE interface-proof boundary.

Open Questions

• What is the current DMICP source-interface catalogue, extract/API capability, data model, and migration route into CORTISONE?
• Which CORTISONE artefacts map Health Connect, HealthShare, IRIS for Health, EMPI, Clinical Viewer, national-service adapters, DSA/DPIA, DCB0129/DCB0160, and operations into a live architecture?

2026-06-21 - North West London and eConsult Current-Source Pass

Searched

• Graphify relationships for North West London ICS, eConsult / UK NHS Triage, UK NHS Evidence, Evidence Matrix, Source Register, Evidence Validation Queue, Source and Evidence Domain Map, and Further Research Priorities.
• Current public North West London source targets across ICB web estates, member-trust material, public recruitment records, and procurement search routes.
• Current public eConsult / Huma / InterSystems / Digital Front Door source targets, including InterSystems partner material, awards pages, public deployment posts, and public procurement notices.

Found

• North West London still has no public ICB, board, procurement, contract-award, or customer programme source found in this pass for an ICS-level Health Connect Cloud operating model.
• Official North West London acute-trust recruitment evidence does support a narrower Health Connect / Trust Integration Engine technical context, including interface development, supplier liaison, and Health Connect experience requirements.
• eConsult evidence has moved beyond the 2026-06-18 state: current InterSystems material says eConsult, part of Huma, chose Health Connect Cloud for NHS integration, and public Digital Front Door signals name InterSystems & eConsult in NHS urgent and emergency care.
• eConsult still lacks a formal Huma, NHS, or customer-approved architecture pack for product versions, HCC versus IRIS role split, clinical-safety artefacts, interface specifications, service levels, and site-by-site deployment scope.

Added / Changed

• Added SRC-237 to SRC-239 for North West London acute-trust Health Connect recruitment evidence, current eConsult / Huma HCC partner evidence, and eConsult Digital Front Door public deployment/procurement signals.
• Updated North West London ICS, eConsult / UK NHS Triage, UK NHS Evidence, Evidence Matrix, Evidence Validation Queue, Source and Evidence Domain Map, and Further Research Priorities.
• Reconciled the UK NHS Evidence anchor confidence state across North West London, eConsult, North Tees, West Midlands cancer/eMDT, MERIT, and ROH without creating a new UK NHS examples evidence-domain page.

Open Questions

• Which public ICB, trust board, procurement, or customer programme source can confirm North West London ICS Health Connect Cloud current scope, supplier role, and operating model?
• Which Huma, eConsult, NHS, or customer source can confirm the current Digital Front Door / eTriage product-version, HCC versus IRIS role split, interface architecture, and safety/deployment artefacts?

2026-06-21 - Actionable What Next Rule

Searched

• Graphify relationships for root agent rules, Project Ops Agent Rules, LLM Wiki Maintenance, Context Map, Starter Instruction, and Research Log.
• Existing response-contract wording for What Next, follow-up discipline, background controls, and sibling-project reuse.

Found

• The project already required exactly three balanced, high-impact What Next steps, but did not explicitly prevent passive trigger conditions or generic maintenance reminders from being counted as numbered steps.
• The durable rule should live in root agent rules, operational wiki maintenance, project-ops agent rules, context map follow-up discipline, and starter instructions so future agents inherit it consistently.

Added / Changed

• Added a rule that What Next slots must be executable next-pass work.
• Clarified that parked trails, "wait until a source appears" triggers, and generic maintenance reminders belong in the summary, Evidence Validation Queue, Research Log, or affected synthesis page rather than in the three numbered next steps.

Open Questions

• None. This is now a project operating rule.

2026-06-21 - DSIC Standards Consistency and ROH Breadth Recheck

Searched

• Graphify relationships for DSIC Digital Services for Integrated Care, DSIC Capability-to-Standard Crosswalk, NHS Standards Directory and DHSC Standards Direction, Source and Evidence Domain Map, UK NHS Evidence, Evidence Validation Queue, Evidence Matrix, Source Register, and Research Log.
• Existing DSIC overview, crosswalk, standards/national-services, and standards-directory pages for PDS, ODS, and SDS wording.
• Current public ROH pages, targeted ROH EPR / InterSystems / TrakCare searches, ROH Medicines Optimisation Strategy 2025-2028, and ROH Green Plan search results.

Found

• DSIC Capability-to-Standard Crosswalk and NHS Standards Directory wording already had explicit ODS/SDS treatment, but the DSIC overview and DSIC Standards and National Services needed light alignment so PDS, ODS/SDS, and capability-linked identity/directory wording are consistent.
• Source and Evidence Domain Map still does not justify a new UK NHS examples evidence-domain page; the right breadth target was to add evidence to an existing example page.
• ROH customer pages still support selection and contract. A stable ROH medicines strategy PDF adds adjacent EPR planning evidence for closed-loop medicines, DMS referrals, EPS prescriptions, reporting, and patient-facing navigation around the chosen/new EPR system.
• No public ROH go-live, implementation-outcome, or clinical-safety update was found. The ROH Green Plan result also referenced EPR deployment, but its short document link returned a server error outside search results, so it was not added as a durable source-register row.

Added / Changed

• Aligned DSIC overview and DSIC Standards and National Services wording with the crosswalk and standards-directory PDS/ODS/SDS treatment.
• Added SRC-236 for ROH Medicines Optimisation Strategy 2025-2028.
• Updated Royal Orthopaedic Hospital EPR, UK NHS Evidence, Evidence Validation Queue, Evidence Matrix, Source and Evidence Domain Map, and Further Research Priorities to record ROH adjacent planning evidence without treating it as TrakCare go-live proof.

Open Questions

• Will ROH publish a programme update, go-live announcement, clinical-safety artefact, implementation-scope statement, or post-implementation outcome evidence naming the new EPR deployment?

2026-06-21 - ODS/SDS Crosswalk Closure and Supplier Catalogue Check

Searched

• Graphify relationships for DSIC Capability-to-Standard Crosswalk, NHS Standards Directory and DHSC Standards Direction, Context Map, NHS England Digital Primary Care Evidence Domain, Evidence Validation Queue, Evidence Matrix, Source Register, and Research Log.
• Current DSIC / Buying Catalogue / Digital Primary Care sources on NHS England Digital, NHS DSIC Confluence buyer guidance, Buying Catalogue guidance, and Find a Tender Digital Primary Care notices.
• Targeted public search for InterSystems, HealthShare, Health Connect, IRIS for Health, and DSIC / Buying Catalogue / Find a Tender supplier evidence.

Found

• ODS/SDS needed explicit treatment in the DSIC crosswalk and NHS Standards Directory map after the PDS/ODS identity-directory pass.
• The current Digital Primary Care Find a Tender notices support replacement-framework/procurement context, not supplier award or InterSystems capability scope.
• The current public search found no indexed DSIC/Buying Catalogue or Find a Tender listing naming InterSystems, HealthShare, Health Connect, IRIS for Health, or a partner capability scope.

Added / Changed

• Updated DSIC Capability-to-Standard Crosswalk to include ODS/SDS in patient information maintenance, document management, and unified care record proof boundaries.
• Updated NHS Standards Directory and DHSC Standards Direction to treat ODS/SDS as national organisation/reference-data and endpoint/addressing dependencies alongside PDS, SDS, NEMS, MESH, and related standards surfaces.
• Updated Context Map, NHS England Digital Primary Care Evidence Domain, Evidence Validation Queue, and Evidence Matrix to park identity-directory pending direct artefacts and to record that the supplier/catalogue search found no public InterSystems listing.

Open Questions

• Will a future DSIC/Buying Catalogue row, Digital Primary Care award, supplier-progress entry, or customer procurement artefact name InterSystems, HealthShare, Health Connect, IRIS for Health, or a partner capability scope?

2026-06-21 - EMPI / Provider Directory PDS and ODS Source Pass

Searched

• Graphify relationships for HealthShare EMPI, HealthShare Provider Directory, DSIC HealthShare Compliance Map, HealthShare Components Evidence Domain, InterSystems Standards Product Map, Evidence Validation Queue, Source and Evidence Domain Map, Evidence Matrix, Context Map, Source Register, and Research Log.
• Current NHS England Digital PDS FHIR API, PDS FHIR technical conformance, PDS FHIR integrated-products, ODS service/API, ODS developer guidance, and ODS news pages.
• Targeted public search for InterSystems / HealthShare / EMPI / Provider Directory references with PDS, NHS number, ODS, and SDS.

Found

• Cycle guard: Care Community remains bounded; identity/directory is an active gap because PDS/ODS requirements can narrow a DSIC assurance question.
• PDS FHIR technical conformance creates concrete local-system requirements around local-copy synchronisation, sensitive patient records, superseded and invalidated NHS numbers, user warnings, local back-office referral, and de-coupling invalid local records from PDS.
• ODS guidance creates concrete organisation-data requirements around ODS-code lookup, validation, relationships, succession, modified-organisation lists for local synchronisation, and dynamic geography/data-quality changes.
• The PDS FHIR integrated-products page lists Intersystems HealthConnect 2020.1 for North West Anglia NHS Foundation Trust as application-restricted, approved 2021-08-25. The pass did not find official PDS integrated-products rows naming HealthShare EMPI or HealthShare Provider Directory.

Added / Changed

• Added SRC-234 for PDS FHIR API technical conformance and integrated-products evidence.
• Added SRC-235 for ODS service, API, and organisation-data guidance.
• Updated HealthShare EMPI, HealthShare Provider Directory, DSIC HealthShare Compliance Map, HealthShare Components Evidence Domain, InterSystems Standards Product Map, Evidence Matrix, Evidence Validation Queue, Source and Evidence Domain Map, Further Research Priorities, and Context Map.

Open Questions

• Is there product/version or customer-approved evidence showing HealthShare EMPI uses PDS FHIR, handles invalid/superseded NHS numbers, and owns matching/stewardship/back-office workflow in a named deployment?
• Is there product/version or customer-approved evidence showing Provider Directory maps to ODS/SDS, synchronises organisation-data changes, and owns directory stewardship/audit in a named deployment?
• Does the Intersystems HealthConnect 2020.1 PDS FHIR row represent a current operational route, a historical approval, or a customer-specific integration that should remain separate from HealthShare component claims?

2026-06-21 - HealthShare Component Consistency and Identity Target

Searched

• Graphify relationships for HealthShare, HealthShare Components Evidence Domain, EMPI, Provider Directory, Health Insight, Personal Community, DSIC HealthShare Compliance Map, InterSystems Standards Product Map, Evidence Matrix, Context Map, and Research Log.
• Existing HealthShare component pages and DSIC component mapping.

Found

• Care Community should stop being the default focus after the source-backed update unless Lincolnshire/customer confirmation becomes a specific requirement.
• Existing component pages are consistent at taxonomy level but needed a cross-component assurance snapshot to keep breadth visible.
• EMPI / Provider Directory identity and directory assurance is the right next non-Care component target because it crosses DSIC shared-care architecture, PDS/NHS number, ODS/SDS, matching/stewardship, synchronisation, audit, and safety ownership.

Added / Changed

• Added a component assurance snapshot to HealthShare Components Evidence Domain.
• Updated HealthShare, DSIC HealthShare Compliance Map, Evidence Matrix, Further Research Priorities, and Context Map to leave Care Community complete-for-now and select EMPI / Provider Directory as the next broader HealthShare evidence target.

Open Questions

• Which sources can prove PDS/NHS number, ODS/SDS, matching/stewardship, directory governance, audit, safety ownership, and live customer deployment artefacts for a named EMPI / Provider Directory deployment?

2026-06-21 - Care Community Evidence Target and What Next Discipline

Searched

• Graphify relationships for HealthShare Care Community, HealthShare Components Evidence Domain, Evidence Matrix, Source Register, Context Map, LLM Wiki Maintenance, Starter Instruction, and root agent rules.
• Current public InterSystems documentation and resource pages for HealthShare Care Community, Personal Community patient contributions to Care Community, and Lincolnshire NHS Care Community usage.

Found

• The next useful Care Community target is real evidence, not another structure-control loop.
• Current public InterSystems documentation supports Personal Community integration mechanics for patient contributions to Care Community care plans, including UCR service-registry and Workbench configuration.
• InterSystems' Care Community resource gives a vendor-published Lincolnshire NHS care-plan signal, including individualised care plans for local care teams and patients, but not independent customer assurance.
• Source and Evidence Domain Map, Evidence Validation Queue, and Context Map should operate as background controls in What Next, not repeated default recommendations.

Added / Changed

• Added SRC-232 and SRC-233 to the Source Register.
• Updated HealthShare Care Community with technical integration evidence, Lincolnshire customer-signal boundaries, and sharper follow-up evidence.
• Updated Evidence Matrix, HealthShare Components Evidence Domain, Evidence Validation Queue, Context Map, LLM Wiki Maintenance, Starter Instruction, and root agent rules.

Open Questions

• Can Lincolnshire ICS/NHS, a DPIA/DSA, procurement record, clinical-safety artefact, or implementation document independently confirm the Care Community care-plan deployment and governance model?

2026-06-21 - Care Community Stop/Go Queue Pass

Searched

• Graphify relationships for HealthShare Care Community, HealthShare Components Evidence Domain, Evidence Validation Queue, Source and Evidence Domain Map, Context Map, and Research Log.
• Existing Care Community page, component-domain source clusters, evidence-matrix component rows, source register, and queue entries.

Found

• Care Community already has a component page and is covered by the HealthShare Components Evidence Domain.
• The unresolved evidence is single-component implementation proof: current technical/configuration documentation, care-plan templates, task workflow, patient/proxy access, FHIR resource use, notifications, local clinical governance, and customer deployment status.
• The stop/go gate does not justify a new page, checklist, request pack, or evidence-domain layer. No sibling project path was supplied, so no external project artifact was changed.

Added / Changed

• Linked Care Community's unresolved implementation gap to the Evidence Validation Queue.
• Expanded the HealthShare components queue row to explicitly cover Care Community as a queue-held component gap.
• Recorded the no-new-structure decision in Source and Evidence Domain Map.

Open Questions

• Which current Care Community technical documentation or customer-side deployment source, if any, can turn vendor positioning into implementation assurance?

2026-06-21 - Stop/Go Agent Contract and Sibling Prompt

Searched

• Graphify relationships for Source and Evidence Domain Map, Evidence Validation Queue, Context Map, LLM Wiki Maintenance, Starter Instruction, and root agent rules.
• Existing stop/go, single-source-gap, sibling-project reuse, and request-pack discipline wording.

Found

• Source and Evidence Domain Map already held the stop/go rule, and Maintenance / Starter Instruction already held most of the reusable assurance discipline.
• The root agent contract did not yet state the stop/go gate or single-source queue rule directly.
• The sibling-project prompt existed in the response history but needed to be persisted in a starter artifact because no external target project path was supplied.

Added / Changed

• Added stop/go, single-source queue, and sibling-project prompt rules to AGENTS.md.
• Added the sibling-project equivalent prompt to Starter Instruction.
• Tightened LLM Wiki Maintenance so the stop/go rule applies to pages, checklists, request packs, and evidence-domain layers, not only evidence-domain pages.

Open Questions

• Which sibling project, if any, should receive the prompt in its own root instructions when a target path is supplied?

2026-06-21 - Evidence Request Consolidation, PRSB Audit, and Structure Gate

Searched

• Graphify relationships for GP Connect InterSystems Supplier Progress, PRSB Core Information Standard, LLM Wiki Maintenance, Starter Instruction, Context Map, Source and Evidence Domain Map, Evidence Matrix, Evidence Validation Queue, Standards and Interoperability Evidence Domain, and Research Log.
• Existing GP Connect request pack wording, PRSB checklist wording, sibling-project reuse rules, and traversal-friction/domain-promotion rules.

Found

• The GP Connect request pack was adding value as a concrete evidence request, but its first sentence and some cross-page references were too process-oriented.
• The PRSB Core Information Standard page still duplicated the generic standards-conformance request pattern even though the canonical pattern had moved to the standards evidence domain.
• The project architecture needed an explicit stop/go rule: request packs are useful for active assurance claims, but overcomplicate the knowledge base when multiplied without a decision, delivery, research, or assurance use case.
• The Source and Evidence Domain Map remains the right gate for new structure; no new page, checklist, request pack, or domain should be added unless it reduces repeated traversal or makes an active assurance claim actionable.

Added / Changed

• Renamed the GP Connect section to Evidence Request Pack and trimmed the wording to focus on the real supplier/customer evidence ask.
• Collapsed the PRSB checklist-heavy section into PRSB-specific assurance scope and linked back to the canonical standards-domain pattern.
• Added a when not to add another request pack rule to LLM Wiki Maintenance and Starter Instruction.
• Updated Context Map, Evidence Validation Queue, Evidence Matrix, and Source and Evidence Domain Map to crystallise the architecture position: reusable request packs are infrastructure, not a default page pattern.

Open Questions

• Which future active assurance claim, if any, needs a claim-specific request pack after the Source and Evidence Domain Map stop/go gate is applied?

2026-06-21 - GP Connect Conformance Request and Sibling Reuse Note

Searched

• Graphify relationships for Evidence Validation Queue, GP Connect InterSystems Supplier Progress, InterSystems GP Connect Evidence Boundary, Standards and Interoperability Evidence Domain, Context Map, Source and Evidence Domain Map, LLM Wiki Maintenance, Starter Instruction, Evidence Matrix, Further Research Priorities, and Research Log.
• Existing GP Connect supplier-progress precision page, reusable standards-conformance request pattern, domain-selection rules, and operational wiki guidance.

Found

• The GP Connect InterSystems supplier-progress row is the best non-Defence assurance claim to receive the generic request pattern: the NHS parsed rows are high-confidence supplier-progress evidence, but still not product configuration, local onboarding, clinical-safety, or customer deployment proof.
• The operational wiki had balanced follow-up discipline, but not a concise sibling-project note that paired the reusable conformance pattern with the breadth/domain-promotion gate.
• The current work does not create traversal friction that justifies another evidence-domain page; the existing standards domain and GP Connect pages remain the right routing layer.

Added / Changed

• Added a GP Connect conformance request application to GP Connect InterSystems Supplier Progress, covering supplier-progress record, validation/test scope, exclusions, component coverage, adjacent standards, and deployment artefacts.
• Updated Evidence Validation Queue, Evidence Matrix, InterSystems GP Connect Evidence Boundary, Standards and Interoperability Evidence Domain, Further Research Priorities, Context Map, and Source and Evidence Domain Map to record the worked non-PRSB request pattern and the no-new-domain decision.
• Added sibling-project reuse guidance to LLM Wiki Maintenance and Starter Instruction so future projects can reuse the conformance pattern and traversal-friction gate.

Open Questions

• Which future assurance claim is being relied on strongly enough to need the same request-pattern treatment: GP Connect customer deployment, DSIC catalogue/supplier evidence, HealthShare AI Assistant governance, or managed FHIR service assurance?

2026-06-20 - Standards Pattern Promotion and Clinical Viewer Audit

Searched

• Graphify relationships for Clinical Viewer, standards-conformance request wording, Standards and Interoperability Evidence Domain, InterSystems Standards Product Map, Source and Evidence Domain Map, Evidence Matrix, Evidence Validation Queue, Further Research Priorities, and Context Map.
• Existing PRSB reusable request checklist, Clinical Viewer page, HealthShare AI Assistant boundary, UCR evidence separation, standards product-map high-risk audits, and breadth-selection wording.

Found

• The reusable conformance-request model was still canonically described on the PRSB CIS page, which made sibling projects depend on a PRSB-specific page for a generic assurance pattern.
• Clinical Viewer needed the same high-risk audit treatment as UCR because presentation, access, RBAC, SSO, AI Assistant / Navigation Application adjacency, clinical-safety, and deployment proof can be over-read as one evidence claim.
• Source and Evidence Domain Map already contained the right promotion principle, but it needed a clearer breadth gate: promote a new domain only when repeated traversal across modules, canonical registers, and the queue creates friction.

Added / Changed

• Promoted the reusable standards-conformance evidence request pattern into Standards and Interoperability Evidence Domain and reframed the PRSB CIS checklist as a PRSB-specific application of that canonical model.
• Added HealthShare Clinical Viewer to InterSystems Standards Product Map with a high-risk row audit separating presentation capability, SSO/RBAC/audit, AI Assistant adjacency, customer deployment, and safety/governance proof.
• Updated Clinical Viewer, HealthShare, HealthShare Components Evidence Domain, Standards and Interoperability, Evidence Matrix, Evidence Validation Queue, Further Research Priorities, Source and Evidence Domain Map, and Context Map to reflect the generic request pattern, Clinical Viewer audit, and breadth-selection discipline.

Open Questions

• Which non-Defence standards or product claim is next actually being used as assurance and therefore needs the reusable request pattern applied before guidance relies on it?

2026-06-20 - Generic Conformance Pattern, UCR Audit, and Defence Containment

Searched

• Graphify relationships for HealthShare Unified Care Record, Clinical Viewer, PRSB Core Information Standard, InterSystems Standards Product Map, Source and Evidence Domain Map, Evidence Matrix, Evidence Validation Queue, Further Research Priorities, and Context Map.
• Existing PRSB request checklist, UCR page, standards product-map high-risk audits, standards evidence domain, and Defence containment wording.

Found

• The PRSB checklist needed to become a generic standards/conformance evidence-request pattern rather than a PRSB-only request list.
• HealthShare Unified Care Record is the next reusable non-Defence high-risk row because UCR product capability, PRSB record-content relevance, Clinical Viewer presentation, DSIC / GP Connect adjacency, and customer deployment proof are easy to conflate.
• Programme CORTISONE / UK Defence should be treated as contained unless a new primary source appears or the user explicitly reopens it; no further Defence information is expected in the current project context.

Added / Changed

• Renamed and reframed the PRSB checklist as a reusable standards-conformance evidence request pattern.
• Added a HealthShare Unified Care Record high-risk row audit to InterSystems Standards Product Map and added an Evidence Separation section to the UCR page.
• Updated Standards and Interoperability, Standards Evidence Domain, Evidence Matrix, Evidence Validation Queue, Further Research Priorities, Source and Evidence Domain Map, and Context Map to reflect the generic request model, UCR audit, and Defence containment boundary.

Open Questions

• Which non-Defence standards or product row next needs the reusable conformance pattern applied because a headline capability or certificate is being used as deployment proof?

2026-06-20 - PRSB Validation-Scope Evidence Request Checklist

Searched

• Graphify relationships for PRSB Core Information Standard, Evidence Validation Queue, Further Research Priorities, Evidence Matrix, and the recent HealthShare / PRSB CIS high-risk audit.
• Existing PRSB CIS page and validation-queue standards rows.

Found

• The PRSB CIS page had follow-up evidence bullets, but not a request-ready structure for certificate, validation scope, exclusions, component coverage, adjacent standards, and deployment artefacts.
• The unresolved PRSB validation-scope work should also appear in the Evidence Validation Queue as To Do.

Added / Changed

• Added a Validation-Scope Evidence Request Checklist to PRSB Core Information Standard.
• Added a PRSB CIS / HealthShare row to the Evidence Validation Queue.

Open Questions

• Can PRSB, InterSystems, an NHS standards owner, or a customer deployment team provide a certificate/register reference, validation-scope summary, exclusions, component coverage, adjacent standards evidence, and customer-approved deployment artefact summary without disclosing sensitive operational details?

2026-06-20 - Graphify Smoke Artifact, Breadth Reassessment, and PRSB Audit

Searched

• Graphify relationships for Graphify Views, Graphify 2D, Graphify 3D, LLM Wiki Maintenance, Source and Evidence Domain Map, Standards Product Map, PRSB CIS, Evidence Matrix, Evidence Validation Queue, Further Research Priorities, and Context Map.
• Existing standards product-map high-risk audits, PRSB Core Information Standard page, Source and Evidence Domain Map, Graphify maintenance notes, package scripts, and test structure.

Found

• Graphify button/chrome regressions had recurred enough to justify a repeatable rendered smoke artifact, but the check should remain separate from npm run verify because it depends on the local wiki server.
• The next breadth target does not justify a new evidence-domain page: standards implementation proof can continue inside the existing Standards and Interoperability Evidence Domain; devolved nations remain the leading future candidate only if traversal pressure grows; UK NHS examples, UK Defence, and international PHC remain navigable.
• HealthShare / PRSB CIS is the next high-risk standards product-map row because PRSB conformance evidence is strong but can be over-read into HealthShare-family, GP Connect, FHIR/HL7/DICOM/IHE, DSIC, local role-view, safety, and deployment claims.

Added / Changed

• Added scripts/smoke-graphify-rendered.mjs and npm run smoke:graphify-rendered for local rendered Graphify overview / 2D / 3D / theme checks.
• Added the smoke command to LLM Wiki Maintenance.
• Added a 2026-06-20 breadth reassessment to Source and Evidence Domain Map and reflected it in the Evidence Validation Queue.
• Added a HealthShare / PRSB CIS high-risk row audit to InterSystems Standards Product Map and updated PRSB CIS, Standards and Interoperability, Standards Evidence Domain, Evidence Matrix, Further Research Priorities, and Context Map.

Open Questions

• Which PRSB certificate, validation pack, or customer artefact can prove section-level CIS scope, exclusions, HealthShare component scope, local role/view configuration, clinical-safety ownership, and deployment status?

2026-06-20 - Graphify Convention and Devolved Parent Link Pass

Searched

• Graphify relationships for Graphify Views, Graphify 2D, Graphify 3D, LLM Wiki Maintenance, GP Connect and Spine Equivalents by Nation, and Source and Evidence Domain Map.
• Existing Graphify maintenance notes, Graphify 2D and 3D pages, Source and Evidence Domain Map devolved traversal-cost check, and the devolved parent comparison page.

Found

• The Graphify 2D and 3D pages now share the raw HTML full-screen button pattern, but the maintenance page did not yet record that convention.
• The three devolved country connectivity pages already point back to the domain-promotion trigger, but the parent GP Connect and Spine Equivalents by Nation page did not.

Added / Changed

• Added a Graphify maintenance convention requiring raw HTML anchors for full-screen Material buttons rather than Markdown attribute-list syntax.
• Added a parent-page link from GP Connect and Spine Equivalents by Nation to the Source and Evidence Domain Map promotion trigger.
• Ran a rendered Graphify overview / 2D / 3D pass for link, button, and Material chrome regressions.

Open Questions

• None.

2026-06-20 - Graphify 2D Button Markup Fix

Searched

• Graphify 2D Relationship Map page, Graphify 3D sibling page, Graphify graph relationships, and presentation test structure.

Found

• The 2D page used Markdown attribute-list button syntax, but the rendered wiki showed the attribute block as literal text instead of producing a Material button.
• The 3D page already used raw HTML anchor markup for the same full-screen button pattern.

Added / Changed

• Replaced the 2D full-screen link with the same explicit Material button HTML pattern used on the 3D page.
• Added a regression test that confirms the 2D page uses the HTML button link and does not reintroduce the literal attribute-list syntax.

Open Questions

• None.

2026-06-20 - Graphify 3D Button Text Visibility Fix

Searched

• Graphify 3D Spatial Map page, root design contract, project-ops design notes, LLM maintenance notes, theme CSS, and theme CSS tests.

Found

• The Graphify 3D page used a valid Material primary button link, but the custom article-link colour selector also matched .md-button links inside .md-content.
• That made the primary-button foreground use the teal article-link colour on a teal primary-button background, so the label was effectively only legible when hover styles changed the foreground.

Added / Changed

• Scoped article-link colour away from .md-button links so Material button controls keep their own foreground colours.
• Added a regression test that prevents the article-link colour rule from targeting Material buttons.
• Updated the design contract and maintenance notes to record that Material button links are excluded from article-link colour and highlight styling.

Open Questions

• None.

2026-06-20 - FHIR Services Audit, ITK Request Template, and Devolved Split Notes

Searched

• Graphify relationships for FHIR Services, NHS ITK Accreditation, Source and Evidence Domain Map, Scotland Connectivity Equivalents, Wales Connectivity Equivalents, Northern Ireland Connectivity Equivalents, Evidence Matrix, Evidence Validation Queue, and Context Map.
• Existing FHIR Services, InterSystems Standards Product Map, NHS ITK Accreditation, Standards and Interoperability, Standards Evidence Domain, Source and Evidence Domain Map, devolved connectivity pages, Evidence Matrix, Evidence Validation Queue, Further Research Priorities, and Context Map pages.

Found

• FHIR Services needed the same high-risk row treatment as Health Connect and IRIS for Health because managed FHIR service mechanics, profile/package support, OAuth/security, Network Connect, cloud settings, and cloud-hosted-service controls can be over-read as NHS profile conformance or customer assurance.
• The NHS ITK checklist was field-complete but needed a supplier/customer request template that could be reused without asking for patient-identifiable information, secrets, or operationally sensitive artefacts.
• The three devolved connectivity pages should point back to the Source and Evidence Domain Map promotion trigger before any future devolved-nations domain split.

Added / Changed

• Added a FHIR Services high-risk row audit to InterSystems Standards Product Map and reflected the same separation on the FHIR Services page.
• Added a supplier/customer evidence request template to NHS ITK Accreditation.
• Added compact Domain Split Trigger notes to Scotland, Wales, and Northern Ireland connectivity-equivalent pages.
• Updated Standards and Interoperability, Standards and Interoperability Evidence Domain, Evidence Matrix, Evidence Validation Queue, Further Research Priorities, and Context Map to keep the model consistent.

Open Questions

• Which customer or supplier artefact can prove a named FHIR Services deployment's UK region, tenancy, support, security, profile-validation, DSA/DPIA, and clinical-safety boundary?
• Will a future devolved-nations pass cross the promotion threshold for a dedicated evidence-domain page?

2026-06-20 - IRIS Product Audit, ITK Evidence Request Checklist, and Devolved Traversal Check

Searched

• Graphify relationships for IRIS for Health, NHS ITK Accreditation, InterSystems Standards Product Map, devolved-nation comparison pages, Source and Evidence Domain Map, Evidence Matrix, Evidence Validation Queue, and Context Map.
• Existing IRIS for Health, Standards Product Map, NHS ITK Accreditation, Standards and Interoperability, Standards Evidence Domain, Evidence Matrix, Evidence Validation Queue, Further Research Priorities, and Context Map pages.
• Devolved-nation structure: GP Connect and Spine Equivalents by Nation, Scotland / Wales / Northern Ireland connectivity-equivalent pages, and InterSystems in Scotland / Wales / Northern Ireland pages.

Found

• IRIS for Health needed the same high-risk row treatment as Health Connect because product positioning, current IRIS ITK documentation, GP Connect supplier-progress evidence, eConsult, and Programme CORTISONE are related but not interchangeable proof types.
• The NHS ITK page had implementation-proof requirements but not a request-ready checklist for product/version, certificate/register status, message bundle/profile, dates, current status, scope, and deployment artefacts.
• The devolved-nation material is currently navigable without a new evidence-domain page: one parent comparison, three connectivity-equivalent pages, three InterSystems-by-nation pages, and canonical register rows are sufficient for now.

Added / Changed

• Added an IRIS for Health high-risk row audit to InterSystems Standards Product Map and reflected the boundary on the IRIS for Health page.
• Added a focused ITK evidence request checklist to NHS ITK Accreditation.
• Added a Devolved Nations Traversal-Cost Check to Source and Evidence Domain Map.
• Updated Standards and Interoperability, Standards and Interoperability Evidence Domain, Evidence Matrix, Evidence Validation Queue, Further Research Priorities, and Context Map to keep the model consistent.

Open Questions

• Can a current IRIS for Health product/version-specific NHS conformance or onboarding record be obtained for ITK, GP Connect, MESH, ITK3, or DSIC-relevant standards?
• Will future cross-nation questions repeatedly require a new devolved evidence-domain page, or can the current parent/child module structure continue to carry the comparison?

2026-06-20 - NHS ITK Current-Source Recheck and Health Connect Audit

Searched

• Graphify relationships for NHS ITK Accreditation, InterSystems Standards Product Map, Standards and Interoperability Evidence Domain, Source and Evidence Domain Map, Evidence Validation Queue, Evidence Matrix, Source Register, and Context Map.
• Current NHS England Digital ITK conformance process, ITK Conformance Catalogue, and Solution Assurance Compliance Catalogue pages.
• Targeted public searches for InterSystems, HealthShare, Health Connect, and IRIS for Health in NHS ITK / conformance-catalogue contexts.
• InterSystems global healthcare standards page and current IRIS for Health ITK documentation references already registered in the wiki.

Found

• NHS England Digital publishes an ITK conformance process and conformance-catalogue route, but the 2026-06-20 pass found no current public NHS or standards-body row naming InterSystems, HealthShare, Health Connect, or IRIS for Health in the rendered ITK catalogue or targeted public search.
• The ITK Conformance Catalogue page says its detailed download is historical and will not be updated beyond 31 May 2026.
• The NHS Solution Assurance Compliance Catalogue explicitly excludes Interoperability Tool Kit Accreditation. Its Healthshare-named Royal Marsden rows are compliance-catalogue evidence, not ITK proof.
• Health Connect is a high-risk standards-product-map row because its product documentation supports standards-oriented integration capability, but not NHS conformance, GP Connect/MESH/ITK/ITK3 onboarding, managed-service assurance, or customer deployment proof.
• No new breadth-domain page is justified in this pass. Devolved nations are the leading future candidate only if traversal across service-equivalence and InterSystems-by-nation pages becomes repetitive; UK Defence and international PHC remain contained.

Added / Changed

• Added the NHS ITK conformance process page to the Source Register.
• Updated NHS ITK Accreditation, Standards and Interoperability Evidence Domain, Evidence Matrix, Evidence Validation Queue, Further Research Priorities, Source and Evidence Domain Map, and Context Map with the current-source boundary.
• Added a Health Connect high-risk row audit to InterSystems Standards Product Map.

Open Questions

• Can NHS England, a standards body, InterSystems, or a customer provide a current product/version-specific ITK row or certificate that is not visible on the rendered public catalogue page?
• Is the historical ITK catalogue spreadsheet retrievable through a manual browser session or official request, and if so does it contain any InterSystems row with product/version, certificate type, message bundle, date, and status?
• If source traversal becomes repetitive, should the next domain page cover devolved nations before UK Defence or international PHC?

2026-06-20 - NHS ITK Proof Slice and Product Map Audit

Searched

• Graphify relationships for NHS ITK Accreditation, InterSystems Standards Product Map, Standards and Interoperability Evidence Domain, UK NHS Evidence, Source and Evidence Domain Map, Evidence Validation Queue, and Context Map.
• Existing standards product map, NHS ITK accreditation page, standards evidence-domain page, UK NHS evidence overview, source/evidence domain map, validation queue, context map, and further research priorities.

Found

• NHS ITK is the narrowest useful implementation-proof slice because the wiki already separates a historical/vendor claim, current IRIS for Health documentation, and an NHS conformance-catalogue route from missing current non-vendor certificate/register and customer deployment proof.
• InterSystems Standards Product Map needed an explicit separation between vendor/product documentation, conformance/assurance evidence, and customer deployment artefacts.
• UK NHS Evidence is broad, but the overview plus independent example pages still provide enough routing. A dedicated UK NHS examples evidence-domain page would be premature until traversal across examples becomes repetitive enough to obscure evidence type and source boundaries.

Added / Changed

• Added NHS ITK implementation-proof requirements to Standards and Interoperability Evidence Domain and NHS ITK Accreditation.
• Added evidence-separation guidance to InterSystems Standards Product Map and registered the product-map boundary in Evidence Matrix.
• Updated Source and Evidence Domain Map, Evidence Validation Queue, Context Map, and Further Research Priorities to record NHS ITK as the selected proof slice and to defer a UK NHS examples evidence-domain page.

Open Questions

• Can a current NHS or standards-body public record be found that names InterSystems, product/version, ITK standard, certificate type, date, and status?
• Which future domain split, if any, will have enough traversal burden to justify promotion: devolved nations, UK Defence, international PHC, or UK NHS examples?

2026-06-20 - Standards Evidence Domain and Update Record Boundary Pass

Searched

• Graphify relationships for Standards and Interoperability, NHS Standards Directory, GP Connect Update Record, GP Connect / MESH / ITK3, Evidence Validation Queue, Context Map, and Source and Evidence Domain Map.
• Existing standards overview, NHS Standards Directory parent, GP Connect / MESH / ITK3 child page, GP Connect Update Record page, current evidence-domain pages, MkDocs navigation, LLM wiki index, and further research priorities.

Found

• Standards/governance evidence had become dense enough to justify its own source/evidence domain page, but the existing module pages should remain the synthesis layer.
• GP Connect Update Record is already documented as a distinct community-pharmacy structured write-back capability, but the MESH/ITK3/FHIR messaging pattern needed a clearer boundary so it is not inferred from Send Document, Access Record, or generic MESH API evidence.
• West Midlands and DUAA/ICO remain live queue items, but they do not need to drive this standards-domain pass.

Added / Changed

• Added Standards and Interoperability Evidence Domain as the third evidence-domain page and wired it into MkDocs navigation, Source and Evidence Domain Map, Standards and Interoperability overview, LLM wiki index, Context Map, Evidence Validation Queue, and Further Research Priorities.
• Added Update Record boundary notes to GP Connect Update Record and NHS Standards Directory GP Connect, MESH, and ITK3, keeping Update Record separate from Send Document, Access Record, Access Document, MESH API, and generic MESH/ITK3 evidence.
• Updated Context Map to record standards/governance as a first-class source/evidence domain and to keep future breadth expansion pointed away from West Midlands and DUAA unless triggered.

Open Questions

• Which future source/evidence domain split is next genuinely justified by traversal cost: UK NHS examples, devolved nations, UK Defence, or international PHC?
• Which standards cluster needs the next implementation-proof pass: clinical safety, terminology/medicines, PDS/events, transfer-of-care/PRSB content, diagnostics, or NHS ITK?

2026-06-19 - Follow-Up Discipline and Next Domain Selection

Searched

• Project operational rules, LLM wiki maintenance notes, starter instruction, Context Map, Source and Evidence Domain Map, Evidence Validation Queue, and Further Research Priorities.
• Existing HealthShare Components Evidence Domain and NHS Standards Directory map pages to decide whether the next breadth target should stay in HealthShare or move to standards/interoperability.

Found

• The response contract required exactly three What Next steps, but it did not yet prevent repeated deepening of the freshest unresolved thread.
• HealthShare Components and NHS England Digital Primary Care already have source/evidence domain pages.
• West Midlands Medicus / HealthShare and DUAA / ICO guidance are valid queue items, but both now have enough holding structure to wait for new evidence, targeted request activity, publication triggers, or explicit user direction.
• The standards/governance cluster is the best next breadth domain because it spans NHS Standards Directory, PRSB, GP Connect, MESH, ITK3, clinical safety, DUAA section 121 / Schedule 15, and NHS England / DHSC stewardship evidence.

Added / Changed

• Added a balanced follow-up discipline to root agent rules, LLM maintenance notes, starter instructions, and Context Map: one closure step, one synthesis or anchor-model step, and one breadth step unless the user asks to stay inside a single evidence trail.
• Added Source and Evidence Domain Map selection notes naming Standards Directory and interoperability mapping as the next non-West-Midlands breadth domain.
• Added Evidence Validation Queue use discipline so West Midlands Medicus / HealthShare, DUAA / ICO guidance, and similar trails remain trigger-driven instead of becoming default next-pass loops.
• Updated Further Research Priorities to mark DUAA and West Midlands work as trigger-based and to promote Standards Directory / interoperability mapping as the next domain-page candidate.

Open Questions

• Should the next breadth pass create a dedicated Standards and Interoperability Evidence Domain page, or is the existing NHS Standards Directory parent plus GP Connect / MESH / ITK3 child page sufficient after one more audit?
• Which standards cluster should be itemised first if the domain page is created: clinical safety, terminology/medicines, PDS/events, transfer-of-care/PRSB content, or diagnostics?

2026-06-19 - Medicus FOI Targets, Route Architecture, and ICO Queue Refresh

Searched

• Official FOI and information-request pages for Birmingham and Solihull ICB, Coventry and Warwickshire ICB, Herefordshire and Worcestershire ICB, UHB, BCHC, ROH, and BSMHFT.
• ICO general data-protection planning, technology planning, ADM/profiling consultation, subject-access, research-provisions, and IDTA/Addendum pages.
• DSIC HealthShare Compliance Map, Evidence Validation Queue, source register, source/evidence domain map, further research priorities, and LLM wiki context.

Found

• The best next public-authority evidence route is targeted rather than broad: ICBs for programme/DSA/DPIA/route scope; UHB for hosting and operational role; participating trusts for workflow/safety/privacy artefacts; NHS England for national-service onboarding evidence; suppliers for voluntary technical/customer-approved artefacts.
• ICO queued topics remain queued. Right of Access in brief and SARs Q&A still have summer 2026 final timing; research provisions are still redrafting / under review; ADM/profiling consultation is closed with winter 2026 final timing; IDTA/Addendum updates remain planned during 2026.

Added / Changed

• Added SRC-230 for official FOI/source-target routes.
• Added a West Midlands Medicus / HealthShare FOI and Source-Target Pack to the Evidence Validation Queue.
• Added a route-specific architecture table to the DSIC HealthShare Compliance Map covering Medicus, HealthShare, GP Connect, MESH, ITK3, NDSA, DSA, DPIA, DCB0129/DCB0160, and supplier/service management.
• Refreshed DUAA / ICO Guidance Tracker rows to record the second 2026-06-19 recheck without converting planned or under-review guidance into final implementation authority.

Open Questions

• Which public-authority route will disclose enough architecture, DSA/NDSA, DPIA, DCB0129/DCB0160, MESH/ITK3, and RACI evidence to close the local West Midlands route gap?
• Will supplier-side Medicus or InterSystems material be customer-approved and specific enough to pair safely with FOI/public-authority evidence?
• Which ICO queued topic reaches final DUAA-updated guidance first and requires a page-by-page replacement pass?

2026-06-19 - Medicus West Midlands Deployment Checklist and ICO Recheck

Searched

• Official NHS GP Connect service and GP Connect DPIA pages for current Medicus, National Data Sharing Arrangement, onboarding, and assurance context.
• Public NHS/customer, ICB, local-programme, safety, information-governance, and deployment terms for Medicus, West Midlands Shared Care Record, GP Connect, MESH, ITK3, DSA, DPIA, DCB0129, and DCB0160.
• ICO general data-protection, technology, automated decision-making/profiling consultation, and IDTA/Addendum transfer guidance pages for DUAA follow-up status.
• Source register, evidence matrix, Evidence Validation Queue, DSIC HealthShare Compliance Map, Birmingham and West Midlands Validation, NHS England Digital Primary Care, GP Connect, source/evidence domain maps, and LLM wiki context.

Found

• NHS GP Connect service material last edited 15 June 2026 supports national Medicus context: Patient Facing APIs are live with Medicus, Access Document is FoT ready for Medicus, several Access Record: Structured sections are FoT ready for Medicus, suppliers must complete onboarding/assurance, and the NDSA sets out GP Connect data-sharing requirements.
• The GP Connect DPIA names Medicus as a new NHS market entrant for GPs and frames the DPIA as a living document for organisations using or developing GP Connect.
• No official public West Midlands NHS/customer source was found for the specific Medicus-to-HealthShare route, local GP Connect/MESH/ITK3 onboarding, final DSA/NDSA adoption, current local DPIA, DCB0129/DCB0160, endpoint/certificate, MESH mailbox, or supplier-responsibility matrix.
• ICO planning remains mixed: Right of Access in brief and SARs Q&A are still expected in summer 2026, research guidance is redrafting with summer 2026 final timing, ADM/profiling final guidance is expected winter 2026, and IDTA/Addendum updates remain planned during 2026.

Added / Changed

• Added SRC-229 for official NHS GP Connect current status, NDSA, and DPIA Medicus context.
• Added a Medicus / West Midlands deployment-evidence checklist to the DSIC HealthShare Compliance Map, separating named deployment identity, route architecture, supplier split, GP Connect provider/consumer roles, patient-facing route, MESH/ITK3 messaging, data-sharing, DPIA/privacy, clinical safety, operations, and DUAA data-subject workflow evidence.
• Updated Birmingham and West Midlands Validation with official source-search status for Medicus national GP Connect status, local deployment route, DSA/NDSA, DPIA, and DCB0129/DCB0160 gaps.
• Updated the Evidence Matrix, Evidence Validation Queue, GP Connect supplier-progress page, NHS England Digital Primary Care pages, HealthShare Components domain, source/evidence domain map, Further Research Priorities, and LLM wiki context to keep national Medicus evidence separate from local West Midlands deployment proof.

Open Questions

• Can official ICB, trust, programme, FOI, procurement, or supplier-customer material confirm the West Midlands Medicus / HealthShare route and current live scope?
• Which deployment pack will expose the signed DSA/NDSA adoption, current DPIA, DCB0129/DCB0160 safety artefacts, endpoint/certificate setup, MESH mailbox, and supplier-responsibility matrix?
• Which final ICO topic-guidance products should replace the remaining DUAA guidance-tracker rows during summer/winter 2026?

2026-06-19 - DUAA Subject Access, GP Connect Parse, and Birmingham Artefact Pack Pass

Searched

• Official NHS GP Connect supplier-progress page and structural HTML table output for InterSystems and Medicus rows.
• ICO DUAA organisation guidance, subject-access guide, general data protection planning page, technology guidance planning page, and international-transfer guidance.
• Birmingham and Solihull ICS Shared Care Record page, Coventry and Warwickshire Integrated Care Record FAQ material, Arden & GEM Coventry/Warks case study, West Midlands Care Association Shared Care Records / GP Connect support page, HTN Medicus/West Midlands report, and InterSystems UKI LinkedIn post.
• Graphify source map, source register, evidence matrix, Evidence Validation Queue, DSIC HealthShare Compliance Map, GP Connect InterSystems Supplier Progress, NHS England Digital Primary Care, standards pages, domain maps, and LLM wiki notes.

Found

• The NHS supplier-progress page edited 5 June 2026 can now be parsed structurally: InterSystems / IRIS For Health (Middleware) maps to Send Document (Send) v2.0.1 only; 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.
• Medicus provider and consumer rows are visible in the same NHS source, which matters because current HTN and InterSystems social material say Medicus GP systems have been connected within the West Midlands Shared Care Record running on HealthShare.
• ICO's main subject-access guide now supports the DUAA reasonable/proportionate-search reading, but Right of Access in brief, SARs Q&A, research, automated decision-making/profiling, and IDTA/Addendum updates remain on the guidance tracker.
• Birmingham / West Midlands public evidence supports a partial artefact pack for DSA-sensitive-information boundaries, DPIA/supplier role, processor/hosting context, GP Connect/DSCR onboarding support, and current Medicus integration signalling; it still does not expose final signed DSA, current full DPIA, DCB0129/DCB0160, endpoint/certificate, MESH mailbox, or named onboarding artefacts.

Added / Changed

• Added source IDs SRC-225 through SRC-228 for ICO subject access, Birmingham / West Midlands governance and DSA evidence, WMCA DSCR/GP Connect support, and the current Medicus / HealthShare integration signal.
• Updated GP Connect InterSystems Supplier Progress, InterSystems GP Connect Evidence Boundary, GP Connect Deep Dive, GP Connect roadmap, Standards and Interoperability, the GP Connect / MESH / ITK3 Standards Directory page, NHS Connectivity and GP Connect, UK NHS Evidence, and source/evidence domain pages to use the parsed InterSystems row mapping.
• Expanded the DSIC HealthShare Compliance Map with a current Birmingham / West Midlands artefact-pack status table covering DSA/DPIA, DCB0129/DCB0160 absence, supplier responsibilities, GP Connect/MESH/ITK3 onboarding, WMCA DSCR support, and current Medicus integration signalling.
• Updated the Evidence Validation Queue, Evidence Matrix, DUAA page, Further Research Priorities, and LLM wiki context so the remaining work is implementation proof, not table parsing.

Open Questions

• Can official NHS/customer Birmingham / West Midlands material confirm the Medicus integration architecture, live status, and whether GP Connect, MESH, or ITK3 is the implemented route?
• Can the final DSA, current DPIA, DCB0129/DCB0160, endpoint/certificate, MESH mailbox, and supplier-responsibility artefacts be obtained or source-linked publicly?
• When ICO publishes Right of Access in brief, SARs Q&A, research, automated decision-making/profiling, and IDTA/Addendum updates, which wiki rows need replacement or narrowing?

2026-06-19 - DUAA ICO Guidance and GP Connect Standards Split Pass

Searched

• Official ICO DUAA organisation guidance, complaints guidance, lawful-basis / recognised legitimate interest / legitimate interests / purpose-limitation guidance, international-transfer guidance, storage/access technologies guidance, and ICO guidance-planning pages.
• Graphify source map, DUAA page, NHS Standards Directory map, DSIC HealthShare Compliance Map, Evidence Validation Queue, evidence matrix, source register, source/evidence domain map, NHS England Digital Primary Care evidence domain, and LLM wiki context.
• Birmingham / West Midlands validation pages for Shared Care Record, Collaborative Shared Care Record DPIA, BCHC privacy notice, NRL references, and HL7 UK OIDs.

Found

• ICO guidance updated on 19 June 2026 says all DUAA data-protection provisions are now in force.
• ICO guidance now replaces GOV.UK factsheet-only treatment for complaints, lawful basis / recognised legitimate interests / purpose limitation, storage/access technologies, and parts of international transfers.
• Subject access, research, automated decision-making/profiling, IDTA/Addendum transfer material, and enforcement/code process updates still need tracking where final ICO guidance is pending.
• The NHS Standards Directory GP Connect / MESH / ITK3 dependency chain had grown too dense for the parent Standards Directory page.
• Birmingham / West Midlands public evidence is sufficient for a partial HealthShare shared-care-record deployment pack, but not for full DSIC foundation compliance or complete DUAA readiness.

Added / Changed

• Added source IDs SRC-219 through SRC-224 for current ICO DUAA regulator guidance and guidance-pipeline sources.
• Added evidence-matrix rows for the 19 June 2026 ICO status, topic-guidance replacement state, and the Birmingham / West Midlands DUAA worked evidence pack.
• Updated the DUAA / ICO Guidance Tracker in the Evidence Validation Queue.
• Added NHS Standards Directory GP Connect, MESH, and ITK3 and linked it from navigation, the parent Standards Directory map, the Standards and Interoperability overview, content map, source/evidence domain map, and LLM notes.
• Added a Birmingham / West Midlands worked example to DSIC HealthShare Compliance Map.

Open Questions

• What final ICO subject-access, research, automated decision-making/profiling, IDTA/Addendum transfer, and enforcement/code guidance changes should replace the remaining queue rows?
• Can a current Birmingham / West Midlands deployment pack provide final DSA/DPIA, DCB0129/DCB0160, supplier-responsibility, GP Connect/MESH/ITK3 onboarding, and architecture artefacts?
• Can NHS supplier-progress evidence be structurally captured for exact InterSystems HealthShare Access Record: Structured and IRIS for Health Send Document capability cells?

2026-06-19 - DUAA Crosswalk and Supplier Artefacts Pass

Searched

• Graphify source map, DUAA page, NHS Standards Directory map, DSIC HealthShare Compliance Map, Evidence Validation Queue, and official ICO guidance-planning page.

Found

• Existing source IDs were sufficient for this follow-up: DUAA section 121 / Schedule 15 remains anchored to SRC-217; named NHS Standards Directory surfaces remain anchored to SRC-183 through SRC-187; ICO topic guidance status remains anchored to SRC-218.
• The Standards Directory page had a DUAA row but not a named-entry crosswalk.
• The DSIC HealthShare page had a DUAA row but not a supplier artefact checklist.
• The Evidence Validation Queue had DUAA rows but not a topic-level ICO replacement tracker.

Added / Changed

• Added a DUAA section 121 / Schedule 15 crosswalk to the NHS Standards Directory and DHSC Standards Direction page.
• Added a DUAA supplier artefact checklist to the DSIC HealthShare Compliance Map.
• Added a DUAA / ICO Guidance Tracker to the Evidence Validation Queue.
• Added a DUAA page pointer to the new standards crosswalk and queue tracker.

Open Questions

• Which ICO DUAA topic guidance will be published first and should replace GOV.UK factsheet summaries?
• Will NHS England / DHSC publish explicit implementation notes for section 121 / Schedule 15 applicability to DSIC, GP Connect, DCB0129/DCB0160, or Standards Directory entries?
• Which real InterSystems customer artefact pack should be used to test the DUAA supplier checklist end to end?

2026-06-19 - Data (Use and Access) Act 2025 Pass

Searched

• Official UK Parliament Bill/stages pages for the Data (Use and Access) Bill / Act.
• GOV.UK Data (Use and Access) Act 2025 collection, commencement plan, data protection and privacy changes guidance, and factsheets.
• Legislation.gov.uk explanatory notes for policy/legal background and health/adult social care information standards.
• ICO guidance-planning page for DUAA-related regulator update status.
• Graphify source map, standards anchor pages, NHS England Digital Primary Care pages, source register, evidence matrix, evidence validation queue, source/evidence domain map, glossary, and LLM wiki notes.

Found

• The Data (Use and Access) Act 2025 was introduced in the House of Lords on 23 October 2024 and received Royal Assent on 19 June 2025.
• DUAA is being commenced in stages; the current GOV.UK plan includes digital verification services on statutory footing from 1 December 2025 and most Part 5 data protection/privacy provisions from 5 February 2026, with other measures staged.
• DUAA amends UK GDPR, DPA 2018, and PECR; it does not replace them.
• The strongest direct health-system point for this wiki is section 121 / Schedule 15: health and adult social care information standards in England can include IT and IT services and can apply to providers of IT, IT services, or information-processing services used or intended for health/adult social care in or in relation to England.
• DUAA is statutory context, not InterSystems product conformance, DSIC catalogue listing, GP Connect assurance, PRSB conformance, clinical-safety approval, or local information-governance approval.
• Callable multi-agent/sub-agent tooling was not exposed in this session, so the pass used separate source streams and a single consolidated integration.

Added / Changed

• Added Data (Use and Access) Act 2025 as a Standards and Interoperability module page.
• Added source IDs SRC-213 through SRC-218 for Parliament, GOV.UK, legislation.gov.uk explanatory notes, and ICO guidance-status material.
• Updated Standards and Interoperability, NHS Standards Directory map, NHS England Digital Primary Care, NHS England Digital Primary Care evidence domain, source/evidence domain map, evidence matrix, evidence validation queue, glossary, content map, LLM wiki index, LLM context map, research priorities, and MkDocs navigation.

Open Questions

• Which DUAA provisions are operationally in force for each InterSystems use case after later commencement regulations?
• What ICO topic guidance should supersede GOV.UK summary factsheets for subject access, automated decision-making, complaints, research, legitimate interests, international transfers, PECR, and enforcement?
• How will NHS England / DHSC apply DUAA section 121 / Schedule 15 to named standards, DSIC capabilities, supplier obligations, and customer deployment artefacts?

2026-06-19 - Footer Link CSS Regression Guard

Searched

• Selected follow-up from the footer-link highlight fix, Graphify source map, DESIGN.md, Project Ops Design, docs/assets/theme.css, presentation tests, and LLM maintenance notes.

Found

• Project Ops Design did not yet record the footer/chrome exclusion as a regression point.
• The test suite covered build-time presentation rules but did not cover CSS selector scope.

Added / Changed

• Added a Project Ops Design note that article link and self-reference highlights must stay scoped to .md-content .md-typeset so Material footer/chrome links are not highlighted.
• Added tests/test_theme_css.py to guard article-link and self-reference highlight selectors against broad .md-typeset targeting.

Open Questions

• None for this regression guard.

2026-06-19 - Footer Link Highlight Scope Fix

Searched

• Browser comment on the Material for MkDocs footer credit, Graphify source map, DESIGN.md, docs/assets/theme.css, presentation rules, presentation tests, LLM maintenance notes, and current rendered DSIC page.

Found

• The article-link highlight CSS was scoped to .md-typeset, and Material's footer metadata also uses .md-typeset.
• This made the generated Material for MkDocs footer credit receive the wiki's article-link highlight treatment.

Added / Changed

• Scoped article link and self-reference styling to .md-content .md-typeset, preserving article highlights while leaving footer and other Material chrome links to the theme defaults.
• Updated DESIGN.md and LLM maintenance notes to record that footer links are excluded from article-link highlighting.

Open Questions

• None for this presentation fix.

2026-06-19 - DSIC GP IT Futures Wording Correction

Searched

• Browser comment on the DSIC overview page, Graphify source map, DSIC overview page, DSIC procurement page, source register, evidence matrix, research priorities, and local wiki text for the flagged GP IT Futures wording.
• Current NHS England Digital DSIC page.

Found

• The flagged GP IT Futures wording appeared once in source Markdown, on the DSIC overview page.
• NHS England Digital describes the products and services developed by the GP IT Futures programme as having evolved into the Digital Services for Integrated Care model. The local source register and evidence matrix already used the safer evolved from GP IT Futures framing.

Added / Changed

• Replaced the ambiguous wording with source-aligned wording on the DSIC overview page.

Open Questions

• None for this wording correction.

2026-06-19 - Agent Contract and HealthShare Domain Pass

Searched

• Graphify source map, root AGENTS.md, Project Ops Agent Rules, source/evidence domain map, evidence matrix, evidence validation queue, HealthShare anchor page, DSIC anchor page, DSIC HealthShare Compliance Map, LLM wiki context map, LLM index, and research priorities.

Found

• The response and agent contract was durable in the LLM wiki but not yet promoted into root agent rules or the Project Ops Agent Rules page.
• HealthShare component evidence was large enough to justify a second source/evidence domain split because component taxonomy, PRSB/NHS standards evidence, AI Assistant boundaries, Birmingham / West Midlands deployment evidence, Programme CORTISONE evidence, and DSIC adjacency were spread across many pages.
• The DSIC and HealthShare anchor pages already kept the main boundary intact: HealthShare is strong shared-care/integration evidence, not proof of a complete DSIC GP foundation clinical system.

Added / Changed

• Promoted the knowledge-base operating model and What Next response contract into AGENTS.md and Project Ops Agent Rules.
• Added HealthShare Components Evidence Domain and wired it into MkDocs navigation, the Source and Evidence Domain Map, Evidence Matrix, LLM index, context map, and research priorities.
• Added DSIC and HealthShare anchor audit notes and moved unresolved HealthShare-backed DSIC role-split and component-deployment gaps into the Evidence Validation Queue.
• Hardened Graphify publication/freshness checking so volatile community numbering does not produce false stale-artifact failures.

Open Questions

• Should the next evidence-domain split cover Standards and Interoperability or UK NHS Examples?
• Can accessible HealthShare 2026.1 component documentation be obtained without relying on account-gated pages?
• Can a HealthShare-backed DSIC solution be evidenced with a concrete supplier-responsibility matrix and catalogue/capability record?

2026-06-19 - Knowledge-Base Operating Model Pass

Searched

• Current LLM wiki starter instruction, maintenance rules, context map, research log, source/evidence domain map, evidence matrix, validation queue, research-priority list, and Graphify source map.

Found

• The wiki already separates source register, evidence matrix, evidence validation queue, research log, synthesis pages, LLM operational notes, generated indexes, and Graphify outputs.
• The durable operating model needed a more explicit anchor-page register and clearer role discipline for To Do, Done, current synthesis, operational rules, source truth, and generated discovery aids.
• Existing research priorities mostly already behave as evidence and confidence gaps rather than final guidance requests.

Added / Changed

• Expanded the reusable starter instruction with the InterSystems-specific purpose, page-role model, anchor-page discipline, evidence/architecture discipline, and response contract.
• Added maintenance rules for the knowledge-base operating model, anchor-page discipline, evidence and terminology discipline, status discipline, and substantive-response format.
• Added an anchor-page register to the LLM context map and linked the LLM index to the maintenance and context-map contracts.

Open Questions

• Should additional anchor pages be promoted for Defence healthcare, Birmingham / West Midlands validation, or international TrakCare PHC once those domains receive another source pass?
• Should the response contract be added to project-level AGENTS.md as well as the LLM wiki if it is intended to govern all future local agents?
• Should source/evidence domain pages be added for Product and Service Taxonomy, HealthShare Components, Standards and Interoperability, UK NHS Evidence, and International TrakCare PHC?

2026-06-19 - NHS England Digital Primary Care Structure Pass

Searched

• Current Graphify source map, MkDocs navigation, DSIC pages, GP Connect pages, source register, evidence matrix, evidence queue, LLM wiki, and knowledge-base overview pages.

Found

• DSIC and GP Connect were still discoverable through separate navigation routes, which made the England-specific primary-care frame less explicit.
• The source register and evidence matrix remained usable as canonical registers, but the DSIC/GP Connect/NHS England source cluster had become large enough to justify a domain navigation layer.
• The DSIC capability-to-standard material was present in prose, but supplier due diligence needed a structured crosswalk.

Added / Changed

• Added NHS England Digital Primary Care as the parent page and moved DSIC and GP Connect under a new first-class MkDocs navigation section.
• Added DSIC Capability-to-Standard Crosswalk as a structured due-diligence table for GP system/service components, national services, InterSystems relevance, and proof required.
• Added Source and Evidence Domain Map plus the first domain page, NHS England Digital Primary Care Evidence Domain, while keeping sources.md and evidence-matrix.md as canonical registers.
• Updated overview, standards, DSIC, GP Connect, evidence, research-priority, validation-queue, and LLM wiki pages to point to the new structure.

Open Questions

• Which additional source/evidence domains merit their own pages after NHS England Digital Primary Care?
• Can exact DSIC Confluence capability-to-standard rows be captured in a structured export rather than a curated wiki crosswalk?
• Are any InterSystems or partner products visible in DSIC/Buying Catalogue entries by capability?

2026-06-19 - DSIC Digital Services for Integrated Care Pass

Searched

• Existing Graphify/source map, MkDocs navigation, UK NHS Evidence, GP Connect pages, HealthShare/Health Connect/IRIS/FHIR product pages, source register, evidence matrix, and LLM wiki notes.
• NHS England Digital and NHS England DSIC sources for Digital Services for Integrated Care, the primary care GP digital-services operating model, DSIC capabilities and standards, capabilities with interoperability relationships, GP software integration with national services, Buying Catalogue buyer guidance, clinical system migration guidance, Tech Innovation Framework, digital tools for general practice, and Digital Primary Care procurement.

Found

• DSIC is an NHS England digital primary-care procurement, capability, standards, assurance, migration, and Buying Catalogue environment. It should be treated as England-only in this wiki.
• DSIC is wider than GP Connect. GP Connect is one service/API and standards family inside the wider DSIC/NHS England primary-care environment.
• The public DSIC capability model supports a GP foundation reading around patient information maintenance, appointments, consultation, prescribing, referral, document, task, reporting, scanning, citizen/patient-facing services, personal health record, and unified care record contexts.
• DSIC capability compliance depends on national-service and standards dependencies including PDS, NHAIS, GP2GP, SCR, GP Connect, GPAD, GPES, MESH/MNS, eMED3, Yellow Card, EPS, e-RS, NHS login, ITK, NDO, NEMS, and related NHS England services.
• HealthShare, Health Connect, IRIS for Health, and FHIR Server are strong DSIC-aligned components for shared care, clinical viewing, identity, provider data, integration, FHIR, and analytics, but current public evidence does not prove HealthShare alone as a DSIC GP foundation system.

Added / Changed

• Added source IDs SRC-202 through SRC-212 for DSIC, the GP digital-services operating model, DSIC capabilities/standards, capability-to-standard relationships, GP software national-service integration, Buying Catalogue, clinical migration, Tech Innovation, digital tools, and Digital Primary Care procurement.
• Added five DSIC pages: overview, GP foundation capabilities, standards and national services, procurement/assurance/migration, and HealthShare compliance map.
• Added the DSIC section to MkDocs navigation under UK NHS Evidence.
• Updated UK NHS Evidence, NHS Connectivity and GP Connect, GP Connect Deep Dive, Standards and Interoperability, evidence matrix, evidence validation queue, research priorities, glossary, content map, knowledge-base overview, information-space, and LLM wiki notes.

Open Questions

• Are any InterSystems, HealthShare, Health Connect, IRIS for Health, or partner services listed in the current DSIC/Buying Catalogue capability catalogue?
• Can the DSIC capability-to-standard relationships be captured in a stable structured local crosswalk for procurement use?
• What exact DSIC capability scope would InterSystems claim for a HealthShare-backed solution: shared-care/UCR, GP Connect consumer, middleware, patient-facing service, analytics, or full GP foundation?
• Which current InterSystems technical documents map HealthShare/Health Connect/IRIS directly to PDS, GP Connect, MESH, ITK3, EPS, e-RS, NHS login, and other DSIC national services?

2026-06-15 - GP Connect and Spine Equivalents Pass

Searched

• Existing Graphify and KB references for GP Connect, Spine, Scotland, Wales, Northern Ireland, DHCW, encompass, CHI, and NHAIS.
• NHS England Digital pages for Spine, PDS, SCR, EPS, e-RS, SDS, and GP Connect.
• Scotland sources for Emergency Care Summary, Key Information Summary, CHI, National Digital Platform, Acute Medication Service / ePharmacy, and SCI Gateway.
• Wales sources for Welsh GP Record, Welsh Clinical Portal, Welsh Clinical Communications Gateway, NHS Wales App, National Data Resource / Care Data Repository, and WDS/PDS relationship.
• Northern Ireland sources for NIECR, encompass, EpicCare Link, My Care, Health and Care Number, Digital Identity Service, NHAIS, and ePharmacy.

Found

• No one-to-one devolved GP Connect clone was found. The safer model is a function-by-function comparison: GP record or summary access, clinical messaging/referrals, patient identity/demographics, prescribing, patient portal, and national platform/backbone.
• No one-to-one devolved NHS England Spine clone was found. Scotland, Wales, and Northern Ireland each have their own identifier, portal, prescribing, record-sharing, and platform routes.
• Scotland maps most closely to ECS/KIS, SCI Gateway, CHI, NDP, AMS/ePharmacy, and MyCare.scot.
• Wales maps most closely to Welsh GP Record, Welsh Clinical Portal, Welsh Clinical Communications Gateway, NHS Wales App, NDR/CDR, and WDS/PDS relationship.
• Northern Ireland maps most closely to NIECR, encompass, EpicCare Link, My Care, HCN/Digital Identity Service, NHAIS, and ePharmacy.

Added / Changed

• Added source IDs SRC-127 through SRC-147 for NHS England Spine services and devolved-nation functional equivalents.
• Added cross-UK comparison plus Scotland, Wales, and Northern Ireland connectivity equivalent pages.
• Reorganised the MkDocs sidebar: UK NHS Evidence now separates Connectivity and National Services, InterSystems by Nation, NHS Example Pages, and Birmingham / West Midlands validation; GP Connect Deep Dive now separates service/architecture, capabilities, and due diligence.
• Updated DESIGN.md to record the new navigation contract.

Open Questions

• Can deeper public technical architecture sources be found for ECS/KIS, SCI Gateway, WCP/WGPR/WCCG, NDR/CDR, NIECR transition, EpicCare Link, HCN/DIS, and ePharmacy?
• Do any future Scotland, Wales, or Northern Ireland roadmaps explicitly adopt GP Connect or Spine terminology?
• Is there any direct InterSystems evidence for these devolved national services beyond the separate Scotland/Wales/Northern Ireland InterSystems country pages?

2026-06-15 - Scotland, Wales, and Northern Ireland InterSystems Evidence Pass

Searched

• Existing Graphify and KB references for Scotland, Wales, Northern Ireland, TrakCare, LIMS, encompass, NHAIS, and GP Connect boundary claims.
• Current public sources for InterSystems offices/presence in Scotland, NHS Scotland TrakCare Patient Management System evidence, Welsh all-Wales LIMS / TrakCare Lab Enterprise evidence, and Northern Ireland InterSystems / HSCNI evidence.
• Public Health Scotland, NHS Shetland, DHCW, Sell2Wales, Find a Tender, Department of Health Northern Ireland, DHCNI, InterSystems, and Rhapsody sources.

Found

• Scotland has direct general InterSystems presence evidence through Edinburgh office pages, official Public Health Scotland TrakCare Patient Management System context, and NHS Shetland board-side TrakCare ED / Ensemble evidence.
• Wales evidence is strongest for all-Wales LIMS 2.0 / TrakCare Lab Enterprise through NHS Wales board material, Sell2Wales procurement, DHCW chronology, and vendor national-scope context.
• Northern Ireland direct InterSystems evidence is narrow: InterSystems Caché licensing for NHAIS applications used primarily for GP registrations. Current HSCNI care-record evidence remains encompass / EpicCare Link / My Care, with Epic and Rhapsody context rather than InterSystems TrakCare or HealthShare.
• No Scotland, Wales, or Northern Ireland source found in this pass supports projecting NHS England GP Connect claims outside England.

Added / Changed

• Added source IDs SRC-116 through SRC-126 for Scotland office/TrakCare evidence, Wales LIMS evidence, and Northern Ireland NHAIS/encompass boundary evidence.
• Added InterSystems in Scotland, InterSystems in Wales, and InterSystems in Northern Ireland pages under UK NHS Evidence.
• Updated NHS Connectivity and GP Connect, UK NHS Evidence, evidence matrix, validation queue, research priorities, glossary, content map, knowledge-base overview, information space, standards overview, TrakCare, and LLM wiki notes.

Open Questions

• Can NHS Scotland / NSS sources confirm current national integration-platform status beyond vendor and NHS Shetland evidence?
• Can DHCW publish or expose richer LIMS 2.0 implementation and interface detail after deployment?
• Is there any official HSCNI / BSO / eTendersNI evidence for InterSystems beyond NHAIS Caché licensing?

2026-06-15 - NHS Connectivity and GP Connect National Context Pass

Searched

• Existing Graphify and KB references for GP Connect, NHS England, Health Connect, HealthShare, TrakCare, FHIR, and UK NHS evidence.
• Current NHS England Digital GP Connect service, architecture, capability, supplier-progress, Send Document, Update Record, and Access Record material.
• Scottish Government digital-health and health/social-care data strategy sources.
• Digital Health and Care Wales FHIR, primary-care, and NHS Wales LIMS / TrakCare Lab Enterprise sources.
• Digital Health and Care Northern Ireland encompass, EpicCare Link, My Care, and primary-care scope sources.
• InterSystems Scotland and Wales public sources where official public-body evidence was unavailable or needed pairing.

Found

• GP Connect remains an NHS England service/API and messaging context in the current evidence set; it is not currently evidenced as a UK-wide NHS capability.
• NHS supplier-progress evidence still names InterSystems rows, but direct Python/BeautifulSoup table capture was blocked by the NHS site Cloudflare challenge; exact HealthShare Access Record: Structured cell mapping remains unresolved.
• Scotland sources support a separate national digital-health/common-standards reading; InterSystems evidence is TrakCare / Ensemble / hosted TrakCare oriented, not GP Connect evidence.
• Wales sources support a DHCW FHIR / National Data Resource, GP2GP, Welsh Clinical Communications Gateway, and all-Wales LIMS / TrakCare Lab Enterprise reading, not GP Connect evidence.
• Northern Ireland sources support an encompass / EpicCare Link / My Care reading; general practice and Primary Care are currently outside encompass scope, and no InterSystems-specific HSCNI evidence was found.

Added / Changed

• Added source IDs SRC-105 through SRC-115 for Scotland, Wales, and Northern Ireland national-context evidence.
• Added NHS Connectivity and GP Connect as a new synthesis page.
• Updated UK NHS Evidence, GP Connect Deep Dive, InterSystems GP Connect Evidence Boundary, Standards and Interoperability, content map, information space, product related links, glossary, evidence matrix, and LLM wiki notes.

Open Questions

• Can the NHS GP Connect supplier-progress page be captured structurally despite the Cloudflare challenge?
• Can NHS Scotland / board-side sources validate current TrakCare, Ensemble, or integrated-care-record connectivity beyond vendor evidence?
• Can richer DHCW technical sources confirm the relationship among FHIR, Care Data Repository, Welsh Clinical Portal, Welsh Clinical Communications Gateway, GP2GP, and LIMS 2.0?
• Will DHCNI later bring primary care into encompass scope, and is there any current InterSystems-specific Northern Ireland evidence?

2026-06-15 - General Follow-up Evidence Pass

Searched

• General Follow-up Evidence and Remaining Follow-up Evidence items across product, standards, GP Connect, HealthShare, FHIR, UK deployment, and TrakCare PHC pages.
• Current InterSystems cloud FHIR, FHIR Server, supported FHIR operations, FHIR security, Network Connect, Health Connect Cloud, HealthShare 2026.1, HealthShare AI Assistant sample, and NHS ITK documentation.
• Current NHS GP Connect supplier-progress material, NHS Solution Assurance compliance-catalogue route, and public searches for North West London ICS, West Midlands cancer/eMDT, MERIT, ROH EPR, and eConsult architecture updates.

Found

• FHIR Server cloud deployment, supported-operations/profile-validation, OAuth/security, Network Connect, and Health Connect Cloud documentation now support stronger technical boundaries for FHIR Services, FHIR Server, FHIR packages, Bulk FHIR Coordinator, and Health Connect.
• HealthShare 2026.1 documentation exists but is WRC-login gated; HealthShare AI Assistant has an official sample repository, but public material still does not resolve model, prompt-governance, clinical-safety, or UK deployment boundaries.
• The GP Connect supplier-progress page edited 5 June 2026 still names InterSystems rows; the 2026-06-15 recheck strengthens the cautious IRIS for Health (Middleware) Send Document (Send) v2.0.1 reading, while HealthShare Access Record: Structured still lacks safe exact cell mapping.
• Current IRIS for Health ITK documentation and the NHS compliance-catalogue route were found, but no public NHS catalogue row or certificate naming InterSystems was exposed.
• No stronger public source was found for North West London ICS official/customer validation, West Midlands Cancer Alliance or UHB HealthShare confirmation, post-31 March 2026 MERIT continuity, ROH go-live/outcomes, or current eConsult InterSystems architecture.

Added / Changed

• Added source IDs SRC-095 through SRC-104 for current FHIR/cloud, HealthShare, AI Assistant, ITK, and NHS compliance-catalogue boundaries.
• Updated the evidence matrix, validation queue, research priorities, product maps, standards pages, GP Connect pages, UK deployment pages, knowledge-base overview, information space, and LLM wiki context map.
• Reworded completed generic follow-up prompts as precise remaining gaps where searches were performed but public evidence was not found.
• Ordered the TrakCare PHC evidence table by directness and strength of PHC/community-health support.

Open Questions

• Can the NHS GP Connect supplier-progress table be captured structurally enough to map the HealthShare Access Record: Structured cells safely?
• Can official customer, procurement, programme, or trust sources close the remaining NW London, West Midlands cancer, MERIT, ROH, and eConsult gaps?
• Can account-gated HealthShare / AI Assistant documentation be reviewed to validate configuration, security, and clinical-governance claims?

2026-06-30 - TrakCare PHC Setting-Specific Section

Searched

• Current and historical web evidence for TrakCare in primary-healthcare, community-health, PHC-centre, outpatient, remote/community, and primary-health-clinic settings.
• Existing TrakCare PHC International Evidence, Source Register, Evidence Matrix, Evidence Validation Queue, Source / Evidence Domain Map, and Context Map.

Found

• Existing evidence already supported several distinct setting types: Australian community health, Chile APS referral/interconsultation workflow, DHAMAN PHC-centre/outpatient network context, Northern Territory remote/community-adjacent public-health infrastructure, and historical Qatar primary-health clinic pharmacy workflow.
• Additional provider-level evidence was found for Nexus Primary Health in Victoria: InterSystems and Healthcare IT News describe Nexus as a community healthcare / primary health provider using TrakCare as its healthcare information system and migrating it to an InterSystems cloud managed service in 2019.
• The stop/go rule does not justify a new page. The existing TrakCare PHC International Evidence module remains the right container.

Added / Changed

• Added a PHC Setting-Specific Reading section to the TrakCare PHC International Evidence module.
• Added SRC-277 for Nexus Primary Health and updated the TrakCare page, Evidence Matrix, Evidence Validation Queue, Source / Evidence Domain Map, and Context Map.

Open Questions

• Can current Nexus Primary Health material confirm live TrakCare status?
• Can a current Victorian Government/provider inventory validate provider-level scope for Victorian community-health TrakCare use?

2026-06-30 - Ask Wiki Cross-Country Evidence Guard

Searched

• Live and local Ask Wiki search-index retrieval for the Chile TrakCare prompt after the country-specific TrakCare PHC sections were deployed.
• Ask browser retrieval and Pages Function prompt code.

Found

• The live/static search index had the new Chile section, so the reported answer was not simply stale deployment.
• The browser snippetter anchored broad Evidence Map excerpts on the first matching generic token such as InterSystems or TrakCare, which could put the unrelated Gateway Health row at the start of an excerpt used for a Chile question.
• The Ask Function prompt did not explicitly forbid using one table row, country, organisation, or setting as evidence for another.

Added / Changed

• Updated the Ask browser snippetter to choose the densest query-token window and added tell to stop words.
• Hardened the Ask Function prompt so broad evidence-map excerpts must be treated as independent rows/sections and unrelated country/customer evidence must be ignored.
• Updated LLM Wiki maintenance notes for the retrieval and prompt boundary.

Open Questions

• After deployment, does the live Ask response for Chile avoid using Gateway Health / Australia evidence as support?

2026-06-30 - TrakCare PHC Answer Blocks and Chile Procurement Pass

Searched

• Rendered Ask Wiki search-index results for Gateway Health, Victoria, and DHAMAN TrakCare queries.
• Chile Mercado Publico, ChileCompra-derived search results, Transparentin, and official purchase-order pages for direct InterSystems Chile / TrakCare / HIS procurement scope.

Found

• Gateway Health, Victoria, and DHAMAN queries still retrieved broad pages or the flattened TrakCare PHC evidence-map row ahead of answer-shaped country sections.
• Official Mercado Publico purchase-order pages show direct Chile public-sector orders to INTERSYSTEMS CHILE LIMITADA: Servicio de Salud Chiloe bought INTERSYSTEMS TRAKCARE ENTERPRISE CHILE EDITION TIER III SaaS, and Hospital de Copiapo / Servicio de Salud Atacama bought HIS electronic clinical-record software subscription.
• Transparentin, as a procurement-data mirror over public ChileCompra data, reports a 2026 SSMS direct award to INTERSYSTEMS CHILE LIMITADA for secondary/tertiary electronic clinical-record software licensing, but the official Mercado Publico detail link still needs validation before relying on full contract terms.

Added / Changed

• Added country-specific answer blocks for Gateway Health, Victoria community health, and DHAMAN in TrakCare PHC International Evidence.
• Added SRC-276 for direct Chile InterSystems TrakCare / HIS procurement evidence and updated TrakCare, Evidence Matrix, Evidence Validation Queue, Source / Evidence Domain Map, and Context Map.
• Tightened the Chile boundary: direct Chile public-sector supplier evidence now exists, but it does not close Chile-wide deployment, named El Bosque APS live scope, or official SSMS detail-link validation.

Open Questions

• Can the official Mercado Publico detail page for SSMS direct award 1057499-220-TD26 / purchase order 1057499-31-FTD25 be retrieved and archived as the primary source?
• Can a formal Gateway Health publication confirm the 2026 community-solution go-live?
• Can current Victorian Government/provider and DHAMAN primary pages validate site-level scope?

2026-06-29 - Chile TrakCare Ask Wiki Correction Pass

Searched

• Current SSMS, El Bosque municipal, Hospital El Pino, Hospital Barros Luco Trudeau / Mercado Publico, and San Bernardo municipal-health sources for TrakCare, InterSystems, Rayen, SIDRA, and APS referral workflow evidence.

Found

• SSMS 2024 public-account material lists TrakCare as a data source and includes TrakCare/Rayen/API MINSAL integration items for 2025-2026.
• Hospital El Pino official pages provide current SSMS-network hospital context: InterSystems / TrakCare implementation discussion, a patient portal developed with InterSystems as electronic clinical-record platform provider, and 2025 TrakCare update/downtime references.
• Mercado Publico 2069-186-LP25 is an adjudicated 2025 Barros Luco Trudeau support / digital-strategy procurement that names hospitalised clinical-record work with TrakCare from InterSystems, but the award is for support personnel supplied by Layner SpA rather than a direct InterSystems contract.
• San Bernardo's 2025 municipal health plan describes Rayen-to-TrakCare / TrakCare-SIDRA referral integration in APS workflows, extending the SSMS APS referral-context picture beyond the older El Bosque source.
• The first public El Bosque municipal-site search did not find a current municipal page naming TrakCare, so named current El Bosque APS live status remains open.

Added / Changed

• Added an answer-shaped Chile / SSMS subsection to TrakCare PHC International Evidence so Ask Wiki can retrieve a clean Chile block rather than a flattened multi-country table row.
• Added SRC-272 through SRC-275 for SSMS public-account, Hospital El Pino, Mercado Publico / Barros Luco Trudeau, and San Bernardo municipal-health evidence.
• Updated TrakCare, the Context Map, Evidence Matrix, Evidence Validation Queue, and Source / Evidence Domain Map to distinguish Chile product-use / workflow evidence from Chile-wide deployment, current El Bosque live-status, and direct InterSystems award proof.

Open Questions

• Can a current SSMS or El Bosque municipal APS source confirm named live TrakCare scope for El Bosque?
• Can procurement, contract, or support records identify direct InterSystems contractual scope for SSMS-network TrakCare services?
• Can a complete APS site-by-site scope be established for TrakCare / TrakCare-SIDRA referral workflows across SSMS municipalities?

2026-06-15 - TrakCare PHC Follow-up Validation Pass

Searched

• Customer-side Gateway Health material for the 2026 TrakCare community-solution go-live, including Gateway Health site results, annual reports, and public executive/customer social posts.
• Current Chile SSMS / El Bosque APS TrakCare evidence, including SSMS network-design, referral, GES, and APS workflow documents.
• Current Qatar PHCC / Ministry of Public Health TrakCare evidence.
• Current Victoria community-health TrakCare status evidence beyond the historical vendor case study.
• Current DHAMAN primary-source site-scope material for PHC and hospital network context.

Found

• Gateway Health's CEO publicly described the InterSystems project as successful implementation of a new clinical information system designed around community health services; no formal Gateway Health website or annual-report go-live item was found.
• A Victorian Healthcare Association paper states that the majority of registered community health services in Victoria use TrakCare as a client-management system, strengthening the current-status boundary beyond the old vendor case study.
• Newer SSMS documents continue to reference TrakCare in APS / referral-management context, but they also document limitations such as limited TrakCare profiles in APS and parallel systems. They do not prove a named current El Bosque go-live state or Chile-wide APS deployment.
• Current DHAMAN pages confirm a 15-PHC / 3-hospital network context, but the official DHAMAN pages found in this pass do not name TrakCare.
• No current Qatar PHCC or Ministry of Public Health source naming TrakCare was found; Qatar should remain historical academic evidence only.

Added / Changed

• Added source IDs SRC-090 through SRC-094 for Gateway CEO customer-side corroboration, newer SSMS workflow evidence, Victoria community-health status, and DHAMAN current network scope.
• Updated the TrakCare PHC evidence map, evidence matrix, validation queue, research priorities, TrakCare page, products/services map, knowledge-base overview, information-space page, and LLM wiki context map.
• Replaced completed follow-up prompts with remaining precise gaps so the page no longer asks for evidence that has already been searched.

Open Questions

• Can a formal Gateway Health publication or annual report confirm the 2026 community-solution go-live?
• Can a current SSMS, El Bosque, or municipal APS source confirm live named scope and any extension across APS networks?
• Can a current DHAMAN primary page or implementation record name TrakCare directly?
• Is there any current Qatar PHCC or Ministry of Public Health source naming TrakCare?

2026-06-15 - TrakCare PHC Correction and Worldwide Reference Check

Searched

• Current public web results for TrakCare primary healthcare, community health, PHC, Gateway Health, Chile APS, Qatar primary-care clinics, DHAMAN, Victoria community health, and Northern Territory remote/community care.
• Existing TrakCare PHC International Evidence, source register, evidence matrix, validation queue, research priorities, and LLM wiki notes.

Found

• The previous country-market item was only a general market-ranking signal and did not meet the page boundary for PHC/community-health implementation evidence.
• Chile was the stronger fit for the user's intended PHC reference because SSMS / El Bosque APS evidence directly concerns primary-care / APS workflows.
• Additional worldwide comparators exist with boundaries: historical Victoria community-health deployment, and DHAMAN/Kuwait primary-healthcare-centre and outpatient-care evidence.
• Northern Territory remains useful only as public-health and remote/community-care adjacent evidence, not a standalone PHC module claim.

Added / Changed

• Removed the country-market item from the TrakCare PHC evidence map and supporting synthesis.
• Added source IDs SRC-087 through SRC-089 for Victoria community health and DHAMAN evidence.
• Updated the evidence matrix, validation queue, research priorities, TrakCare page, products/services map, knowledge-base overview, information-space page, and LLM wiki notes.

Open Questions

• Can Gateway Health, Victoria, Chile SSMS / APS, DHAMAN, and Qatar be revalidated with current customer-side or government primary sources for live scope and current status?

2026-06-15 - Verification Hardening and Project Ops Expansion

Searched

• Existing package scripts, GitHub Pages workflow, Project Ops pages, maintenance notes, presentation hook, and Graphify map.
• Current public evidence search results for the largest open validation gaps: GP Connect InterSystems supplier rows, North West London official/customer confirmation, West Midlands cancer/eMDT official confirmation, MERIT continuity, and Royal Orthopaedic Hospital EPR milestones.

Found

• The generated-index stale message still pointed maintainers to npm run kb:code-index even though npm run kb:update is now the standard regeneration path.
• npm run check did not exercise presentation-rule behavior, strict MkDocs, or Graphify freshness.
• The GitHub Pages workflow ran the shorter project check and strict MkDocs, but not the Graphify freshness gate.
• Project Ops wiki pages were bridge stubs rather than usable operational summaries.
• Current evidence searches did not close the major source gaps already tracked in the Evidence Validation Queue; the existing content queue remains the right source-work backlog.

Added / Changed

• Added npm run verify as the full validation gate.
• Added a local/CI-safe MkDocs strict-build wrapper.
• Added presentation-rule unit tests for source-ID cleanup, source-column removal, auto-linking boundaries, and product-name phrase wrapping.
• Updated GitHub Pages to run npm run verify.
• Expanded Project Ops pages for deployment, design, and agent handoff.
• Updated maintenance and LLM wiki notes to reflect the new verification flow.

Open Questions

• Whether future source-research passes should be handled as one focused evidence domain at a time, starting with GP Connect supplier-progress structural capture or North West London official/customer validation.

2026-06-14 - Graphify Wiki View Split and Cross-Link Edges

Searched

• Existing InterSystems Graphify assets, LLM wiki page, MkDocs navigation, and graphify-out/graph.json.
• Sibling ITIL and EPMA project Graphify wiki rendering patterns.
• Local Markdown links available to connect otherwise isolated Graphify document hub-and-spoke islands.

Found

• InterSystems had only a raw docs/assets/graphify/graph.html asset linked from docs/llm-wiki/graphify.md; it did not have wiki-embedded 2D or 3D Graphify pages.
• The sibling ITIL project renders graphify-2d.md and graphify-3d.md as iframe pages and publishes graph-3d.html.
• The InterSystems publisher named communities, but the same named data was not available in a 3D view.
• The graph contained many local Markdown links that can be represented as explicit links to edges to reduce disconnected hub-and-spoke islands without inferring unsupported relationships.

Added / Changed

• Added wiki pages for Graphify 2D and 3D views.
• Updated navigation to group Graphify under Graphify Views.
• Updated Graphify publishing to emit graph-3d.html and summary.json.
• Added source-backed Markdown-link edges to both the 2D and 3D graph views.
• Added the new generated Graphify assets to the freshness check contract.

Open Questions

• Whether future passes should add MkDocs navigation-derived edges as a separate edge type if inline Markdown links are still too sparse for some content clusters.

2026-06-13 - Sidebar, Graphify, Evidence Queue, and TrakCare PHC Pass

Searched

• Browser-rendered /knowledge-base/ sidebar metrics at page top and after scroll.
• Sibling project Graphify publisher implementation that resolves numeric communities to source-aware labels.
• International public evidence for TrakCare in PHC, community health, and remote/community-care adjacent settings, including Australia, Chile, Qatar, and Northern Territory.

Found

• The primary sidebar looked lower at page top because MkDocs Material's main-content top margin placed the sidebar 30px below its sticky after-scroll position.
• The sibling project names Graphify communities by dominant source file plus a representative node; this project previously left published communities as numeric labels.
• Gateway Health in Australia and SSMS / El Bosque APS in Chile are the strongest public PHC/community-health TrakCare evidence found in this pass.
• Northern Territory Acacia is strong official evidence for TrakCare-based public-health infrastructure reaching remote/community settings, but not a standalone PHC module claim.
• Qatar evidence is historical academic evidence from 2009.

Added / Changed

• Added desktop sidebar top correction so the page-top sidebar matches the sticky after-scroll position.
• Added evidence-status chip styling and a consolidated Evidence Validation Queue.
• Added TrakCare PHC International Evidence.
• Added source IDs SRC-079 through SRC-085.
• Updated TrakCare, Products and Services, Content Map, Knowledge Base, evidence matrix, research priorities, LLM wiki notes, Graphify docs, and navigation.
• Enhanced Graphify publishing to add named communities to committed browser assets.
• Changed Graphify cleanup to remove stale local graphify-out before regeneration and changed the freshness check to regenerate in a temporary repository copy so live browser assets are not removed during checks.

Open Questions

• Can a customer-side Gateway Health source confirm the June 2026 TrakCare community-solution go-live?
• Is the Chile SSMS / El Bosque APS TrakCare deployment still live, and did the scope expand?
• Is there a current Qatar PHCC source for TrakCare, or has the historical primary-care use been replaced?

2026-06-13 - GP Connect Due Diligence Navigation Split

Searched

• Existing Graphify structure, GP Connect capability pages, the Access Record Structured due-diligence page, navigation, module index, knowledge-base overview, and LLM wiki notes.

Found

• The sidebar exposed Access Record Structured Due Diligence as a single peer under GP Connect Deep Dive rather than as one item in a capability-aligned due-diligence section.
• The capability map already had the desired order: Access Record: HTML, Access Record: Structured, Access Document, Send Document, Update Record, and Patient Facing APIs.

Added / Changed

• Added a GP Connect Due Diligence parent section under GP Connect Deep Dive immediately after GP Connect Capability Map.
• Added due-diligence pages for all six GP Connect capability groups in the same order as the capability map.
• Moved the existing Access Record Structured due-diligence content to the new due-diligence file naming pattern and updated related links, navigation, module index, knowledge-base summaries, and LLM wiki notes.

Open Questions

• Whether future evidence passes should add deeper deployment-check templates under each due-diligence page for specific InterSystems products or named NHS deployments.

2026-06-13 - GP Connect Supplier Precision and UK Validation Pass

Searched

• Existing Graphify structure and the GP Connect, UK NHS evidence, Birmingham/West Midlands, Clinical Viewer, MERIT, North Tees, North West London, source-register, evidence-matrix, and LLM-wiki pages.
• NHS GP Connect supplier-progress material for InterSystems IRIS for Health (Middleware) and InterSytems Healthshare rows.
• Official/customer/procurement-style sources for North West London ICS, West Midlands cancer/eMDT, ROH, MERIT, and North Tees.
• Published DPIA/FOI/trust sources for H&W ICWR, Black Country MERIT, and North Tees TrakCare.

Found

• NHS supplier-progress material edited 5 June 2026 names InterSystems IRIS For Health (Middleware) and InterSytems Healthshare. Rendered-text column order supports a cautious IRIS for Health (Middleware) Send Document (Send) v2.0.1 reading; HealthShare Access Record: Structured version values remain unmapped to exact cells pending visual/structural confirmation.
• North West London gained AWS and 6B corroboration, but no official NHS/customer/procurement source naming the InterSystems component was found in this pass.
• North Tees gained stronger trust-side evidence for TrakCare reference-site and digital programme claims.
• MERIT gained Black Country Healthcare FOI evidence supporting InterSystems supplier/integration status as of 2023, but current post-31 March 2026 status remains open.
• The H&W ICWR DPIA strengthens the shared regional HealthShare/UHB-hosting/Clinical Viewer evidence trail for the Birmingham and West Midlands record architecture.
• No official UHB or West Midlands Cancer Alliance source naming InterSystems HealthShare for the cancer registry/eMDT claim was found in this pass.

Added / Changed

• Added source IDs SRC-073 through SRC-078.
• Added GP Connect InterSystems Supplier Progress.
• Updated GP Connect evidence boundary, UK NHS evidence pages, Birmingham and West Midlands validation pages, Clinical Viewer, source register, evidence matrix, research priorities, knowledge-base summaries, LLM wiki, navigation, and this log.

Open Questions

• Can the NHS supplier-progress table be captured visually or structurally enough to map the HealthShare Access Record: Structured row to exact capability/version cells?
• Which official North West London ICS or member-trust source names Health Connect Cloud or HealthShare Health Connect directly?
• Which UHB or West Midlands Cancer Alliance source names InterSystems HealthShare for cancer registry/eMDT?
• Did MERIT continue, change supplier, or get replaced after 31 March 2026?

2026-06-13 - Technical Product and HealthShare Component Expansion

Searched

• Existing Graphify structure, product/service modules, HealthShare, Clinical Viewer, GP Connect evidence boundary, UK NHS example pages, source register, evidence matrix, navigation, and LLM wiki notes.
• Official InterSystems technical documentation for FHIR Server, FHIR profiles/adaptations, Bulk FHIR Coordinator, OMOP, Health Connect transformations, SDA, and CDA.
• Official InterSystems product/component pages for EMPI, Provider Directory, Health Insight, Personal Community, Care Community, and HealthShare AI Assistant.
• NHS GP Connect supplier progress and external/customer-side sources for North West London, eConsult, North Tees, and West Midlands cancer/eMDT.

Found

• Technical documentation supports separate pages for FHIR Server, FHIR packages/profiles, Bulk FHIR Coordinator, OMOP, and SDA/CDA transformation.
• HealthShare is better represented as a suite with distinct component pages rather than a single undifferentiated page.
• The HealthShare AI Assistant launch release places the assistant inside Clinical Viewer and Navigation Application workflows, with RBAC/audit/source-traceability claims that need their own boundary note.
• NHS GP Connect supplier progress names InterSystems products in current row-level material, but exact capability mapping should not be inferred from flattened table text.
• eConsult and North Tees have customer-side validation sources; North West London and West Midlands cancer/eMDT have independent trade corroboration but still need official NHS/customer sources for the InterSystems component.

Added / Changed

• Added source IDs SRC-050 through SRC-072.
• Added technical pages for InterSystems FHIR Server, FHIR Packages and Profiles, Bulk FHIR Coordinator, InterSystems OMOP, and SDA/CDA Transformation.
• Added HealthShare component pages for EMPI, Provider Directory, Health Insight, Personal Community, Care Community, and HealthShare AI Assistant.
• Expanded Clinical Viewer with a Clinical Viewer / Navigation Application and AI Assistant subsection.
• Updated GP Connect evidence boundary, UK NHS example pages, products/services overview, module index, navigation, glossary, knowledge-base overview, information-space, evidence matrix, research priorities, LLM wiki, and this log.

Open Questions

• Which public source can structurally map the NHS supplier-progress InterSystems rows to exact GP Connect capability columns and product versions?
• Which official NHS/customer source can validate North West London Health Connect Cloud and West Midlands HealthShare cancer/eMDT beyond independent trade reporting?
• What current product documentation covers HealthShare AI Assistant clinical safety, prompts, model boundaries, RBAC, audit, and UK availability?

2026-06-13 - GP Connect Capability Expansion

Searched

• Local GP Connect capability map, GP Connect overview and architecture pages, source register, evidence matrix, LLM context map, and research priorities.
• Official NHS England Digital GP Connect service, developer specification, API catalogue, Send Document, and Update Record pages.

Found

• GP Connect Capability Map had only a summary table and did not give each capability its own explanation.
• Update Record needed stronger separation from Send Document because NHS England Digital describes it as a community-pharmacy structured update integration over MESH/ITK3/FHIR STU3, not a generic write-back capability.

Added / Changed

• Added dedicated subsections for Access Record: HTML, Access Record: Structured, Access Document, Send Document, Update Record, and Patient Facing APIs.
• Added NHS source-register rows for Access Record: HTML, Access Document, Send Document API, Send Document service page, and Update Record.
• Updated evidence matrix, research priorities, research log, and LLM context map.

Open Questions

• Which supplier progress records and InterSystems technical documents best map Health Connect or HealthShare to each GP Connect capability?

2026-06-13 - GP Connect Capability Subpage Split

Searched

• Local GP Connect capability map, GP Connect overview, module index, navigation, and Graphify structure.

Found

• The expanded GP Connect capability content was still on one page.
• Each capability needed to live as a dedicated subpage under the GP Connect Capability Map navigation branch.

Added / Changed

• Added dedicated capability pages for Access Record: HTML, Access Record: Structured Capability, Access Document, Send Document, Update Record, and Patient Facing APIs.
• Reduced GP Connect Capability Map back to a summary/routing page.
• Nested capability pages under GP Connect Capability Map in navigation and updated GP Connect overview/module index links.

Open Questions

• Whether any capability should later receive deeper subpages for supplier progress, API assurance, or InterSystems product mapping.

2026-06-13 - Standards Page Split

Searched

• Local standards and interoperability page, source register, evidence matrix, product pages, module index, knowledge-base overview, navigation, LLM context map, and research priorities.

Found

• Standards and Interoperability mixed product standards claims, GP Connect context, PRSB validation, NHS ITK claims, and HL7 UK OID evidence in one page.
• GP Connect already has a separate evidence cluster, so the standards page should route to it rather than restating its detailed content.

Added / Changed

• Split standards evidence into independent pages for InterSystems product standards positioning, NHS ITK accreditation, PRSB Core Information Standard evidence, and HL7 UK InterSystems OIDs.
• Reduced Standards and Interoperability to an overview and routing page.
• Updated module index, knowledge-base overview, LLM context map, research priorities, and navigation.

Open Questions

• Which current NHS or standards-body source best validates the InterSystems ITK accreditation claim?
• Is detailed PRSB validation scope for HealthShare publicly available beyond the conformance listing?

2026-06-13 - GP Connect Page Split

Searched

• Local GP Connect deep dive, standards and interoperability module, Health Connect product page, source register, evidence matrix, navigation, module index, knowledge-base index, LLM context map, and research priorities.

Found

• GP Connect Deep Dive combined NHS service definition, capability taxonomy, architecture patterns, Access Record Structured due diligence, and InterSystems-specific evidence boundaries in one page.
• Existing source IDs already support the split without adding new claims.

Added / Changed

• Added independent pages for GP Connect service context, capability map, architecture patterns, Access Record Structured due diligence, and InterSystems GP Connect evidence boundary.
• Reduced GP Connect Deep Dive to an overview and routing page.
• Updated Standards and Interoperability, Health Connect related links, navigation, module index, knowledge-base index, research priorities, research log, and LLM context map.

Open Questions

• Which public source can best validate current InterSystems GP Connect product support: InterSystems technical documentation, NHS supplier assurance records, or customer-side deployment evidence?

2026-06-13 - Birmingham Validation Page Split

Searched

• Local Birmingham / West Midlands validation page, UK NHS evidence pages, source register, evidence matrix, module index, navigation, LLM context map, and research priorities.

Found

• The Birmingham / West Midlands validation page still held multiple distinct evidence strands in one table.
• ROH, MERIT, and West Midlands cancer/eMDT already had independent pages, but the shared-care-record programme, DPIA, BCHC privacy notice, National Record Locator, and HL7 UK OID evidence did not.

Added / Changed

• Added independent validation pages for Birmingham and Solihull Shared Care Record, Collaborative Shared Care Record DPIA, BCHC Shared Care Record Privacy Notice, National Record Locator West Midlands references, and HL7 UK West Midlands OIDs.
• Converted Birmingham and West Midlands Validation into a regional routing/overview page with links to each evidence strand.
• Updated navigation, module index, knowledge-base index, research priorities, research log, and LLM context map.

Open Questions

• Which split validation strand should receive the next external-source update: current live status, contract/procurement, NRL implementation detail, or OID usage?

2026-06-13 - JJ Commit Workflow Rule

Searched

• Local Git/JJ status, JJ bookmark and commit help, root agent rules, and LLM maintenance notes.

Found

• The repository is colocated and Git-backed, with Git main currently mirrored as a JJ bookmark.
• jj commit records the working-copy change but does not automatically move bookmarks forward.
• Git remains the published source of truth, so file-changing development passes need both a JJ commit and clean Git/JJ verification.

Added / Changed

• Updated AGENTS.md to require every file-changing development pass to end with a JJ commit.
• Updated maintenance notes to include the JJ commit step and bookmark/Git clean-state verification.
• Recorded this workflow rule change in the research log.

Open Questions

• Whether a remote should be configured for main so push verification can be completed after each pass.

2026-06-13 - Revision Section Hidden

Searched

• Local navigation, design contract, revision pages, and LLM wiki maintenance notes.

Found

• Revision / Learning was still exposed as a primary navigation section even though this project does not need the learning workflow in the visible sidebar.
• MkDocs 1.6.1 supports not_in_nav, allowing retained scaffold pages to be intentionally omitted from navigation while keeping strict builds clean.

Added / Changed

• Removed the Revision / Learning navigation group from mkdocs.yml.
• Added not_in_nav for revision/**.
• Updated DESIGN.md, app-flow, maintenance notes, and research log to record that revision tooling is retained but hidden for this project.

Open Questions

• Whether the revision pages and assets should be deleted entirely if this project will never need browser-local learning tools.

2026-06-12 - Clinical Viewer Classification Pass

Searched

• Official InterSystems HealthShare documentation index, UK Unified Care Record product page, global Unified Care Record resource page, and local HealthShare, UCR, Health Connect, product-map, source, evidence, navigation, and LLM-wiki pages.

Found

• InterSystems documentation lists Clinical Viewer and Unified Care Record as separate included HealthShare products/components.
• InterSystems UCR material positions Clinical Viewer as the desktop/mobile, browser-accessible, or embedded route for users to view HealthShare longitudinal-record data.
• The local Health Connect page had no explicit boundary note separating integration-engine scope from Clinical Viewer presentation scope.

Added / Changed

• Added HealthShare Clinical Viewer as an independent product/service module page.
• Added source IDs SRC-034 and SRC-035.
• Updated HealthShare, Unified Care Record, Health Connect, Products and Services, source register, evidence matrix, glossary, navigation, module index, knowledge-base index, information-space, research priorities, research log, and LLM context notes.

Open Questions

• Which current Clinical Viewer technical documentation best establishes deployment architecture, SSO, embedded workflow behaviour, version differences, and specialty-view configuration?
• Which UK customer or programme sources show how Clinical Viewer is actually deployed in shared-care-record workflows?

2026-06-12 - Product and Service Page Split

Searched

• Local products and services module, navigation, module index, knowledge-base index, information-space page, and research priorities.

Found

• Products and Services mixed the portfolio table, product-family notes, and validation tasks in one page.
• The UK NHS evidence area had already moved to overview plus independent example pages, making the product area structurally inconsistent.

Added / Changed

• Split the official product/service rows into independent pages for IRIS for Health, FHIR Services, HealthShare, HealthShare Unified Care Record, Health Connect, TrakCare, and IntelliCare.
• Reduced Products and Services to a portfolio overview table with links and evidence-management notes.
• Updated navigation, module index, knowledge-base index, information-space, research priorities, research log, and LLM context map.

Open Questions

• Which product page should receive the first current technical-documentation validation pass?
• Whether HealthShare subproducts, TrakCare modules, IntelliCare AI features, FHIR Server, and OMOP should become separate second-level product pages.

2026-06-12 - UK NHS Example Page Split

Searched

• Local wiki structure and existing UK NHS evidence pages.

Found

• UK NHS Evidence was carrying both the official InterSystems example table and detailed analysis for multiple example rows.
• Only Birmingham / West Midlands validation had its own independent module page.

Added / Changed

• Split each official InterSystems UK example row into an independent module page.
• Reduced UK NHS Evidence to an overview and linked source table.
• Moved Birmingham / West Midlands validation into the UK NHS Evidence navigation group instead of leaving it as the only standalone example-style page.
• Updated module index, knowledge-base index, navigation, research log, and LLM context map.

Open Questions

• Whether each example page should later receive customer-side source validation, procurement evidence, and implementation timeline sections as new source passes are completed.

2026-06-12 - Birmingham, PRSB, and GP Connect Validation Pass

Searched

• NHS England Digital GP Connect service, developer, API, architecture, and National Record Locator pages.
• PRSB Core Information Standard and conformant partner register.
• Customer/local sources for Birmingham and West Midlands evidence, including ROH, Birmingham Community Healthcare, Birmingham and Solihull ICS, NHS Data Sharing DPIA material, BSMHFT FOI PDFs, and HL7 UK OID catalogue.

Found

• PRSB lists InterSystems Healthshare as Core Information Standard Version 2, Level 2 conformant, valid until 17.06.2028.
• ROH customer-side pages confirm InterSystems EPR partner selection on 23 October 2025 and contract signature on 13 March 2026.
• Birmingham Community Healthcare states BSOL CCC shared data is retained in the Shared Care Record until the InterSystems contract ends on 31 March 2029.
• NHS England Digital's National Record Locator roadmap names three InterSystems sites including Birmingham and Solihull ICB in 2024 International Patient Summary pointer activity.
• NHS England Digital GP Connect material defines product capabilities, SSP/MESH/API-platform patterns, and Access Record Structured security/testing/onboarding controls.
• Birmingham and Solihull ICS describes the Shared Care Record scope and participating organisations.
• A Collaborative Shared Care Record DPIA describes InterSystems as software/system supplier, cloud hosting, and processor with HealthShare architecture.
• BSMHFT FOI material supports MERIT supplier and contract trail.
• HL7 UK OID catalogue includes InterSystems HealthShare West Midlands and Birmingham/Solihull identifiers.

Added / Changed

• Added source IDs SRC-020 through SRC-033.
• Added docs/knowledge-base/modules/gp-connect-deep-dive.md.
• Added docs/knowledge-base/modules/birmingham-west-midlands-validation.md.
• Updated the evidence matrix, standards module, UK NHS evidence module, source rules, navigation, glossary, information-space, research priorities, context map, and revision cards.

Open Questions

• Is there a current public contract/procurement notice for the Collaborative Shared Care Record that should be linked alongside the DPIA?
• Did MERIT continue, change supplier, or get replaced after 31 March 2026?
• Can UHB or West Midlands Cancer Alliance source the HealthShare cancer registry/eMDT claim directly?
• Which InterSystems technical documentation best maps Health Connect and HealthShare to current GP Connect assurance requirements?

2026-06-12 - Official InterSystems UK Healthcare Pass

Searched

• Official InterSystems UK pages for healthcare products, services, NHS positioning, standards, and UK customer examples.
• Search scope intentionally limited to intersystems.com/uk.

Found

• InterSystems UK healthcare portfolio pages covering IRIS for Health, FHIR Services, HealthShare, Health Connect, Unified Care Record, TrakCare, and IntelliCare.
• NHS-facing positioning for HealthShare and TrakCare.
• Official InterSystems pages for North West London ICS, eConsult, and North Tees and Hartlepool NHS Foundation Trust.
• Official InterSystems Birmingham / West Midlands pages covering West Midlands cancer registry data sharing through HealthShare, MERIT mental-health crisis-care data sharing involving Birmingham and Solihull Mental Health NHS Foundation Trust, and The Royal Orthopaedic Hospital selecting InterSystems as EPR partner.
• Official InterSystems standards page with UK NHS ITK accreditation claim.
• Official InterSystems pages referencing GP Connect support in Health Connect and HealthShare certification.
• NHS England Digital GP Connect service page.

Not Found

• Independent NHS/customer validation sources; these were outside the requested official-website-only scope.
• Detailed technical documentation, licensing, service-level, hosting, or commercial terms.

Added / Changed

• Populated docs/sources.md with official InterSystems UK source IDs.
• Expanded docs/evidence-matrix.md with product, service, standards, and UK example claims.
• Built knowledge-base module pages for products/services, UK NHS evidence, and standards/interoperability.
• Updated glossary, comparative-analysis frame, information-space, and research priorities.
• Added Birmingham / West Midlands applications to the UK NHS evidence page and evidence matrix.
• Added GP Connect to the source register, evidence matrix, standards/interoperability page, glossary, information-space, and research priorities.

Open Questions

• Which NHS/customer sources should be added next to validate vendor-published outcome claims?
• Which product family should receive a deeper technical-due-diligence page first?
• Are Birmingham / West Midlands sources in scope for the next validation pass outside the InterSystems website?
• Should GP Connect implementation details be expanded into a dedicated page using NHS API specifications and InterSystems technical docs?

2026-06-12 - Scaffold Specialization

Searched

• Local scaffold files only.

Found

• The project was a generic MkDocs Material knowledge-wiki scaffold.
• Topic-specific InterSystems metadata and structure were not yet configured.

Not Found

• Source-backed InterSystems content has not been gathered yet.
• Git repository metadata, GitHub Pages workflow, and Graphify publication artifacts were not present at review time.

Added / Changed

• Specialized the scaffold for an InterSystems knowledge wiki.
• Added explicit evidence-gathering tasks while avoiding unsupported domain claims.

Open Questions

• Which official InterSystems source set should anchor the first research pass?