Introduction
This specification enables the updating of the patient's GP record using ITK3, GP Connect data model (based on STU3), and MESH.
FHIR Messaging components specified within this site have been developed by NHS England and use GP Connect profiles created in collaboration with the INTEROPen community.
The INTEROPen vision is to create a library of nationally defined HL7® FHIR® resources and interaction patterns that implementers can adopt to simplify integration and interoperability within England’s health and social care systems.
Use of ITK3 for this capability
Due to timeline constraints, a decision was made to pivot to using ITK3/MESH as the delivery mechanism, with the GP Connect data model to be used in the payload.
This capability is only authorized for Pharmacy First. The intention is to focus on the ingestion of STU3 Care Connect profiles using ITK3 for pharmacy, and then swap out the delivery mechanism for a full API at a later date. The full API will still use the STU3 representation of the GP Connect data model, only the delivery mechanism will change.
The GP Connect data model, which is a STU3 representation, has been chosen for this capability to align to Access Record: Structured. Suppliers have already developed against this specification, so it will be quicker to ingest the data from these profiles. The strategic goal is to create a RESTful GP Connect API for both accessing and updating the patient GP record within FHIR R4 (UK Core), harnessing the GP Connect data model, promoting usage of services such as the National Record Locator and the National Event Manager where possible.
Clinical engagement
To help ensure that the functionality being developed will be able to support GP practices, Direct Care APIs has engaged with a range of GP practice staff to get an understanding of how that data may be used and what is required to support that use.
This engagement has included:
- general practitioners
- pharmacists
- practice managers
- GP practice administration staff
The initial use case for this specification will be for data flowing between Community Pharmacy, and GP systems, for the following services:
- Blood pressure service
- Contraception service
- CPCS Minor illness (including the common conditions extension) service
How to get started with this capability
1. Confirming the Update Record (ITK3) capability fulfils the use case requirements
Read through this specification to ensure that it fulfils the requirements for your use case, and that the sending or receiving system(s) can meet the data requirements - for example, having the information required to populate the FHIR resources as described in this specification.
2. Submit your use case for the Update Record (ITK3) capability
Contact gpconnect@nhs.net about your use case for the Update Record (ITK3) capability.
3. Getting your use case approved
Use cases are approved on the basis that development is started for the capability approved within six months. If this date is missed, then a review of the case will be required.
4. Getting conformance
Once approved, the service practitioner will:
- introduce the assurance process and artefacts to gain technical conformance
- set up a Microsoft Teams page which will be used to raise queries
5. Assurance
The developed solution will require assurance before it can be enabled in production. Read more on the GP Connect Consumer Support Hub wiki.
Suppliers using this capability
This is due to certain use cases that require data to be sent but not necessarily received.
Senders should take care to ensure that supplier systems and other intended recipients have implemented the capability to receive.
Please review the progress by supplier for a complete list of suppliers and implemented GP Connect capabilities.