Source and Evidence Domain Map

This page splits the large source register and evidence matrix into working domains. It does not replace Sources or Evidence Matrix, which remain the canonical source-ID and claim registers.

Use this page to decide which domain page or evidence cluster to read first.

Domain Index

Domain	Core pages	Evidence handling
Product portfolio and InterSystems product documentation	Products and Services, HealthShare, FHIR Services, InterSystems Standards Product Map	Vendor product positioning and technical documentation. Strong for product taxonomy and documented mechanics, not customer deployment.
HealthShare components and connected-care architecture	HealthShare, DSIC HealthShare Compliance Map, HealthShare Components Evidence Domain	HealthShare component taxonomy, connected-care deployment context, PRSB/NHS standards relevance, AI Assistant boundary, DUAA/ICO supplier artefact checks, Birmingham / West Midlands artefact-pack status, current Medicus integration signal, official national Medicus GP Connect context, Care Community integration evidence, PDS/ODS identity-directory dependency evidence, and DSIC adjacency. Keep product family, component, customer deployment, and supplier-assurance claims separate.
NHS England Digital Primary Care	NHS England Digital Primary Care, DSIC Digital Services for Integrated Care, GP Connect Deep Dive	DSIC, GP Connect, standards-directory, GP software, Buying Catalogue, migration, national-service evidence, PDS/ODS identity and organisation-data dependencies, DUAA subject-access guidance, and Birmingham / West Midlands GP Connect / Medicus adjacency. Keep service definition separate from InterSystems implementation.
UK NHS examples and Birmingham / West Midlands validation	UK NHS Evidence, Birmingham and West Midlands Validation	Mix of vendor, customer, procurement, FOI, DPIA, local-programme, social-care support, official national Medicus GP Connect context, source-target routes, trade/vendor integration evidence, ROH adjacent EPR planning evidence, North West London acute-trust Health Connect recruitment evidence, and current eConsult/Huma HCC / Digital Front Door public signals. Check source type before using outcome, architecture, procurement, or assurance claims.
Devolved UK nations	GP Connect and Spine Equivalents by Nation, InterSystems in Scotland, InterSystems in Wales, InterSystems in Northern Ireland	Scotland, Wales, and Northern Ireland use their own national digital-health routes. Compare by function, not by GP Connect/DSIC label.
Standards bodies, statutory data layer, and governance	Standards and Interoperability, Data (Use and Access) Act 2025, UK Healthcare Recording Legal and Professional Position, Healthcare Record Source Layers, PRSB Standards, NHS Standards Directory and DHSC Standards Direction, NHS Standards Directory GP Connect, MESH, and ITK3, Standards and Interoperability Evidence Domain	Standards-surface, statutory data/IT standards context, healthcare-recording legal/professional position, source-layer routing, UK GDPR, DPA 2018, PECR, DSA/DPIA, confidentiality, Caldicott, section 251, records management, public records, access-route separation, candour, clinical safety DCB0129/DCB0160, conformance, PDS/ODS implementation dependencies, reusable conformance-request pattern, ICO guidance status including subject access, supplier-role boundaries, Update Record separation, and governance evidence. Do not convert standards presence, statutory context, DUAA commencement, regulator guidance, professional-record duties, public-records/access-route context, DSA/DPIA, DCB0129/DCB0160, PDS/ODS adjacency, or MESH/ITK3 adjacency into supplier implementation proof.
UK Defence healthcare	Programme CORTISONE / UK Defence Healthcare	Contained NHS-adjacent public-sector healthcare evidence including DMICP baseline, CORTISONE programme intent, InterSystems IP/EMPI licence evidence, and Defence/NHS interface context. Do not treat it as NHS England DSIC/GP Connect evidence or as a default breadth target; use it for the Executive Summary exam question only with explicit interface-proof boundaries.
International PHC and community-health evidence	TrakCare PHC International Evidence	International examples for TrakCare PHC/community-health patterns. Do not project into UK DSIC or NHS deployment claims.
RAG and project tooling	LLM Wiki, Graphify	Operational knowledge, generated indexes, graph views, and optional interchange bundles. These are navigation, discovery, or portability layers, not source evidence. Regenerate with `npm run kb:update` after docs/workflow changes.

Domain Pages

