Skip to content

GP Connect Professional APIs

GP Connect is an NHS service for authorised health and care systems to access GP record information for direct care. GP Connect architecture material distinguishes patterns using Spine Secure Proxy (SSP), Message Exchange for Social Care and Health (MESH), and NHS API Platform routes. Access Record Structured is a professional API with controls and prerequisites including Spine Secure Proxy patterns.

Official GP Connect non-functional requirements also make enablement a local control point: provider systems must allow the practice data controller to disable or enable GP Connect globally and by individual assured capability, with capabilities deployed disabled by default.

Why It Is Separate from Patient Facing APIs

Professional GP Connect APIs are not the same as GP Connect Patient Facing APIs. They answer different use cases, use different assurance and access models, and should not be used as proof that the NHS App can show the same data to a patient.

DPHC Questions

  • Do Defence Primary Healthcare (DPHC) clinicians consume GP Connect professional APIs?
  • Do NHS clinicians consume DPHC GP data through GP Connect professional APIs?
  • Does Programme Cortisone expose or consume professional GP Connect APIs?
  • Does professional API availability imply anything about patient-facing availability? Treat this as unproven until sourced.
  • Which data controller, supplier, and practice-level enablement choices apply to DPHC Firmbase and DPHC Overseas [DPHC(O)] routes?