GP Connect Send Document

This guidance is under active development by NHS Digital and content may be added or updated on a regular basis.
This version of GP Connect Send Document supports one use-case which is a Consultation Summary (PDF).
Additional use-cases are expected to be supported in 2023.

Design overview

The Send Document capability provides a simple and standardised means of sending a document, such as a PDF, an image, or HTML file to a GP practice system. Each message sent using the Send Document capability makes use of the GP Connect Messaging components, MESH, and ITK3 to deliver the message.

All messages sent using this capability will be FHIR® Messages, defined as a FHIR composition, constructed to meet the ITK3 standard and have a specific payload structure.

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 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.

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:

Who will be interested in this capability?

Two main audiences will be interested in this specification:

  1. message senders: NHS organisations seeking to send messages
  2. message receivers: GP practices seeking to receive and process messages
back to top