Skip to content

Guidance Decision Model

This page converts the evidence base into guidance-facing decisions. It does not replace the Evidence Matrix or Evidence Validation Queue; it states what the wiki can safely say now, and what evidence would change the answer.

Use Registration State Model to classify the patient before applying this table.

Current Answer

Defence Primary Healthcare (DPHC)-registered patients do not currently have access to the mobile NHS App. The immediate decision is whether to enable access and core national services for DPHC patients across the UK through the NHS England route, test appointment information and messages from participating NHS providers in England where relevant to their care, and authorise bounded development of one-way DPHC Firmbase reminders. GP-linked services, appointment inventory and management, and wider clinical-data capabilities remain separate decisions.

The NHS App is an NHS England service. The project owner confirms that all MOD-registered patients retain their first NHS England registration throughout MOD registration, irrespective of UK residence. Secondary registration in Scotland or Wales, where applicable, does not replace it. Secondary registration in Northern Ireland is intended but is not yet in place. The proposed enablement therefore covers MOD-registered patients for that period through their continuing NHS England registration, including residents of Scotland, Wales and Northern Ireland; age, proxy and service-specific access conditions remain separate. They would be able to use applicable core national services, see appointment information from participating NHS providers in England where relevant to their care, and receive Defence Medical Information Capability Programme (DMICP) appointment reminders through the App once that route is implemented and assured. The corrected programme baseline places 89 of 103 UK DPHC Medical Centres in England, approximately 86% of the estate; this supports operational scale rather than defining a residence boundary.

Decision Inputs

Input Allowed values Why it matters Primary source page
Registration context Ordinary NHS GP, DPHC Firmbase, DPHC Overseas [DPHC(O)] / Defence Global Practice, unknown Determines whether NHS App dependencies see an ordinary registered GP context or an unresolved MOD context. Registration State Model
Transition state Steady state, transition into DPHC, transition out of DPHC, overseas posting, return from DPHC(O), unknown Prevents transition evidence from being treated as steady-state availability. Registration State Model
Age band Under 13, 13 to 15, 16+, adult Determines own NHS App access, child proxy rules, and age milestone review. Eligibility and Registration
Access mode Self, parent / guardian proxy, adult proxy, linked profile, invalid informal account sharing Separates own access from managed access for another person. Linked Profiles and Proxy Access
Family / proxy relationship Same GP practice, split ordinary NHS GP / DPHC practice, dependant with ordinary NHS GP registration, dependant with DPHC registration, carer/proxy relationship, not applicable, unknown Affects formal proxy / linked-profile setup and dependant analysis. Linked Profiles and Proxy Access
Feature route Account access, profile function, registration transition, core national service, GP-linked feature, Secondary healthcare (SHC) appointment, DPHC Firmbase reminder, DMICP Primary healthcare (PHC) visibility, DMICP PHC management, clinical correspondence, test result, CORTISONE patient data Prevents evidence from one route being generalised to another route. NHS App Service Overview
Source / interface route Public NHS.UK content, NHS Service Search, NHS login web integration, NHS 111 online, NHS Pathways, Directory of Services, NHS Blood and Transplant API, Spine preference service, Register with a GP surgery, online consultation system, personal health record, NHS account, Personal Demographics Service (PDS), Organisation Data Service (ODS), Spine Directory Service (SDS), GP Connect PFS, Interface Mechanism 1 (IM1), Electronic Prescription Service (EPS), e-RS, Patient Care Aggregator / Wayfinder appointment summary, Patient Engagement Portal (PEP) appointment or booking function, SHC provider document route, PEP document route, provider results system, PEP results-release route, NHS Notify, DMICP, CORTISONE Identifies the exact implementation and assurance path. Architecture Index

Decision Statuses

