Background

The GP Connect API 1.6.2 release contains numerous changes intended to improve and clarify guidance for both Providers and Consumers. Some examples of key changes included are:

• Update dose syntax to support Information Standards Notice DAPB4013

• Resources may contain a ‘no disclosure to patient’ security label

• Test groups, test reports and test reports may have many filing comments

• Profiles link through to Simplifier

Outline Plan

All Suppliers must be compliant against this updated Standard by the Effective Date.

Summary of Change

Full Specification

The GP Connect Update Record Standard will be uplifted on the Effective Date with the changes outlined in the Summary of Change above.

Assurance Approach

• Assurance Approach for the GP systems (i.e., GP Connect API Providers) 

Technical assurance of the GP systems will follow the established assurance process. Suppliers will be provided, in advance of onboarding for assurance, an uplifted automated Provider API test pack for GP Connect version 1.6.2 along with a manual test pack containing test scenarios for the delta changes which are not covered through the automated API test pack.

GP system suppliers are accountable for the testing of their solution and are expected to have also test scripted and executed their own internal tests as per their organisation testing processes in addition to the NHS England supplied test packs. The NHS England test packs are supplier system agnostic and therefore cannot be expected to cover any supplier system specific implementation.

Additional NHS England clinical assurance would be required to mitigate any clinical risks associated with the implementation and clinical safety assurance process would have to be followed in addition to the above assurance for the clinical safety report and clinical hazard logs as per the DCB0129 standard.

• Assurance Approach for the GP Connect API Consumer systems 

Technical Assurance for GP Connect API Consumer suppliers will be driven through the established Supplier Conformance Assessment List  (SCAL) approach. It will be supported by NHS England provided test scenario and the proxy GP Connect provider test implementation called Demonstrator which will be available to test within the internet facing environment and in the INT path to live test environment. To support end to end testing, the test environment in the INT path to live test environment will also be available to support testing with the assured GP Connect API Provider Suppliers FHIR endpoints via Spine Security Proxy