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 2 Next »

ID

RM160

Version1.0.1
TypeRoadmap Item
Frameworks
Title

GP Connect Send Document 

Description

Support for multiple use cases and displaying 'For Action (FA)' / 'For Information (FI)' flag by Receiving Solutions

Date Added

 

Standards and Capabilities

GP Connect, Patient Information Maintenance - GP, Interoperability Standard

Change Route

Managed Capacity - Minor/Patch uplifts

Change Type

Uplift

Status

Published

Publication Date

 

Effective Date 
Incentives / Funding

No

Incentive Dates

N/A


Background

Currently, the GP Connect Send Document Solution only caters for the Consultation Summary document. If any other type of document were to be sent it would be labelled as ‘Consultation Summary’ by the Receiving Solutions and the GP Practice Users will not be able to identify the type of documents that are received without opening each document. The GP Connect Send Document 2.0.0 specification has been updated to support the identification and labelling of the documents; not by using MESH workflow ID, but by using SNOMED codes. The Receiving Solutions should display a label for each document type, allowing the GP Practice Users to be able to view the document type and be able to sort or filter by that document type. This change supports future document types. 

In addition, the 'For Action' and 'For Information' flags that are sent via GP Connect Send Document are currently not shown. In the Receiving Solutions, the 'For Action' and 'For Information' flags will be displayed.

In conclusion, there are 2 changes to be implemented for the Receiving Solutions as part of this uplift:

  1. Labelling: the different documents will be labelled (have human readable visibility) with the type of document being sent, and ideally it should be possible to sort or filter by these different document types. 

  2. Identification of 'For Action' or 'For information' flag: in the Receiving Solutions, the 'For Action' and 'For Information' flags will be displayed and provide the GP Practice Users with the ability to have human readable visibility of the 'For Action' or 'For Information' flag that is sent to allow identification of cases that they may wish to prioritise. Ideally it would also be possible to sort or filter by the 'For Action' or 'For Information' flag.

    Receiving Solutions must ensure that the MESH Workflow ID supports backwards compatibility for GP Connect Send Document v1.3.1 or v1.3.2, i.e. a Consultation Summary could be received via the MESH Workflow ID or the new SNOMED code.


Outline Plan

Changes cannot be fully implemented by Sending Solution Suppliers until the Receiving Solution Suppliers have completed their work and the changes are live.

  • Receiving Suppliers to complete development of the changes before 15th June 2023
  • Assurance process to be completed 2 weeks before the Effective date 
  • Changes to be deployed to all instances of the Solution on or before the Effective date


Summary of Change

The following changes will be applied to the model.

Update to GP Connect:

GP Connect Send Document for GP Connect will be updated from v1.3.1. to v2.0.0.

The current GP Connect Specifications are:

Update to Patient Information Maintenance - GP:

E00180 - GP Connect Send Document

As a Health or Care Professional 

I want to receive Patient consultation notes documents from other Healthcare Organisations

So that Patient consultation notes documents from other Healthcare Organisations can be stored in Electronic Patient Records (EPRs)

Acceptance criterion 1: view Patient Consultation Summary Reports sent via GP Connect Messaging documents

Given that Patient consultation notes have been sent to the Healthcare Organisation documents have been received by the Healthcare Organisation

When the Health or Care Professional selects to view the Patient's consultation notes received via GP Connect Messaging documents

Then the Patient’s consultation notes are displayed

Then the label for each document is displayed

And the flag for each document is displayed 

And the Health or Care Professional can view the Patient documents

E00180 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:

E00180 - Supporting Information

  • Examples of Patient document labels MAY include, but are not limited to:

    • Consultation Summary

    • Online Consultation Summary

    • Online Consultation Request

    • Attendance at a course / support group (e.g. diabetic structured education)

    • Screening results (e.g. diabetic eye screening results)

    • Clinical letters (e.g. relating to Secondary Care Nephrology / kidney function)

    • Fit notes (e.g. copy of signed fit note from Clinicians for returning to GP Record)

    • Advice & Guidance

  • Examples of Patient document flag(s) MAY include, but are not limited to:

    • For Information (FI)

    • For Action (FA)

  • Examples of filtering or sorting Patient documents MAY include but are not limited to:

    • By label

    • By flag


Full Specification

GP Connect v6.1.0

Patient Information Maintenance - GP v3.1.0


Assurance Approach

Receiving Solutions already assured for compliance with GP Connect Send Document v1.3.1 or v1.3.2 would require additional assurance as below for the compliance uplift with GP Connect Send Document 2.0.0:

  • Assurance of the Supplier's test evidence of the testing done in the integration (INT) environment using the Message Exchange for Social Care and Health (MESH) transport layer for the changes required to support the ‘Labelling’. Test evidence for assurance purposes can be provided by the onboarding Supplier in the form of a test pack with supporting request and response messages which test the specific changes within the ‘Labelling’.
  • Assurance of the Supplier's test evidence to support identification of ‘For Action' or 'For Information’. Test evidence for assurance purposes can be provided by the onboarding Supplier in the form of either an online interactive demo session of the implemented changes to support this requirement or an offline video file demonstrating the same
  • Assurance of the Supplier's test evidence of the testing done in the INT environment using MESH transport layer to support the ‘Backwards Compatibility’. Test Evidence for assurance purposes can be provided by the onboarding Supplier in the form of test pack with supporting request and response messages which evidence that backward compatibility is maintained to support the GP Connect - Send Document Sender Solutions who have implemented earlier versions of GP Connect - Send Document capability
  • Self-certification statement from the onboarding Supplier that the regression testing for the existing live functionality has been successfully completed without any defects

A GP Connect Send Document Sender system Supplier implementing this would be assured through the Supplier Conformance Assessment List (SCAL) process.



  • No labels