- Introduction
- 1.6.2 changes
- General
- Access Documents
- Access Record Structured
- Correct syntax in examples
- Update dose syntax to support Information Standards Notice DAPB4013
- Clarify handling for MedicationRequest with intent of order when plan has been discontinued
- Update Specimen collection.extension[fastingStatus] to include coded concept
- Add links to clarify guidance for multiple clinical area searches
- Clarify list population for Consultations and Problems
- Clarify allergy/intolerance category use
- Allow ProcedureRequest.supportingInfo to reference a Resource
- Clarify MedicationStatement.dateAsserted
- DiagnosticReport.identifier may be the lab report ID
- Test groups, test reports and test results may have many filing comments
- Clarify overarching principles for MedicationRequest element population
- Remove potentially confusing statement from Medication.code
- Clarify how legacy MedicationRequest.prescriptionType data should be handled
- Fix typo on medication resource relationship diagrams
- Clarify use of MedicationRequest.dispenseRequest.quantity and MedicationRequest.dispenseRequest.quantityText
- Binding strength for VaccinationProcedure reduced to preferred
- Update MedicationRequest.medication and MedicationStatement.medication datatype
- Add HealthcareService to list of administrative resources
Introduction
The GP Connect API 1.6.2-beta release contains:
- dose syntax changes
The changes that are inherited from 1.6.1 can be found in 1.6.1 release notes.
Changes may affect more than one capability. Please see the Affects label for details of the capabilities changed.
1.6.2 changes
General
Updates to capability statement
Affects: Access Documents, Access Record Structured, Foundations
Impacts: Provider and consumer systems
Description:
- version number has been changed to 1.6.2
CareConnect-GPC-Practitioner-1profile version updated to 1.3CareConnect-GPC-ProcedureRequest-1profile version updated to 1.4
Pages changed:
- Get the FHIR® capability statement for Access Document
- Get the FHIR® capability statement for Access Record Structured
- Get the FHIR® capability statement for Foundations
Practitioner.name.family cardinality has been relaxed to optional
Affects: Access Documents, Access Record Structured, Foundations
Impacts: Provider and consumer systems
Description:
- The cardinality of Practitioner.name.family has been relaxed to be optional
Pages changed:
Resources may contain a ‘no disclosure to patient’ security label
Affects: Access Documents, Access Record Structured
Impacts: N/A
Description:
- Resources may have Meta.security populated with a security label indicating information is not to be disclosed to the patient
Pages changed:
- FHIR resources
- AllergyIntolerance
- DiagnosticReport
- Diary entry
- DocumentReference
- Encounter
- Immunization
- MedicationRequest
- MedicationStatement
- Observation (blood pressure)
- Observation (filing comments)
- Observation (narrative)
- Observation (test group)
- Observation (test header)
- Observation (uncategorised data)
- ProblemHeader (Condition)
- ProcedureRequest
- ReferralRequest
- Specimen
CareConnect-SDSJobRoleName-1 CodeSystem updated with additional job roles
Affects: Access Documents, Access Record Structured
Impacts: Provider and consumer systems
Description:
- A number of additional job roles have been added to the CareConnect-SDSJobRoleName-1 CodeSystem
Pages changed:
- N/A
Access Documents
Clarify documents search API author parameter can not be used to search by practitioner
Affects: Access Documents
Impacts: Consumer systems
Description:
- Documents search API author parameter only searches for organisation authors
Pages changed:
Clarify 100MB file size is not a limit for migrate a document
Affects: Access Documents
Impacts: Consumer systems
Description:
- Clarify 100MB file size is not a limit for the migrate a document API response
Pages changed:
Access Record Structured
Correct syntax in examples
Affects: Access Record Structured
Impacts: N/A
Description:
- Correct syntax in examples
Pages changed:
Update dose syntax to support Information Standards Notice DAPB4013
Affects: Access Record Structured
Impacts: Provider and consumer systems
Description:
- Dose syntax has been updated to provide compliance with Information Standards Notice ISN DAPB4013
Pages changed:
- Guidance for populating and consuming the MedicationRequest profile
- Guidance for populating and consuming the MedicationStatement profile
Clarify handling for MedicationRequest with intent of order when plan has been discontinued
Affects: Access Record Structured
Impacts: Provider and consumer systems
Description:
- The guidance for a MedicationRequest’s status in a scenario where a MedicationRequest with intent of order that is part of a discontinued plan has been clarified i.e. it should not be updated to stopped
Pages changed:
Update Specimen collection.extension[fastingStatus] to include coded concept
Affects: Access Record Structured
Impacts: Provider and consumer systems
Description:
- Specimen collection.extension[fastingStatus] has been updated to be returned as a coding using relevantClincialInformation ValueSet alongside the text
Pages changed:
Add links to clarify guidance for multiple clinical area searches
Affects: Access Record Structured
Impacts: N/A
Description:
- Additional links to existing guidance have been added to the guidance for multiple clinical area searches on patient record retrieval
Pages changed:
Clarify list population for Consultations and Problems
Affects: Access Record Structured
Impacts: N/A
Description:
- Clarify list population for Consultations and Problems within the response payload, based on the info from the Linkages page
Pages changed:
Clarify allergy/intolerance category use
Affects: Access Record Structured
Impacts: Provider systems
Description:
- AllergyIntolerance.category MUST use
medicationwhen allergy type is not distinguishable betweenmedicationandenvironment
Pages changed:
Allow ProcedureRequest.supportingInfo to reference a Resource
Affects: Access Record Structured
Impacts: N/A
Description:
- ProcedureRequest.supportingInfo can reference a Resource, facilitating the linking of a document
Pages changed:
Clarify MedicationStatement.dateAsserted
Affects: Access Record Structured
Impacts: N/A
Description:
- Clarified MedicationStatement.dateAsserted should be the date the authorisation is entered onto the record if the information source is unclear
Pages changed:
DiagnosticReport.identifier may be the lab report ID
Affects: Access Record Structured
Impacts: Provider and consumer systems
Description:
- If the lab report ID uses the NHS PMIP Report Numbers CodeSystem and it could be used by consumers to match lab reports it can be included in DiagnosticReport.identifier
Pages changed:
Test groups, test reports and test results may have many filing comments
Affects: Access Record Structured
Impacts: Provider and consumer systems
Description:
- Test groups, test reports and test results are not limited to a single filing comment. Guidance and diagrams have been updated to reflect this
Pages changed:
Clarify overarching principles for MedicationRequest element population
Affects: Access Record Structured
Impacts: Provider and consumer systems
Description:
- MedicationRequest elements should be populated when data is available, even if that means there is duplication in other MedicationRequest resources
Pages changed:
Remove potentially confusing statement from Medication.code
Affects: Access Record Structured
Impacts: N/A
Description:
- A potentially confusing statement has been removed from the Medication.code element guidance. The (already linked) CodeableConcept guidance document is more prominent
Pages changed:
Clarify how legacy MedicationRequest.prescriptionType data should be handled
Affects: Access Record Structured
Impacts: Provider and consumer systems
Description:
- How to handle MedicationRequest.prescriptionType when no data is available has been clarified
Pages changed:
Fix typo on medication resource relationship diagrams
Affects: Access Record Structured
Impacts: N/A
Description:
- Medication resource relationship diagrams have been corrected so all cardinalities are numeric
Pages changed:
Clarify use of MedicationRequest.dispenseRequest.quantity and MedicationRequest.dispenseRequest.quantityText
Affects: Access Record Structured
Impacts: Provider and consumer systems
Description:
- Clarified how MedicationRequest.dispenseRequest.quantity and MedicationRequest.dispenseRequest.quantityText should be used
Pages changed:
Binding strength for VaccinationProcedure reduced to preferred
Affects: Access Record Structured
Impacts: Provider and consumer systems
Description:
- The binding strength of the VaccinationProcedure extension element for the Immunization profile has been reduced from required to preferred
Pages changed:
- N/A
Update MedicationRequest.medication and MedicationStatement.medication datatype
Affects: Access Record Structured
Impacts: Provider and consumer systems
Description:
- MedicationRequest and MedicationStatement profiles have had the constraint on the medication element relaxed so they align with the base profile i.e. medication can be either a reference or a CodeableConcept. This is to accommodate use cases such as updating the record where only a single medication is needed and a CodeableConcept would mean a separate Medication resource is not needed as there would be no other references to it. The guidance is for both consumers and suppliers to treat the element as if it is a reference.
Pages changed:
Add HealthcareService to list of administrative resources
Affects: Access Record Structured
Impacts: N/A
Description:
- HealthcareService has been listed as an administrative resource
Pages changed: