Skip to content

GP Connect Patient Facing APIs Due Diligence

This page tracks due-diligence requirements for GP Connect Patient Facing APIs.

Use GP Connect Patient Facing APIs for the capability definition. This page is the implementation and assurance checklist.

Why It Matters

Patient Facing APIs are not the same as clinician-facing Access Record. They support approved patient-facing applications such as the NHS App for GP record, prescription, and permission-related functions, and NHS evidence describes specific current onboarding constraints.

NHS Implementation Controls

NHS evidence points to these checks:

  • Confirm whether the use case is patient-facing rather than direct-care clinician-facing access.
  • Confirm the NHS API Platform pattern and which Patient Facing API area is in scope: Access Record, Prescriptions, or User Permissions.
  • Confirm provider eligibility and onboarding state; NHS evidence says these APIs are currently available for New Market Entrant suppliers as data providers and are in use with the NHS App as consumer, with additional consumer suppliers not being onboarded at the time noted.
  • Confirm alignment with NHS App roadmap work around GP record access, linked profiles, record discovery, and download/share journeys.
  • Confirm patient consent, proxy/linked-profile, authentication, audit, and record-visibility handling with current NHS and supplier documentation.

Evidence Status

Confidence is high for NHS taxonomy and current constraint statements. This page does not prove InterSystems support or availability for a patient-facing use case.

Follow-up Evidence

  • Current NHS onboarding status for Patient Facing APIs.
  • Supplier evidence for patient-facing GP Connect data-provider support.
  • Customer or product evidence distinguishing patient-facing APIs from clinician-facing shared-record access.