From 6fa186bae43db79d3c9dab676f4a51786732a779 Mon Sep 17 00:00:00 2001
From: Adrian Clay <adrian.clay1@nhs.net>
Date: Mon, 14 Oct 2024 11:38:19 +0100
Subject: [PATCH] Add 2.1.0 to CHANGELOG.md (#936)

---
 CHANGELOG.md | 40 +++++++++++++++++++++++-----------------
 1 file changed, 23 insertions(+), 17 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index a1cec1ef2..51e21c479 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -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