Skip to content

Context Map

The 1 October 2026 summary row separation gives pathology and imaging their own ordering rows, each directly above its results/reports row, and separates professional viewing from patient viewing. The summary now has 38 grouped comparison rows; the matrix already separates these functions and remains at 43. Existing Access labels, six paired Med IS markers and evidence limits are retained.

The 1 October 2026 Current Med IS summary alignment repeats the matrix’s six user-reported England service markers in the summary: PDS, ODS, EDIFACT pathology over MESH, e-RS, MESH documents and HSCN. A new Healthcare network row makes the summary 36 grouped rows; the matrix remains 43 unique functions. The combined referrals/documents cell holds two ticks, so six summary markers highlight five service cells. Access cells remain neutral, and network Access is Other because it denotes transport rather than a clinical API. Both legends retain 21 September 2026, including data-med-is-date="2026-09-21"; pathology excludes the FHIR pilot. Stable data-med-is keys, mapped England service cells and the common date are checked before review acknowledgement can be recorded. This repeats an existing user report without changing source-review dates or adding supplier-assurance claims.

The 1 October 2026 core-services reconciliation makes the reading order Executive Summary → Matrix → Landscape, followed by country detail. The summary remains independent and immediately before the matrix. Entry links, DSIC topic coverage and existing flag, authentication and opt-out interface qualifications are reconciled without resetting external-source review dates. Preserve 43 unique matrix functions, 35 grouped summary rows, six Med IS markers and existing Service/Access styling. The gate now covers the summary body and 11 source pages including the landscape, checks five topic tables, a DSIC explanation, cross-border entries and identical safeguarding repeats within each page, and still requires manual semantic review before explicit acknowledgement. This closes the selected reading-order/synchronisation correction, not all WN-007 editorial work; WN-008, WN-002 and WN-006 remain unselected options.

The 30 September 2026 safeguarding view repeats the existing child-protection and FGM rows under Safety, Prevention and Care Planning in both the summary and matrix. This is a focused reading of existing functions, not a new inventory or additional unique functions. Keep each repeated row aligned with its original and preserve GIRFEC’s framework scope and all national-interface limits.

The 30 September 2026 summary expansion follows the user’s six browser comments and subsequent column clarification: all five requested topic groups have executive sections, and each nation’s service description has a separate Access column to the right. System replaces the S2S label; Portal, Local, Files, Other, Planned and Unverified identify the other routes, with mixed values where described. England flag APIs, ScotAccount authentication and opt-out list checking have focused source-backed country detail. Keep production, deprecated and successor internal/beta routes distinct. The matrix’s authored content remains unchanged. The paired review gate also includes terminology, for ten dependencies; grouped accessible headers and neutral Access boxes are part of DESIGN and the maintenance contract.

The 30 September 2026 core-services summary adds an independent executive summary immediately before the matrix in navigation. The matrix’s 43 rows and six Med IS markers are preserved. Named S2S exchanges are distinct from portals, local configurations, unverified interfaces and planned services; EpicCare Link is a portal route, while NI EDT is a separate software feed. Summary/matrix/country/diagnostic/DSIC anchors were reconciled from existing evidence, not freshly researched nationwide. The paired maintenance rule and nine-page digest gate require explicit summary review after source changes; they do not monitor external sources or automatically certify content.

The 29 September 2026 safeguarding clarification separates child-protection information sharing from FGM indicators, bringing the matrix to 43 functions. GIRFEC is Scotland’s wider wellbeing/support framework; child’s plans, Child Protection Plans, local-authority registers and digital flags remain distinct. The Scotland subsection and glossary explain the relationship using SRC-652 and existing SRC-608; refreshed SRC-402 supports England’s separate CP-IS/FGM-IS functions. The matrix, country and evidence anchors were checked; no national Scottish NHS safeguarding API or supplier implementation is inferred. All six Med IS markers remain unchanged.

The 29 September 2026 suggestion reconciliation adds What Next: Suggestions and Decisions as the working record for unpursued, merged and completed follow-ups. Record and reconcile future response recommendations there before presenting them; use stable WN IDs and plain-English value/completion criteria. The GP API suggestion is parked pending a specific connection decision; registration/identity is a partly covered synthesis option. Urgent-care comparison is complete, and its two worked-example suggestions are merged. Evidence gaps remain in the queue, research priorities retain strategic scope, and completed passes remain in the log. Maintenance, priorities, queue and four-nation anchors were checked for overlap; no new supplier evidence or implementation claim is introduced.

The 29 September 2026 urgent-care follow-up expands the matrix from 37 to 42 functions without adding pages. Keep triage, clinical service discovery, referral delivery, receiving-service acceptance, appointment ownership and GP notification distinct. England has separate UEC DoS/e-RS DoS/DoHS routes; DoS Search clinical operations remain unavailable despite published schemas. S33 receiving, S93 pharmacy-referral roles and S107 pharmacy-directory scope are separate DSIC obligations. Scottish FNC local ownership, Welsh CPSS/ECNS and border referral routing, and NI locality-specific Phone First/OOH differ from shared APIs. Preserve planned navigation/directory/HSC 111 transitions and source conflicts. Sources SRC-630–651 plus refreshed SRC-169/206/380, canonical claims and queue hold provenance; the PRSB and adapter pages hold the reusable content/workflow boundaries. Country, landscape, England-primary-care and DSIC anchors were checked before and after the pass. All six existing Med IS markers remain unchanged.

