GP Connect aims to support better clinical care by opening up information and data held within GP Practice IT systems for use across health and social care.
The first phase of GP Connect provides access to and enables the following:
- A patient's care record as an HTML view (Access Record HTML)
- Medications and Allergies section of a patient's care record in clinically coded and structured Fast Healthcare Interoperability Resources (FHIR) format (Access Record Structured)
- The ability for a third-party organisation to directly book and manage Appointments in a GP practice (Appointments Management)
- The ability to ‘writeback’ or send a document e.g. consultation update, to a GP Practice for attachment to a patient’s record (GP Connect Messaging Send Document)
A demonstrator application of the GP Connect FHIR APIs is available, as is additional information at NHS Digital's GP Connect homepage.
Compliance, Assurance and Testing
To achieve GP Connect compliance suppliers follow a process involving technical testing and completion of a Target Operating Model (TOM) assessment (which covers wider requirements, such as IG, Clinical Safety, Business Requirements, etc). This assessment is a point-in-time assessment of the solution.
For advice, access to testing resources, and support contact firstname.lastname@example.org.
The current GP Connect Specifications are:
For the definitive list of GP Connect API versions please see GP Connect Specification Versions
It is expected that this specification will require uplifting to support achievement of FRA under existing GP Connect arrangements. Suppliers will be required to meet these uplifts before GP Connect FRA is awarded. The GP Connect programme will work to ensure these uplifts contain critical FRA impacting changes only, any other changes will be built into roadmap specifications on the new Futures framework.
All technical documentation, including information on testing, environments and assurance, is hosted on NHS Developer Network.
Creating a compliant implementation requires implementing the following dependent interface standards:
*May be sourced indirectly by existing PDS interface provided by PIM solution, either via API to PIM solution, or as a shared application resource if delivered as part of the same solution.