GP2GP
ID | S43 |
Version | 6.0.1 |
Type | Standard |
Status | Effective |
Effective Date | Dec 4, 2025 |
Contracting Vehicle(s) |
Introduction
The GP2GP record transfer mechanism enables an Electronic Patient's Record (EPR) to be electronically transferred directly and securely when they move from one Practice to another.
Requirements
Applicable Suppliers | ID | Description | Level |
Suppliers of Solutions which ARE currently deployed into an operational environment, and have implemented GP2GP HL7. | GP2GP00 | GP2GP 1.1a Suppliers must meet the requirements for GP2GP 1.1a | MUST |
GP2GP01 | GP2GP 2.2a Suppliers must meet the requirements for GP2GP 2.2a  | MUST | |
GP2GP02 | Available Documentation Suppliers must make available documentation to ensure that suppliers receiving GP2GP messages are fully able to interpret, consume and process the data to minimise data loss and degradation. This must include (but is not limited to):
| MUST | |
GP2GP03 | Receivers of GP2GP Messages Suppliers must provide support to receivers of GP2GP messages to resolve any issues with interpreting, consuming and processing received messages | MUST | |
GP2GP04 | GP2GP 2.2b Suppliers must meet the requirements for GP2GP 2.2b and GP2GP Automatic Integration Specification v1.0 | MUST | |
GP2GP05 | Management Information Suppliers must implement and maintain the GP Registrations Management Information API inline with the latest specification version | MUST | |
GP2GP06 | Suppliers must meet the requirements for GP2GP Redactions v1.01 The new Schema definition file to be consistent with the following Schema version: | MUST | |
| GP2GP07 | GP2GP FHIR Implementation - GP2GP Sending Adaptor Implement and maintain the GP2GP Sending Adaptor inline with the latest Standard version | MUST |
GP2GP08 | GP2GP FHIR Implementation - GP2GP Requesting Adaptor Implement and maintain the GP2GP Requesting Adaptor inline with the latest Standard version | MUST | |
GP2GP09 | Management Information Suppliers must implement and maintain the GP Registrations Management Information API inline with the latest specification version | MUST |
Compliance and Assurance
GP2GP FHIR Implementation
See the GP2GP (including GP2GP Sending Adaptor/GP2GP Requesting Adaptor) section on Onboarding Overview of the Digital Care Services Interoperability Standards and Requirements.
GP2GP HL7
For Suppliers of Solutions which ARE currently deployed into an operational environment and have implemented GP2GP HL7:
The compliance baseline for GP2GP and document locations were correct at the time of original publication, but referenced documents can now be found embedded on this page, below. The exceptions to this are the references to the NHS Messaging Implementation Manual (MIM) and External Interface Specification (EIS) (follow these links for details).
The GP2GP assurance is split into 2 streams:
Compliance testing - this tests the spine messaging patterns and functionality
Interoperability Testing - the testing of the clinically semantic testing of the message payload between different systems
For advice and support on assurance please contact businesspartners@nhs.net or visit https://digital.nhs.uk/services/nhs-business-partners
Documentation
GP2GP FHIR Implementation
For Suppliers of new Solutions and Solutions that have implemented the GP2GP FHIR Implementation:
GP2GP HL7
For Suppliers of Solutions which ARE currently deployed into an operational environment and have implemented GP2GP HL7:
Message Fragments and Examples
Supplementary specifications
The following supplemental specifications contain additional requirements and guidance for GP2GP implementation:
NPFIT-PC-BLD-0069 24 GP2GP Spine Technical Design v7.1.pdf
NPFIT-PC-BLD-0083.08 GP2GP Response Codes.pdf
NPFIT-PC-BLD-0099.04 GP2GP Handling Missing Attachments.pdf
NPFIT-PC-BLD-0132.03 GP2GP Supplementary Specification on Structured Degrade Handling.pdf
NPFIT-PC-BLD-0134.05 GP2GP Supplementary Specification Representing PMIP Data in GP2GP Messages.pdf
NPFIT-PC-BLD-0158 GP2GP Supplementary Specification Attachment References.pdf
NPFIT-PC-BLD-0163.02 Topic and Category Handling in GP2GP.pdf
NPFIT-PC-BLD-0170.03 GP2GP SS Handling Large Messages.pdf
NPFIT-PC-BLD-0172.02 GP2GP UC1 Transfer Electronic Health Record.pdf
NPFIT-PC-BLD-0175.03 GP2GP SS Handling A-B-A Transfers v1.3.pdf
NPFIT-PC-BLD-0177.01 GP2GP SS User Experience.pdf
NPFIT-PC-BLD-0178 02 GP2GP Coding Scheme Translation v1.1.pdf
NPFIT-PC-BLD-0180.02 GP2GP Transfer of Patient Facing Service Settings 04.pdf
NPFIT-PC-BLD-181.02 GP2GP Handling the SCR indicator v03.pdf
NPFIT-FNT-TO-IG-DES-0115.01 Statement on Data Retention v1.0.pdf
NPFIT-FNT-TO-TAR-0017.07 Compliance Requirements for Patient Registration.pdf
NPFIT-FNT-TO-TIN-0289.08 GP2GP Supplementary Specification on Handling Attachment Types.pdf
Dependencies
Creating a compliant implementation requires implementing the following dependent interface standards:
GP2GP FHIR Implementation
For Suppliers of new Solutions and Solutions that have implemented the GP2GP FHIR Implementation:
Personal Demographics Service (PDS) - using FHIR API
GP Connect Access Record Structured - Refer to ‘Migrate a Patient’s structured record' and ‘Migrate a document’ for more information
GPGP HL7
For Suppliers of Solutions which ARE currently deployed into an operational environment and have implemented GP2GP HL7:
Roadmap
Items on the Roadmap which impact or relate to this Standard