Versions Compared

Version Old Version 13 New Version 14
Changes made by

Devishree Nath (Unlicensed)

Katharine Smith

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page Properties
id1


IDRM13
Version1.0.1
TypeRoadmap Item





Page Properties
id2


Title1391133486
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
StatusPublishedDraft
Publication date 
Effective Date Dec 2019 
Incentives / FundingNo
Incentive DatesN/A




Summary

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

GP solutions require the following features:

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

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

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.