The 29 September 2026 DSIC-lens extension expands the UK Core Services Matrix to 37 functions without adding pages. Read its grouped access/registration, prevention/safety and reporting/payment tables alongside the DSIC version/role crosswalk and nation anchors. Preserve all six 21 September user-reported Med IS markers; no added row acquires availability by inference. Keep DSIC effective dates, service onboarding, supplier rollout and devolved adoption separate. Actual reuse includes Welsh NHS login/PCRM/Spine, NI BSO → Wales FPPS, Scottish NHSCR movement links and shared terminology; UK Core is collaborative standards work, not automatic shared APIs. CHS supersedes Scottish CHSP/SIRS; PCIS follows SPIRE; NI GPIP/QOF supersedes PCAS. Welsh Audit+ and NI child-health/registration/screening cutovers retain explicit limits. Source Register SRC-593–629, claims and queue are canonical. Affected landscape, England-primary-care, terminology, devolved-comparison and country anchors were checked before and after the pass; no new evidence-domain layer or tool dependency.

The 25 September 2026 UK Clinical Platform Estate baseline adds five reader-facing pages and a single structured dataset, with 193 observations and 168 source URLs. Route shared-record supplier geography, hospital EPR/PAS and EpicCare Link, and diagnostic order/result/LIMS/RIS/PACS questions to their separate matrices and interactive map. England uses the current 36-ICB April 2026 baseline; programme source footprints can be narrower than successor ICBs. Map shading is evidence count, never exclusive supplier coverage or market share. Scottish TrakCare PMS and Welsh WPAS evidence is administration scope, not a complete national clinical EPR. Unknowns, phased plans, historical systems and replacements remain explicit. BSMHFT FOIs now independently support collaborative HealthShare supplier/three-area/contract facts, while signed schedules, exact March/April 2029 end and MERIT-specific continuity remain distinct. The affected anchors are UK NHS Evidence, UK Healthcare Connectivity Landscape, Diagnostic Results and Image Exchange, HealthShare, nation pages and the new estate hub; their links and claim boundaries were checked before and after this pass.

The wiki topic is InterSystems.

Current Domain

The UK Core Services Matrix and Executive Summary each carry the same six user-reported current Med IS service markers dated 21 September 2026: England PDS/NHS number, ODS, EDIFACT pathology results over MESH, e-RS, MESH document/message exchange and HSCN. Keep the stable marker keys and mapped England service cells aligned across both pages; summary Access cells remain neutral. Keep this operational annotation separate from the national-service source review. The pathology marker does not cover the separate FHIR reporting API pilot; unmarked services have no current Med IS status recorded by this annotation.

The UK NHS section is titled UK NHS Digital Connectivity and Interoperability Evidence. Its overview routes to the Core Services Executive Summary, detailed matrix and then the four-nation landscape before the supplier examples. Keep uk-nhs-evidence.md and the legacy #uk-nhs-evidence fragment stable; historical Research Log wording retains the old title through maintained auto-link aliases. Country-service names, source titles and supplier examples keep their specific wording.

The current focus is UK InterSystems healthcare products and services using official InterSystems UK website sources plus selected InterSystems technical documentation, NHS, PRSB, customer trust, local-programme, FOI, marketplace, independent trade, and standards validation sources.

The Home navigation now includes an Executive Summary page that frames the core exam question: how Health Connect and HealthShare can mediate DMICP / CORTISONE connectivity with NHS England against DSIC compliance, and how the same pattern can extend to Wales, Scotland, and Northern Ireland through nation-specific connectivity routes. The Executive Summary includes a DUAA decision boundary, a healthcare-recording legal alignment boundary, and direct proof-table links: DUAA section 121 / Schedule 15 supplies an England health/adult social care information-standard governance layer, while the Act also changes UK-wide data-protection law that sharpens named-standard supplier-role questions, not a DSIC or product compliance badge; healthcare-recording legal alignment is a general creation-and-maintenance model for recorded care, not a product, DSIC, or supplier-conformance label.

The Executive Summary Reference Architecture uses a compact Mermaid diagram with short labels. Keep detailed adapter names and proof requirements in the DSIC HealthShare Compliance Map, NHS England Digital Primary Care, Programme CORTISONE / UK Defence Healthcare, GP Connect and Spine Equivalents by Nation, and consolidated Evidence Matrix row rather than forcing long labels into the diagram. The Executive Summary interface-strategy table also has a compact GP2GP record-transfer row linked to the GP2GP Record Transfer page; keep supplier/customer proof gaps in the Evidence Validation Queue until a source appears.

The 2026-08-11 public DSIC refresh adds current official catalogue evidence for the route split used in the England adapter: S99 Access Record Structured is structured read, S101 Send Document is document delivery, and S102 Update Record is structured write-back. Keep their provider/consumer/sender/receiver roles and dependencies distinct. Treat the broader effective S102 contracting-vehicle surface separately from the narrower public evidence for assured community-pharmacy workflows, and do not infer a DMICP/CORTISONE or InterSystems implementation from either layer.

The 2026-09-08 full review adds IRIS for Health / Health Connect 2026.2 release and FHIR changes, public HealthShare support alerts, and vendor IntelliCare/TrakCare EU MDR statements. Keep software release, managed-service rollout, regulatory scope and customer remediation separate. The Clinical Viewer NRL advisory is an implementation signal without a named customer. Existing pages carry these changes; no new domain or request pack is justified.

