ID	S43
Version	5.0.0
Type	Standard
Status	Effective
Effective Date	30 Jun 2024
Framework(s)	GP IT Futures Tech Innovation

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): Structure of data Any know issues or anomalies and how they should be handled Code sets and associated meanings Field specifications (types, lengths etc.)	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
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

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:

Click here to expand...

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