Versions Compared

Version Old Version 9 New Version 10
Changes made by

Lorraine Olowosuko (Unlicensed)

Lorraine Olowosuko (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Changed mention of 'capabilities' to 'features' and text case changes in Summary Section


Page Properties
id1


IDRM13
Version1.0.0
TypeRoadmap Item





Page Properties
id2


TitleGP Connect Messaging - Send Document
Description

Introduction of GP Connect messaging for sending documents. Specification v1.2.0

Date Added 
Standards and CapabilitiesGP Connect, Patient Information Maintenance
Change RouteManaged Capacity – SRO Priority
Change TypeNew
StatusPublished
Effective Date 
Incentives / FundingNo
Incentive DatesN/A
Notes




Summary

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

GP solutions require the following capabilitiesfeatures:

  • 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 feature that will be supported by GP Connect Messaging, and thus defined in the existing requirements, is the Send Document capabilityfeature. 

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.