GP Connect Access Record HTML
ID | S98 |
---|---|
Version | 1.0.0 |
Type | Standard |
Status | Effective |
Effective Date | Feb 23, 2024 |
Contracting Vehicle(s) |
Â
Introduction
The GP Connect Access Record HTML API provides Health and Care Professionals with read only access to a Patient’s GP Practice Electronic Patient Record (EPR) by requesting sections or headings. Where appropriate, a date range can be defined to filter the retrieval of larger sections. These views can be incorporated directly into Consumer Solutions.
See Access Record HTML (developer.nhs.uk) for further information.
Requirements
Applicable Suppliers | ID | Requirement | Level |
---|---|---|---|
Provider | GPCARH01 | Implement and maintain the GP Connect Access Record HTML Provider requirements inline with the latest specification version. | MUST |
Consumer | GPCARH02 | Implement and maintain the GP Connect Access Record HTML 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 |
---|