Skip to content

Core National Services and Roadmap

The NHS App presents more than GP-linked records, prescriptions, and appointments. It also gives users a route to national health information, urgent-care triage, local service finding, health choices, research participation, vaccination services, profile functions, and other nationally managed capabilities. This page is the project's user-facing capability catalogue as well as its core-service and roadmap synthesis. NHS England's current step-by-step guidance states that people registered at a Defence Medical Services (DMS) surgery cannot use the mobile NHS App; these services therefore strengthen the case for Defence Primary Healthcare (DPHC)-registered patient access even before a DPHC clinical-system integration is available (SRC-095 to SRC-106, SRC-114 to SRC-117).

Terminology Boundary

Use core national services for the national information, guidance, signposting, profile, health-choice, research, prevention, and messaging functions that do not require a DPHC clinical-system connection. Use NHS App-presented services as the broader technical term for everything visible through the App, including GP-linked, provider, and partner functions. Do not use native as a synonym for either group:

  • the mobile NHS App uses a hybrid architecture and presents API integrations, responsive web integrations, and links to external services;
  • native code in the current NHS App roadmap refers specifically to iOS and Android implementation work;
  • NHS.UK health advice and guidance is public patient information, while e-Referral Service Advice and Guidance is a professional-to-professional referral workflow.

Use the current user-visible labels where they exist:

  • NHS Health A to Z for the App's health-conditions, symptoms, treatments, and medicines information route;
  • Find NHS services near you for the NHS Service Search journey;
  • Check symptoms using NHS 111 online for the urgent-care triage journey.

Current User-Facing Capability Map

The 2026 NHS App groups its main experience into Home, Messages, and Profile. The catalogue below prevents the project from reducing the App to GP records and appointments while keeping unlike routes separate (SRC-114 to SRC-116).

Current App area User-visible capabilities Evidence and dependency boundary
NHS information and support Check symptoms using NHS 111 online; NHS Health A to Z; Find NHS services near you Public or authenticated national web routes. Mobile App access is the DPHC barrier, but the underlying services retain their own age, location, eligibility, and fallback rules.
Home health and care Prescriptions; appointments; appointment notes; test results; vaccinations; health conditions, allergies and adverse reactions; documents A mixture of GP-system, national, provider, and campaign routes. The same screen location does not establish the same source, release control, or DPHC availability.
Messages NHS App messages, NHS Notify messages, provider communications, reminders, invitations, and digital letters where onboarded Sender/provider onboarding, contactability, notification settings, suppression, fallback, proxy behaviour, and message provenance remain service-specific.
Profile NHS number; contact details; home address; current GP surgery; health choices; App settings; family and carer access; care plans where an integrated service supplies them Some profile data is national/account data, some comes from NHS records or a GP practice, and some is supplier/provider-specific. View and change permissions are not equivalent.
Connected requests and partner services Ask a GP about a health problem; request a letter, fit note, test-result information or referral; hospital referrals, waiting lists, documents and questionnaires; personal health records, care plans, trackers, and video/online consultations where integrated GP, provider, Patient Care Aggregator / Wayfinder, e-RS, Patient Engagement Portal (PEP), online-consultation, or personal-health-record routes. Availability depends on the named supplier and organisation.

Core National Service Baseline