The same review advances MyCare.scot from planned to initial national web/mobile availability, adds a Golden Jubilee TrakCare upgrade milestone and phased Welsh LIMS delivery, and records Cardiff and Vale CDR data flow plus Welsh EPS Spine/PDS reuse. The CORTISONE chronology includes the January 2026 TPP EHR award; Acacia scope is constrained by the August parliamentary inquiry. Supplier/programme facts still require separate interface and customer assurance evidence.

The 2026-09-09 direction is broader content review. IntelliCare/EMC follow-ups are parked in the existing queue; do not resume them as the default next pass. Home and the Knowledge Base now lead with product roles, documented use and standards explanations; the Executive Summary retains its specific Defence connectivity application. The comparator page has its first sourced external FHIR examples and makes no supplier ranking. Current priorities describe cross-domain evidence and synthesis gaps rather than supplier-response work.

The 2026-09-15 whole-UK connectivity review introduces a reader-facing UK Healthcare Connectivity Landscape master page, an England Spine/national-services drill-down and a combined diagnostics exchange page. The user explicitly chose the whole landscape with InterSystems evidence marked. This meets the repeated-traversal gate; it does not create a fourth evidence-domain register. Existing Scotland, Wales and NI pages retain their paths and add network, identity, clinical exchange and programme status. Keep NIDIS identity delivery separate from NHAIS registration/screening retirement, FHIR pathology pilot separate from rollout, and NIR limited beta use separate from completed IEP replacement. The Executive Summary remains the Defence application, with an early link to the whole-UK map.

The same-day NCRS correction makes the England page’s NCRS section the feature-map anchor: NCRS is the multi-service professional application, SCR one of its sources. Keep demographics, NRL documents, flags, vaccinations, birth and chargeable-status workflows distinct, with feature-level permissions and separate GP Connect/shared-record pilot status. The national-records page and whole-UK landscape link to that section rather than repeat the feature inventory.

The subsequent portal pass adds NCRS activity/role permissions and separate source-service and application-launch diagrams. Existing country pages now carry professional and patient portal feature/access breakdowns, linked from the master’s portal comparison. Keep national availability, local feature rollout, patient proxy access and professional permissions distinct; local access policies are not England activity codes. No extra page or evidence-domain layer is needed.

The subsequent terminology audit searched all 132 authored Markdown pages and reviewed 31 with SCR/NCRS terms. Use SCR for the national Summary Care Record, NCRS for the multi-service access application, and spell out regional Shared Care Record in synthesis prose. Keep accurate SCR-specific GP obligations and official source titles intact. The glossary now defines both records separately; the remaining checklist and regional-acronym ambiguities are corrected.

The 2026-09-16 content and narrative review is recorded as future editorial and presentation work, not implemented changes. Keep product understanding, healthcare connectivity, evidence/assurance and the Defence application as distinct reading arcs. The backlog covers clearer entry points, a HealthShare workflow pilot, chronology separation, table/link readability, reader-visible history/source preservation and a cross-nation portal journey. Maintenance records the preservation boundary: current linked content retains unique evidence, pushed Git commits retain page revisions, and JJ adds local recovery. No new page or evidence-domain layer is justified by this review.

The subsequent 2026-09-16 user request authorises the UK Core Services Matrix as a dedicated national-services-only comparison. It reduces repeated traversal and meets the structure gate independently of the earlier editorial backlog. Mark gaps explicitly; separate pathology/radiology requesting, reports and images; qualify pilots, rollouts and SCI Store's dated national origins. Northern Ireland HSC-wide services qualify, but local hospital products do not fill empty national cells. Organisation code repositories are distinct from system-endpoint directories. The country pages retain the evidence detail; the wider narrative redesign remains future work. The user then clarified that non-national delivery must be described, rather than left as an undifferentiated “Gap”. Keep named national counterparts, but state trust/laboratory, imaging-provider or Scottish health-board routes where evidenced. NI “regional” can mean HSC-wide. ECS/KIS through NIECR and EDT are now documented; current summary-feed completeness remains a separate uncertainty. Pathology requesting means clinician-to-laboratory ordering; NPEx is laboratory-to-laboratory exchange.

Anchor Pages

The 2026-09-15 interface review adds sourced screenshots within existing product/component pages and a screenshot navigation table in Products and Services. Keep full-size local originals, descriptive alt text, workflow captions and date/version boundaries. docs/assets/product-ui/provenance.json records source URLs and file hashes; it complements the Source Register rather than replacing it. Clinical Viewer is the illustrated UCR access surface, and the SDA/CDA page shows the shared DTL editor. Historical or demonstration screens are not deployment or outcome evidence. IntelliCare now appears explicitly in the Knowledge Base product summary. Missing current UI examples stay in the existing queue.

