Skip to content

DMedC NHS App Overview

This wiki sets out how Defence Medical Command (DMedC) can introduce mobile NHS App access and selected functionality for Defence Primary Healthcare (DPHC)-registered patients. It begins with standard App-presented services and existing NHS provider routes, then considers bounded DPHC-specific messaging and later clinical integration.

Start with Guidance Decision Model for the current decision status and Registration State Model for cohort classification.

NHS England states directly that people registered at a Defence Medical Services (DMS) surgery cannot currently use the mobile NHS App. The implementation questions are how to change that position for defined cohorts and how each service route treats DPHC registration, age, proxy, source-system, provider, and assurance dependencies. GP-linked functions add registered-practice, GP-system, Organisation Data Service (ODS), Personal Demographics Service (PDS), Spine Directory Service (SDS), GP Connect Patient Facing API, Interface Mechanism 1 (IM1), and practice-enablement questions. Minors, dependants, and carers add age bands, proxy setup, same-practice rules, and the distinction between own and linked-profile access.

Working Thesis

DPHC NHS App introduction is a patient-service, access, architecture, and assurance programme, not just an app-installation task.

The controlling delivery horizons are:

The Phase 0-6 model on NHS App Adoption and Implementation remains a technical route catalogue, not a mandatory dependency chain.

%%{init: {"themeVariables": {"fontSize": "11px"}, "flowchart": {"nodeSpacing": 18, "rankSpacing": 24}, "sequence": {"actorFontSize": 11, "messageFontSize": 11, "noteFontSize": 11}}}%%
graph TD
  User["DPHC-registered patient"] --> Account["NHS account / NHS login"]
  Account --> Access["DPHC mobile access gate"]
  Access --> App["NHS App"]
  App --> Standard["Standard App-presented services"]
  App --> GPLinked["GP-linked services"]
  App --> ProviderServices["Provider and national services"]
  GPLinked --> PDS["PDS registered GP context"]
  GPLinked --> ODS["ODS organisation identity"]
  GPLinked --> GPPFS["GP Connect Patient Facing APIs"]
  GPPFS --> GPSystem["GP clinical system"]
  ProviderServices --> PCA["Patient Care Aggregator\n/ Wayfinder"]
  PCA --> ERS["e-RS"]
  PCA --> PEP["Patient Engagement Portals"]
  ProviderServices --> Notify["NHS Notify"]
  Notify --> PDS
  ProviderServices --> SHC["SHC appointments / correspondence"]
  SHC --> PCA
  DPHC --> Reminder["DMICP appointment event / feed"]
  Reminder -. "candidate" .-> Adapter["Controlled adapter"]
  Adapter -. "candidate" .-> Notify
  DPHC --> DMICPVisibility["DMICP PHC appointment visibility"]
  DMICPVisibility -. "feed and NHS-facing route evidence needed" .-> GPLinked
  DPHC -. "management likely not available on current evidence" .-> DMICPManagement["DMICP PHC appointment management"]
  DMICPManagement -. "write-back evidence needed" .-> GPLinked
  DPHC["DPHC practice / MOD system"] -. evidence gap .-> GPSystem
  Cortisone["Programme Cortisone"] -. "candidate enablement" .-> Adapter
  Cortisone -. integration unknown .-> GPLinked

Evidence Boundary

The current no-access position is directly evidenced. The remaining boundaries concern the enabling route, service-by-service outcomes, and feature availability for DPHC Firmbase adults, DPHC Overseas [DPHC(O)] patients, dependants, minors, and linked-profile users.

See NHS App Adoption and Implementation for the staged adoption roadmap and CORTISONE / InterSystems cross-deck reading.