NHS App Service Overview
The NHS App is a patient-facing digital route into NHS services, accessed with an NHS account. NHS England states that people registered at a Defence Medical Services (DMS) surgery cannot currently use it. NHS England Digital roadmap material describes ongoing work across urgent-care triage, health information, GP records, prescriptions, appointments, referrals, linked profiles, messages, and integrated services.
For this project, NHS App functions should be separated into four practical groups, with route families kept visible inside each group:
| Group | Examples | DPHC relevance |
|---|---|---|
| Account, profile and identity | NHS account, NHS login, identity proofing, NHS number, contact details, home address, current GP surgery, view/change GP surgery, App settings, own access, minors, linked profiles, proxy access | Determines whether the user can sign in, see or change supported profile data, and act for themselves or others. A GP-surgery change adds practice acceptance, PCRM, Personal Demographics Service (PDS), GP2GP, transition, and continuity controls. View, correction, change and proxy permissions must remain distinct. |
| Core and national services | NHS Health A to Z, Find NHS services near you, NHS 111 online, organ donation, National Data Opt-Out, Be Part of Research, vaccination services, digital health checks | Uses public web, authenticated web, national API, or NHS login routes. These functions must not be made dependent on Defence Primary Healthcare (DPHC) GP-system integration where the official architecture does not require it. |
| GP-linked services | GP records, GP-filed document views, GP-filed result views, medicines, repeat prescriptions, prescription requests, nominated pharmacy, GP appointments, online medical and administrative requests, GP permissions | Most likely to depend on registered GP practice, GP system, PDS, Organisation Data Service (ODS), GP Connect PFS or Interface Mechanism 1 (IM1), online-consultation supplier, Electronic Prescription Service (EPS), supplier configuration, and practice enablement. |
| National, provider or partner services | Messages, Secondary healthcare (SHC) appointments, referrals, waiting-list information, provider documents and questionnaires, provider results, care plans, personal health records, health trackers, online/video consultations, Patient Care Aggregator / Wayfinder, Patient Engagement Portals (PEPs), NHS App integrations | May depend on NHS Notify, Patient Care Aggregator / Wayfinder, e-RS, provider systems, Patient Engagement Portal (PEP) route functions, personal-health-record suppliers, or other onboarded services rather than the DPHC GP system alone. |
Use Core National Services and Roadmap for the non-GP service baseline and strategic direction. Use Service Architecture for the service-layer diagrams that connect these groups to account access, GP-linked dependencies, and national / provider service routes. Use Interface and Assurance Layer for the lower implementation routes, including Spine Directory Service (SDS), Interface Mechanism 1, NHS Notify API / Message Exchange for Social Care and Health (MESH), Patient Care Aggregator / Wayfinder integration APIs, and partner onboarding.
Do not collapse route-family evidence. A PEP appointment or booking source does not prove a PEP document route or PEP results-release route. A GP-filed document view does not prove a GP-filed result view. Each route family needs its own source, cohort, access-mode, release-control, onboarding, and DPHC registration evidence.
Current Priority
The highest-priority task is to map each NHS App function to the NHS service or API that supplies it, then test whether mobile account access, service-specific eligibility, or DPHC registration satisfies that dependency. Do not require GP-system evidence for a public or national service unless the official route actually uses the GP system.
The immediate implementation conclusion is to enable mobile access for defined cohorts and validate standard App-presented services independently. NHS-side SHC journeys follow through existing provider routes. A one-way DPHC Firmbase reminder is a separate bounded workstream; Primary healthcare (PHC) appointment inventory, management, and wider clinical-data integration remain later capabilities.