Check these pages before and after domain work when the change affects their model:

  • docs/knowledge-base/modules/products-and-services.md: product and service taxonomy anchor.
  • docs/executive-summary.md: answer-led Home-section anchor for the DMICP / CORTISONE / DSIC / four-nation connectivity thesis.
  • docs/knowledge-base/modules/healthshare.md: HealthShare family and component-boundary anchor.
  • docs/evidence-domains/healthshare-components.md: HealthShare source/evidence domain split and connected-care component evidence-routing anchor.
  • docs/evidence-domains/standards-interoperability.md: standards, governance, supplier-role, Standards Directory, GP Connect / MESH / ITK3, Update Record, DUAA, and implementation-proof routing anchor.
  • docs/knowledge-base/modules/terminology-code-management.md: Read Version 2 / CTV3 retirement, Read-to-SNOMED mapping, SNOMED CT UK Edition, dm+d, NHS Terminology Server, local terminology-service, and local-code / extension governance anchor.
  • docs/knowledge-base/modules/fhir-services.md: FHIR Services, FHIR Server, profiles/packages, Bulk FHIR Coordinator, OMOP, and SDA/CDA technical-depth anchor.
  • docs/knowledge-base/modules/standards-and-interoperability.md: standards, assurance, and interoperability framing anchor.
  • docs/knowledge-base/modules/data-use-and-access-act-2025.md: DUAA statutory data, privacy, digital identity, and England health/adult social care IT standards anchor.
  • docs/knowledge-base/modules/uk-healthcare-recording-legal-professional-position.md: UK healthcare-recording legal, professional, provider-governance, confidentiality, PECR, records-management, candour, and digital-standards assurance anchor; its legal alignment section is the general model for healthcare-record creation, maintenance, sharing, correction, retention, provenance, audit, and disposal.
  • docs/knowledge-base/modules/uk-nhs-evidence.md: UK NHS Digital Connectivity and Interoperability Evidence anchor for national-service routes and InterSystems supplier/deployment evidence.
  • docs/knowledge-base/modules/nhs-england-digital-primary-care.md: DSIC, GP Connect, digital primary-care procurement, standards, migration, and HealthShare compliance-map anchor.
  • docs/knowledge-base/modules/gp2gp-record-transfer.md: GP-practice transfer and four-nation boundary anchor.
  • docs/knowledge-base/modules/gp2gp-requesting-adapter.md: England requesting implementation anchor; distinguish GP Connect migration reuse, supplier clinical responsibilities, standards, software maturity and deployment proof.
  • docs/knowledge-base/modules/uk-healthcare-connectivity-landscape.md: whole-UK network, identity, exchange, record and programme-status anchor; routes to four countries and diagnostics, with InterSystems evidence separately labelled.
  • docs/knowledge-base/modules/uk-core-services-summary.md: first national-service reading with named System/Portal/Local/Unverified indicators; independent page immediately before the matrix, followed by the landscape. Reconcile all three through the review gate and manual semantic review.
  • docs/knowledge-base/modules/uk-core-services-matrix.md: grouped service counterpart map with DSIC relevance and actual cross-nation reuse; explicit delivery levels, evidence limits and request/result/image separation, linked to the country anchors.
  • docs/knowledge-base/modules/diagnostic-results-and-image-exchange.md: pathology/FHIR, NIR/IEP and cross-nation diagnostic exchange status/version anchor.
  • docs/knowledge-base/modules/devolved-connectivity-equivalents.md: Scotland, Wales, and Northern Ireland functional-equivalence anchor.
  • docs/source-evidence-domain-map.md: domain split and source/evidence navigation anchor.

If a new source changes one of these models, update the anchor, affected synthesis pages, sources.md, evidence-matrix.md, evidence-validation-queue.md, log.md, glossary entries, and LLM notes as needed in the same pass.

Follow-Up Discipline

Use the suggestion register before proposing follow-ups. Save the three concrete suggestions before publishing the response, reconcile overlap and retain completed/merged/retired decisions. The register is the selection layer; this context map and the evidence queue retain their existing roles.

Use What Next as a balanced work-selection mechanism, not as an automatic descent into the freshest unresolved thread. Unless the user asks to stay within one trail, recommendations should include one current-gap closure step, one anchor-model or synthesis step, and one breadth step that moves into an adjacent source/evidence domain. Each numbered step must be executable in the next pass; passive trigger conditions, "wait until a source appears" statements, and generic maintenance reminders should be recorded as boundaries in the summary, Evidence Validation Queue, Research Log, or affected synthesis page rather than occupying a What Next slot. Source and Evidence Domain Map, Evidence Validation Queue, and Context Map are background controls, not default recommendation text; mention them in What Next only when they contain the concrete artifact being changed or the next pass genuinely needs a recorded gate decision.

The current containment boundary includes IntelliCare/EMC pilot outcomes as well as West Midlands Medicus / HealthShare, DUAA / ICO guidance, North West London ICS procurement confirmation, eConsult current architecture proof, and the Executive Summary architecture-boundary proof gap: those remain live Evidence Validation Queue items, but they should not dominate follow-up passes until a new source, FOI response, regulator publication, assurance decision, or user instruction changes the evidence state. Use the Executive Summary architecture-boundary row as the single holding item for missing DMICP / CORTISONE, Health Connect, HealthShare, NHS England, and four-nation adapter implementation artefacts; the DSIC HealthShare Compliance Map translates that boundary into the England artefacts GP Connect, MESH, ITK3, PDS, ODS/SDS, DSA/DPIA, and DCB0129/DCB0160. Standards Directory and interoperability mapping is now a first-class source/evidence domain. Choose a new breadth target only when repeated traversal across module pages, sources.md, evidence-matrix.md, and the Evidence Validation Queue is creating friction for the same class of question. The reusable standards-conformance request pattern and breadth gate are now recorded for sibling-project reuse in docs/llm-wiki/maintenance.md and docs/llm-wiki/starter-instruction.md; apply them from this context map before adding new request packs, checklists, or domain pages. The architecture position is that request packs add value when they make an active assurance claim actionable, but they overcomplicate the knowledge base when they multiply without a decision, delivery, research, or assurance use case. UK NHS examples have been reassessed and do not yet need a separate evidence-domain page because the overview plus independent pages remain navigable. The 2026-06-20 devolved-nations traversal-cost check was superseded for reader-facing synthesis by the 2026-09-15 whole-UK request: the new master, England and diagnostics modules reduce that repeated traversal. No duplicate evidence-domain register or generic request pack is justified. UK Defence remains contained as a source domain; use it only where the Executive Summary exam question requires CORTISONE/DMICP interface evidence. Programme CORTISONE now carries a What DMICP Is section plus a compact DMICP interface-proof table for source interface, Health Connect mediation, HealthShare target role, and onward adapter artefacts. The 2025 Primary Dental Care procurement notice is only a dental replacement signal; do not expand that trail without procurement outcome evidence or a specific assurance need. International PHC remains contained.

