Introduction

GP Connect Update Record provides a simple and standardised means for a Sender Solution to send structured data to a GP Practice Receiver Solution so that it can be added to a Patient’s GP Practice Electronic Patient Record (EPR).

Requirements

Compliance, Assurance and Testing

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

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

Documentation

• Developer Implementation Guide

• GP Connect service information

• Develop GP Connect services

Dependencies

• Interoperability Toolkit (ITK) - ITK3 Messaging Distribution

• Messaging Exchange for Social Care and Health (MESH)

• Personal Demographics Service (PDS) * or Spine Mini Services

*May be sourced indirectly by existing PDS interface provided by a Patient Information Maintenance - GP Solution, either via API to this Solution, or as a shared application resource if delivered as part of the same Solution.

Roadmap