GP Connect Messaging 1.3.1 - Send Document
ID | RM124 |
|---|---|
Version | 1.0.0 |
Type | Roadmap Item |
Title | GP Connect Messaging 1.3.1 - Send Document |
|---|---|
Description | This capability provides a simple and standardised means of sending and receiving a document containing a consultation update to a GP Practice system. |
Date Added | Nov 10, 2021 |
Standards and Capabilities | Patient Information Maintenance, Interoperability Standard, GP Connect |
Change Route | Managed Capacity - Minor/Patch uplifts |
Change Type | Uplift |
Status | Closed |
Publication Date | Dec 31, 2021 |
Effective Date | Mar 31, 2022 |
Incentives / Funding | No |
Incentive Dates | N/A |
Background
The GP Connect capabilities support the development of products that enable different systems to communicate so that clinicians in different care settings can:
view a patient’s GP practice record with Access Record: HTML
manage GP appointments with Appointment Management
import or download Patient data with Access Record: Structured
send a consultation update back to the GP Practice System with GP Connect Messaging Send Document
The GP Connect Messaging Send Document capability provides a simple and standardised means of sending and receiving a document containing a consultation update to a GP Practice system, helping to ‘close the loop’ and provide latest information to the patient’s registered GP.
Outline Plan
See publication and effective dates above.
Summary of Change
GP Connect Messaging has been uplifted to version 1.3.1 to add additional requirements to support sending local ID when using MESH. This allows for the sending organisation's ODS code to be visible when reporting activity.
Full Specification
Link to the full specification for RM13: GP Connect Messaging - Send Document
A new Interoperability Standard "GP Connect v5.0.0" has been added.
Link to the Published Interoperability Standard for GP Connect: GP Connect v5.0.0
The GP Connect Messaging specification describes the messaging approach being taken by GP Connect for record update scenarios. These will need implementing alongside the Generic FHIR Receiver component requirements.
Assurance Approach
Link to the assurance documentation for RM13: GP Connect Messaging - Send Document