Status Meaning Use
Available Evidence supports the feature for the stated cohort and route. Use only where direct service or implementation evidence confirms availability.
Conditional Ordinary NHS or named service route exists, but DPHC availability depends on a specific registration, supplier, provider, age, proxy, or onboarding condition. Use where the NHS route is evidenced but DPHC operation is not fully proven.
Not currently available The current service position is that the stated DPHC cohort does not have the feature, but the wiki tracks the implementation route needed to change that position. Use for baseline DPHC mobile NHS App access where the current state is no access and the work is an implementation route, not merely an evidence search.
Not evidenced Current sources do not prove availability for the stated DPHC cohort and route. Default for unresolved DPHC-specific questions.
Likely not available Current public evidence and architecture constraints make availability unlikely at this stage, but direct service-owner evidence is still required. Use sparingly, especially for DMICP PHC appointment management.
Not applicable The feature or route does not apply to the cohort or phase being assessed. Use where the route is outside the patient's state or service scope.

Core National Service Decisions

These services should be assessed before requiring DPHC GP-system integration. The official NHS App architecture places them on public web, authenticated web, national API, account/profile, or connected national-service routes. Mobile NHS App access is still the controlling DPHC barrier, and each service retains its own age, identity, eligibility, registration, or data-source rules (SRC-095 to SRC-106, SRC-114 to SRC-117).

For the current IRTB(P), apply an outcome-led priority: core national services first; appointment information and messages from participating NHS providers in England as the critical initial provider-connected function where relevant to the patient's care; one-way DPHC Firmbase reminders as a bounded workstream; then separately funded clinical capabilities. The project-owner-validated DMSR finding supports the appointment-communication priority within its reviewed-case scope; it is supporting evidence rather than the opening or sole case for change.

Capability Primary route Current DPHC position Guidance statement Evidence needed to change the position
NHS Health A to Z Public responsive web content Public web available; integrated mobile App route not currently available DPHC patients can use public NHS health information outside the App. Enabling the mobile NHS App would restore the integrated Health A to Z journey without requiring a DPHC GP clinical-system interface. Mobile NHS App account/access test by cohort, navigation test, accessibility and assisted-digital review.
Find NHS services near you Public responsive web content and NHS Service Search data Public web available; integrated mobile App route not currently available The App journey can find dentists, pharmacies, hospitals, urgent-care services, GP surgeries, and other services by postcode or device location. Results support navigation but do not prove eligibility, acceptance, capacity, or DPHC service representation. Account/navigation test, location permission and postcode handling, overseas boundary, accessibility, data accuracy, and service-specific eligibility checks.
NHS 111 online NHS login-enabled web integration, NHS Pathways, Directory of Services Public website available for eligible users; mobile App route not currently available NHS 111 online is a national urgent-care triage route for people in England aged 5 or over. It is separate from DPHC triage and appointment access. Mobile account test, age/proxy behaviour, England/postcode handling, hand-off and fallback test, clinical-safety and support confirmation.
Organ donation decision NHS Blood and Transplant Organ Donation API and NHS Organ Donor Register Mobile App route not currently available The NHS App can make, check, confirm, or change a decision; the NHS Organ Donor Register is the authoritative record. This is not a GP-linked feature. Account/identity test by cohort, API entitlement, age/consent handling, privacy and support confirmation.
National Data Opt-Out NHS App-presented web route and Spine preference record Mobile App route not currently available; other channels remain available The service is a national information-rights function. Own digital choice and child/proxy routes must follow the service's age and legal-authority rules. Account/identity test, NHS-number/Spine match, age/proxy handling, and confirmation of mobile/web channel availability.
Be Part of Research NHS login-enabled NIHR web integration Mobile App route not currently available; public service remains available outside the App Treat research participation as a national service benefit, not a GP-linked clinical-record function. Account hand-off, eligibility, consent, privacy, accessibility, and task-completion test.
Vaccination and digital health-check services Authenticated national web integrations and NHS App messages Conditional on campaign, eligibility, service rollout, and mobile access Do not generalise a pilot, campaign, or eligible cohort into universal DPHC availability. Named service, eligibility, location, age/proxy, message, booking, record, and fallback evidence.
NHS number and profile basics NHS App Profile using account, PDS, GP-record, and service-specific data Mobile App route not currently available; source channels remain available Profile can show NHS number, contact details, home address, current GP surgery, health choices, and settings, but each field has separate view, correction, change, rollout, and proxy rules. Mobile account test, field provenance, correction/change route, age/proxy handling, DPHC registration effect, and support test.
View or change GP surgery Register with a GP surgery connected service, NHS login where used, NHS-record matching, practice acceptance, Personal Demographics Service (PDS), Primary Care Registration Management (PCRM), GP2GP, and NHS Notify Ordinary NHS route evidenced; DPHC transition effect not evidenced Treat this as a registration-transition function. Primary Care Registration Management (PCRM)'s stated coverage includes Defence Medical Services (DMS), but this does not make a DPHC organisation an ordinary NHS GP practice or prove mobile NHS App access. The reviewed proxy journey does not currently support changing GP surgery for another person. Defence Medical Command (DMedC) policy, DPHC transition scenario, current-GP display, practice search/catchment, application result, PCRM completion, before/after PDS state, GP2GP record-transfer effect, exception handling, proxy exclusion, safety-netting, and continuity test.

