Skip to content

Evidence Validation Queue

This queue records the evidence still needed before the wiki can support clear Defence Medical Command (DMedC) / Defence Primary Healthcare (DPHC) NHS App guidance. A queued item is not just a research interest; it is a blocker, boundary, or confidence gap for guidance.

Use Evidence Work Packages for the prioritised package view that ties queue items to the Guidance Decision Model.

Queue items are the default home for unresolved evidence needs. Do not turn a queue item into a new checklist, request pack, page, or evidence-domain layer unless the stop/go rule in LLM Wiki Maintenance is satisfied. Long evidence lists in this queue are blockers or acceptance prompts, not standalone request packs, unless a live assurance, delivery, research, procurement, or implementation decision needs a concrete request artefact.

Work Package View

Work package Queue items covered Decision unlocked
Cohort and registration baseline DPHC Firmbase registration, DPHC Organisation Data Service (ODS) model, initial provision cohort matrix, core national service entitlement, minors, dependants, linked profiles, DPHC(O) cohorts, supplier assurance. Initial provision, core national service, linked-profile / proxy status, and registration-state decisions.
Appointments route separation Defence Medical Services (DMS) / DPHC appointment access, implementation delivery horizons, Phase 0-6 technical references, Secondary healthcare (SHC) appointments, the bounded Defence Medical Information Capability Programme (DMICP) Primary healthcare (PHC) reminder workstream, DMICP PHC appointment visibility, DMICP PHC appointment management, NHS Notify, and Patient Care Aggregator / Wayfinder. Patient-service value, SHC appointment, DMICP PHC reminder, DMICP PHC visibility, and DMICP PHC management route decisions.
Document and result route separation Clinical correspondence, test results, SHC provider document routes, Patient Engagement Portal (PEP) document routes, provider results systems, PEP results-release routes, GP-filed document views, and GP-filed result views. Correspondence and test-result route decisions.
CORTISONE / InterSystems integration Programme Cortisone / CORTISONE, CORTISONE / InterSystems patient-data route, DMICP adaptation / evolution option. Later CORTISONE patient-data route decisions.
Assurance and onboarding Partner onboarding / assurance, NHS Notify, Interface Mechanism 1 (IM1), Patient Engagement Portals (PEPs), supplier assurance. Whether a documented route can become a live, guidance-ready service route.
Source freshness and follow-up Annual-report strand, roadmap/API status, live partner evidence, supplier/vendor evidence. Whether existing high-confidence claims remain current enough for decision use.

Queue Items

