Skip to content

Commit 6fa186b

Browse files
author
Adrian Clay
authored
Add 2.1.0 to CHANGELOG.md (#936)
1 parent 21c86a2 commit 6fa186b

File tree

1 file changed

+23
-17
lines changed

1 file changed

+23
-17
lines changed

CHANGELOG.md

Lines changed: 23 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -6,38 +6,44 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
66

77
## [Unreleased]
88

9-
### Fixed
10-
11-
* When mapping `ProcedureRequests` with an `occurrencePeriod` which contains only a start date, then the `text` element
12-
in the resultant XML will no longer contain the superfluous 'Earliest Recall Date: <startDate>' value.
13-
* When mapping `ProcedureRequests` with a `requestor` referencing a `device` without a `manufacturer` a spurious
14-
`"null"` is no longer output in the generated `"Recall Device:"` text.
15-
* When mapping an `Encounter` without a Recorder `participant`, now send the author as `nulFlavor=UNK`.
16-
Previously this would raise the error "EhrMapperException: Encounter.participant recorder is required" and send a
17-
failure to the requesting system.
18-
19-
### Added
20-
21-
* When mapping consultations which are "flat" (i.e., they contain a `TOPIC` without a `CATEGORY`) we now wrap the
22-
resource into a virtual `CATEGORY`.
23-
* Added a scheduled delay checker to update EhrExtract to "Integration Failure" state if sentAt exceeds 8 days and no acknowledgment is received.
249
* When mapping a `DocumentReference` which contains a `NOPAT` `meta.security` or `NOPAT` `securityLabel` tag the resultant XML for that resource
2510
will contain a `NOPAT` `confidentialityCode` element.
2611
* When mapping `AllergyIntolerances` which contain a `NOPAT` `meta.security` tag the resultant XML for that resource
2712
will contain a `NOPAT` `confidentialityCode` element.
2813
* When mapping a `DiagnosticReport` or `Specimen` which contains a `NOPAT` `meta.security` tag the resultant XML for that resource
2914
will contain a `NOPAT` `confidentialityCode` element.
30-
* When mapping a `TestResult`, `TestGroupHeader` or `FilingComment` which contains a `NOPAT` `meta.security` tag the resultant XML
15+
* When mapping a `TestResult`, `TestGroupHeader` or `FilingComment` which contains a `NOPAT` `meta.security` tag the resultant XML
3116
for that resource will contain a `NOPAT` `confidentialityCode` element.
3217
* When mapping a `Condition` which contains a `NOPAT` `meta.security` tag the resultant XML for that resource
3318
will contain a `NOPAT` `confidentialityCode` element.
34-
* When mapping a `MedicationRequest (PLAN)` which contains a `NOPAT` `meta.security` tag the resultant XML for that
19+
* When mapping a `MedicationRequest (PLAN)` which contains a `NOPAT` `meta.security` tag the resultant XML for that
3520
resource will contain a `NOPAT` `confidentialityCode` element.
3621
* When mapping a `MedicationRequest (ORDER)` which contains a `NOPAT` `meta.security` tag the resultant XML for that
3722
resource will contain a `NOPAT` `confidentialityCode` element.
3823
* When mapping `Immunizations` which contain a `NOPAT` `meta.security` tag, the resultant XML for that resource
3924
will contain a `NOPAT` `confidentialityCode` element.
4025

26+
## [2.1.0] - 2024-10-14
27+
28+
### Added
29+
30+
* Added functionality to automatically update the migration status to `FAILED_INCUMBENT` for any transfer where the
31+
adaptor hasn't received an acknowledgement from the requesting GP surgery and the health record was sent to them more
32+
than 8 days ago.
33+
34+
### Fixed
35+
36+
* When mapping consultations which are "flat" (i.e., they contain a `TOPIC` without a `CATEGORY`) we now wrap the
37+
resource into a virtual `CATEGORY`.
38+
This provides compatability with a GP2GP system which would reject the transfer otherwise.
39+
* When mapping an `Encounter` without a Recorder `participant`, now send the author as `nulFlavor=UNK`.
40+
Previously this would raise the error "EhrMapperException: Encounter.participant recorder is required" and send a
41+
failure to the requesting system.
42+
* When mapping `ProcedureRequests` with an `occurrencePeriod` which contains only a start date, then the `text` element
43+
in the resultant XML will no longer contain the superfluous 'Earliest Recall Date: <startDate>' value.
44+
* When mapping `ProcedureRequests` with a `requestor` referencing a `device` without a `manufacturer` a spurious
45+
`"null"` is no longer output in the generated `"Recall Device:"` text.
46+
4147
## [2.0.6] - 2024-07-29
4248

4349
### Added

0 commit comments

Comments
 (0)