GP2GP
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 services which ARE currently deployed into an operational environment, and have existing GP2GP compliance. | 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 | MUST | |
| GP2GP05 | Management Information Suppliers must implement and maintain the GP Registrations Management Information API inline with the latest specification version | MUST | |
| Suppliers of new services or applications (i.e. those which are NOT currently deployed into an operational environment with existing GP2GPs compliance). | 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 |
Documentation
GP2GP FHIR Implementation
For Suppliers of new services or applications:
- API Catalogue - GP2GP Requesting Adaptor
- API Catalogue - GP2GP Sending Adaptor
- GP Registrations Management Information API
- Message Handling System (MHS) Adaptor
GP2GP HL7
For Suppliers of services which ARE currently deployed into an operational environment:
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
Compliance and Assurance
GP2GP FHIR Implementation
For Suppliers of new services or applications:
A risk-based assurance to be followed by all New Foundation Solution Suppliers (NFSS).
- Technical Assurance - The Suppliers need to demonstrate that the GP2GP Sending Adapter and GP2GP Requesting Adaptor are successfully integrated and technically assured through a specific set of Technical risks.
- E2E Solution Assurance - The Suppliers need to demonstrate that the GP2GP FHIR Implementation Solution meets the E2E functional interoperability requirements through a set of Clinical and Technical risks covering the below high-level scenarios:
- NFSS as a winning Practice
- NFSS as losing Practice
- Pathways assurance from NFSS to Incumbent Solutions
- Pathways assurance from Incumbents to NFSS Solutions
- Export of data from NFSS Solutions
Suppliers must contact Solution Assurance team through the Tech Innovation mailbox (gpit.techinnovation@nhs.net) to arrange a witness testing slot to provide evidence. Successful completion of the witness testing and evidencing will constitute compliance against this Roadmap Item.
An Assurance Statement will be provided when a supplier completes their testing and assurance related activities. The report will be used as the readiness for further onboarding stages and progression to Live assurance.
GP2GP HL7
For Suppliers of services which ARE currently deployed into an operational environment:
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
Dependencies
Creating a compliant implementation requires implementing the following dependent interface standards:
GP2GP FHIR Implementation
For Suppliers of new services or applications:
- Personal Demographics Service (PDS) - using FHIR API
- Spine Directory Service - FHIR API
- GP Connect - Access Record Structured API v1.6.0
- GP Registrations Management Information API
GP2GP HL7
For Suppliers of services which ARE currently deployed into an operational environment: