Source Freshness
This page records source volatility and recheck rules for the wiki. It complements the Source Register, which remains the canonical provenance list.
R41 implementation source check — 23 October 2026
Rechecked the existing NHS eligibility guidance, hospital-service guidance (SRC-069, last edited 16 October), messaging guidance (SRC-055, last edited 2 October), and family/carer limits (SRC-059, dated 1 July). The Defence Medical Services (DMS) exclusion remains; hospital-service age limits and additional features require provider-specific checks. Separate e-RS referral notices from appointment and reminder evidence. Use the initial NHS provider validation requirements for the bounded follow-up. This check does not establish MOD access, name participating providers or confirm programme ownership or funding.
Freshness Tiers
| Tier | Meaning | Recheck trigger |
|---|---|---|
| Stable reference | Source is unlikely to change materially after publication. | Recheck when a claim is challenged or a newer source supersedes it. |
| Roadmap-sensitive | Source describes planned, current, or evolving capability. | Recheck before implementation, publication, or guidance decisions. |
| API-status-sensitive | Source describes an API, standard, onboarding route, live partner list, or capability status. | Recheck before claiming current availability or selecting an integration route. |
| Annual-report-sensitive | Source is stable after publication but the series may add new annual evidence. | Recheck when a new annual report or update is published. |
| Supplier-sensitive | Source comes from supplier/vendor product or programme material. | Recheck before treating product fit as implementation evidence. |
| Cross-deck synthesis | Source is another local wiki or synthesis artifact. | Carry over only with primary source IDs or explicit secondary-synthesis status. |
Current Source Groups
| Source group | Freshness tier | Current use |
|---|---|---|
| NHS App public, feature-catalogue, and service pages | Roadmap-sensitive / API-status-sensitive | Public baseline, current DMS exclusion, exact user-visible labels, current Home/Messages/Profile grouping, feature scope, technical integration patterns, profile and GP-registration-transition functions, messaging, hospital appointments, current national implementation status, and GP-record views. |
| Family and carer access and patient support | Roadmap-sensitive / operational-support-sensitive | Proxy limits, child access and support routes rechecked 21 September 2026. Recheck before selecting initial patient groups or claiming hospital/message access through a proxy. Confirm practice setup and Defence/NHS support ownership; overseas sign-in troubleshooting does not establish eligibility. |
| NHS App and NHS login roadmaps / integration | Roadmap-sensitive / API-status-sensitive | Future direction, release changes, live partner taxonomy, and integration route evidence. |
| Core, profile, registration-transition, and national NHS App-presented services | API-status-sensitive / roadmap-sensitive | NHS App integration styles, NHS Health A to Z, Find NHS services near you, NHS 111 online, profile basics, current/change GP surgery, Primary Care Registration Management (PCRM) / Personal Demographics Service (PDS) / GP2GP registration transitions, NHS Pathways, organ donation, National Data Opt-Out, and research participation. Recheck each named service, displayed field, registration component, and transition route independently before claiming mobile Defence Primary Healthcare (DPHC) entitlement. |
| NHS digital-front-door strategy and planning | Roadmap-sensitive | NHS App, NHS.UK, Ten Year Health Plan, and medium-term implementation direction. Use for strategic alignment, not current DPHC feature availability. |
| NHS APIs, GP Connect, Interface Mechanism 1 (IM1), onboarding | API-status-sensitive | Architecture, route, enablement, and assurance evidence. |
| Organisation Data Service (ODS), GP-practice, and GP Connect transparency data | API-status-sensitive / dynamic reference data | PDS registered-GP dependency, ODS organisation identity, GP Practice / Prescribing Cost Centre semantics, MOD / DMS ODS identifier boundary, and GP Connect transparency checks. |
| Patient Care Aggregator / Wayfinder appointment routes | API-status-sensitive | Secondary healthcare (SHC) appointment, referral, booking, Record Service, Get Appointments API, Patient Engagement Portal (PEP) appointment or booking deep-link routes, age / trust participation, and current national connection/visibility status. |
| Appointment messaging and reminder value | API-status-sensitive / roadmap-sensitive / internal-workflow-sensitive | NHS Notify, GOV.UK Notify and NHS App messaging routes, national appointment-reminder use, current push-notification coverage, and general administrative value. GOV.UK Notify can supply email, SMS and letter delivery and may be used by NHS Notify, but direct use of GOV.UK Notify does not provide the NHS App channel. SRC-137 records the project-owner-reported DPHC GOV.UK Notify workflow and the proposed parallel-to-App-first transition model; recheck it against current service, API, configuration, pilot, channel-performance and approval artefacts before assurance, delivery or routine SMS replacement. These sources do not prove Defence Medical Command (DMedC) NHS Notify sender onboarding, Defence Medical Information Capability Programme (DMICP) event/feed availability, DPHC cohort access, a replacement case or attributable Defence outcomes. |
| NHS App provider document and live partner routes | API-status-sensitive / roadmap-sensitive | SHC provider documents, PEP document route taxonomy, questionnaires, paperless preferences, live partner functions, and provider-route availability. |
| PEP results-release and wider PEP clinical guidance | Roadmap-sensitive / API-status-sensitive | PEP results-release, PIFU, and general PEP / NHS App patient-engagement context; use only when route function and provider context are identified. |
| MOD / DMedC / DPHC public context | Roadmap-sensitive / supplier-sensitive where programme details evolve | Command identity, DPHC context, DPHC(O) / Defence Global Practice, DMS registration semantics, CORTISONE, DMICP, DPHC Total Triage appointment-access context. |
| Armed Forces Covenant annual reports | Annual-report-sensitive | Official report-series evidence and NHS App / CORTISONE / digital-health signal tracking. |
| Regulator evidence | Stable reference until superseded | CQC-reported DPHC information-system and appointment-search context. |
| InterSystems product, supplier, and CORTISONE carry-over sources | Supplier-sensitive / API-status-sensitive | Product fit, supplier-role tracking, IP / Enterprise Master Patient Index (EMPI) licence evidence, HealthShare / IRIS licence-package evidence, and GP Connect supplier-progress touchpoints; not NHS App availability proof. |
| InterSystems sibling wiki synthesis | Cross-deck synthesis | Local cross-wiki reading only; not primary evidence by itself. |
| Business-case, Defence writing, digital-content, accessibility, security-marking, and IRTB(P) format evidence | Stable reference until superseded / policy-sensitive | Five Case completeness, appraisal, MOD digital-content and accessibility rules, GOV.UK style, Defence terminology and security-marking entry points, documented MOD / DE&S use of IRTB briefs, the four- and five-heading format family, and historical Defence options/submission examples. SRC-119 is withdrawn for new-procurement policy use; SRC-120, SRC-121 and SRC-130 are historical or legacy. Use historical sources only within their stated limits and confirm current internal Defence policy before formal issue. |
| Retained IRTB(P) working document | Local project artefact | Design authority for this project's continuous layout, numbering and visual treatment; not public policy authority. Recheck when the current internal Defence template or approval route is confirmed. |
| DMSR external-referral delay analysis | Internal-validated / scope-sensitive | Project-owner validation supports use of the 84% finding for the reviewed external-referral delay cases. The primary artefact is not retained in the repository. Recheck only if the underlying analysis is revised or the wording is proposed for a wider purpose; never generalise beyond the reviewed cases. |
| Historical DPHC patient-access requirement | Stable historical draft / uncontrolled procurement artefact | Historical evidence of DPHC patient-access intent, including advice, NHS App, appointment, reminder, record, prescription, triage, and communication needs. Do not use as current service-state, procurement-outcome, or implementation evidence. |
| DPHC Medical Centre geographic baseline | Internal-validated / estate-sensitive | The corrected programme baseline is 89 of 103 centres in England. It supersedes the earlier project-owner counts of 91 and the earlier denominator of 106. SRC-086 remains a separate public 105-centre comparison from the April 2025 Total Triage context. Recheck when the estate changes or before using the baseline outside the current decision context. |
| DPHC UK-wide NHS England registration baseline | Registration-sensitive / internal-validated | Project-owner direction states that all DPHC patients are registered as NHS England patients irrespective of UK residence, including patients resident in Scotland, Wales and Northern Ireland. Recheck if the registration model changes and before formal scope approval; obtain retained PDS, ODS, policy and representative cohort evidence before treating this as proof of mobile access, any core national service, participating-provider appointment visibility or DMICP reminder delivery. |
| DPHC patient-facing Medical Centre display | Registration-sensitive / internal-workflow-sensitive | PDS defines the NHS number and registered GP practice fields. Project-owner direction reports that the DPHC display uses the civilianised Medical Centre name and address. Recheck against a live patient screenshot, PDS extract or representative cohort test before issuing estate-wide guidance or inferring GP-linked feature enablement. |
Freshness Rules
- Recheck roadmap-sensitive and API-status-sensitive sources before moving any Guidance Decision Model row to
Available. - Recheck the NHS App technical specification, feature catalogue, current navigation, step-by-step guide, roadmap, release notes, integrated-service list, NHS.UK roadmap, and each named core/profile/national service before staffing an IRTB(P) or making an implementation decision.
- Treat SRC-118 to SRC-121 as stable evidence that the IRTB / IRTB(P) format family exists in public MOD material. Recheck only when a current JSP 101 template, local staffing instruction or replacement policy is obtained; do not repeatedly search for proof that the format exists.
- Recheck SRC-125, SRC-126 and SRC-129 before a major public release or formal issue because MOD digital-content, accessibility, classification and online-publication rules can change. Treat SRC-127 and SRC-128 as live GOV.UK style guidance, SRC-109 as supporting DCDC writing guidance, and SRC-130 as a legacy lookup aid rather than current terminology authority.
- Keep current service, release, and strategic intent separate: a release note can prove a change, a technical specification can prove a route, and a roadmap can prove direction, but none alone proves DPHC entitlement.
- Recheck Patient Care Aggregator / Wayfinder, PEP appointment, PEP document, PEP results-release, and NHS App live-partner sources before treating provider-route evidence as current implementation status.
- Treat these source groups as route-family groupings rather than exclusive buckets: where one source has multiple Source Register tags, recheck it under each route family used in the decision.
- Recheck annual-report-sensitive sources when a new Armed Forces Covenant annual report or update appears.
- Keep source wording for Programme Cortisone, Programme CORTISONE, and Op CORTISONE time-specific.
- Treat supplier-sensitive sources as product or supplier evidence until matched to MOD, NHS, NHS England Digital, regulator, FOI, standard, or implementation evidence.
- Treat cross-deck synthesis as a navigation aid unless the Cross-Deck Evidence Carry-Over checklist is satisfied.