Domain Evidence Gap Status Notes
DPHC Firmbase registration Whether DPHC-registered adult patients can use every NHS App GP-linked feature while registered to a domestic UK MOD DPHC Firmbase practice rather than an ordinary NHS GP surgery. Boundary Public NHS guidance gives the GP surgery in England eligibility boundary. Current Primary Care Registration Management (PCRM) service and registration-guide evidence explicitly includes DMS in the stated registration-service scope, narrowing the national-infrastructure gap. It still does not provide a named DPHC Firmbase PCRM configuration, Personal Demographics Service (PDS) registered-GP state, GP Practice role, GP2GP outcome, supplier, GP Connect / IM1, proxy setup, practice-capability, or NHS App feature evidence. Do not keep cycling on this as a public-source closure path; use it as a registration boundary while testing whether CORTISONE / InterSystems can supply a separate enablement route.
DMS / DPHC appointment access Current status of the reported NHS App appointment-booking access issue for the source-defined under-13 DMS primary-healthcare cohort. Boundary The 2024 Armed Forces Covenant annual report records NHS work to resolve this. A 2026-06-21 recheck found no direct 2025 annual-report resolution signal, and the 2025 MOD Total Triage source describes a separate DPHC online form / phone triage route rather than NHS App booking. Follow-up status, age boundary, affected GP-system / ODS / registration configuration, proxy status, and wider applicability are still required.
Annual-report strand Current follow-up across Armed Forces Covenant annual reports for NHS App, NHS account, NHS login, appointment booking, linked profiles, proxy access, medical-record transfer, Defence Medical Information Service / Programme, Programme CORTISONE, Op CORTISONE, and electronic health-record integration. Boundary The direct NHS App hit is the 2024 appointment-booking access issue for a source-defined cohort. Pre-2020 reports add general digital-health and MOD/NHS interoperability evidence but no literal NHS App, NHS account, NHS login, or CORTISONE hits in the current review.
Programme Cortisone / CORTISONE Exact relationship between the MOD digital medical-record ecosystem, InterSystems IP / Enterprise Master Patient Index (EMPI) / HealthShare / IRIS for Health licence evidence, TPP-delivered record work, and NHS App, NHS account, PDS, ODS, Spine Directory Service (SDS), GP Connect Patient Facing APIs, Interface Mechanism 1, Electronic Prescription Service (EPS), NHS Notify, Patient Care Aggregator / Wayfinder, and partner onboarding. Needed Source wording is time-specific and mixed: GOV.UK uses Programme Cortisone and Programme CORTISONE; the 2025 annual report uses Op CORTISONE, treated here as the same programme strand unless later evidence distinguishes a separate operation. Cross-deck primary-source carry-over now supports CORTISONE IP / EMPI and InterSystems licence-package evidence, but still does not define NHS App interfaces or patient-facing consequences.
DPHC ODS model ODS organisation codes and GP-system supplier records for DPHC Firmbase and DPHC Overseas [DPHC(O)] practices that would govern GP Connect and NHS App feature availability. Needed Required to distinguish ordinary NHS GP practice routes from MOD DPHC Firmbase and DPHC(O) registration routes. Do not treat a DMS provider code, MOD government-department code, Scottish GP Practice code, Prescribing Cost Centre, default MoD commissioner code, DGP guide postcode, or ODS name-search non-finding as sufficient proof of DPHC Firmbase or DPHC(O) GP-linked NHS App availability.
Initial provision cohort matrix How to move from no current mobile NHS App access for DPHC-registered patients to baseline account, registration, proxy, linked-profile, and feature-dependency provision. Needed Project-owner direction states that all MOD-registered patients retain their first NHS England registration throughout MOD registration; secondary registration in Scotland or Wales, where applicable, does not replace it. The proposed cohort includes MOD-registered patients across the UK for that period. Retain the national-registration arrangements and before/after states at entry to and exit from MOD registration. Split DPHC Firmbase adults, DPHC(O), under-13 minors, 13-to-15-year-olds, dependants, proxy users, linked-profile users, and split ordinary NHS GP / DPHC family registrations; confirm mobile access and each core national, England-provider appointment, and DMICP reminder outcome through retained registration evidence and representative tests.
Core, profile, and national service entitlement Which NHS App-presented public, profile, connected national, and national-choice services become available when a defined DPHC cohort receives mobile account access, kept separate from GP-linked feature enablement. Needed Official sources now define NHS Health A to Z, Find NHS services near you, NHS 111 online, NHS number/profile basics, view/change GP surgery, organ donation, National Data Opt-Out, Be Part of Research, vaccination, health-check, and messaging routes. Project-owner direction reports the DPHC registered-practice display as the civilianised Medical Centre name and address; confirm that value through representative cohort tests. Need account/identity, source-field, registration-transition, age/proxy, eligibility, location, channel, accessibility, fallback, and task tests by DPHC cohort. Public web availability, a displayed profile field, a search result, or one successful service does not prove the others.
IRTB(P) decision and approval inputs Current internal Defence / local staff-work template, security marking, distribution, staffing route, approving authority, DMedC owner, cohort scope, baseline demand, resource/cost evidence, delivery ownership, and benefits measures for the NHS App decision paper. Needed Public MOD sources establish the IRTB / IRTB(P) format family and its Issue, Recommendation(s), Timing, Background and Presentation sequence; historical Defence guidance also supports listing genuine alternatives, including business as usual, before selecting one option (SRC-118 to SRC-121). The retained document controls this project's continuous layout and visual treatment. SRC-131 and SRC-135 are now project-owner validated for their defined scopes. The remaining gap is the current internal/local route, authority, ownership, resources, delivery evidence, security marking, and staffing route. Use the IRTB(P) Evidence Brief and machine-readable build contract; do not create a separate request pack unless a live staffing action requires it.
NHS App architecture Precise NHS App runtime architecture for each feature: hybrid mobile shell, public web, authenticated web, link-out, national API, NHS account, NHS 111 online, NHS Pathways, Directory of Services, NHS Blood and Transplant Organ Donor Register, National Data Opt-Out / Spine, GP Connect PFS, Interface Mechanism 1, EPS, Patient Care Aggregator / Wayfinder, PEP appointment or booking functions, SHC provider document routes, PEP document routes, provider results systems, PEP results-release routes, e-RS, PDS, ODS, Spine Directory Service, NHS Notify, partner onboarding, and local provider systems. Moderate Current wiki has official system-context and component evidence, but not a complete entitlement, end-to-end implementation, and assurance trace for every DPHC cohort and feature.
NHS App implementation delivery horizons Evidence for UK-wide mobile access through the NHS England route, core national services, appointment information from participating NHS providers in England where relevant, a bounded DMICP PHC reminder workstream introduced alongside current SMS, and later DPHC clinical integration. The Phase 0-6 model remains the detailed technical reference for visibility, management, correspondence, results, and CORTISONE patient data. Needed Each outcome needs direct cohort, source-system, interface, onboarding, assurance, fallback, and exclusion evidence before it can be treated as available for DPHC patients. Any later App-first reminder delivery or replacement of routine SMS for defined cohorts also needs parallel-run measures and a recorded service decision. Decision papers should lead with patient outcomes and delivery horizons rather than internal wiki phase labels.
DMICP PHC appointment reminders Whether the current SMS reminder workflow can provide a documented DMICP appointment trigger or feed that passes through a controlled adapter and is submitted to NHS Notify for NHS App delivery, initially alongside current SMS reminders. Needed This is the bounded first DPHC-specific appointment target. Project-owner direction reports current GOV.UK Notify use and requires initial parallel App/SMS operation; obtain the retained service/configuration artefact before treating that as confirmed implementation evidence. Need the DMICP source contract, event timing and update semantics, patient/NHS-number and organisation matching, reminder payload and template, suppression/opt-out rules, PDS contactability, restricted-record handling, NHS Notify sender onboarding, fallback channels, delivery receipts, reconciliation, audit, support, and clinical-safety evidence. Define the parallel-run baseline, channel-performance measures, exception cohorts, retained fallback, cost effect and approval threshold before considering App-first delivery or routine SMS replacement. GOV.UK Notify can deliver SMS, email and letters and is used by NHS Notify as a communication supplier, but direct GOV.UK Notify use does not provide NHS App delivery or prove NHS Notify onboarding. Programme CORTISONE / Health Connect is one possible adapter, not the selected design. No reviewed official source names a separate national “Appointments Reminder API”. PEP/PCA is not required merely to deliver a reminder.
DMICP PHC appointment visibility Whether a DMICP appointment inventory can pass through a controlled adapter to a read-only NHS App, PCA/PEP, or linked-portal visibility route. Needed Need DMICP API/feed contract, patient identity, organisation identity, appointment identifier, appointment-status model, time/location, service/team/clinician label, triage context, patient/NHS number matching, PDS/ODS/SDS handling, display/web/portal route mapping, supplier/practice enablement, NHS login assumptions, suppression rules, audit/provenance, and explicit NHS England evidence accepting a DPHC PHC source into PCA/PEP or another named NHS-facing display route. Programme CORTISONE / Health Connect is one possible adapter. Reminder delivery through NHS Notify does not prove appointment inventory or visibility.
DMICP PHC appointment management Whether DMICP can safely support booking, cancellation, rescheduling, slot search, appointment-change requests, and write-back through CORTISONE / Health Connect or another transformation layer to an NHS-facing management route. Needed Likely not available at this stage on current public evidence. Need bidirectional DMICP/CORTISONE interface evidence, writable slot/schedule state, conflict handling, patient/proxy permissions, audit, clinical safety, supplier/practice enablement, and NHS-facing GP Connect / IM1 / direct-web onboarding proof.
DMICP adaptation / evolution option Whether DMICP can be adapted, wrapped, retired, replaced, or evolved through CORTISONE / HealthShare / Health Connect / IRIS for Health or another layer to support visibility or management. Needed Project-owner direction reports that DMICP cannot currently provide the approved clinical or provider-system connections required for the wider NHS App functions. Open sources do not expose the detailed current capability or adaptation/evolution plans. The live hypothesis is now CORTISONE / InterSystems enablement rather than direct DPHC practice-level evidence, but adapter, feed, write-back, replacement, information-governance, Defence-security, cost and deliverability options remain unknown until component mapping, source-system coverage, NHS-facing route, assurance and investment evidence is available.
Patient Care Aggregator / Wayfinder Whether DPHC Firmbase or DPHC(O) patients' NHS secondary-care referrals and bookings are visible through Patient Care Aggregator / Wayfinder, and whether NHS England would accept a separate DPHC PHC appointment source. Needed The April 2026 NHS England report says every acute trust was connected and 64% of hospital appointments were visible nationally, strengthening the SHC route. It does not prove DPHC cohort behaviour, under-age/proxy behaviour, full provider coverage, or acceptance of DMICP/DPHC PHC data into PCA. Keep the SHC route and proposed PHC route separate. Apply the initial NHS provider validation requirements: obtain named provider/service coverage, the actual MOD referral route, separate display and reminder results, permitted age/proxy use, update and failure tests, support and a scoped introduction decision. Providers, programme owner and funding remain unconfirmed.
PEP appointment or booking function Which connected PEP appointment or booking functions support appointment detail, booking, change, cancellation, or NHS App deep-link behaviour for DPHC-relevant secondary-care journeys. Needed Must identify provider, product, supported appointment action, NHS App connection, authentication route, age/proxy behaviour, and whether the patient journey is SHC rather than DPHC PHC. Retain dated evidence using the initial provider checks; distinguish a requested booking change from a completed source-system change.
Clinical correspondence Which clinical correspondence is visible to DPHC patients through SHC provider document routes, PEP document routes, GP-filed document views, or another NHS App-connected route. Needed Appointment letters, outcome letters, discharge summaries, questionnaires, provider-held correspondence, GP-record filing state, and patient-facing display routes must be tagged separately from test results and CORTISONE-held data.
PEP document route Which provider-held documents are available through a PEP document route for DPHC-relevant patients. Needed Must identify provider, product, document type, display or deep-link route, authentication, access controls, age/proxy handling, and DPHC registration effect.
GP-filed document view Whether documents filed into a GP record are visible through NHS App GP health-record access for DPHC Firmbase, DPHC(O), dependants, minors, and proxy users. Needed Needs GP clinical-system supplier, PDS/ODS state, document filing state, release setting, practice capability, patient cohort, and age/proxy evidence. Ordinary NHS GP evidence is a baseline only.
Test results Which test results are visible to DPHC patients through GP-filed result views, provider results systems, PEP results-release routes, or later CORTISONE patient-data routes. Needed GP and hospital-ordered test results, provider results systems, clinical release controls, PEP results-release routes, GP-record filing state, and CORTISONE-held data must be tagged separately.
PEP results-release route Which provider-held test results are released through a PEP or NHS App-connected digital route for DPHC-relevant patients. Needed Must identify provider, product, result type, release timing, clinical review / override controls, suppression rules, patient-facing route, age/proxy handling, audit, and DPHC registration effect.
GP-filed result view Whether GP or hospital-ordered results filed into a GP record are visible through NHS App GP health-record access for DPHC Firmbase, DPHC(O), dependants, minors, and proxy users. Needed Needs result source, GP filing state, clinical review / release controls, GP clinical-system supplier, PDS/ODS state, practice capability, patient cohort, and age/proxy evidence.
NHS Notify Whether DMedC / DPHC can onboard to NHS Notify and submit appointment reminders or other patient communications for DPHC cohorts through the NHS App, initially alongside current SMS and with retained exception/fallback routes. Needed NHS Notify scope and API are clear. Project-owner direction reports that the current DPHC SMS workflow uses GOV.UK Notify and requires initial parallel App/SMS operation, but no retained implementation artefact confirms that route. GOV.UK Notify and NHS Notify are distinct: NHS Notify can select the NHS App channel and may use GOV.UK Notify as a supplier for fallback channels. The DMICP source trigger/feed, DPHC sender eligibility and ODS identity, onboarding, template/routing configuration, PDS contact sufficiency, suppression and opt-out rules, fallback policy, restricted-record handling, delivery receipts, parallel reconciliation, channel-transition measures, audit, support, funding and approval remain unsourced. NHS Notify can deliver reminders; it does not create appointment inventory, PEP/PCA visibility, booking/management capability, or authority to withdraw routine SMS.
Interface Mechanism 1 Whether any DPHC Firmbase, DPHC(O), or Programme Cortisone route uses IM1, IM1 PFS Auth, supplier Pairing and Integration Packs, or IM1 pairing for GP records, appointments, prescriptions, or GP-practice communication. Needed Official IM1 sources define the interface and assurance model, but not DPHC supplier use, practice configuration, or patient-facing NHS App feature availability.
CORTISONE / InterSystems patient-data route Whether Programme Cortisone uses HealthShare Unified Care Record (UCR), Health Connect / Integration Platform components, IRIS for Health, EMPI, IM1, GP Connect Patient Facing APIs, or another route to expose patient data through NHS App-visible services. Needed Current evidence now supports supplier / programme-role tracking, IP / EMPI and HealthShare / IRIS licence evidence, and InterSystems GP Connect supplier-progress touchpoints. It still does not prove live NHS App publication, GP-provider role, DPHC cohort coverage, GP Connect PFS enablement for DPHC, IM1 pairing, or completed NHS assurance.
Partner onboarding / assurance Whether DMedC / DPHC, MOD suppliers, or Programme Cortisone have completed NHS England onboarding for NHS App, NHS Notify, Patient Care Aggregator / Wayfinder, GP Connect, IM1 Auth Proxy Service, Message Exchange for Social Care and Health (MESH), PDS APIs, or related services. Needed Official onboarding sources define clinical safety, data protection, technical assurance, and information-security assessment areas, but do not identify DPHC status.
Patient Engagement Portals Which PEP meaning is being used in each source: Wayfinder-connected secondary-care booking portal, PEP appointment or booking function, PEP document route, PEP results-release route, eForm route, PIFU route, or general provider-portal capability. Boundary PEP is not automatically NHS App-specific; tag the function and route before drawing continuation and/or adoption conclusions.
Minors How DPHC-registered children move through under-13, 13-to-15 own-access, and 16+ adult/proxy boundaries in the NHS App. Needed NHS public guidance defines ordinary age, capacity, consent, and GP surgery setup rules. It does not establish how DPHC Firmbase or DPHC(O) registration is treated.
Dependants Whether NHS App access for dependants follows the dependant's own GP registration and age, and how access behaves when the service person and dependant are split across ordinary NHS GP and DPHC registration models. Needed Public NHS sources do not define dependants as a separate access category. The same-GP-practice proxy rule makes split registration a specific validation issue.
Linked profiles How linked-profile and proxy access behaves for DPHC-registered patients, dependants, DPHC(O) families, and children transitioning through age thresholds. Needed The 2026-09-21 recheck confirms the same-practice requirement and excludes hospital services and messages from the cared-for person's NHS App profile. For the first-stage patient groups, retain separate own-access and proxy results for each proposed service, including age milestones, consent, permission withdrawal and split-practice families. Agree practice, supplier, NHS login and NHS App support responsibilities; do not substitute proxy access for a working alternative channel. See Linked Profiles and Proxy Access. MOD-specific registration, consent, and GP-system behaviour remain unproven.
DPHC(O) cohorts Whether Defence Global Practice / DPHC(O) patients have NHS App access, and which features remain available after posting or registration change. Boundary Current DGP guidance supports DPHC(O) / Defence Global Practice registration and UK primary-healthcare record-management context, including de-registration from the previous UK General Practice when registered with DGP. It does not establish NHS App, PDS registered-GP, ODS, GP Connect, IM1, proxy setup, or feature-test behaviour.
Supplier assurance GP Connect Patient Facing API, Interface Mechanism 1, and practice/capability enablement status for any DPHC-relevant GP clinical system or CORTISONE / InterSystems route. Needed NHS GP Connect supplier-progress evidence names InterSystems rows, but not DPHC / CORTISONE deployment or NHS App availability. Needs supplier documentation, Pairing and Integration Pack evidence, CORTISONE architecture, NHS onboarding, and cohort feature-test evidence.