Interoperability and GP Connect

This page applies the governance and legal questions to GP Connect's products, permitted uses and assurance conditions. Use NHS exchange mechanisms and standards for the wider technical landscape.

GP Connect offers useful patterns for clinical access and correspondence. Its published specifications do not establish approval for the proposed Defence service. The architecture must distinguish an internal implementation of a data standard from participation in a national service.

Current capabilities and constraints

The following assessment reflects official pages retrieved on 14 October 2026. Product availability, supplier support and approved uses require confirmation before implementation.

The first three capabilities are described on the Access Record page. Structured data may be imported and processed within its permitted purposes and assurance requirements. Describing all GP Connect access as view-only would therefore be inaccurate. Conversely, access is not an unrestricted copy of every lifetime record component. ⁰²²

These products support different interactions with the same GP record, which has both a source role and the primary record of care (PRC) role. A shared care view may use permitted access to show GP information alongside community or hospital information. Access alone does not update the GP record or establish acceptance of clinical work.

The main service page, updated 1 September 2026, closes new-developer onboarding for Update Record, Send Document and Appointment Management. Existing consumer suppliers can still onboard end users. This is an onboarding constraint, not an announcement that those live products have closed. ⁰²³

Updates enter a clinical workflow

NHS England's November 2025 FAQ limits Update Record assurance to Pharmacy First, Blood Pressure Check and Contraception services. Summaries create GP workflow tasks; optional automatic filing still creates a review task. Rejected messages do not notify the sender, while urgent actions require agreed direct communication. Pharmacy professionals remain responsible for their treatment decisions. These details illustrate why filing and clinical handover cannot be treated as equivalent. ⁰²⁴

The API catalogue describes FHIR STU3 payloads over ITK3 and MESH, with PDS, access-control and clinical-safety prerequisites. Its October 2025 invitation to submit onboarding use cases predates the September 2026 restriction. The newer statement should inform planning, with the current route confirmed by the service owner. ^{025, 023}

Assurance and purpose

GP Connect requires an assured system, applicable connection and acceptable-use agreements, and the National Data Sharing Arrangement. Consumer organisations retain responsibility for fitness for intended use and local clinical-risk management. Conformance with a message schema is only one part of this process. ⁰²⁶

The NDSA adds organisational conditions, including an appropriate supplier route, DSPT coverage for the applying ODS code, transparency and audit arrangements. Shared Care Records also need local governance. Existing organisational access does not establish permission for a different purpose, product or workflow. ⁰²⁷

Defence recruitment provides a concrete boundary. The NDG's 2023–24 report records a proposal to use GP Connect for candidate fitness-to-serve decisions. Despite proposed explicit consent, the NDG did not support this use because pre-employment decisions fell outside direct care. This is dated advice on that particular proposal, not a blanket prohibition on Defence clinical care. No later official reversal was established in this review. ⁰²⁸

Proposed Defence use

COPPER TIGER may evaluate compatible clinical data structures and document patterns. National-service use remains conditional on confirmation of the exact patient cohort, purpose, supplier, product and assurance route. Current public evidence does not establish a general Defence Update Record write-back service.

The expanded military clinical scope should therefore be mapped to specific flows before selecting a service. An aviation assessment, a treatment encounter and a command fitness report are distinct intended uses, even when they concern the same patient. The proposed permissions model identifies the decisions needed. ⁰³⁶

The design should preserve source provenance and distinguish direct care from recruitment, employment and command decisions. It should also separate access from primary-record continuity and from the clinical tasks attached to correspondence. These are design requirements requiring validation under the governance model, not claims of an existing exemption or approved deployment.

Continue with public Defence mechanisms to compare the proposed exchanges with dated evidence of actual use and explicit implementation unknowns.