Evidence Boundaries and Risks
Evidence Boundaries
- Public NHS App eligibility does not automatically resolve Defence Primary Healthcare (DPHC) registration.
- Public NHS child and proxy-access rules do not automatically resolve DPHC minors, dependants, same-practice proxy constraints, or split ordinary NHS GP / DPHC family registrations.
- GP Connect Patient Facing API availability does not automatically prove local DPHC feature availability.
- Professional GP Connect API support does not automatically prove patient-facing NHS App support.
- Interface Mechanism 1 (IM1), Message Exchange for Social Care and Health (MESH), NHS Notify API, or partner-onboarding evidence does not automatically prove DPHC patient-facing NHS App feature availability.
- Programme Cortisone integration with the NHS does not automatically mean NHS App integration.
- A Defence Medical Services (DMS) / DPHC appointment-booking issue in one source-defined cohort does not automatically apply to adults or all DPHC patient groups.
- Armed Forces Covenant annual reports are authoritative for reported issues and programme status, but they are not NHS App feature specifications.
- The direct annual-report NHS App evidence is currently a 2024 appointment-booking access issue for a source-defined child cohort; the broader 2012 to 2025 report-series evidence is NHS App-adjacent digital-health, continuity, and interoperability evidence.
Risks
| Risk | Impact | Mitigation |
|---|---|---|
| Over-generalising from ordinary NHS GP registration | Incorrect patient guidance or service design | Require DPHC-specific source evidence. |
| Treating roadmap items as live features | Operational mismatch | Recheck NHS roadmap and API status. |
| Confusing GP Connect professional and patient-facing APIs | Wrong architecture assumptions | Keep API pages separate and capability-specific. |
| Collapsing supplier interfaces and national routes | False confidence that a component exists end-to-end | Map each feature to NHS App integration, GP Connect, IM1, NHS Notify, MESH, Patient Care Aggregator / Wayfinder, Patient Engagement Portal (PEP), Electronic Prescription Service (EPS), e-RS, and partner-onboarding evidence separately. |
| Ignoring minors, dependants, and proxy access | Missed safeguarding, consent, capacity, and same-practice constraints | Track own access, linked profiles, proxy setup, age boundaries, and dependant registration explicitly. |
| Ignoring DPHC Overseas [DPHC(O)] cohorts | Incomplete armed-forces coverage | Track Defence Global Practice and DPHC(O) separately from DPHC Firmbase. |