GP Connect aims to support better clinical care by opening up information and data held within GP principal clinical systems for use across health and social care. The GP Connect vision will be achieved by standardising integration and simplifying the operating model. Find out more on the NHS Digital GP Connect homepage.
GP Connect has initially focused on delivering HTTP FHIR® APIs. The current GP Connect FHIR API specification is found at https://nhsconnect.github.io/gpconnect/. An additional set of capabilities, under the badge GP Connect Messaging, is described in this specification. These new capabilities are focused on enabling updates to GP practice systems.
The resulting full set of capabilities delivered through GP Connect is illustrated below:
Using Messaging to perform updates
In contrast to the synchronous FHIR® API approach, which has been taken to enable read-only access to patient information, updates to patient data will be fulfilled through a messaging approach.
Update messages will:
- be sent using MESH
- use the HL7 FHIR® STU3 interoperability standard to define their structure
- include FHIR® messaging information as defined by the ITK3 message distribution, v2.5.0 standard
Who will be interested in these capabilities?
Two main audiences will be interested in this specification:
- message senders: NHS organisations seeking to send messages
- message receivers: GP practices seeking to receive and process messages
This specification is primarily aimed at message senders. Where the specification contains information for message receivers, this is explicitly stated.