GP Connect Access Record Structured

ID

S99

Version

1.0.0

Type

Standard

Status

Effective

Effective Date

Feb 23, 2024

Contracting Vehicle(s)

 

Introduction

The GP Connect Access Record Structured API enables a Solution to request and consume a Patient’s GP Practice Electronic Patient Record (EPR) in a structured and coded format that is machine readable. The data will be made available via a standard API. Structured data allows the Consumer Solution to import and process the Patient data in the way it requires to best support Patients and the Health and Care Professionals treating them.

See Access Record Structured (developer.nhs.uk) for further information.

Requirements

Applicable Suppliers

ID

Requirement

Level

Applicable Suppliers

ID

Requirement

Level

Provider

GPCARS01

Implement and maintain the GP Connect Access Record Structured Provider requirements inline with the latest specification version.

MUST

Consumer

GPCARS02

Implement and maintain the GP Connect Access Record Structured Consumer requirements inline with the latest specification version.

MUST

Compliance, Assurance and Testing

To achieve GP Connect compliance as a Provider, Suppliers will need to complete the relevant Assurance Approach detailed under each of the specific requirement pages. To achieve GP Connect compliance as a Consumer, Suppliers will need to follow the Supplier Conformance Assessment List (SCAL). More detail on this can be found here.

For advice, access to testing resources, and support contact gpconnect@nhs.net.

Documentation

Dependencies

Creating a compliant implementation requires implementing the following dependent interface Standards:

*May be sourced indirectly by existing PDS interface provided by a Patient Information Maintenance - GP Solution, either via API to this Solution, or as a shared application resource if delivered as part of the same Solution.

Roadmap

Items on the Roadmap which impact or relate to this Standard

Items on the Roadmap which impact or relate to this Standard