GP Connect (Patient Facing) APIs Change 3 - Access Record - FHIR API

Owned by Linley Wareham
Last updated: 15-10-2024 by Alan GordonVersion comment
3 min read

ContentBody{} FormattedBody{value='

ID

RM216

Version

1.0.1

Type

Roadmap Item

Contracting Vehicle(s)

Title

GP Connect (Patient Facing) APIs Change 3 - Access Record - FHIR API

Description

Requirements relating to the new GP Connect Access Record - FHIR API

Date Added

Feb 22, 2024

Standards and Capabilities

Patient Information Maintenance - GP, View Record - Citizen, IM1 - Interface Mechanism, Interoperability Standard

Change Route

TBC

Change Type

Uplift

Status

Draft

Publication Date

TBC

Effective Date

TBC

Incentives / Funding

TBC

Incentive / Funding Dates

TBC

Background

Patient Facing Services (PFS) ensure that Citizens (Patients and their Proxies) have the tools to access information and services digitally, providing real-time access to their record, so they can more actively participate in managing their own health and care, through an enhanced offering of Patient Facing Apps. GP Connect PFS APIs allow all Patients and their Proxies to view a Patient’s detailed Electronic Patient Record (EPR), order their repeat Prescriptions, and book/manage their health and care Appointments.

There is no single Standard across all GP systems for extracting the Electronic Patient Record (EPR) for PFS. Interface Mechanism 1 (IM1) is the current option for providing PFS APIs from Foundation Solutions. IM1 PFS interfaces, created by the Foundation Suppliers, are based on high level functional specifications rather than technical Standards aligned to Interoperability Standards. PFS Consumers cannot integrate in a standardised way with Foundation Suppliers so undertake a separate development with each Supplier. Consumers must apply significant development time and effort to integrate with each differing bespoke API, which introduces technical complexity and inconsistency and negatively impacts New Market Entrants (NMEs) and innovation.

Outline Plan

A number of new GP Connect PFS APIs are being developed:

  • Prescriptions - FHIR API

  • User Permissions API

  • Access Record - FHIR API

The GP Connect PFS API specifications will continue to be uplifted so that they all adhere to the future specifications that are deemed appropriate and fit for purpose. The requirements for these APIs will be added via separate Roadmap Items.

This Roadmap Item will establish that:

  • Incumbent Provider Solutions MUST deliver GP Connect (Patient Facing) Access Record - FHIR API and continue to support IM1 (Patient Interface)

  • Incumbent Consumer Solutions may deliver either IM1 or GP Connect Access Record - FHIR API, this will be driven by what is supported by the Provider Solution

  • NME Consumer Solutions MUST only deliver GP Connect Access Record - FHIR API

Summary of Change

Full Specification

The updated Patient Information Maintenance - GP, View Record - Citizen, IM1 - Interface Mechanism and Interoperability Standard will be added at a later date. Proposed changes can be viewed in the Summary of Change above.

Assurance Approach

The Assurance Approach for Providers and Consumers will be provided at a later date.

', representation=storage}