GP Connect Messaging: Send Update rest of record (Phase 3)

Owned by norris.orighoye1 (Unlicensed)
Last updated: 26-10-2022 by Jenna Bennett (Unlicensed)Version comment
2 min read
ID

RM139

Version1.0.1
TypeRoadmap Item
Frameworks

  • GP IT Futures

  • Tech Innovation


Title

GP Connect Messaging: Send Update rest of record (Phase 3)

Description

Ingestion of additional FHIR resources over and above Online Consultation use case to support both the Send Document Generic use case and a fully FHIR structured Send Update payload containing all clinical areas of the patient record

Date Added

TBC

Standards and Capabilities

GP Connect, Patient Information Maintenance, Unified Care Record 

Change Route

Opportunity Item

Change Type

Uplift

Status

Closed

Publication Date 
Effective Date

 

Incentives / Funding

TBC

Incentive Dates

TBC


Background

As care pathways include patients being seen in more care settings, there is an increasing need for patient related updates to be received by GP practice.   

The GPC Messaging specification will be uplifted to enable a greater set of structured information to be captured via additional FHIR resources available for population in the payload. This supports the sending of structured / SNOMED coded information to reduce admin burden at GP Practice, standardise and improve patient information being sent back to the GP clinical system. 


Outline Plan

Development Iteration Phase 3 Scope:  

GP Connect Messaging: Send Update rest of record (ingestion of additional FHIR resources over and above Online Consultation use case to support both the Send Document Generic use case and a fully FHIR structured payload containing all clinical areas of the patient record) 

Dev & Assurance complete FOT Complete (Publication Date) Effective Date 
 
 
 


Summary of Change

The GP Connect Messaging specification has been uplifted to support the business need to allow information to be captured in wider care settings, sent back to and received by the GP Practice and where appropriate, automatically ingested and added to the patient record. This will require ingestion of the structured / coded FHIR resources contained in the uplifted specification(s) and implementation of any supporting requirements identified.  

It is envisaged that the development to support the full GP Connect Messaging uplifted specification will be delivered in several iterations. This roadmap item covers Phase 3 of the 3 proposed phases. Phase 3 will include the ingestion of additional FHIR resources over and above Online Consultation use case to support both the Send Document Generic use case and a fully FHIR structured Send Update payload containing all clinical areas of the patient record. 

For more information on Phase 1 & Phase 2, please see: 

  • GP Connect Messaging: Send Update for Online Consultation (Phase 1)
  • GP Connect Messaging: Send Update for Online Consultation (Phase 2) 


Full Specification

Please access the following links for more information on the full specification for this Roadmap item: 

  • GP Connect Messaging 1.5.1 
  • GP Connect Messaging 1.6.0 (to be published) 


Assurance Approach

We will follow a risk-based approach to assurance. A detailed assurance approach will be provided alongside Publication of the relevant specifications.