Introduction
The GP Connect API 1.2.4-beta release contains:
1.2.4-beta changes
Core
Foundations
Change version number in CapabilityStatement to 1.2.4-beta
Tickets: #694
Affects: Foundations
Description:
- Update version number in CapabilityStatement to 1.2.4-beta
Pages changed:
Update GetStructuredRecord OperationDefinition reference in CapabilityStatement to point to correct version
Tickets: #666
Affects: Access Record Structured, Foundations
Description:
- The reference to the
GPConnect-GetStructuredRecord-Operation-1OperationDefinition has been updated to point at the version that is supported in 1.2.4 of the GP Connect API specification.
Pages changed:
Update sample CapabilityStatement to use JSON Boolean values
Tickets: #833
Affects: Foundations
Description:
- the values for
CapabilityStatement.rest.security.corsandCapabilityStatement.rest.resource.updateCreatenow use Boolean values
Pages changed:
Appointment Management
Clarify position on Read/Retrieve/Amend/Cancel Appointments for non-GP Connect booked appointments
Tickets: #663
Affects: Appointment Management
Description:
-
Read an Appointment/Retrieve a Patient’s Appointments/Amend an Appointment/Cancel an Appointment all operate regardless of whether the appointment was booked via GP Connect or not
-
The specification has been amended to make this clear
Pages changed:
- Retrieve a patient’s appointments
- Read an appointment
- Amend an appointment
- Cancel an appointment
- Amend use case section of each page to add clarification
DOS service discovery
Tickets: #662
Affects: Appointment Management, Core, Foundations
Description:
- PDS allows an Appointment Management consumer to determine a patient’s registered practice. Where an appointment booking at another practice is required, the specification now documents the flows required to determine this other practice, including integration with the Directory of Services (DOS) system for Urgent and Emergency Care consumers.
Pages changed:
- Spine integration illustrated
- Add new Overview section with high level GP Connect flow diagram and description
- Add call out box on Appointment Management Service Discovery
- Add note to step 2 in the worked example
- Appointment Management Service Discovery
- New page to outline different mechanisms for determining the GP practice to book into
Access Record Structured
Add forwards compatibility support
Tickets: #669
Affects: Access Record Structured
Description:
- This version of the GP Connect API specification requires a mechanism for handling forwards compatibility, providers are now required to warn consumers about parameters that were unrecognised.
- Bundle in response may contain an OperationOutcome resource containing warnings
- Providers will now only reject a request when it contains no valid parameters
- Consumers must check for the presence of warnings about unrecognised parameters
Pages changed:
Update List to include more than one warning code
Tickets: #647
Affects: Access Record Structured
Description:
- The
Listresource has been updated to allow more than one warning code to be included.
Pages changed:
Update link to OperationDefinition in API page to point to correct version
Tickets: #667
Affects: Access Record Structured
Description:
- The link to the
GPConnect-GetStructuredRecord-Operation-1OperationDefinition has been updated to point at the version that is supported in 1.2.4 of the GP Connect API specification.
Pages changed:
Changes to MedicationRequest
Tickets: #654
Affects: Access Record Structured
Description:
- Clarification on when
dispenseRequest.performershould be populated - Added system for EPS identifier to
identifier- https://fhir.nhs.uk/Id/eps-line-item-identifier
Pages changed: