Evidence matrix

Read this alongside the architecture and source register. A supported statement remains bounded by its source and date.

Claim	Support	State	Limitation
CLM-001 — The GP record is the primary record of care and continues through changes of GP.	^{004, 006}	Supported published guidance	England scope; continuity is a record-management principle, not proof of flawless transfer.
CLM-002 — Source record is a term used in NHS England digital-primary-care guidance.	⁰⁰⁵	Supported, retrieval limited	Official indexed content; direct page challenged.
CLM-003 — GP2GP does not mean all record portability.	^{007, 008}	Supported service/operational evidence	GP2GP and same-supplier continuity differ; specific Armed Forces printing FAQ does not rule out every other arrangement.
CLM-004 — The normal single-GP model has Armed Forces dual-registration exceptions.	⁰¹⁰	Supported, retrieval limited	Use the policy conditions; no universal single-registration assertion.
CLM-005 — MOD is controller for DPHC personal data.	⁰¹²	Supported official notice	Different systems are not automatically distinct controllers; purposes and responsibilities still need mapping.
CLM-006 — A formal answer announced rollout beginning in 2027.	⁰¹¹	Historical formal statement	Not evidence of completed rollout or current reliable planning date.
CLM-007 — On 14 October the owner qualified the earlier announced timetable.	⁰³⁰	Historical owner context	Cannot establish the current public-source baseline; no independently verified revised public timetable.
CLM-008 — The model connects the continuing GP record, specialist source records and shared care access as a proposed architecture.	^{001, 003}	Design intent	Source-record and PRC roles overlap; shared access is distinct from updating the PRC. No mandate for separate applications.
CLM-009 — GMS record duties include reports from other clinicians.	^{015, 016}	Supported legislation	Applies within the specified GMS provisions and exceptions; not automatically every MOD service.
CLM-010 — Contractual correspondence deadlines vary by service and communication.	⁰¹⁷	Supported contract	Use applicable service categories; urgent action cannot wait for a maximum deadline.
CLM-011 — Transfer of a message or record is distinct from transfer of clinical responsibility.	^{018, 020, 021}	Supported distinction / design inference	Explicit local workflow and responsibility assignment still needed.
CLM-012 — Direct-access diagnostics and straight-to-test pathways differ.	⁰¹⁹	Supported policy with age caveat	Displayed review date has passed; confirm the implemented pathway.
CLM-013 — GP Connect products have distinct scope and onboarding restrictions.	^{022, 023, 025, 026}	Supported; conflicting dated guidance	September 2026 restrictions qualify older onboarding invitations; exact Defence route unconfirmed.
CLM-014 — Update Record is assured for specified pharmacy flows, not arbitrary specialist write-back.	^{024, 025}	Supported service scope	Reuse of a specification does not confer national service eligibility.
CLM-015 — A proposed MOD recruitment use was not supported by the NDG.	⁰²⁸	Supported dated advice	Specific pre-employment purpose; not a blanket ban on all Defence direct-care uses.
CLM-016 — Record sharing requires purpose-specific legal, access and confidentiality analysis.	^{031, 032, 033}	Supported governance guidance	Shared MOD control does not confer unrestricted clinical or command access.
CLM-017 — Section 251B creates a conditional sharing duty within its statutory scope.	^{034, 035}	Supported legislation	Subject to best interests, exceptions, data protection and common-law constraints; assess Defence applicability.
CLM-018 — The expanded design preserves civilian history within the lifelong primary record and addresses military clinical access and sharing.	⁰³⁶	Owner-directed scope / design intent	Does not establish a separate unchanged civilian record or a delivered capability.
CLM-019 — Temporary NHS care during service can feed the continuing DMS primary record.	⁰³⁷	Supported patient guidance	DMS remains the main registered GP in the described arrangement; temporary registration differs from authorised dual registration.
CLM-020 — DHSC describes full Defence Health Record transfer on NHS GP request and further interoperability work.	⁰³⁸	Supported dated ministerial statement	January 2026 statement; no guarantee of automatic transfer, complete local availability or a later rollout schedule.
CLM-021 — Military medicine includes specialist occupational, aviation, diving and operational contexts alongside general clinical care.	^{013, 040, 041}	Supported clinical scope	Organisation/training descriptions are neither an exhaustive taxonomy nor an access policy.
CLM-022 — The Medical Operating Concept calls for digitised pathways that can function in degraded conditions.	⁰³⁹	Published future concept	Proposed offline handover and reconciliation requirements need local design and assurance; implementation is not verified.
CLM-023 — Expanded access and sharing should be specified by purpose, role, patient relationship, information and permitted action.	^{012, 032, 033, 036}	Governance synthesis / proposed design	Treatment, occupational assessment, command outputs and other purposes require separate assessment; no blanket Defence access permission.
CLM-024 — Chinese tiger tallies used separately held, matching halves to authenticate troop-deployment orders.	⁰⁴²	Supported museum description	Explains the historical type; does not identify the pictured object as the museum's specimen or establish its age, material or provenance.
CLM-025 — Health-data processing requires both an Article 6 basis and an Article 9 condition; confidentiality remains a separate assessment.	^{043, 044, 046}	Supported current law and professional guidance	Exact NHS–MOD activity and secrecy safeguards still require assessment; no generic MOD permission inferred.
CLM-026 — The domestic health/social-care condition includes occupational medicine and working-capacity assessment.	^{045, 033}	Supported legislation with disclosure distinction	This does not authorise unrestricted disclosure of clinical history to command or an employer.
CLM-027 — Section 251 support under the NHS Act 2006 and the section 251B sharing duty under the HSC Act 2012 have distinct roles.	^{047, 048, 034, 035}	Supported legal distinction	CAG support does not compel a controller to release data; the duty has statutory limits and England scope.
CLM-028 — England's national data opt-out does not prevent individual-care sharing and is not a universal disclosure veto.	^{049, 046}	Supported NHS policy and professional guidance	Check policy scope/exceptions; a particular direct-care objection requires its own confidentiality assessment.
CLM-029 — A sharing agreement and DPIA document accountability and risk but do not create missing legal authority.	^{050, 051, 059}	Supported guidance / legal synthesis	Article 26/28 obligations depend on actual roles; this wiki has not approved a local flow or completed a programme DPIA.
CLM-030 — The 2026 lawful-basis guidance includes recognised legitimate interest, which cannot support public authorities' official tasks.	^{043, 054, 059}	Supported current regulator guidance and revised legislation	Listing defence among recognised purposes does not create blanket MOD access or remove health-data/confidentiality requirements.
CLM-031 — Clinical content, terminology, technical representation and transport are distinct parts of the acute discharge standard.	⁰⁶²	Supported information standard	DAPB4042 has a defined provider and exchange scope; it is not a universal Defence correspondence mandate.
CLM-032 — Referral, outpatient, emergency and mental health discharge standards have different content scopes and exclusions.	^{060, 061, 063, 064}	Supported standards taxonomy	The wiki's wider correspondence taxonomy is an analytical grouping, not an exhaustive national classification.
CLM-033 — The published live Transfer of Care profiles remain listed as 2.9.0-live on FHIR STU3.	⁰⁶⁵	Supported current specification listing	Technical version differs from content model version; publication does not prove deployment or permit automatic substitution of FHIR R4.
CLM-034 — The 111 standard distinguishes an information-only GP post-event message from a referral requiring action.	⁰⁶⁷	Supported content and workflow distinction	UK-wide content scope does not establish common routes or implementation coverage across nations.
CLM-035 — The public NHS e-RS description lists Defence medical services among its users.	⁰⁷¹	Supported current service description	Does not establish use by every Defence unit, every referral pathway or all clinical correspondence.
CLM-036 — The October 2026 pathology API description uses FHIR R4 with Patient Data Manager and Multicast Notification Service, with restricted onboarding.	⁰⁶⁹	Published developing API specification	Described as in development and private beta with invitation-only onboarding; not evidence of universal availability or completed EDIFACT retirement.
CLM-037 — DMICP's clinical record, analytical warehouse and personnel administration serve different functions.	⁰⁷⁹	Supported official statistical-method description	Does not provide a complete clinical-system inventory or interface specification; FMed23 medical discharge concerns leaving service.
CLM-038 — Published PCRM scope includes Defence Medical Services, independently of clinical-record transfer.	^{075, 006}	Supported national service description	Does not establish a particular Defence application's interface or an NHS–Defence GP2GP service.
CLM-039 — DMS is identified among e-RS users, with local CQC evidence of external Defence referrals using e-RS.	^{071, 076}	Supported service description and local inspection evidence	Stonehouse report retrieved through official indexed passages only; no estate-wide coverage or interface claim.
CLM-040 — Public inspections describe DMICP tasking, referral follow-up and diagnostic-result handling as distinct local processes.	^{076, 077}	Supported, retrieval limited	Official indexed CQC passages; direct PDFs blocked. No inference of HL7, FHIR, ADT or other wire protocols.
CLM-041 — CQC reports bounded examples of deployed-record limitations and later recording of outage or specialist communications.	^{078, 077}	Supported local observations	Does not establish current Defence-wide offline access, synchronisation or reconciliation algorithms.
CLM-042 — NHSmail guidance expressly identifies a secure healthcare-email route to mod.gov.uk; transport security does not establish disclosure authority or clinical completion.	^{085, 086, 012}	Supported transport guidance / governance synthesis	Check current accreditation, local rules, recipient, record filing and follow-up; guidance is not unrestricted permission.
CLM-043 — ITK2 and ITK3 have different formats and lifecycle status; the cited ITK3 catalogue is STU3-based.	^{090, 091, 098}	Supported published specifications	ITK2 deprecation does not retire all HL7 v2 interfaces; UK Core does not silently change a service's FHIR release.
CLM-044 — ADT events, clinical documents and clinical-task completion represent different information.	^{093, 094, 095, 018}	Standards distinction / design synthesis	HL7 v2.5.1 is an educational reference; the worked recovery sequence is proposed, not a Defence implementation.
CLM-045 — MESH retrieval acknowledgement and application responses do not establish human clinical review.	^{092, 094, 021}	Supported technical distinction / clinical synthesis	Exact workflow, retries and action ownership must be specified per route.
CLM-046 — Patient identity, organisation identity and clinical coding have distinct roles in an exchange.	^{096, 097, 099}	Supported NHS reference services	Patient or organisation identifiers do not independently confer access or identify an approved clinical destination.
CLM-047 — The October 2026 directory marks NEMS deprecated with retirement planned for 30 September 2029.	^{103, 102, 107}	Current directory / service-notice update	Later than the API page's deprecation-review wording; service notice retrieved through official extraction with direct HTTP blocked. Replacement use-case availability remains specific.
CLM-048 — DCB0129 and DCB0160 address manufacture and deployment/use respectively.	^{100, 106}	Supported clinical-safety standard scope	Review notices do not constitute a replacement standard or a completed local safety case.
CLM-049 — A complete exchange design specifies purpose, content, profile, route, identity, responses and clinical work.	^{032, 062, 094, 100}	Proposed reference model grounded in public standards	The interface-contract and legal-record templates are COPPER TIGER synthesis, not mandated NHS forms or approved implementations.
CLM-050 — The October DPC notice is planned procurement, with indicative timing and an estimated £838,749,369 excluding VAT.	¹⁰⁹	Supported official UK3 record	Not an open tender, award or committed expenditure; final UK4 documentation takes precedence.
CLM-051 — MOD and NHS bodies across all four UK nations are included in anticipated buyer scope.	¹⁰⁹	Supported planned buyer scope	Does not establish final eligibility, a MOD call-off, supplier selection, national-service access or deployment.
CLM-052 — The planned lots distinguish foundation EPR, clinical/operational support and R&D.	¹⁰⁹	Supported planned structure	Final capability requirements await tender documents; Lot 3 enrolment follows Lot 1/2 success unless opted out.
CLM-053 — NHS England confirms TIF extension to 30 September 2027 while the replacement framework develops.	^{111, 112}	Supported current programme statement	Does not establish every incumbent contract term or import all TIF requirements into every new lot.
CLM-055 — Foundation capability assurance and a component or non-foundation role require different evidence.	^{115, 026}	Published assurance distinction / design inference	Generic integration capability does not establish a complete GP foundation system or national-service approval.
CLM-056 — The UK3 structured EOI date conflicts with its explicit no-response narrative.	¹⁰⁹	Recorded source discrepancy	10 November 2026 is not presented as a live bid deadline; follow the eventual UK4 notice.
CLM-057 — The DSIC requirement hierarchy distinguishes MUST/MAY epics, acceptance criteria, implementation details and guidance.	¹¹⁶	Supported supplier guidance	Contracting vehicles or supplementary standards can mandate MAY functionality; applicable versions still matter.
CLM-058 — Patient Information Maintenance C13 v10.0.3 is effective from 13 October 2026; v14.0.0 has a future effective date.	¹²⁵	Supported versioned specification	The page lists Digital Primary Care, but final tender documents must establish the applicable requirement version.
CLM-059 — Digital Diagnostics C8 v1.0.2 treats request/result reconciliation as MAY.	^{126, 116}	Supported requirement distinction	Not proof that any named product omits reconciliation; a contracting vehicle can make it mandatory.
CLM-060 — Task Management C50 v1.1.0 treats assignment and overdue flags as MAY.	^{127, 116}	Supported requirement distinction	Basic capability coverage is not proof of every handover or escalation function; final DPC conditions may differ.
CLM-061 — RM270 added three named support capabilities before the October DPC notice.	¹¹⁸	Supported DSIC roadmap history	Digital Dictation, Medical Reports and Self-service Appointment Check-in are not established here as newly invented October terminology or AI requirements.
CLM-062 — The clinical system migration guide is intended for established foundation suppliers, not new-supplier onboarding.	¹²³	Supported guidance scope	Some steps may apply to new suppliers; the guide is not a complete local migration plan.
CLM-063 — TIF assurance distinguishes interoperability, core capabilities, overarching standards and clinical release.	^{117, 112}	Supported assurance description	The detailed assurance page is dated November 2025; its supplier-status table is not a fresh October 2026 approval decision.
CLM-064 — Framework call-off selection differs from a competitive flexible tendering procedure.	^{119, 120, 109}	Supported guidance / recorded terminology discrepancy	UK3 call-off wording needs final-document clarification; this does not determine an individual contract route.
CLM-065 — Lot 3 describes R&D from discovery through public beta, with admission following Lot 1 or Lot 2 success unless opted out.	^{109, 121, 122}	Supported planned scope / contextual lifecycle explanation	Examples are project synthesis; the notice does not specify work packages, IP allocation, payment or production-operation funding.
CLM-068 — GP IT Futures expired on 31 March 2023; its name is not a universal current GP purchasing route.	^{130, 112, 109}	Published framework history and current/planned route distinction	April 2026 continuity text reaches only June 2026. TIF extension does not establish every incumbent contract or admission to the planned successor.

The validation queue holds unresolved decisions. Project updates retain owner-provided context separately from public evidence.

Historical supplier-comparison claim identities are retired from the current synthesis and preserved in release v1.0.0. They are not reused.

Programme-wide definition

Claim	Support	State	Limitation
CLM-090 — COPPER TIGER scope includes the whole operating model; Care Hub is a potential Cortisone rebranding.	²¹¹	Owner direction	Not an approved programme or confirmed rename.
CLM-091 — Continuing PRC plus internal Defence shared care record is the leading evolving principle.	²¹¹	Proposed direction	Storage, responsibility and implementation remain to be tested.
CLM-092 — England SPR policy builds on existing records; the bill remained in scrutiny.	^{193, 194}	Public policy and parliamentary stage	No enacted mandate or Defence integration established.
CLM-093 — National and devolved services have distinct scope and participation conditions.	^{196, 201, 206, 207}	Bounded public findings	No universal UK contract or Defence entitlement inferred.
CLM-094 — Internal work and purpose controls must remain explicit across external interfaces.	^{211, 032, 209}	Architectural inference	Requires pathway-specific discovery and assurance.

Shared-record capability clarification

Claim	Support	State	Limitation
CLM-095 — The DShCR should provide a comprehensive, primarily read-only overview alongside the continuing PRC and authoritative source records.	²¹²	Proposed direction	Coverage is an objective, subject to permissions and source availability. Storage and any capture functions remain undecided.
CLM-096 — The IntP should broker information and support publish–subscribe exchange; other tools may process clinical work.	²¹²	Proposed direction	Does not assign workflow ownership to the broker or require every exchange to traverse the DShCR.
CLM-097 — The HPD should support configurable profiles, provider relationships and permanent or temporary facilities, with controlled location information.	²¹²	Proposed direction	Detailed permissions and enforcement remain open. The directory alone is not a complete identity and access management design.
CLM-098 — The EMPI should link patient identities and provide a shared demographic profile; wider patient administration belongs in other tools or features.	²¹²	Proposed core capability	Demographic authority and conflict resolution are required service functions; rules and methods remain TBC. No identifier format is selected.
CLM-099 — Patient-facing services may provide access, patient contributions and return flows through the IntP.	²¹²	Proposed option	Features and incorporation rules remain open; patient contributions do not automatically overwrite professional records or the PRC.
CLM-100 — NHS England's capability model defines PHRs through patient management and contribution as well as secure online access.	²¹³	Published capability definition	A patient-facing viewer is not necessarily a PHR; this reference does not establish a Defence service.
CLM-101 — Published NHS references support investigating fallback record access, recovery processes and visible downtime-related data gaps.	^{214, 215}	Bounded public guidance and dated requirements	No automatic MOD mandate, storage choice or numerical service target. The DShCR's continuity and forms options remain to be designed and tested.
CLM-102 — Identity, version, provenance and content fingerprints serve distinct purposes in reconciling information.	^{216, 217, 218}	Standards distinction and architectural synthesis	A hash alone cannot establish clinical equivalence, author, patient match or freshness. No FHIR version, identifier scheme or hash algorithm is selected.
CLM-103 — Maintain patients’ lifelong GP records to applicable NHS conventions and standards to support continuity and transfer to NHS general practice when care arrangements change, alongside a complementary DShCR.	²¹⁹	Proposed direction	Includes Armed Forces and civilian patients within Defence healthcare scope. Does not establish a universal transfer trigger, equal care entitlements, current compliance, organisational approval or a working transfer mechanism.
CLM-104 — The DShCR should present a contiguous, longitudinal overview across multiple source systems, with authorised access to complete contributing clinical source records.	²²⁰	Proposed direction	Connected presentation and continuity over time do not establish complete source coverage, current information or universal access. Source systems retain their originating accounts and corrections.
CLM-105 — The associated IntP should coordinate two-way exchange of core clinical information to support CDSS in independent specialist source systems.	²²⁰	Proposed direction	Conditions, medications, vaccinations and allergies need defined authority, provenance, currency, correction and reconciliation rules. EMPI/HPD context is distinct from clinical source records; no automatic overwrite, central clinical authority or broker-owned workflow is selected.
CLM-106 — The DShCR should support business continuity, exploring retained information, consultation capture and later reconciliation.	^{212, 220}	Proposed capability and options	Failure scenarios, coverage, capture responsibilities, recovery targets and implementation remain to be determined. A retained copy is not proof of an available continuity service.
CLM-107 — The continuing GP-record objective includes transfer from and to NHS general practice when Defence care arrangements begin and end.	²²⁰	Proposed direction	Includes Armed Forces and civilian patients within scope. This refines the transfer wording in CLM-103; it does not establish universal registration changes, care entitlements or delivered transfer capability.
CLM-108 — In this programme framing, Defence healthcare is the wider scope; occupational health-led qualifies military medicine.	²²¹	Proposed terminology and scope clarification	Retains Armed Forces and civilian patients within scope. Does not turn all clinical care into occupational assessment, select new permissions, change entitlements or establish an official taxonomy. Earlier wording remains dated history.