Background

GP2GP allows Electronic Patient Records (EPR) to be transferred directly, securely, and quickly, between their old and new GP Practice. Existing Suppliers have implemented GP2GP using HL7 as the messaging format.

Consideration is being given to the strategic future direction of GP2GP and this will likely result in a move away from the legacy HL7 to GP Connect.

At this time an extension has been made to GP Connect that will facilitate the transfer of EPR’s upon a Patient registering at a GP Practice. These are requirements of GP Connect - Access Record Structured API v1.6.0 and cover the below functions:

• Migrate Patient Record

• Migrate Document

This builds on the strategic direction for the movement of EPRs between Healthcare Organisations using GP Connect structured FHIR and will support decisions on the strategic direction of GP2GP.

New Foundation Solutions must provide GP2GP functionality using GP Connect v1.6.0. Additionally they will be required to comply with two adaptors and their technical and business requirements. These two adaptors will mimic GP2GP and allow a mixed economy of GP2GP HL7 and GP2GP over GP Connect messages to interoperate. The introduction of these adaptors for new Solutions means there are no changes required for Solutions already assured for GP2GP using HL7.

Outline Plan

• An uplift to the GP2GP Standard requirements introduced via this roadmap item

• A new set of requirements that are only applicable to new solutions wanting to provide GP2GP functionality - No impact on existing solutions

• Once any new GP2GP requirements and messaging have been proved this will help formulate the strategic solution for GP2GP, including the requirements for transfers where sending and receiving Solutions are both using GP Connect to implement GP2GP

Summary of Change

Additional requirements added to GP2GP Standard applicable to Suppliers of new services or applications only:

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

Dependencies

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

GP2GP FHIR Implementation

For Suppliers of new services or applications:

• GP2GP Requesting Adaptor

• GP2GP Sending Adaptor

• 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

Full Specification

• GP2GP Standard v4.01

• GP2GP Requesting Adaptor v1.0.0

• GP2GP Sending Adaptor v1.0.0

Assurance Approach

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.