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.

Introduction

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.


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 gpconnect@nhs.net 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.

OR
OR
Use-case approved by NHS Digital
Use-case approved by...
MESH API
compliance
MESH API...
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...
ITK3
conformance
ITK3...
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