Additional domain pages should be added only when they reduce repeated traversal of the canonical registers. Do not duplicate every row from sources.md or evidence-matrix.md; summarize the domain and link back to the canonical evidence.

OKF Compatibility Gate

Open Knowledge Format (OKF) compatibility belongs under RAG and project tooling unless a future pass proves that it changes the source/evidence model. It can be useful as an interoperability contract: typed page metadata, portable concept IDs, agent traversal hints, validation checks, and a reusable export surface for sibling projects.

The current decision is non-destructive: prefer a generated sidecar bundle such as okf-out/intersystems-wiki/ over an in-place conversion. Keep docs/ canonical. Do not place generated OKF output where MkDocs, generated indexes, or Graphify will treat it as new project evidence unless that ingestion behavior is deliberately changed and verified.

An in-place OKF profile is possible because the Markdown file count is small, but it needs a separate stop/go decision. The risk is semantic churn: OKF gives reserved meaning to index.md and log.md, while this wiki already uses those filenames for MkDocs indexes, home/module entry points, and the Research Log. Before converting in place, prototype representative files, map local page roles to OKF type values, then run strict MkDocs, generated-index, and Graphify checks.

Next Domain Selection

The Standards Directory and interoperability mapping breadth domain has now been promoted into a dedicated evidence-domain page. HealthShare Components, NHS England Digital Primary Care, and Standards and Interoperability are the current first-class domain pages.

Use the standards domain as a routing layer for named standards, source-layer labels, supplier-role questions, reusable conformance requests, and product/deployment proof boundaries. The first narrow implementation-proof slice is NHS ITK because it has a clear current evidence boundary: vendor and product-documentation evidence exists, but the 2026-06-20 current-source recheck still found no current public non-vendor certificate/register row or customer deployment proof for a named InterSystems product/version.

Structure stop/go rule: do not add a new page, checklist, request pack, or evidence-domain layer unless it reduces repeated traversal or turns an active assurance claim into a concrete evidence request. If the issue is only an unresolved source, a single supplier response target, or a generic concern, keep it in the existing module or Evidence Validation Queue and link to the reusable standards-conformance pattern.

UK NHS examples were reassessed after the standards-domain pass. Do not create a UK NHS examples evidence-domain page yet: the overview plus independent example pages still provide sufficient routing. Reassess only if the canonical registers or example pages become difficult to traverse across North West London, eConsult, North Tees, West Midlands, MERIT, ROH, Scotland, Wales, and Northern Ireland evidence. Keep Defence contained unless a new primary source appears.

The 2026-06-21 breadth rotations used this rule to add depth to existing UK NHS example pages rather than creating a new evidence-domain page. ROH gained adjacent EPR planning evidence. North West London gained acute-trust Health Connect / TIE technical context but not ICB procurement proof. eConsult gained current InterSystems/Huma HCC and Digital Front Door public-signal evidence but not formal Huma/NHS architecture proof.

Keep West Midlands FOI/source-target work and DUAA / ICO publication tracking in the Evidence Validation Queue until new evidence arrives or a scheduled recheck is needed. The 2026-06-21 traversal-friction check does not justify a new domain page now. Devolved nations remain the leading future candidate only if traversal pressure grows because Scotland, Wales, and Northern Ireland already have service-equivalence and InterSystems-by-nation pages. UK Defence is contained unless new evidence appears; international PHC remains contained in a single module plus source/evidence rows.

2026-06-20 Breadth Reassessment

No new evidence-domain page is justified in this pass. Choose the next breadth target only when the same class of question repeatedly requires traversal across multiple module pages, sources.md, evidence-matrix.md, and the Evidence Validation Queue. If the issue is a single unresolved artefact, keep it in the existing module or queue instead of promoting a new domain.