Service User outcome NHS App route DPHC relevance and boundary
NHS Health A to Z Read clinically maintained information about conditions, symptoms, treatments, medicines, healthy living, and next steps. Public responsive web integration; NHS login is not required for the public content. Useful without a GP-system dependency. The content remains available on the public web, but current DPHC mobile NHS App exclusion removes the integrated App journey.
Find NHS services near you (NHS Service Search) Find dentists, pharmacies, hospitals, urgent-care services, GP surgeries, and other NHS services using postcode or device location, with address, contact, opening-time, distance, and some acceptance information. Public web integration with NHS service data; NHS login is not required at the public-content layer. Particularly relevant to mobile families, postings, unfamiliar locations, and transitions. Search results do not prove eligibility, entitlement, capacity, acceptance, or that a DPHC route is represented.
NHS 111 online Complete urgent-care triage and receive advice on the appropriate next action or locally commissioned service. Responsive web integration from the NHS App with NHS login credential hand-off. NHS Pathways supplies the clinical triage logic and the Urgent and Emergency Care Directory of Services supplies local service options. Provides a national urgent-care route for people in England aged 5 or over. It does not diagnose, replace 999, or prove DPHC appointment access. The public website remains an alternative route.
Organ donation decision Make, check, confirm, or change an organ donation decision. API integration with the NHS Blood and Transplant Organ Donation API. The decision is recorded on the NHS Organ Donor Register. A national health-choice function rather than a GP-linked function. The NHS App is a presentation and transaction route; the Organ Donor Register is the authoritative record.
National Data Opt-Out View or change whether confidential patient information can be used for research and planning. NHS App-presented web route; the choice is recorded against the NHS number on Spine. A national information-rights function. Own digital choice starts at age 13; parent or legal-guardian handling for a child under 13 uses a non-digital route in the reviewed guidance.
Be Part of Research Register interest in health and care research and receive study information. Web integration with the National Institute for Health and Care Research service and NHS login credential hand-off. A national participation route. Availability through the NHS App should be tested separately from GP-linked service availability.
Vaccination services Receive invitations and, where eligible, open national vaccine booking and record services. Authenticated web integrations, supported by NHS App messages or notifications. Eligibility, campaign scope, age, location, and service rollout remain service-specific.
Digital NHS Health Check Complete an online health-check journey where the service is available. Web integration, currently described as a pilot in the technical specification. Prevention value is relevant to the business case, but pilot or local availability must not be generalised to all DPHC cohorts.
NHS App messages Receive national or provider communications, reminders, and invitations. NHS App API and NHS Notify routes. Potentially reduces dependence on SMS and letters, but Defence Medical Command (DMedC) / DPHC sender onboarding, contactability, fallback, and restricted-record handling remain unproven.
NHS number and profile basics View NHS number, contact details, home address, current GP surgery, health choices, and App settings; change only the fields and settings supported by the relevant route. NHS account/Profile presentation drawing on NHS login, Personal Demographics Service (PDS), GP-record, and service-specific data. Valuable for identity, continuity, and support, but view, correction, and change rights differ. Address-change rollout and proxy behaviour must not be generalised.
View or change GP surgery View the currently recorded GP surgery and, where applicable, apply through the connected Register with a GP surgery service. Connected national web service using NHS login where chosen, NHS-record matching, practice catchment and acceptance, Personal Demographics Service (PDS), Primary Care Registration Management (PCRM), GP2GP, and NHS Notify. Important for transition into or out of DPHC care. Primary Care Registration Management (PCRM)'s stated service coverage includes DMS, but this must not be presented as proof that a DPHC practice is an ordinary NHS GP practice or that a DPHC cohort has mobile NHS App access. Proxy users cannot currently use the reviewed change-GP journey for another person.

The NHS 111 online service is live, supported continuously, and uses the same NHS Pathways triage algorithm as the telephone service. It is intended for urgent but not life-threatening needs and can direct users to emergency care, urgent treatment, out-of-hours general practice, nurse callback, specialist dental or mental-health support, pharmacy, the user's own GP surgery, or self-care. This is not the same as a DPHC triage, appointment, or booking route.

Capabilities Requiring Separate Route Evidence

The following current NHS App functions add business-case value but should remain on their existing specialist pages rather than being relabelled as core national services:

Capability group Included functions Controlling route distinction
Prescriptions and pharmacy View medicines; request repeat prescriptions; see request or dispensing status where supported; use a prescription barcode; view or change a nominated pharmacy GP-system request route, Electronic Prescription Service (EPS) status/barcode, Personal Demographics Service pharmacy nomination, pharmacy participation, proxy limits
GP contact and administration Ask about a health problem; send a non-urgent request; request a letter, fit note, test-result information, referral, or other administrative support Named online-consultation supplier, NHS login hand-off, GP practice configuration and workflow
GP health information Appointment notes, medicines, test results, vaccinations, health conditions, allergies/adverse reactions, and documents GP record scope, prospective/detailed record permissions, supplier route, clinical release and safeguarding controls
Secondary and specialist care Referrals, provider choice, appointments, waiting-time information, resources, letters, documents, questionnaires, results and patient-initiated follow-up where supported e-RS, Patient Care Aggregator / Wayfinder, provider system, PEP function, age threshold, provider onboarding and release control
Personal health records and partner tools Care plans, messaging with care teams, health trackers, patient-contributed data, medicines, documents, test results or imaging, and video/online consultations where integrated Named integrated partner and product; these are not universal NHS App functions
Family and carer access Switch profile and use the subset of GP services granted for another person; limited electronic proxy application where trialled Same-practice relationship, GP approval, permission scope, age/capacity/safeguarding, supplier support; many provider and national services remain unavailable through proxy

Integration View

%%{init: {"themeVariables": {"fontSize": "11px"}, "flowchart": {"nodeSpacing": 18, "rankSpacing": 24}, "sequence": {"actorFontSize": 11, "messageFontSize": 11, "noteFontSize": 11}}}%%
flowchart LR
  App["NHS App"] --> Public["Public content<br/>Health A to Z / Find services"]
  App --> Web["Authenticated web<br/>111 / research / vaccines"]
  App --> API["National APIs<br/>organ donation / messages"]
  App --> GP["GP and provider routes<br/>records / appointments / portals"]

The service route matters. Public content can be used outside the NHS App; authenticated web and API services require the applicable account, identity, eligibility, or source-system state; GP and provider services add local supplier, organisation, onboarding, and clinical-release dependencies.

Roadmap Direction