Use Core National Services and Roadmap for the service and roadmap synthesis. A successful test of one service must not be used as proof of every national, provider, or GP-linked feature.

Feature Decision Matrix

The matrix and phase map use named document route and named result route as guidance-facing shorthand. The detailed route-family gate belongs in the current guidance table, evidence matrix, validation queue, and route pages: clinical correspondence may be a SHC provider document route, PEP document route, or GP-filed document view; test results may be a provider results system, PEP results-release route, or GP-filed result view.

Registration / cohort state Initial provision SHC appointments DMICP PHC visibility DMICP PHC management Clinical correspondence Test results CORTISONE patient data
Ordinary NHS GP baseline Available where public age / account / GP-registration rules are satisfied. Conditional on Patient Care Aggregator / Wayfinder appointment summary, e-RS, secondary-care booking system, or PEP appointment or booking function participation. Not applicable unless the patient also has DPHC PHC care. Not applicable unless the patient also has DPHC PHC care. Conditional where a named document route is evidenced. Conditional where a named result route and release controls are evidenced. Not applicable unless CORTISONE holds relevant patient data.
DPHC Firmbase adult Not currently available. Conditional only after mobile access is enabled for the cohort and the connected NHS SHC route is active for that patient journey. Not evidenced; the separate one-way reminder workstream does not prove appointment inventory or visibility. Likely not available. Conditional where a named document route and DPHC registration effect are evidenced. Conditional where a named result route, release controls, and DPHC registration effect are evidenced. Not evidenced.
DPHC(O) patient Not currently available. Conditional on referral / connected NHS SHC appointment route and NHS account state. Not evidenced. Likely not available. Conditional where a named document route and DPHC(O) registration effect are evidenced. Conditional where a named result route, release controls, and DPHC(O) registration effect are evidenced. Not evidenced.
Under-13 DMS / DPHC child Own access is outside the public own-account baseline; parent / guardian proxy route must be tested separately. Conditional by PEP appointment or booking function, e-RS / connected NHS SHC appointment route, and proxy / age handling. Not evidenced; source records an appointment-booking issue that must not be treated as proof of visibility. Likely not available. Conditional by proxy access, named document route, and age handling. Conditional by proxy access, named result route, release controls, and age handling. Not evidenced.
13-to-15 DPHC young person Not evidenced for DPHC setup equivalence. Conditional by PEP appointment or booking function, e-RS / connected NHS SHC appointment route, and age rules. Not evidenced. Likely not available. Conditional by own/proxy access, named document route, and age handling. Conditional by own/proxy access, named result route, release controls, and age handling. Not evidenced.
Dependant with ordinary NHS GP registration Conditional on dependant's own registration and age. Conditional by PEP appointment or booking function or connected NHS SHC appointment route. Not applicable unless the dependant is DPHC-registered. Not applicable unless the dependant is DPHC-registered. Conditional by named document route and any proxy state. Conditional by named result route, release controls, and any proxy state. Not applicable unless CORTISONE holds data.
Split ordinary NHS GP / DPHC family registration Not evidenced for cross-registration linked-profile behaviour. Conditional by PEP appointment or booking function, connected NHS SHC appointment route, and proxy limits. Not evidenced where DPHC PHC applies. Likely not available. Conditional by named document route, same-practice interpretation, and proxy state. Conditional by named result route, release controls, same-practice interpretation, and proxy state. Not evidenced.

