Skip to content

GP Connect Update Record Due Diligence

This page tracks due-diligence requirements for GP Connect Update Record.

Use GP Connect Update Record for the capability definition. This page is the implementation and assurance checklist.

Why It Matters

Update Record is easily overread as a general GP record write-back capability. Current DSIC evidence makes S102 an effective standard across four contracting vehicles, while NHS API/service evidence frames the publicly assured clinical use as controlled community-pharmacy to general-practice workflows. The broader standard surface does not replace use-case approval or supplier assurance.

NHS Implementation Controls

NHS evidence points to these checks:

  • Confirm that S102 v1.0.3 is the applicable standard, identify the contracting vehicle, and record whether the solution is sender, receiver, or both.
  • Confirm the workflow is within the approved community-pharmacy scope, including Pharmacy First, Blood Pressure Check, or Pharmacy Contraception services where relevant.
  • Confirm MESH, GP Connect Messaging components, ITK3 compliance, FHIR STU3 payload handling, PDS or Spine Mini Services, and the GPCONNECT_UPDATE_RECORD workflow ID.
  • Confirm whether the GP and community-pharmacy suppliers are assured for the relevant service at the time of deployment.
  • Confirm local RBAC, GP Connect Direct Care API IG compliance, clinical-safety ownership, DCB0129, and any required DCB0160 responsibilities.
  • Confirm operational handling for message failure, fallback, filing, visibility, consent, and pharmacy consultation data items.

Evidence Status

Confidence is high for the DSIC standard, role/dependency model, NHS prerequisites, and service-facing constraints. This page does not prove a DMICP/CORTISONE approved use case, InterSystems support, supplier rollout, or a live write-back deployment.

Follow-up Evidence