Introduction

GP Connect allows authorised clinical staff to share and view GP Practice clinical information and data between IT systems, quickly and efficiently.

The service makes Patient medical information available to all appropriate Clinicians when and where they need it to support direct Patient care, leading to improvements in both care and outcomes.

GP Connect currently includes the following Standards:

1. Access Record HTML: This enables a read only view of the Patient’s GP electronic Patient Record held at the GP Practice.

2. Appointment Management: This enables the management of GP Practice Appointments between different systems.

3. Access Record Structured: This enables structured information to be retrieved from the electronic Patient record at the GP Practice. Currently live access only includes Medications and Allergies information but work to expand out to cover the full GP Clinical Record is in delivery.

4. Send Document: This capability provides a simple and standardised means of sending a document to a GP Practice system.

A demonstrator application of the GP Connect FHIR APIs is available, as is additional information at NHS Digital's GP Connect homepage.

Compliance, Assurance and Testing

To achieve GP Connect compliance, as a Provider Suppliers will need to complete the relevant NHS Digital Assurance Approach detailed under each of the specific requirement pages. To achieve GP Connect compliance as a Consumer, Suppliers will need to follow the SCAL (Supplier Conformance Assessment List). More detail on this can be found here.

For advice, access to testing resources, and support contact gpconnect@nhs.net.

Requirements

The current GP Connect Specifications are:

• GP Connect 0.7.4 for Access Record HTML
• GP Connect 1.5.1 for Access Record Structured
• GP Connect 1.2.7 for Appointments Management 
• GP Connect Messaging 1.3.1 for GP Connect Messaging Send Document

For the definitive list of GP Connect API versions please see GP Connect Specification Versions.

Documentation

All technical documentation, including information on testing, environments and assurance, is hosted on NHS Developer Network.

Dependencies

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

• Personal Demographics Service (PDS) *

     Or 

• Spine Mini Services

     Or

• Generic FHIR Receiver

*May be sourced indirectly by existing PDS interface provided by PIM solution, either via API to PIM solution, or as a shared application resource if delivered as part of the same solution.

Roadmap