GP Connect API 1.3.2-beta released on 24th February 2020

Introduction

The GP Connect API 1.3.2-beta release contains updates to the additional profiles and extended API for accessing the Access Record Structured capability.

This release also contains changes from the 1.2.6 of the GP Connect API specification.

1.3.2-beta changes

Impacts provider and consumer systems

Access Record Structured

Updates to API

Tickets:  #848

Affects:  Access Record Structured

Impacts: Provider and Consumer systems

Description:

  • corrected an issue with the error handling for ‘consultationSearchPeriod’ - “The end date of the consultationSearchPeriod part parameter is greater than the start date” has been corrected to “The start date of the consultationSearchPeriod part parameter is greater than the end date”
  • in the example the value for ‘includeNumberOfMostRecent’ has been corrected to use an ‘integer’ and not a ‘string’
  • updated ‘includeNumberOfMostRecent’ to use the ‘positiveInt’ datatype instead of an ‘integer’
  • added error condition for a part parameter with no value
  • clarification stating that it is valid to include an empty Parameters.parameter in the case where it has only specified with optional part parameters
  • A set of rules have been added around combinations of parameters that consumers MUST NOT use due to potential clinical issues.
  • An error condition has been added for when a consumer has included a combination of parameters that isn’t permitted

Pages changed:

Updates to Search Criteria

Tickets:  #848

Affects:  Access Record Structured

Impacts: Provider and Consumer systems

Description:

  • changed the description for the use of consultation part parameters to make them mutually exclusive in accordance with other areas of the specification
  • added a section on requesting multiple clinical areas, potential for clinical risk in this situation and mitigations

Pages changed:

Added a new page for search examples

Affects:  Access Record Structured

Impacts: Provider and Consumer systems

Description:

  • Added a page that contains examples of what we think are likely to be common searches. It includes different approaches to searching for similar data

Pages changed:

Updates to Linkages

Tickets:  #919

Affects:  Access Record Structured

Impacts: Provider and Consumer systems

Description:

  • added a subsection ‘Dealing with confidential items’ to detail an exception for linkages to confidential problems

Pages changed:

Updates to Search Criteria and Linkages

Tickets:  #850

Affects:  Access Record Structured

Impacts: Provider and Consumer systems

Description:

  • updated the search criteria and linkages pages diagrams to represent all items from clinical areas being returned in the relevant list resource

Pages changed:

Updates to Consultations

Tickets:  #923

Affects:  Access Record Structured

Impacts: Provider and consumer systems

Description:

  • removed reference to the list.source from within the description for the participant element of an encounter

Pages changed:

Updates to uncategorised data guidance

Tickets: #681

Affects:  Access Record Structured

Impacts: Provider and consumer systems

Description:

  • updated to include guidance on how to represent blood pressure in GP Connect

Pages changed:

Added a page for observation blood pressure

Tickets: #681

Affects:  Access Record Structured

Impacts: Provider and consumer systems

Description:

  • details how the GP Connect observation profile is used to transport blood pressure

Pages changed:

Updates to Observation uncategorised data

Tickets: 

Affects:  Access Record Structured

Impacts: Provider and consumer systems

Description:

  • any reference ranges that contain a < or > operator should be sent as text in the referenceRange.text field

Pages changed:

Updates to Profiles

Tickets: 

Affects:  Access Record Structured

Impacts: Provider and consumer systems

Description:

  • small corrections to the following profiles
    • Encounter - participant valueset now has an option for AUTH to specify who recorded the Encounter
    • ProblemHeader - Condition.code.text cardinality relaxed from mandatory
    • MedicationRequest - extension[repeatInformation].numberOfRepeatPrescriptionsIssued data type has been changed to an unsignedInt as it needs to allow the value to be zero
    • Immunization - The fixed value on notGiven has been removed
  • The crossCareSettingIdentifier slice on identifier has been removed from the following profiles:
    • https://fhir.nhs.uk/STU3/StructureDefinition/CareConnect-GPC-Immunization-1
    • https://fhir.nhs.uk/STU3/StructureDefinition/CareConnect-GPC-Observation-1
    • https://fhir.nhs.uk/STU3/StructureDefinition/CareConnect-GPC-Encounter-1
    • https://fhir.nhs.uk/STU3/StructureDefinition/CareConnect-GPC-List-1
    • https://fhir.nhs.uk/STU3/StructureDefinition/CareConnect-GPC-ProblemHeader-Condition-1

Profiles changed:

Updates to Population of the codeable concept

Tickets: 

Affects:  Access Record Structured

Impacts: Provider and Consumer systems

Description:

  • The codable concept is a fundamental data type in the FHIR specification. In the UK we have extended this data type so that it is able to carry the SNOMED ConceptId AND DescriptionId. Extending in this way means there are a number of ways that these fields could be populated. This document describes in detail how this data type MUST be populated in the UK. Following a change of approach in the SNOMED for primary care project the way in which this is specified has changed significantly. All consumer and provider suppliers need to read the updated guidance in full and ensure they thoroughly understand the different scenarios that can occur and are documented here.

Pages changed:

Impacts provider systems

Foundations

Change version number in CapabilityStatement to 1.3.2

Affects:  Foundations

Description:

  • update version number in CapabilityStatement to 1.3.2

Pages changed:

Updates to Immunization

Tickets:  #885

Affects:  Access Record Structured

Impacts: Provider systems

Description:

  • expanded the description for the use of practitioner role codes

Pages changed:

Access Record Structured

Update Access Record Structured capability statement

Affects:  Access Record Structured

Description:

  • update version number in CapabilityStatement to 1.3.2
  • update minor version numbers in profile listing
  • update OperationDefinition minor version number

Pages changed:

No impact

Access Record Structured

Updates to Uncategorised example

Tickets: 

Affects:  Access Record Structured

Impacts: No impact

Description:

  • added missing list item for one of the returned Observation Resources

Pages changed:

Updates to consultations example

Tickets: 

Affects:  Access Record Structured

Impacts: No impact

Description:

  • includeNumberOfMostRecent has been corrected to use an integer and not a string

Pages changed:

Added search example page

Tickets: 

Affects:  Access Record Structured

Impacts: No impact

Description:

  • A page has been added that contains examples of searches that can be performed using the Access Record Structured capability

Pages changed: