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

Version 1 Next »

TitleGP Connect Messaging - Send Document
TypeRoadmap Item
Capability/StandardGP Connect
Status
Implementation DateTBC
DescriptionAsynchronous messaging capabilities to deliver the initial FHIR use case covered by GP Connect 
Change Type

Summary

GP Connect is initially focused on delivering synchronous FHIR® APIs for patient record retrieval and appointment booking. A new set of capabilities, under the badge of GP Connect Messaging, is used to send and receive updates to GP practice systems. The GP Connect Messaging capabilities are based on the FHIR standard and sent asynchronously using MESH and ITK3 technologies. 

GP solutions require the following capabilities:

  • send GP Connect messages to a receiving system via ITK3/MESH
  • receive GP Connect FHIR messages via the Generic FHIR Receiver

The initial messaging capability that will be supported by GP Connect Messaging, and thus defined in the existing requirements, is the Send Document capability. 

Documentation

The GP Connect Messaging specification, which can be accessed via the GP Connect Messaging site, describes the messaging approach being taken by GP Connect for record update scenarios. These will need implementing alongside the Generic FHIR Receiver component requirements.

Details of the payload to support the initial update use case can be found here.




  • No labels