Versions Compared

Old Version 7

changes.mady.by.user Linley Wareham

Saved on

compared with

New Version Current

changes.mady.by.user Linley Wareham

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Roadmap retired as effective date has been reached and changes applied to relevant Capability and Standard.

...

Info

This Roadmap Item has been updated to refer to specification 1.1.0 following comments and points of clarification from Suppliers.

Page Properties
id2

Title

GP Connect Update Patient Record (Structured Update) - ITK3

Description

Update structured record of Encounter, Medicine and Observation

Date Added

Standards and Capabilities

Interoperability Standard, GP Connect, Patient Information Maintenance- GP

Change Route

Managed Capacity - Minor/Patch uplifts

Change Type

New

Status

PublishedClosed

Publication Date

Effective Date

Incentives / Funding

Yes

Incentive / Funding Dates

TBC

...

GP Connect: New Update Record - ITK3

GP Connect currently includes the following Standards:

  1. Access Record HTML: This enables a read only view of the Patient’s GP electronic Patient Record held at the GP Practice.

  2. Appointment Management: This enables the management of GP Practice Appointments between different systems.

  3. Access Record Structured: This enables structured information to be retrieved from the electronic Patient record at the GP Practice. Currently live access only includes Medications and Allergies information but work to expand out to cover the full GP clinical Record is in delivery.

  4. Send Document: This capability provides a simple and standardised means of sending a document to a GP Practice system.

  5. Update Record: This capability provides the ability to send and receive structured data.

The current GP Connect Specifications are:

  • GP Connect 0.7.4 for 4 for Access Record HTML

  • GP Connect 1.5.1 for 1 for Access Record Structured

  • GP Connect 1.2.7 for Appointments Management 

  • GP Connect Send Document 1.3.1

  • GP Connect Update Record - ITK3

Patient Information Maintenance - GP: New Epic

E00440 - GP Connect- Update Patient Record

As a Health or Care Professional

I want to receive structured clinical updates for Patients from other Healthcare Organisations

So that structured clinical updates from other Healthcare Organisations can be stored in Electronic Patient Records (EPRs)

Acceptance criterion 1: view received structured clinical updates

Given that structure clinical updates for a Patient have been sent to the Healthcare Organisation

When the Health or Care Professional selects to view the Electronic Patient Record (EPR)

Then the received Patient encounter information is displayed

And the received Patient observations are displayed

And the received Patient medications are displayed

E00440 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:

Full Specification

Assurance Approach

Assurance of the GP systems (i.e., recipients of the Update Record) will follow the Solution Assurance (SA) risk-based assurance approach. Suppliers will be provided in advance of onboarding for assurance, a SA Risk log listing risk items for the technical Interoperability, functional, non-functional, clinical, Information Governance and Security areas pertaining to this roadmap item. The SA Risk log will also explicitly state for each of the risk items in the risk log as to what are the risk mitigations expected from an onboarding GP system Supplier from a testing perspective. The GP system suppliers will also be provided access to the ITK Toolkit Workbench (TKW) test tooling for testing with their systems to mitigate the identified technical interoperability risks where possible to do so with the test tooling. Suppliers will also be provided with a manual test pack containing high level generic (i.e., system agnostic) test scenarios for risks items which cannot be tested using the ITK TKW test tooling. GP system suppliers are accountable for the testing of their solution and are expected to have also developed their internal test suite in addition to the SA supplied test tooling and test packs as these are supplier system agnostic and cannot be expected to cover specific supplier system functionality. There will be some risk items which would be more appropriate to assure through online demonstration sessions setup by the supplier and these would be explicitly specified in the SA risk log . The completed SA risk log submission from the supplier with all the completed risk mitigation asks would be reviewed and signed off by Solution assurance in conjunction with the Direct Care APIs Programme. 

...