GP Connect - Send Document

Part of the GP Connect product family
Note: A minor revision has been made to this version of the specification due to issues in some of the guidance.
Full details of changes can be found in the release notes in version 2.0.1-public-beta.


This specification enables the sharing of documents using ITK3, Care Connect FHIR API standards (based on STU3), and MESH.

FHIR Messaging components specified within this site have been developed by NHS Digital and use CareConnect profiles created in collaboration with the INTEROPen community.

The INTEROPen vision is to create a library of nationally defined HL7® FHIR® resources and interaction patterns that implementers can adopt to simplify integration and interoperability within England’s health and social care systems.

Find out more on the INTEROPen website.

Clinical engagement

To help ensure that the functionality being developed will be able to support GP practices, GP Connect has engaged with a range of GP practice staff to get an understanding of how that data may be used and what is required to support that use.

This engagement has included:

  • general practitioners
  • GP nurses
  • GP pharmacists
  • practice managers
  • GP practice administration staff

The feedback from these stakeholders has been used to develop the use case for the Send Document capability.

New Use Cases have been submitted by Consumer Suppliers working with commissioning organisations and Health Care Settings that want to use the send document functionality and these have been discussed within the clinical input group for Direct Care APIs / GP Connect prior to assurance.

How to get started with this capability

The enablement team can help get you started by guiding you in the following:

1. Confirming the Send Document capability fulfils the use case requirements

Read through this specification to ensure that it fulfils the requirements for your use case, and that the sending or receiving system(s) can meet the data requirements - for example, having the information required to populate the FHIR resources as described in this specification.

2. Submit your use case for the Send Document capability

Contact about your use case for the Send Document capability.

3. Getting your use case approved

Use cases are approved on the basis that development is started for the capability approved within six months. If this date is missed, then a review of the case will be required.

Important: Additional development will require a new use case submission.
4. Getting conformance

Once approved, the service practitioner will:

  • introduce the assurance process and artefacts to gain technical conformance
  • set up a Microsoft Teams page which will be used to raise queries
Note: Complex or unique use cases are taken to a weekly board for approval.
5. Assurance

The developed solution will require assurance before it can be enabled in production. Read more on the GP Connect Consumer Support Hub wiki.

Use-case approved by NHS Digital
Use-case approved by...
MESH Client
MESH Client
Technical conformance received
Technical con...
Develop to specification
Develop to specifica...
Complete the requirements in the GP Connect SCAL and provide supporting evidence
Complete the requirements in the GP Connect SCAL and provide...
Gate 3
Test within Integration  (INT) environment
Gate 3...
Gate 4
Test against providers
via INT
Gate 4...
Sign connection agreement
Sign connecti...
Enabled for use in production
Enabled for u...
Text is not SVG - cannot display

Suppliers using this capability

Important: The adopters of this specification are currently split between senders and receivers.

This is due to certain use cases that require data to be sent but not necessarily received.

Senders should take care to ensure that supplier systems and other intended recipients have implemented the capability to receive.

Please review the progress by supplier for a complete list of suppliers and implemented GP Connect capabilities.

back to top