Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Effective Date Reached. Roadmap Item Retired.
Page Properties
id1

ID

RM151

Version

1.1.0

Type

Roadmap Item

Frameworks

Page Properties
id2

Title

GP2GP (FHIR) Implementation

Description

GP2GP FHIR Sending and Requesting Adaptors

Date Added

Standards and Capabilities

GP2GP, Patient  Patient Information Maintenance - GP, Interoperability  Interoperability Standard

Change Route

Managed Capacity - Other

Change Type

New

Status

PublishedClosed

Publication Date

Effective Date

Incentives / Funding

No

Incentive / Funding Dates

N/A

...

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 0 and cover the below functions:

...

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

Applicable Suppliers

ID

Description

Level

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 the GP2GP Sending Adaptor inline Adaptor inline with the latest version

Status
colourRed
titleMUST

GP2GP08

GP2GP FHIR Implementation - GP2GP Requesting Adaptor

Implement and maintain the GP2GP the GP2GP Requesting Adaptor inline with the latest version

Status
colourRed
titleMUST

GP2GP09

Management Information

Suppliers must implement and maintain the GP Registrations Management Information API inline API inline with the latest specification version

Status
colourRed
titleMUST

...

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:

...

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.

...