GP Connect Access Record Structured
ID | S99 |
Version | 1.0.3 |
Type | Standard |
Status | Effective |
Effective Date | Dec 4, 2025 |
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 |
Provider | GPCARS01 | Implement and maintain the GP Connect Access Record Structured Provider requirements inline with the latest specification version as per the Data by Capability section | MUST |
Consumer | GPCARS02 | Implement and maintain the GP Connect Access Record Structured Consumer requirements inline with the latest specification version as per the Data by Capability section | MUST |
Data by Capability Mapping
Capability | Medications | Uncategorised items | Investigations | Allergies | Immunisations | Consultations | Problems | Referrals (Outbound) | Diary Entries |
Compliance, Assurance and Testing
See the GP Connect Access Record Structured - Provider/Consumer section on Onboarding Overview of the Digital Care Services Interoperability Standards and Requirements.
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