Skip to content

Research Log

2026-06-25 - OKF Compatibility Boundary

Changed

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.

Changed

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.

Changed

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

Changed

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.

Changed

Changed

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.

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

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.

Changed

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

Changed

2026-06-22 - DUAA Executive Decision Boundary

Changed

Changed

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

Changed

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Open Questions

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

Searched

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

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

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

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

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

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

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

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

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

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?

Searched

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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?

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.

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

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

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

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-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.

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

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

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

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

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

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

Found

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

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?