Evidence Clusters

  1. Product portfolio: core product/service rows route to an existing page or dedicated subsection: IRIS for Health, FHIR Services, HealthShare, HealthShare Unified Care Record, HealthShare Clinical Viewer, Health Connect, TrakCare, TrakCare PHC International Evidence, IntelliCare, and the TrakCare Lab Enterprise subsection. Health Connect deployment choices, historical IRIS supplier status and CIS standard-versus-software version are reconciled across product and standards anchors.
  2. Technical product depth: FHIR Server, FHIR packages/profiles, Bulk FHIR Coordinator, OMOP, and SDA/CDA transformation now have independent pages backed by InterSystems technical documentation; the 2026-06-18 follow-up pass added FHIR cloud deployment, R4 profile-validation, OAuth/security, Network Connect, Cloud Services Portal, cloud-hosted service, and Health Connect Cloud boundaries.
  3. HealthShare component split: HealthShare overview routes to independent or dedicated component pages for UCR, Clinical Viewer, EMPI, Provider Directory, Health Insight, Personal Community, Care Community, HealthShare AI Assistant, and Health Connect. The HealthShare Components Evidence Domain now groups component taxonomy, connected-care architecture, standards relevance, deployment-boundary, AI Assistant, and DSIC-adjacent evidence, with a component assurance snapshot separating shared-record/viewing, identity/directory, analytics, patient-facing/care-management, integration/standards, and AI-adjacent presentation claims. HealthShare 2026.1 detail is account-gated and AI Assistant has public sample artefacts but not full governance evidence. Care Community has accessible patient-contribution care-plan mechanics and a vendor-published Lincolnshire signal; its customer-confirmation trail remains parked. July 2026 permission alerts now create a separate component/version/correction evidence trigger. The EMPI / Provider Directory identity-directory trail is parked pending direct artefacts: the wiki has stronger PDS/ODS national-service dependency evidence and one PDS integrated-products row for Intersystems HealthConnect 2020.1; the 2026-06-28 Provider Directory pass adds public data-stewardship, API, managed-service, and version-boundary evidence plus a legacy Coordinate My Care usage signal. The current UCP breadth check points to Better / Valida / London Care Record / UCP web portal / National Record Locator routes and does not name InterSystems or Provider Directory as the live platform, directory, or ODS/SDS owner. It still has no current public proof of EMPI or Provider Directory PDS/ODS/SDS implementation, stewardship, safety, or live deployment assurance. Reopen only for current product/version scope, PDS FHIR onboarding, ODS/SDS mapping, matching/stewardship, directory governance, synchronisation, audit, safety ownership, DSA/DPIA, DCB0129/DCB0160, or customer deployment artefacts.
  4. UK NHS digital connectivity and interoperability: EPR, connected care, interoperability, regional/national public-sector healthcare, and a dedicated cross-UK connectivity page that treats GP Connect as NHS England evidence while keeping Scotland, Wales, and Northern Ireland in their own source-backed digital-health contexts. Dedicated pages now track InterSystems in Scotland, Wales, and Northern Ireland.
  5. Standards and interoperability: FHIR, HL7 v2/v3, DICOM, IHE profiles, APIs, cloud-based data exchange, Network Connect, Cloud Services Portal, NHS England / DHSC standards-governance direction, Data (Use and Access) Act 2025 statutory context and staged commencement, ICO data-protection-provision status, a dedicated NHS Standards Directory relevance map covering FHIR/UK Core, GP Connect, MESH/ITK3, PDS/events, GP2GP/NHAIS, terminology, medicines, clinical safety, transfer-of-care, shared-record/life-stage content, imaging, and diagnostics, a GP Connect / MESH / ITK3 Standards Directory child page, a dedicated GP2GP Record Transfer page for England / Wales / Scotland / Northern Ireland record-transfer boundaries and InterSystems proof limits, a dedicated Terminology Code Management and Read-to-SNOMED page for Read Version 2 / CTV3 retirement, Read-to-SNOMED mapping, SNOMED CT UK Edition, dm+d, NHS Terminology Server, local terminology services, and local-code / extension governance, a Standards and Interoperability Evidence Domain routing layer and canonical reusable standards-conformance evidence request pattern, a PRSB Standards parent page for record-content standards families plus the NHS England CISS funding/stewardship caveat, a PRSB Core Information Standard child page for HealthShare conformance with PRSB-specific assurance scope rather than a duplicate generic request table, NHS ITK accreditation claims, HL7 UK OIDs, GP Connect service/capability/architecture subpages, dedicated GP Connect capability subpages, a mirrored GP Connect Due Diligence section in the same capability order, the September 2026 NHS supplier table retaining HealthShare’s Access Record: Structured Medications / Allergies / Immunisations / Uncategorised cells, with the June IRIS for Health (Middleware) Send Document v2.0.1 row now historical and current status unconfirmed, and separate pages for product standards positioning, DUAA, NHS Standards Directory, terminology, ITK, PRSB, OID, GP2GP, and cross-UK connectivity evidence. DMICP is now defined as the Armed Forces electronic patient record / Defence primary-healthcare source baseline, but its interface, coding/free-text/scanned-record, migration, and CORTISONE implementation proof remains in the Executive Summary architecture-boundary row. GP2GP remains a GP-practice transfer workflow; its England FHIR implementation reuses GP Connect migration operations but ordinary consumer status is not transfer assurance, shared-care-record access, or InterSystems implementation proof without product/version, supplier-role, onboarding, migration, safety, and customer-deployment artefacts. Read-to-SNOMED maps and terminology-service availability are standards/model evidence, not proof that a product or deployment has loaded specific releases, preserved source-code provenance, clinically validated local maps, or governed CodeSystem / ValueSet / ConceptMap resources. Update Record remains separate from Send Document and Access Record: its effective S102 catalogue surface is broader than the current public evidence for assured community-pharmacy workflows, and neither layer proves generic write-back, DMICP/CORTISONE applicability, MESH API support, or InterSystems implementation. NHS ITK is the current narrow implementation-proof slice: current product documentation and historical vendor claims are not enough without a current non-vendor certificate/register row, product/version scope, message/profile scope, assurance pack, and customer deployment artefacts. The 2026-06-20 current-source recheck found no current public NHS or standards-body InterSystems row in the rendered ITK catalogue or targeted public search; the Solution Assurance compliance catalogue excludes ITK Accreditation, so Healthshare-named rows there are not ITK proof. The ITK page now includes a focused evidence-request checklist and supplier/customer request template. The GP Connect InterSystems supplier-progress page translates NHS supplier-progress rows into product/version, validation-scope, exclusion, component-coverage, adjacent-standard, and deployment-artefact requests only when those rows are used for assurance. Health Connect, IRIS for Health, FHIR Services, HealthShare Unified Care Record, HealthShare Clinical Viewer, and HealthShare / PRSB CIS are high-risk product-map rows audited for product capability, presentation/access, AI-adjacent, or conformance facts versus NHS conformance, onboarding, programme/customer evidence, validation scope, profile support, SSO/RBAC/audit configuration, managed-service assurance, terminology governance, and customer deployment proof.
  6. DUAA: use Royal Assent date 19 June 2025 and staged commencement. ICO guidance now says all DUAA data-protection provisions are in force as of 19 June 2026. Treat section 121 / Schedule 15 as an England health/adult social care information-standard layer that can include IT and IT services and can apply to providers of IT, IT services, or information-processing services. Do not use DUAA as product conformance, DSIC catalogue, GP Connect assurance, PRSB conformance, or clinical-safety evidence. The maintained follow-up structures are the DUAA crosswalk on the NHS Standards Directory map, the GP Connect / MESH / ITK3 Standards Directory child page, the supplier artefact checklist and Birmingham / West Midlands worked evidence pack on the DSIC HealthShare Compliance Map, and the DUAA / ICO Guidance Tracker in the Evidence Validation Queue. ICO guidance now replaces GOV.UK factsheet-only treatment for complaints, lawful basis / recognised legitimate interests / purpose limitation, storage/access technologies, the main subject-access guide, and parts of international transfers; The 8 September tracker check closes Right of Access in brief as published. SARs Q&A remains drafting for autumn 2026; general research guidance remains redrafting despite its elapsed summer target; research anonymisation/pseudonymisation is in open consultation and ADM/profiling is drafting after consultation closed, both with winter 2026 final targets. Transfer/enforcement details retain earlier check dates. Keep stricter significant-automated-decision restrictions for special-category health data in the AI assurance boundary.
  7. Healthcare recording legal/professional position: use the UK healthcare-recording page as the anchor for UK GDPR, Data Protection Act 2018, PECR, Public Records Acts / archival governance, Access to Health Records Act 1990, Access to Health Records (Northern Ireland) Order 1993, Access to Medical Reports Act 1988, FOIA section 46 / personal-information boundaries, common law confidentiality, Caldicott, 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, DUAA 2025, professional record duties, provider governance, candour, devolved records-management codes, SNOMED CT, dm+d, Read / CTV3 migration, local terminology governance, PRSB/provenance, DSA/DPIA, DCB0129/DCB0160, and deployment proof packs. Treat these as separate evidence layers. Use its legal alignment section for the general healthcare-record creation and maintenance model before translating that model into DSIC, HealthShare, Health Connect, DMICP, patient-facing, analytics, or AI deployment evidence. Use its public-records and health-record access route section to keep preservation/archive duties, living-patient SARs, deceased-record access, FOI/EIR, and medical-report access separate. Use Healthcare Record Source Layers for source-layer acronyms and shorthand labels such as GMC, NMC, HCPC, GPhC, CQC, NICE, PRSB, DSA/DPIA, DCB0129/DCB0160, provider governance, professional duties, records-management code, and terminology code management. Keep Evidence Matrix and Evidence Validation Queue source-ID-first; add visible source-layer links there only when a row defines a reusable route or synthesis boundary. Do not use product capability, DSIC status, terminology-service availability, mapping artefacts, or a generic "NHS Act" label as proof of legal/professional record compliance.
  8. NHS England Digital Primary Care: this is now a first-class parent section for DSIC and GP Connect together. It covers digital primary-care procurement, capability, standards, assurance, migration, Buying Catalogue, Tech Innovation, Digital Primary Care replacement-framework context, GP Connect deep-dive material, and the DSIC capability-to-standard crosswalk. The HealthShare compliance map treats HealthShare as a strong shared-care/integration component but not a proven complete DSIC GP foundation system without capability, standards, national-service, catalogue, and deployment evidence; it now has an Executive Summary alignment table separating Health Connect mediation, HealthShare shared-care roles, GP Connect/MESH/ITK3/PDS/ODS/SDS proof, supplier-specific adapters, and regional/four-nation adapter boundaries. It also carries the England implementation artefact map for GP Connect, MESH, ITK3, PDS, ODS/SDS, DSA/DPIA, and DCB0129/DCB0160 so those proof gaps stay tied to the consolidated architecture boundary rather than spreading into duplicate queue trails. Its visible proof-table labels link to the source-layer map for DSA/DPIA, Caldicott/confidentiality, records management, information standards, and clinical safety where readers need explanatory routing. Its legal alignment section translates the general healthcare-record creation and maintenance model into a DSIC/HealthShare evidence test. Its DUAA boundary is England standards-governance only: ask which named NHS information standard applies to which supplier role and component, then require DSIC, GP Connect, PRSB, clinical-safety, information-governance, and deployment proof separately.
  9. Devolved connectivity comparison: GP Connect and DSIC remain England-specific in this evidence set; the health/adult social care information-standard provision in DUAA section 121 / Schedule 15 applies to England. Spine infrastructure is also used in Wales, including Welsh EPS; national governance boundaries must not be mistaken for infrastructure isolation. Use function-by-function comparisons for Scotland ECS/KIS/CHI/NDP/SCI/ePharmacy/MyCare.scot and GP record transfer, Wales WGPR/WCP/WCCG/GP2GP/NDR/WDS/NHS Wales App, and Northern Ireland NIECR/encompass/EpicCare Link/HCN/DIS/ePharmacy and GP IT Modernisation / GP2GP. GP Connect and Spine Equivalents by Nation now carries the cross-nation legal-record alignment note, compact four-nation adapter proof table, and Health Connect / HealthShare adapter-logic table for the Executive Summary architecture question. The GP2GP page carries the record-transfer boundary across England, Wales, Scotland, and Northern Ireland, and records that no current public source proves InterSystems GP2GP implementation in any of those routes. Legal-record alignment is UK-wide as a structure, but records-management, candour, national-service, IG, safety, and deployment proof remain nation-specific; do not extend England DSIC or DUAA section 121 / Schedule 15 health-standard applicability to another administration; assess the Act’s UK-wide data-protection changes separately. The three country connectivity pages still point back to the Source and Evidence Domain Map promotion trigger before any future devolved-domain split.
  10. UK examples: each official InterSystems UK example has an independent page: North West London ICS, eConsult, North Tees and Hartlepool, West Midlands cancer registry/eMDT, MERIT, and ROH EPR. eConsult, North Tees, MERIT, and ROH now have stronger customer, FOI, trust, vendor, public-signal, or procurement evidence. The 2026-06-21 pass added North West London acute-trust Health Connect / Trust Integration Engine technical context, but still found no public ICB/customer programme, board, procurement, or contract-award proof for an ICS-level Health Connect Cloud operating model. The same pass added current eConsult / Huma Health Connect Cloud vendor evidence and Digital Front Door public signals naming InterSystems & eConsult, but still found no Huma, NHS, or customer-approved technical architecture pack for the current product-version and safety/deployment boundary. West Midlands cancer UHB/WMCA validation, post-2026 MERIT continuity, and ROH go-live/outcomes also remain unresolved. A separate UK NHS examples evidence-domain page is not currently needed because the overview and independent pages still provide sufficient routing; reassess only when traversal across examples becomes repetitive enough to obscure evidence type and source boundaries.
  11. Birmingham / West Midlands validation: the regional validation overview now routes to independent pages for Birmingham and Solihull ICS Shared Care Record, Collaborative Shared Care Record DPIAs, BCHC InterSystems contract-end privacy statement, NHS NRL InterSystems references, HL7 UK OIDs, ROH customer-side EPR pages, BSMHFT and Black Country Healthcare MERIT FOI records, and West Midlands cancer/eMDT context. The DSIC HealthShare Compliance Map now carries a current public artefact-pack status table, route-specific Medicus / HealthShare / GP Connect architecture table, and Medicus / West Midlands deployment-evidence checklist covering DSA/DPIA, DCB0129/DCB0160 absence, supplier responsibilities, GP Connect/MESH/ITK3 onboarding gaps, WMCA DSCR support, current Medicus/HealthShare integration signal, and official national Medicus GP Connect status. The Evidence Validation Queue now carries a FOI/source-target pack. The model boundary is explicit: national NHS Medicus evidence does not confirm the local West Midlands HealthShare route or artefacts.
  12. International TrakCare PHC/community-health evidence: use the TrakCare PHC page's setting-specific section first when the question is about PHC settings. Gateway Health has customer-executive corroboration but still needs a formal Gateway publication; Nexus Primary Health adds provider-level historical primary-health/community-health evidence in Victoria; Victoria also has historical vendor evidence plus a contemporary Victorian Healthcare Association status signal; SSMS / El Bosque APS in Chile has direct SSMS APS / referral-workflow evidence, newer SSMS-network hospital, public-account, procurement, and municipal-health context, and direct InterSystems Chile public-procurement signals, but still needs named current El Bosque APS live-scope validation and should not be treated as Chile-wide deployment; the 2026 SSMS direct-award signal is mirror-derived and needs official Mercado Publico detail-link validation; DHAMAN has TrakCare-specific trade/press evidence plus current official PHC/hospital network context but no current primary page naming TrakCare; Northern Territory Acacia is public-health infrastructure with remote-care relevance; the August 2026 inquiry records FG0/FG1 delivered and later medicines/primary-care phases deferred, so it is not completed PHC deployment evidence; Qatar remains historical academic evidence only and current PHCC sources found in the 2026-06-18 pass do not support a present Qatar TrakCare claim.
  13. Source/evidence domain split: sources.md and evidence-matrix.md remain canonical. source-evidence-domain-map.md, evidence-domains/nhs-england-digital-primary-care.md, evidence-domains/healthshare-components.md, and evidence-domains/standards-interoperability.md provide domain navigation for large source clusters without duplicating every row.
  14. Graphify and optional OKF export boundary: wiki-embedded 2D and 3D views use the same enhanced graph.json, with source-derived community names plus explicit Markdown links to, source-reference, MkDocs navigation, filesystem, and file-reference edges connecting document and code islands. Open Knowledge Format compatibility is a potential portability layer over the canonical wiki, not a new evidence domain or replacement for Graphify. Prefer a generated okf-out/ sidecar before any in-place OKF profile, and keep generated OKF output out of MkDocs and Graphify ingestion unless the tooling rules are intentionally changed.

