Prescriptions and Pharmacy

Prescription journeys in the NHS App should not be collapsed into a single dependency. GP Connect Patient Facing Prescriptions supports patient-facing repeat-prescription requests. The Electronic Prescription Service (EPS) is a separate national prescription infrastructure and has its own FHIR API context.

Interface Mechanism 1 (IM1) is also relevant to prescription analysis because the IM1 Patient API evidence includes repeat-medication viewing and repeat-prescription request functions where specified by the GP practice. Treat that as a supplier-interface route, not as proof that GP Connect PFS or EPS is enabled for Defence Primary Healthcare (DPHC) patients.

Working Split

Step	Evidence route	DPHC issue
Patient requests repeat prescription	GP Connect Patient Facing Prescriptions	Does the DPHC GP system expose the API and workflow?
Patient uses a supplier-specific patient-facing route	Interface Mechanism 1 Patient API	Does the DPHC GP supplier and practice configuration support the relevant patient API functions?
Prescription is issued and dispensed	EPS and prescribing/dispensing systems	Does DPHC prescribing use ordinary EPS routing, MOD-specific routes, or a hybrid?
Patient manages nominated pharmacy	NHS App / EPS context	Does registration with DPHC affect nomination or dispensing visibility?

The current wiki has enough evidence to separate GP Connect PFS from EPS, but not enough to define DPHC prescription feature availability.