Skip to content

Commit

Permalink
Add 2.1.0 to CHANGELOG.md (#936)
Browse files Browse the repository at this point in the history
  • Loading branch information
adrianclay authored Oct 14, 2024
1 parent 21c86a2 commit 6fa186b
Showing 1 changed file with 23 additions and 17 deletions.
40 changes: 23 additions & 17 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,38 +6,44 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### Fixed

* When mapping `ProcedureRequests` with an `occurrencePeriod` which contains only a start date, then the `text` element
in the resultant XML will no longer contain the superfluous 'Earliest Recall Date: <startDate>' value.
* When mapping `ProcedureRequests` with a `requestor` referencing a `device` without a `manufacturer` a spurious
`"null"` is no longer output in the generated `"Recall Device:"` text.
* When mapping an `Encounter` without a Recorder `participant`, now send the author as `nulFlavor=UNK`.
Previously this would raise the error "EhrMapperException: Encounter.participant recorder is required" and send a
failure to the requesting system.

### Added

* When mapping consultations which are "flat" (i.e., they contain a `TOPIC` without a `CATEGORY`) we now wrap the
resource into a virtual `CATEGORY`.
* Added a scheduled delay checker to update EhrExtract to "Integration Failure" state if sentAt exceeds 8 days and no acknowledgment is received.
* When mapping a `DocumentReference` which contains a `NOPAT` `meta.security` or `NOPAT` `securityLabel` tag the resultant XML for that resource
will contain a `NOPAT` `confidentialityCode` element.
* When mapping `AllergyIntolerances` which contain a `NOPAT` `meta.security` tag the resultant XML for that resource
will contain a `NOPAT` `confidentialityCode` element.
* When mapping a `DiagnosticReport` or `Specimen` which contains a `NOPAT` `meta.security` tag the resultant XML for that resource
will contain a `NOPAT` `confidentialityCode` element.
* When mapping a `TestResult`, `TestGroupHeader` or `FilingComment` which contains a `NOPAT` `meta.security` tag the resultant XML
* When mapping a `TestResult`, `TestGroupHeader` or `FilingComment` which contains a `NOPAT` `meta.security` tag the resultant XML
for that resource will contain a `NOPAT` `confidentialityCode` element.
* When mapping a `Condition` which contains a `NOPAT` `meta.security` tag the resultant XML for that resource
will contain a `NOPAT` `confidentialityCode` element.
* When mapping a `MedicationRequest (PLAN)` which contains a `NOPAT` `meta.security` tag the resultant XML for that
* When mapping a `MedicationRequest (PLAN)` which contains a `NOPAT` `meta.security` tag the resultant XML for that
resource will contain a `NOPAT` `confidentialityCode` element.
* When mapping a `MedicationRequest (ORDER)` which contains a `NOPAT` `meta.security` tag the resultant XML for that
resource will contain a `NOPAT` `confidentialityCode` element.
* When mapping `Immunizations` which contain a `NOPAT` `meta.security` tag, the resultant XML for that resource
will contain a `NOPAT` `confidentialityCode` element.

## [2.1.0] - 2024-10-14

### Added

* Added functionality to automatically update the migration status to `FAILED_INCUMBENT` for any transfer where the
adaptor hasn't received an acknowledgement from the requesting GP surgery and the health record was sent to them more
than 8 days ago.

### Fixed

* When mapping consultations which are "flat" (i.e., they contain a `TOPIC` without a `CATEGORY`) we now wrap the
resource into a virtual `CATEGORY`.
This provides compatability with a GP2GP system which would reject the transfer otherwise.
* When mapping an `Encounter` without a Recorder `participant`, now send the author as `nulFlavor=UNK`.
Previously this would raise the error "EhrMapperException: Encounter.participant recorder is required" and send a
failure to the requesting system.
* When mapping `ProcedureRequests` with an `occurrencePeriod` which contains only a start date, then the `text` element
in the resultant XML will no longer contain the superfluous 'Earliest Recall Date: <startDate>' value.
* When mapping `ProcedureRequests` with a `requestor` referencing a `device` without a `manufacturer` a spurious
`"null"` is no longer output in the generated `"Recall Device:"` text.

## [2.0.6] - 2024-07-29

### Added
Expand Down

0 comments on commit 6fa186b

Please sign in to comment.