GP Connect Update Record

This page tracks GP Connect Update Record as a distinct capability.

Supported Conclusion

Update Record is a distinct write-back capability and needs to be treated separately from Send Document. NHS England Digital describes it as an integration for updating a patient's GP record from a community pharmacy with structured data.

Approved Scope

The approved scope is narrower than the generic phrase "update a GP record" suggests. NHS England Digital says the integration has only been approved for community pharmacy use cases, giving examples such as a pharmacy informing the GP that a patient has been prescribed antibiotics, had their blood pressure checked, or been prescribed contraceptive medication.

Architecture Pattern

The architecture pattern is GP Connect Messaging over MESH. Each message uses GP Connect Messaging components, MESH, ITK3, and a FHIR STU3 message payload using the GP Connect data model. Technical prerequisites include HSCN or internet access for ITK3 messages over MESH, MESH API compliance or MESH client access, ITK3 compliance, and PDS capability. Information-governance and clinical-safety prerequisites include GP Connect Direct Care API IG compliance, local RBAC, direct-care use, and a clinical safety officer responsible for DCB0129 and, where needed, DCB0160.

Standards Directory Boundary

Update Record is standards-adjacent because it uses the MESH / ITK3 / FHIR STU3 messaging pattern, but it should not be inferred from GP Connect Send Document, Access Record, Access Document, or generic MESH API evidence. The current wiki keeps Update Record on this capability page and in the due-diligence mirror; the NHS Standards Directory GP Connect, MESH, and ITK3 page records it as an adjacency and role-split issue rather than treating it as proof of InterSystems support.

Operational Boundaries

NHS England Digital lists the integration as in production but notes that it might not be fully supported by all providing systems. It uses MESH as a silver service and the GPCONNECT_UPDATE_RECORD workflow ID. The integration itself does not perform end-user authentication or authorisation checks; the calling system is expected to perform them.

Roadmap and Future Updates

Contemporary NHS sources reinforce that Update Record is a controlled pharmacy-to-GP workflow rather than a general-purpose GP record update API. NHS England Digital's service-facing GP Connect: Update Record page says the capability has been technically and clinically assured between community pharmacy and general practice for Pharmacy First, Blood Pressure Check, and Pharmacy Contraception services. It identifies EMIS and TPP as the GP clinical-system suppliers and Cegedim Healthcare Solutions, EMIS Pinnacle, Positive Solutions, and Sonar Informatics as the community pharmacy suppliers assured for this use at the time of the page.

The current GP Connect specifications for developers directory lists a GP Connect Update Record release dated 8 May 2026 with 1.2.1-public-beta release notes, API test suite, and implementation guide artefacts. The May 2026 GP Connect transparency appendix expands the data-item picture for Update Record around pharmacy consultation information, patient information, medicines, presenting complaint, observations, service information, and consent/visibility constraints. Use GP Connect Roadmap and Future Updates for the wider roadmap context across supplier progress, NCRS pilots, NHS App patient-facing APIs, and Single Patient Record direction.

Evidence Status

Evidence status is high for the NHS API/integration definition and scope. It does not prove InterSystems support, supplier rollout, local pharmacy enablement, or configured deployment in any named programme.

Follow-up Evidence

GP Connect supplier progress for Update Record provider and consumer support, especially changes after the 5 June 2026 NHS supplier-progress snapshot.
Current InterSystems documentation mapping Health Connect or HealthShare to Update Record MESH/ITK3 routing.
Customer-side evidence for live pharmacy write-back use.