Official sources describe four related but distinct roadmap layers:

  1. NHS App delivery roadmap. Current work includes AI-assisted triage, patient-initiated follow-up, invite-to-book models, improved referral status, wider prescription tracking, combined test-result views, record download/sharing, a single inbox, improved proxy/profile control, passkeys, and GP Connect Patient Facing API support. These are time-sensitive intentions, not proof of DPHC availability.
  2. NHS.UK 2026/27 roadmap. Health advice and guidance is being made more structured, reusable, and personalised, with more seamless movement between NHS.UK, the NHS App, self-referral, and service-finding journeys.
  3. NHS medium-term implementation direction. NHS England expects wider adoption of existing NHS App capabilities, migration of direct-to-patient communications to NHS Notify, unified digital triage, and integration of core national products during 2026/27 to 2028/29.
  4. Ten Year Health Plan direction. The NHS App is intended to become a fuller front door to advice, appointments, communication, care plans, self-referral, prevention, and urgent-care access. The plan describes strategic intent to 2028 and beyond, not current service entitlement.

Recent release notes provide a narrower live-change signal. July 2026 releases expanded organ-donation confirmation and added NHS 111 urgent-advice signposting to error pages. Release notes show that capability changes incrementally and must be rechecked before publication or implementation decisions.

Business-Case Value

Enabling DPHC-registered patients to use the mobile NHS App is not only a request for parity with an ordinary NHS GP practice. It is also a route to:

  • trusted advice, urgent-care triage, and service finding;
  • NHS number, profile, current-GP, health-choice, support, and notification functions;
  • national health choices and information rights;
  • prevention, vaccination, health-check, and research opportunities where eligible;
  • national and provider messaging through a preferred NHS digital channel;
  • connected GP requests, pharmacy journeys, provider care, and personal-health-record functions where the named route is enabled;
  • continuity when patients move between NHS and MOD DPHC Firmbase or DPHC Overseas [DPHC(O)] care models;
  • future national digital-front-door capabilities without requiring every function to be built into Programme Cortisone.

These are potential benefits, not automatic outcomes. The implementation case must still prove mobile NHS App account access, age and proxy handling, service-specific eligibility, accessibility, assisted-digital and offline alternatives, data protection, clinical safety, support, and measurement.

IRTB(P) priority

For the IRTB(P), core national services are the access foundation rather than a secondary benefit. They should be followed by appointment information and messages from participating NHS providers in England, where relevant to a DPHC patient's care, as the critical initial provider-connected function. A project-owner-validated internal DMSR analysis identified Defence-related causes in 84% of the reviewed external-referral delay cases, including inaccurate contact details and delays passing appointment information to patients. Use that figure only within its reviewed-case scope and as supporting evidence for the appointment-communication priority.

These services form the immediate patient-value case. After mobile access is enabled, each should be tested independently and should not wait for DPHC clinical-system integration unless its documented route requires it. Existing public, telephone, paper, and assisted-digital alternatives remain part of the service.

Official NHS evidence supports the direction of that priority. By April 2026, every acute trust was connected to the NHS App secondary-care route, 64% of hospital appointments were visible nationally, and around half of trusts could send appointment reminders using NHS App push notifications. This does not prove visibility for every DPHC patient, but it makes the existing NHS provider route the first appointment capability to test.

The next bounded DPHC opportunity is Firmbase appointment reminders. A candidate route would take a documented Defence Medical Information Capability Programme (DMICP) appointment event/feed through a controlled adapter and NHS Notify for NHS App messaging and fallback delivery. Initial operation should run alongside the current DMICP SMS reminder route. NHS App messages could later become the primary route and replace routine SMS for defined cohorts only if delivery, reconciliation, accessibility, support, safety, cost, exception handling, and fallback evidence supports a separate recorded decision. Programme Cortisone / Health Connect is one possible adapter, not the selected design. Patient Care Aggregator / Wayfinder plus a PEP is the separate route for appointment summaries and detail, and current public onboarding is written for secondary-care booking systems. More complex DPHC appointment management and clinical-data functions require dedicated funded work and NHS collaboration.

  • Treat mobile NHS App access and core national services as a distinct implementation objective from DPHC GP-linked feature integration.
  • Use NHS Health A to Z and Find NHS services near you in user-facing material, with health advice and guidance and NHS Service Search retained as content/service architecture terms.
  • Use a capability-by-capability entitlement test after account enablement; do not assume that one successful national service proves every other service.
  • Treat view/change GP surgery as a governed registration-transition function for DPHC cohorts, not an automatic benefit or evidence of DPHC practice equivalence.
  • Preserve public web, telephone, paper, and assisted-digital alternatives so the NHS App does not become the only safe route.
  • Introduce DMICP reminders alongside current SMS; move to App-first delivery or replace routine SMS only for defined cohorts after an evidenced and approved channel-transition decision.
  • Measure activation, successful task completion, channel shift, urgent-care routing, message-read rates, support demand, proxy outcomes, and equity by DPHC cohort.
  • Recheck roadmap and release-note sources before each formal IRTB(P), assurance, or implementation decision.