The 8 September 2026 DSIC recheck retains S99 v1.0.4, S101 v1.0.3 and S102 v1.0.3 effective standards, while the main GP Connect service now closes new-developer onboarding for Update Record, Send Document and Appointment Management. Existing consumer suppliers can still onboard end users. Effective catalogue standards do not establish supplier-entry feasibility. Medicus Access Document status differs between the current service page (FoT ready) and supplier table (development); retain both source-specific statements.

The same-day IntelliCare follow-up adds customer-side EMC implementation evidence, Medcare UAE and King's Jeddah adoption agreements, and RedSalud transition evidence. Route through IntelliCare’s named-deployment table; Middle East clinical go-live remains unconfirmed. Preserve the distinction between adoption, rollout and enabled AI features, and do not relabel the TrakCare installed base as IntelliCare (SRC-337 to SRC-340).

The 9 September IntelliCare pass adds a functional AI-to-TrakCare workflow map and an EMC outcome-provenance table. Distinguish configuration continuity from verified upgrade compatibility, draft/review from executed actions, implementation from independent effects, and earlier TrakCare completeness/rollout claims from IntelliCare usability examples. The study-result gap stays in the existing queue (SRC-341 to SRC-347).

The 25 September 2026 Requesting Adapter pass adds a dedicated implementation synthesis and SRC-427 to SRC-442. Route technical questions there instead of treating GP2GP and GP Connect as independent stacks. Keep documentary status, implementation code and deployed acceptance distinct; specific source conflicts and unavailable runtime details are parked in the validation queue.

