Introduction
This specification enables patients to book, view and delete their appointments through third-party applications. The FHIR Messaging components are based on FHIR STU3 and are detailed FHIR Resources.
FHIR Messaging components specified within this API have been developed by NHS Digital and use CareConnect 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.
Find out more on the INTEROPen's Twitter.
Getting started
The enablement team can help get you started by guiding you in the following:
1. Confirming the GP Connect (Patient Facing) Appointment Management 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 Appointment Management capability
Contact gpconnect@nhs.net about your use case for the Appointment Management 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.