Further Research Priorities
The wiki is intended to inform Defence Medical Command (DMedC) / Defence Primary Healthcare (DPHC) NHS App guidance for DPHC Firmbase patients, DPHC Overseas [DPHC(O)] patients, dependants, minors, proxy users, and linked-profile users. That guidance is the output this evidence base supports, not a research priority in itself.
Use Evidence Work Packages for the prioritised package view. This page remains the broader research-priority list.
- Core, profile, and national service entitlement after mobile account enablement: NHS Health A to Z, Find NHS services near you, NHS 111 online, NHS number/profile basics, current/change GP surgery, organ donation, National Data Opt-Out, research, vaccination, health checks, and messages, tested by DPHC cohort, field/data source, registration-transition effect, age, proxy, location, channel, eligibility, accessibility, and fallback.
- IRTB(P) decision inputs: current internal Defence / local staff-work instruction, security marking, staffing and approval route, DMedC owner, cohort scope, baseline demand, benefits measures, resources, affordability, commercial/technical roles, assurance ownership, and delivery plan. Public-source confirmation of the IRTB / IRTB(P) format family is complete (SRC-118 to SRC-121); do not keep researching whether the format exists unless a new current policy source appears.
- Phase evidence for NHS App adoption and implementation: initial provision, secondary healthcare (SHC) appointments, Defence Medical Information Capability Programme (DMICP) primary healthcare (PHC) appointment visibility, DMICP Primary healthcare (PHC) appointment management, clinical correspondence and test results, and later CORTISONE patient data.
- Programme Cortisone / CORTISONE technical architecture, including supplier system, DMICP appointment / diary feed handling, DMICP adaptation / evolution options, HealthShare Unified Care Record (UCR), Health Connect / Integration Platform evidence, Enterprise Master Patient Index (EMPI), NHS integration model, Interface Mechanism 1 (IM1), GP Connect scope, Spine Directory Service (SDS), NHS Notify, Patient Care Aggregator / Wayfinder, Personal Demographics Service (PDS)/Organisation Data Service (ODS) registration handling, and NHS App implications.
- NHS App feature-by-feature architecture map: public web, authenticated web, profile and national API services; NHS Health A to Z; Find NHS services near you; GP registration transition; GP records; online medical/admin requests; repeat prescriptions, prescription tracking/barcodes and nominated pharmacy; appointments, referrals, waiting times, messages, linked profiles, notifications, care plans/personal health records, Secondary healthcare (SHC) documents/results, and each lower interface/assurance path.
- GP Connect Patient Facing API, Interface Mechanism 1 pairing, partner-onboarding, and supplier-progress evidence for any DPHC-relevant clinical system.
- ODS and practice-code model for Defence Primary Healthcare practices and whether they are treated as GP practices in NHS App flows.
- Armed Forces Covenant annual-report follow-up, separating direct NHS App issue resolution from pre-2020 Defence Medical Information Service / Programme language, wider medical-record transfer, Programme CORTISONE / Op CORTISONE source wording, and MOD/NHS electronic-health-record evidence.
- Status update on the NHS App appointment-booking access issue for the source-defined Defence Medical Services (DMS) primary-healthcare cohort recorded in the 2024 Armed Forces Covenant report.
- Data-protection, clinical-safety, technical-assurance, information-security, and service-management evidence for DPHC patient access to NHS App features.