GP Connect API 1.2.4-beta released on 30th August 2019

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-1 OperationDefinition 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.cors and CapabilityStatement.rest.resource.updateCreate now 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:


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:


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 List resource has been updated to allow more than one warning code to be included.

Pages changed:


Tickets#667

Affects:  Access Record Structured

Description:

  • The link to the GPConnect-GetStructuredRecord-Operation-1 OperationDefinition 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:

Pages changed:

MedicationRequest