DPHC Phase-to-Decision Map

Use this table to translate the phased technical references into a cohort decision. It is stricter than the high-level matrix: every phase must keep the cohort, access mode, source route, and implementation route attached to the decision. The bounded Firmbase reminder workstream is independent of Phase 2 and is recorded separately in the Current Guidance Table.

DPHC cohort / state Phase 0 initial provision Phase 1 SHC appointments Phase 2 DMICP PHC visibility Phase 3 DMICP PHC management Phase 4 clinical correspondence Phase 5 test results Phase 6 CORTISONE patient data
DPHC Firmbase adult Not currently available; NHS England directly records the current DMS exclusion, while the enabling route and GP-linked setup remain unresolved. Conditional only after mobile access is enabled for the cohort and the NHS SHC provider, Patient Care Aggregator / Wayfinder appointment summary, e-RS, PEP appointment or booking function, NHS login state, and age/proxy handling are evidenced. Not evidenced until a DMICP inventory feed, identity / organisation mapping, controlled adapter, and NHS-facing display route are proven. Likely not available until bidirectional write-back, slot state, permissions, audit, and route assurance are proven. Conditional only where the named document route and DPHC registration effect are evidenced. Conditional only where the named result route, release controls, and DPHC registration effect are evidenced. Not evidenced; CORTISONE / InterSystems is a candidate enablement route until source role, HealthShare / IRIS / Health Connect mapping, IM1 / GP Connect PFS route, onboarding, access-mode tests, and patient-facing publication are proven.
DPHC Overseas [DPHC(O)] patient Not currently available; no current mobile NHS App access, and Defence Global Practice evidence supports DPHC(O) registration / record-management context but not NHS App provision. Conditional where the overseas / return referral produces a connected NHS SHC appointment route and the patient can authenticate. Not evidenced until DPHC(O) appointment-source and display-route evidence exists. Likely not available on current public evidence; overseas source-of-truth and write-back route are unproven. Conditional only where the named document route and DPHC(O) registration effect are evidenced. Conditional only where the named result route, release controls, and DPHC(O) registration effect are evidenced. Not evidenced until CORTISONE coverage for DPHC(O) and NHS App publication route are proven.
Under-13 DMS / DPHC child Own access is Not applicable; parent / guardian proxy is Conditional on GP-practice setup, same-practice rules, and DPHC supplier behaviour. Conditional by PEP appointment or booking function, e-RS / connected NHS SHC appointment route, proxy route, and age handling. Not evidenced; the reported appointment-booking issue does not prove PHC visibility. Likely not available; management would require child/proxy permissions plus write-back and assurance. Conditional only where proxy access, a named document route, and age handling are evidenced. Conditional only where proxy access, a named result route, clinical release controls, and age handling are evidenced. Not evidenced; child/proxy CORTISONE publication and NHS App exposure are unproven.
13-to-15 DPHC young person Not evidenced until DPHC practice setup, capacity / consent checks, and age-band workflow are proven. Conditional by PEP appointment or booking function, e-RS / connected NHS SHC appointment route, NHS login state, and young-person access rules. Not evidenced until DMICP display and young-person access rules are proven. Likely not available; management needs age/proxy permissions and write-back evidence. Conditional only where own/proxy access, a named document route, and age handling are evidenced. Conditional only where own/proxy access, a named result route, clinical release controls, and age handling are evidenced. Not evidenced until CORTISONE publication and age-band rules are proven.
Dependant with ordinary NHS GP registration Conditional on the dependant's own ordinary NHS GP registration, age, account state, and proxy state. Conditional by PEP appointment or booking function or connected NHS SHC appointment route and the dependant's own NHS App eligibility. Not applicable unless the dependant is also DPHC-registered for PHC. Not applicable unless the dependant is also DPHC-registered for PHC. Conditional only where a named document route and any proxy state are evidenced. Conditional only where a named result route, release controls, and any proxy state are evidenced. Not applicable unless CORTISONE holds relevant dependant data.
Split ordinary NHS GP / DPHC family registration Not evidenced for linked-profile behaviour across split registration states. Conditional by PEP appointment or booking function or connected NHS SHC appointment route and proxy limits. Not evidenced where DPHC PHC applies. Likely not available where DPHC PHC management is requested. Conditional only where a named document route, same-practice interpretation, and proxy state are evidenced. Conditional only where a named result route, release controls, same-practice interpretation, and proxy state are evidenced. Not evidenced until CORTISONE cohort, family/proxy, and publication rules are proven.

