Introduction

The GP2GP record transfer mechanism enables a patient's record to be electronically transferred directly and securely when they move from one practice to another.

Compliance and Assurance

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).

Open

The GP2GP assurance is split into 2 streams:

1. Compliance testing - this tests the spine messaging patterns and functionality

2. 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

Requirements

ID	Description	Level

ID	Description	Level
GP2GP00	Suppliers must meet the requirements for GP2GP 1.1a	MUST
GP2GP01	Suppliers must meet the requirements for GP2GP 2.2a Open	MUST
GP2GP02	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	Suppliers must provide support to receivers of GP2GP messages to resolve any issues with interpreting,consuming and processing received messages	MUST
GP2GP04	Suppliers must meet the requirements for GP2GP 2.2b Open	MUST

Message Fragments and Examples

Open

Supplementary specifications

The following supplemental specifications contain additional requirements and guidance for GP2GP implementation:

NPFIT-PC-BLD-0171.02 GP2GP SS Harvesting Management Information.pdf

Dependencies

Creating a compliant implementation requires implementing the following dependent interface standards:

Roadmap