GP Connect Patient Facing APIs
GP Connect Patient Facing APIs support patient-facing access to GP services, including GP record access, repeat-prescription requests, and user permissions.
The GP Connect architecture route for patient-facing products uses the NHS API Platform. The GP Connect API uses the patient's NHS number to retrieve the registered GP from Personal Demographics Service (PDS) as an Organisation Data Service (ODS) code, can depend on Spine Directory Service (SDS) endpoint lookup in registered-GP booking / referral routes, routes the request to the provider, and returns the provider response to the consumer system.
Capabilities
| Capability | Source | DPHC question |
|---|---|---|
| Access Record | GP Connect Patient Facing Access Record | Can Defence Primary Healthcare (DPHC)-registered patients view DPHC GP record data? |
| Prescriptions | GP Connect Patient Facing Prescriptions | Can DPHC-registered patients request repeat prescriptions through the NHS App route? |
| User Permissions | GP Connect Patient Facing User Permissions | Are DPHC user permissions exposed and interpreted correctly? |
Due Diligence
For DPHC continuation and/or adoption, confirm:
- GP system supplier and API support.
- Practice-level ODS organisation identity, role, and onboarding.
- PDS registered GP behaviour.
- NHS App feature enablement.
- GP Connect enablement at practice and capability level.
- Whether any GP-system supplier route uses Interface Mechanism 1 (IM1) rather than, or as well as, a GP Connect Patient Facing API route.
- Any clinical-safety, data-sharing, or MOD policy constraints.
DPHC ODS Boundary
The current DPHC ODS / DGP pass strengthens the registration-context model but does not prove this GP Connect route. Current evidence identifies MOD / Defence Medical Services (DMS) organisation records and DGP-postcode candidate prescribing-cost-centre records, while simple active ORD name searches did not return a directly named Defence Global Practice or Central European Practice record.
For DPHC Firmbase and DPHC Overseas [DPHC(O)] decisions, treat those findings as candidate organisation context only. A GP-linked NHS App feature still needs PDS registered-GP state, practice-level ODS code and role, supplier and GP clinical-system evidence, GP Connect PFS capability enablement, proxy setup where relevant, and feature-test evidence.
Supplier Interface Boundary
Interface Mechanism 1 is a separate GP supplier interface route. NHS England Digital describes IM1 as API standards for integrating with principal GP clinical systems, including supplier-specific pairing and patient API functions such as appointments, repeat medication, prescription requests, medical-record viewing, and GP-practice communication. IM1 evidence therefore belongs in the lower interface layer. It should not be treated as proof that GP Connect Patient Facing APIs are enabled for a DPHC practice, or that NHS App GP-linked features work for DPHC-registered patients.