The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| Send Document | Page | Introduction to the GP Connect Messaging Send Document capability |
| Business requirements | Page | Business requirements for Send Federated Consultation Report use case |
| Clinical engagement | Page | Clinical engagement for Send Federated Consultation Report |
| PDF layout | Page | PDF layout for Send Federated Consultation Report use case |
| Error handling | Page | Error handling details for the Send Federated Consultation Report use case |
| Message example | Page | Send Federated Consultation Report - example message. |
| ITK3 header requirements | Page | Details of how the ITK3 header is populated to fulfil the Send Federated Consultation Report use case |
| MESH message configuration | Page | Federated consultation - MESH configuration |
| Overview | Page | Overview of the use case to send a federated consultation report to the registered practice of a patient |
| Payload requirements | Page | Details of the FHIR resources which make up the payload for the Send Federated Consultation Report use case. |
| Triggering message creation | Page | Options for triggering the creation of a federated consultation summary message |
| Send Document - payload structure | Page | Send Document capability - the structure of the payload to be used for all use cases of the Send Document capability |
| User stories | Page | User stories for Send Federated Consultation Report |