For read-only access and “pull registration” questions, use the Requesting Adapter's dedicated section: the receiving GP system owns the permanent-registration/PDS update before a new transfer; PDS lookup is separate from changing registration. GP Connect Access Record: HTML supports viewing at the existing registered practice. Neither the adapter's full-record parameter nor the HTML view proves complete cross-NHS coverage or availability of every original attachment.

For technical feasibility, apply S94 Step 10: the sender checks PDS and returns NACK 19 if the requester is not the current registered GP. Separating the adapter call from the PDS write does not remove this protocol check. Existing registered-requester retries/resends are distinct from third-party viewing; do not claim live supplier behaviour was tested.

Confidence

Product-positioning claims from official InterSystems product pages are high-confidence vendor claims. Technical documentation is high-confidence for documented product mechanics, not for customer deployment. Customer outcome and adoption claims from vendor success stories/news are moderate until externally validated. Birmingham / West Midlands now has stronger external validation for supplier existence, regional architecture, standards identifiers, programme scope, and some contract milestones, but current operational outcomes still require direct programme evidence.

For UK nations, GP Connect remains England-specific in the current evidence, while the Spine service explicitly covers England, Wales and the Isle of Man. Welsh EPS is a confirmed infrastructure-sharing example. Scotland evidence is grounded in Scottish Government / COSLA digital-health and data-standards sources plus InterSystems Edinburgh office, Public Health Scotland TrakCare Patient Management System, NHS Shetland TrakCare ED / Ensemble, and vendor Scotland evidence. TrakCare PMS and TrakCare ED are source/local system labels for TrakCare in specific patient-management and emergency-department settings, not separate products or national services. Wales evidence is grounded in DHCW FHIR, primary-care, and all-Wales LIMS / TrakCare Lab Enterprise board/procurement evidence. Northern Ireland evidence is grounded in the narrow Caché / NHAIS licensing source plus DHCNI encompass / EpicCare Link / My Care and Department of Health / Rhapsody boundary evidence. The devolved connectivity pages compare similar national-service functions; GP Connect scope and InterSystems supplier claims remain separate from national-service and shared-infrastructure evidence.