Current Guidance Table

Cohort / state Feature or phase Primary route Current status Safe guidance statement Evidence needed to change status
Ordinary NHS GP registration Own NHS App / NHS account baseline NHS account, NHS App, GP surgery in England or the Isle of Man Available Public NHS sources support ordinary age and GP-registration eligibility for NHS App / NHS account use (SRC-002, rechecked 18 September 2026). Recheck public NHS guidance before operational publication.
DPHC Firmbase adult Initial provision and GP-linked features NHS account, PDS, ODS, GP system, GP Connect Patient Facing APIs, IM1 where relevant Not currently available State that people registered at a DMS surgery cannot currently use the mobile NHS App. DMS-registration and ODS evidence confirms MOD-provided primary-care context and relevant identifiers, but not the enabling route, PDS registered-GP state, GP Practice role, supplier, GP Connect / IM1 enablement, proxy setup, practice capability, or feature tests. DPHC and NHS service-owner agreement on the enabling route, PDS registered-GP state, practice-level ODS code and role, supplier / GP Connect / IM1 enablement, practice capability, proxy setup, and feature tests.
DPHC Overseas [DPHC(O)] patient Initial provision and GP-linked features Defence Global Practice / DPHC(O), NHS account, PDS / ODS state Not currently available State that people registered at a DMS surgery cannot currently use the mobile NHS App. Official DGP and DMS-registration evidence supports DPHC(O) as a distinct registration / record-management context, but it does not prove an enabling route, PDS registered-GP representation, ODS route, GP Connect PFS, IM1, proxy setup, or GP-linked feature availability. Defence Global Practice / DPHC(O) registration model, PDS/ODS state, NHS App eligibility interpretation, supplier / GP-system evidence, proxy setup, and feature tests.
Minor under 13 registered with DMS / DPHC primary healthcare Own NHS App / NHS account access NHS account and public age baseline Not applicable Under current public NHS account / NHS App rules, under-13 own access is outside the ordinary own-account baseline. Analyse parent / guardian proxy or named service routes instead. Recheck public NHS age rules before operational publication; DPHC evidence cannot by itself convert under-13 own access into an available route.
Minor under 13 registered with DMS / DPHC primary healthcare Parent / guardian proxy or linked-profile access GP-practice proxy setup, same-practice rule, permitted services, age-review rules Conditional Ordinary NHS proxy routes exist, but DPHC practice setup, same-practice treatment, supplier behaviour, and service permissions are not proven for this cohort. DPHC proxy setup process, same-practice interpretation, supplier behaviour, permitted-service list, and linked-profile test evidence.
Minor under 13 registered with DMS / DPHC primary healthcare NHS App appointment-booking issue Appointment route, proxy state, GP-system configuration, ODS state, registration context Not evidenced The 2024 annual report records a direct NHS App appointment-booking issue for this source-defined cohort. A 2025 annual-report recheck does not resolve it, and MOD Total Triage evidence describes a separate DPHC online form / phone triage route rather than NHS App booking. Direct resolution evidence, root cause, age/proxy setup, GP-system configuration, ODS state, appointment route, and current NHS App test result.
Young person aged 13 to 15 with DPHC registration Own access and proxy / linked-profile access NHS account, GP-practice setup, age/capacity checks Not evidenced Apply ordinary NHS age and GP-surgery setup rules as the baseline; DPHC practice equivalence remains unproven. DPHC GP-practice setup process, supplier behaviour, age/capacity workflow, and NHS App own-access test.
Dependant with ordinary NHS GP registration Own NHS App access Dependant's own age, account, and GP registration Conditional Analyse the dependant directly. Ordinary NHS registration may satisfy ordinary NHS App access, but split-family proxy access still needs same-practice validation. Dependant registration, proxy relationship, same-practice status, and linked-profile setup evidence.
Split ordinary NHS GP / DPHC family registration Linked profile / proxy access GP-practice proxy setup and same-practice rule Not evidenced Do not assume linked profiles work across split NHS GP and DPHC registration states. Same-practice interpretation, DPHC practice setup, supplier linking evidence, age/proxy permissions.
Any DPHC cohort with NHS secondary-care referral or booking SHC appointments, referrals, waiting lists Patient Care Aggregator / Wayfinder appointment summary, e-RS, PEP appointment or booking function, secondary-care booking systems Conditional Treat appointment information from participating NHS providers in England as the critical initial provider-connected function where relevant to the patient's care, but only after mobile NHS App access is enabled and the named provider route is active for that journey. Every acute trust was connected and 64% of hospital appointments were visible nationally by April 2026; coverage is not universal. Do not use this row as proof of documents or results. Mobile access, trust / PEP appointment participation, e-RS or booking-system record, NHS App display test, age/proxy behaviour, paperless settings, and message fallback.
DPHC Firmbase patient One-way PHC appointment reminder DMICP appointment event/feed, controlled adapter, NHS Notify API, NHS App message and fallback Conditional implementation target A bounded one-way reminder service is a candidate route using known NHS messaging interfaces; it is not implemented evidence. Initial operation should run alongside current DMICP SMS reminders. App-first delivery or replacement of routine SMS for defined cohorts requires a separate decision after delivery, reconciliation, accessibility, support, safety, cost, exception, and fallback evidence is available. Programme Cortisone / Health Connect is one possible adapter, not the selected design. NHS Notify transports messages; it does not provide appointment inventory, management, or DMICP write-back. DMICP source event/feed, identifiers/statuses, patient and ODS matching, NHS Notify sender eligibility/onboarding, template/routing, callbacks, fallback, reconciliation, funding, safety, parallel-run baseline, channel-transition criteria, recorded approval, and end-to-end test.
DPHC Firmbase patient DMICP PHC appointment visibility DMICP appointment inventory feed, controlled adapter, accepted NHS-facing display route Not evidenced Treat read-only DPHC PHC appointment visibility as a later candidate architecture. Current PCA onboarding is framed for secondary-care systems; DPHC Firmbase eligibility and acceptance are unproven. Reminder delivery does not change this status. DMICP feed/API contract, identity and organisation mapping, transformation evidence, NHS-facing route acceptance, portal or display route, NHS login, onboarding, assurance, and end-to-end test.
DPHC Overseas [DPHC(O)] patient DPHC PHC reminders or visibility DPHC(O) source, communication and visibility routes Not evidenced Do not extend the Firmbase reminder hypothesis to DPHC(O) without separate source, identity, legal, connectivity, support, time-zone and fallback evidence. DPHC(O) source-of-truth, event/feed, NHS number/PDS/ODS state, contact policy, route acceptance, assurance, support and live test.
DPHC Firmbase or DPHC(O) patient DMICP PHC appointment management Bidirectional DMICP / CORTISONE write-back, GP Connect Appointment Management, IM1, direct web integration, or other assured route Likely not available Record as a target and evidence gap. Do not imply patients can book, cancel, reschedule, or change DPHC PHC appointments through the NHS App on current public evidence. Writable appointment-book interface, slot/schedule state, conflict handling, patient/proxy permissions, audit, clinical safety, route assurance, supplier enablement.
Any DPHC cohort Clinical correspondence SHC provider document route, PEP document route, GP-filed document view Conditional Route-tag every correspondence claim. Evidence for an SHC provider document route does not prove a PEP document sub-route; evidence for a PEP document route does not prove PEP results-release, GP-filed document access, or any test-result route. Source item, SHC provider document route, PEP document route where used, GP filing state where used, patient-facing display route, age/proxy effect, DPHC registration effect.
Any DPHC cohort Test results GP-filed result view, provider results system, PEP results-release route Conditional Route-tag every result claim. Evidence for a provider results system does not prove a PEP results-release sub-route; evidence for a PEP results-release route does not prove correspondence, CORTISONE patient data, or DPHC GP-record equivalence. Result source, provider results system, PEP results-release route where used, GP filing state where used, patient-facing display route, clinical release controls, age/proxy effect, DPHC registration effect.
DPHC cohorts in later CORTISONE scope CORTISONE patient data through NHS App-visible services Programme CORTISONE, HealthShare HealthShare Unified Care Record (UCR), Health Connect / Integration Platform, IRIS for Health, Enterprise Master Patient Index (EMPI), IM1, GP Connect Patient Facing APIs Not evidenced Current evidence now supports programme scope, InterSystems IP / EMPI and HealthShare / IRIS licence-package tracking, and InterSystems GP Connect supplier-progress touchpoints. Treat this as a candidate enablement route, not NHS App publication or feature availability. CORTISONE architecture, provider/source role, HealthShare / IRIS / Health Connect component mapping, IM1 / GP Connect / NHS API route, partner onboarding, patient cohort feature tests, and access-mode / proxy tests.

