The Open API Ecosystem
GP Connect is part of the a wider initiative to expose standards based Open APIs to promote innovation and improve care across the NHS.
Capabilities
A capability is an area of focus for the GP Connect APIs. There are several initial capabilities defined.
Become an API Consumer
If you’re planning on consuming data using GP Connect APIs then you’re a Consumer system (e.g. access record).
Become an API Provider
If you’re planning on providing data using GP Connect APIs then you’re a Provider system.
1. Get Started
- Read about the GP Connect Priority Capabilities.
- Look through the Design Decisions made so far in relation to each capability packs (Foundations, Access Record HTML, Access Record Structured, Appointment Management and Task Management) and get involved:
- SELECTED / DECISION A decision has been made for first release.
- ASSUMPTION An assumption has been made which is under review/needs validated.
2. Explore
- Try out the GP Connect Demonstrator system.
- Try out our Interactive API documentation online.
- Optionally download the GP Connect Demonstrator Codebase to see how it works.
3. Develop
- Familiarise yourself with HL7® FHIR® (Fast Health Interoperability Resources) (developer intro, exec summary, or clinical intro).
- Grab an open source FHIR development library for your favourite programming language.
- Familiarise yourself with our GP Connect FHIR API Guidance common to all APIs.
- Explore the GP Connect Profiled Fhir Resources, a variation of the international FHIR Resources, for Foundations, AccessRecord HTML and Appointment Management.
- Dig in deep and explore one or more of the GP Connect Capability Packs and start building new or hitting existing APIs.
- Foundations capability pack (e.g. resolve a patient to their logical identifier for further API calls).
- Note the foundation per-requisites are mandatory and may restrict your ability to utilise the GP Connect APIs.
- Access Record HTML capability pack (e.g. Access html views from the primary care record).
- Access Record Structured capability pack (e.g. Access structured data from the primary care record).
- Appointment Management capability pack (e.g. Book an appointment for a patient).
- Task Management Capability Pack (e.g. Send a notification task to a general practice organisation).
- Foundations capability pack (e.g. resolve a patient to their logical identifier for further API calls).
- Finally take a look at cross-cutting areas:
- JSON Web Token - Provides Cross Organisation Audit and Provenance details.
- Additional HTTP headers and Proxy URL - This gives you access to the Spine Security Proxy, the secure ‘front door’ of GP Connect APIs.
- Configure HTTPS and TLS MA - Security Guidance allows you to secure and mutually authenticate your service with the Spine (which refers to two parties authenticating each other at the same time).
4. Assure
- Read about the Provider Testing and Consumer Testing process.
5. Deploy
- Become a First of Type deployment!
Provide Feedback
To provide feedback on the GP Connect specification please send an email to the GP Connect Team Inbox.
Some early feedback on the May 2016 release of the GP Connect draft specification can be found on the Openhealthhub Forum under the category of “FHIR Implementation”.
Community Engagement
GP Connect is working closely with a number of interoperability communities:
- Code4Health Interoperability Community
- INTEROPen Supplier-led Healthcare IT Interoperability Community
Timescales, benefits and more
The content here is designed for a technical audience (i.e. developers, architects and data scientists) for other details (i.e. the vision, timescales, business benefits and case studies) then please see the NHS Digital GP Connect Homepage.