Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 3.0.3 to CHANGELOG.md #786

Merged
merged 1 commit into from
Aug 23, 2024
Merged

Add 3.0.3 to CHANGELOG.md #786

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 14 additions & 7 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,13 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),

## [Unreleased]

## [3.0.3] - 2024-08-23

> [!NOTE]
> **Upgrade information** This release includes an update to the SNOMED database
> Users will need to perform an [update of their patient switching SNOMED database](OPERATING.md#updating-the-snomed-database).
> This will need to be performed first, followed by deploying the updated version of the translator image.

## Added
* If a `medicationStatement` or `medicationRequest` record includes a `confidentialityCode`, the `meta.security` field of the
corresponding FHIR resource will now be [appropriately populated][nopat-docs].
Expand All @@ -22,19 +29,19 @@ corresponding FHIR resource will now be [appropriately populated][nopat-docs].
corresponding FHIR resource will now be [appropriately populated][nopat-docs].
* If a `Observation`, `Specimen`, `DiagnosticReport` record includes a `confidentialityCode`, the `meta.security` field of the
corresponding FHIR resource will now be [appropriately populated][nopat-docs].
* Addressed a bug in the PS adaptor where immunizations were incorrectly mapped to observations.
The adaptor now verifies the Snomed CT ID against both the Concept ID and the Description ID, ensuring
that immunizations are correctly identified when a match is found.

### Fixed
* Resolved issue where the SNOMED import script would reject a password containing a '%' character.
* Fixed some Test Results being given a duplicated `Observation.category` entries for `Laboratory`.
* Fixed issue where the GPC Facade was not returning an error when an invalid `ConversationId` header
was provided.
was provided. The Facade will now return a 400 instead of a 500 HTTP response.
* Filing Comments were creating with incorrect `effectiveDateTime`, this is now set from the
`ehrComposition /author / time` instead.
* Filing Comments were creating with an incorrect `performer`, this now references the
`ehrComposition / author / agentRef` instead.
`ehrComposition /author / time` instead.
* Filing Comments were creating with an incorrect `performer`, this now references the
`ehrComposition / author / agentRef` instead.
* Addressed a bug in the PS adaptor where immunizations were incorrectly mapped to observations when
the Snomed CT code being sent was a Description ID. The adaptor previously only checked against
known vaccination Concept IDs.

## [3.0.2] - 2024-07-18

Expand Down