Candidate	Current traversal	Decision
Standards implementation proof	Already has Standards and Interoperability Evidence Domain, product-map audits, ITK evidence request material, PRSB CIS page, NHS Standards Directory map, and GP Connect / MESH / ITK3 child page.	Continue high-risk product-map row audits and implementation-proof slices inside the existing domain; do not create another standards domain page.
Devolved UK nations	Parent service-equivalence page, three country connectivity pages, three InterSystems-by-nation pages, and canonical register rows are still navigable.	Still the leading future breadth candidate, but no promotion until repeated cross-nation questions require all layers plus `sources.md` and `evidence-matrix.md`.
UK NHS examples	Overview plus independent example pages remain enough for North West London, eConsult, North Tees, West Midlands, MERIT, ROH, Scotland, Wales, and Northern Ireland references.	No new page. Reassess only if example/source-type traversal becomes repetitive.
UK Defence healthcare	Single Programme CORTISONE / UK Defence Healthcare module plus source/evidence rows, now including a DMICP baseline source for the Executive Summary question.	Contained. Do not create a domain page or use as a default next step. Use the existing CORTISONE page and validation-queue row when the exam question requires DMICP/CORTISONE interface proof.
International PHC	Single TrakCare PHC international module plus source/evidence rows.	No new page. Add depth to the existing module first if new customer/government evidence appears.

2026-06-21 Traversal-Friction Check

No new evidence-domain page is justified for the current generic-conformance pass. The GP Connect supplier-progress claim is an implementation-proof slice inside the existing Standards and Interoperability Evidence Domain, not a new source/evidence domain.

Candidate	Current traversal	Decision
GP Connect supplier-progress evidence requests	Evidence Validation Queue, GP Connect InterSystems Supplier Progress, InterSystems GP Connect Evidence Boundary, Standards and Interoperability Evidence Domain, Evidence Matrix, and Source Register.	Keep inside existing GP Connect and standards pages. The new request pack closes the assurance-pattern gap without needing another domain page.
PRSB CIS checklist collapse	PRSB Core Information Standard, Standards and Interoperability Evidence Domain, Evidence Validation Queue, Evidence Matrix, and Source Register.	Collapsed the duplicate generic request table; PRSB now keeps PRSB-specific assurance scope and relies on the canonical standards-domain pattern. Do not create another checklist or request-pack page.
HealthShare Care Community implementation gap	Existing Care Community module, HealthShare Components Evidence Domain, Evidence Matrix, Source Register, and Evidence Validation Queue.	No new page, request pack, checklist, or domain layer. Keep current technical-documentation and customer-deployment gaps in the existing module and HealthShare components queue until a new source or assurance decision appears.
Sibling-project reusable assurance mechanics	Context Map, LLM Wiki Maintenance, Starter Instruction, Standards and Interoperability Evidence Domain, and Source and Evidence Domain Map.	Operational note only. Reuse the pattern across projects, but do not create a project-agnostic evidence domain or duplicate request packs inside this wiki.
Devolved nations, UK NHS examples, international PHC	Existing 2026-06-20 checks remain valid: each area is navigable through current module pages and canonical registers.	No promotion. Reassess only when the same cross-page question repeatedly forces traversal across modules, `sources.md`, `evidence-matrix.md`, and the queue.

Devolved Nations Traversal-Cost Check

Light check completed 2026-06-20. Do not create a Devolved UK Nations evidence-domain page yet.

Slice checked	Current routing	Traversal cost	Decision
Cross-nation service equivalence	GP Connect and Spine Equivalents by Nation, plus Scotland, Wales, and Northern Ireland connectivity-equivalent pages.	Moderate but navigable: one parent comparison and three country child pages carry the service-function split.	Keep as module pages for now.
InterSystems by nation	InterSystems in Scotland, InterSystems in Wales, and InterSystems in Northern Ireland.	Low: each page has a narrow country-specific product boundary and follow-up list.	Keep as module pages for now.
Canonical source/evidence lookup	Source IDs SRC-105 to SRC-147, SRC-198, and SRC-199; evidence-matrix devolved rows; validation-queue UK nations rows.	Moderate: enough rows to monitor, not yet enough friction to justify a duplicate domain layer.	Use this map plus existing pages.

Promotion trigger: create a dedicated Devolved UK Nations evidence-domain page only if a future pass repeatedly needs to traverse the parent comparison, three connectivity pages, three InterSystems-by-nation pages, sources.md, and evidence-matrix.md to answer the same class of cross-nation question. Until then, add depth to the existing country pages rather than introducing another routing layer.

Source Register Contract

docs/sources.md remains the stable source-ID register.
docs/evidence-matrix.md remains the canonical claim-to-source matrix.
Domain pages are navigational synthesis layers.
If a domain page introduces a new durable claim, add it to the evidence matrix.
If a domain page introduces a new source, add it to the source register first.