Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

ID

RM124

Version1.0.0
TypeRoadmap Item


Title
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

 

Standards and Capabilities

Patient Information MaintenanceInteroperability StandardGP Connect v4.0.0

Change Route

Managed Capacity - Minor/Patch uplifts

Change Type

Uplift

Status

Published

Publication Date 
Effective Date

 

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


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.



  • No labels