| Table of Contents |
|---|
| minLevel | 1 |
|---|
| maxLevel | 3 |
|---|
| outline | false |
|---|
| style | disc |
|---|
| type | list |
|---|
| printable | false |
|---|
|
Introduction
GP Connect Send Document provides a simple and standardised means of sending a document, such as a PDF, an image, or HTML file to a GP Practice Receiver Solution. Each message sent using GP Connect Send Document makes use of the GP Connect Messaging components, Messaging Exchange for Social Care and Health (MESH) and ITK3 Messaging Distribution to deliver the message.
See Send Document (developer.nhs.uk) for further information.
Requirements
Applicable Suppliers | ID | Requirement | Level |
|---|
Receiver | GPCSD01 | Implement and maintain the GP Connect Send Document Receiver requirements inline with the latest specification version. | |
Sender | GPCSD02 | Implement and maintain the GP Connect Send Document Sender requirements inline with the latest specification version. | |
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
Dependencies
Creating a compliant implementation requires implementing the following dependent interface Standards:
| Excerpt |
|---|
| name | Interoperability toolkit MESH FHIR |
|---|
|
|
Roadmap
Items on the Roadmap which impact or relate to this Standard |
|---|
| Page Properties Report |
|---|
| firstcolumn | Roadmap Item |
|---|
| headings | Standards and Capabilities, Status, Effective Date, Description, Change Type, Change Route |
|---|
| pageSize | 300 |
|---|
| sortBy | Effective Date |
|---|
| cql | label = "s101" and space in ( currentSpace ( ) , "DCSDR" , "DCSDCS" ) |
|---|
|
|