Use Rules

Validation Queue Mapping

Decision area Blocking evidence package Current queue relationship
Core national services Cohort and registration baseline Mobile account access, service-specific identity/eligibility, age/proxy handling, accessibility, fallback, and feature tests without unnecessary GP-system assumptions.
DPHC Firmbase baseline Cohort and registration baseline DPHC Firmbase registration, DPHC ODS model, GP supplier assurance, initial provision cohort matrix.
DPHC(O) baseline Cohort and registration baseline DPHC(O) cohorts, Defence Global Practice / DPHC(O), registration-state evidence.
Minors, dependants, proxy / linked profiles Cohort and registration baseline Under-13 own-access exclusion, under-13 proxy route, under-13 DMS / DPHC appointment-booking issue, 13-to-15 own/proxy access, dependants, linked profiles, and same-practice proxy rule.
SHC appointments Appointments route separation Patient Care Aggregator / Wayfinder appointment summary, PEP appointment or booking function, e-RS / connected NHS SHC appointment route, age/proxy behaviour.
DMICP PHC reminders Appointments route separation DMICP event/feed, adapter, NHS Notify sender/onboarding, template/routing, callbacks, fallback, reconciliation, safety, funding, parallel-run baseline, channel-transition criteria, recorded approval, and end-to-end test.
DMICP PHC visibility Appointments route separation DMICP feed, Patient Care Aggregator / PEP eligibility, Record Service and Get Appointments interfaces, NHS login, identity / organisation mapping, onboarding / assurance.
DMICP PHC management Appointments route separation Write-back, slot/schedule model, conflict handling, permissions, audit, route assurance.
Clinical correspondence Document and result route separation SHC provider document route, PEP document route, GP-filed document view, patient-facing display route.
Test results Document and result route separation GP-filed result view, PEP results-release route, provider results systems, clinical release controls, DPHC registration effect.
CORTISONE patient data CORTISONE / InterSystems integration CORTISONE architecture, HealthShare / Health Connect / EMPI role, IM1 / GP Connect PFS evidence, NHS App exposure.
Any route promoted to live guidance Assurance and onboarding Partner onboarding, clinical safety, data protection, technical assurance, information security, supplier/practice enablement.