updates per feedback

Author: KendalBond007

articles/healthcare-apis/azure-api-for-fhir/release-notes.md

@@ -17,6 +17,18 @@ ms.author: kavitagaddam
 
 Azure API for FHIR® provides a fully managed deployment of the Microsoft FHIR Server for Azure. The server is an implementation of the [FHIR](https://hl7.org/fhir) standard. This document provides details about the features and enhancements made to Azure API for FHIR.
 
+## **October 2024**
+
+### FHIR service
+
+**Bug fixes**
+
+- Export Validation: An issue was identified where exports proceeded despite invalid search parameters. We are introducing a change that prevents exports under these conditions. This feature is currently behind a strict validation flag and will become the default behavior on or after October 30th. [Reference #4617]
+- Search Parameter Inclusion: We resolved an issue where additional search parameters (for instance, `_include`, `_has`) did not return all expected results, sometimes omitting the next link. [Reference 4613]
+- Export Job Execution: A rare occurrence of `System.ObjectDisposedException` during export job completion has been addressed by preventing premature exits. [Reference #4268]
+- HTTP Status Code Update: The HTTP status code for invalid parameters during `$reindex` job creation is now updated to 400, ensuring better error handling. [Reference #4439]
+- Search Parameter Cleanup: A fix has been implemented to ensure complete cleanup of search parameters in the database when triggered with delete API calls, addressing issues related to incomplete deletions. [Reference #4623]
+
 ## **August 2024**
 
 ### FHIR service

articles/healthcare-apis/release-notes-2024.md

@@ -19,48 +19,17 @@ This article describes features, enhancements, and bug fixes released in 2024 fo
 
 ### Azure Health Data Services
 
-#### Bug fixes
-
-- Export Validation: An issue was identified where exports proceeded despite invalid search parameters. We're introducing a change that prevents exports under these conditions. This feature is currently behind a strict validation flag and will become the default behavior on or after October 30. [Reference #4617]
-
-- Search Parameter Inclusion: We resolved an issue where additional search parameters (such as `_include`, `_has`) didn't return all expected results, sometimes omitting the next link. [Reference 4613]
-
-- Export Job Execution: A rare occurrence of `System.ObjectDisposedException` during export job completion has been addressed by preventing premature exits. [Reference #4268]
-
-- HTTP Status Code Update: The HTTP status code for invalid parameters during `$reindex` job creation is now updated to 400, ensuring better error handling. [Reference #4439]
-
-- Search Parameter Cleanup: A fix has been implemented to ensure complete cleanup of search parameters in the database when triggered with delete API calls, addressing issues related to incomplete deletions. [Reference #4623]
-
-- Descending Sort Issue: Resolved an issue where descending sort operations returned no resources if the sorted field had no data in the database, even when relevant resources existed. [Reference #4661]
-
-- Authentication Failure Handling: Added a new catch block to manage authentication failures when import requests are executed with managed identity turned off. [Reference #4255]
-
 ### FHIR service
 
-#### Enhancements
-
-- Delete Operation: The FHIR service now supports both `_hardDelete` and `hardDelete` query parameters for delete operations. This change ensures consistent outcomes when using either parameter. [Reference #4662]
-
-- Arithmetic Overflow Handling: Implemented a better error handling to address arithmetic overflow exceptions for import requests or API calls with decimal precision exceeding FHIR specifications, now returning an HTTP status code of 400. [Reference #4587]
-
-### Azure API for FHIR
-
-#### Enhancements
-
-- Delete Operation: The FHIR service now supports both `_hardDelete` and `hardDelete` query parameters for delete operations. This change ensures consistent outcomes when using either parameter. [Reference #4662]
-
 #### Bug fixes
 
 - Export Validation: An issue was identified where exports proceeded despite invalid search parameters. We're introducing a change that prevents exports under these conditions. This feature is currently behind a strict validation flag and will become the default behavior on or after October 30. [Reference #4617]
-
-- Search Parameter Inclusion: We resolved an issue where additional search parameters (for example, `_include`, `_has`) didn't return all expected results, sometimes omitting the next link. [Reference 4613]
-
+- Search Parameter Inclusion: We resolved an issue where additional search parameters (for instance, `_include`, `_has`) didn't return all expected results, sometimes omitting the next link. [Reference 4613]
 - Export Job Execution: A rare occurrence of `System.ObjectDisposedException` during export job completion has been addressed by preventing premature exits. [Reference #4268]
-
 - HTTP Status Code Update: The HTTP status code for invalid parameters during `$reindex` job creation is now updated to 400, ensuring better error handling. [Reference #4439]
-
 - Search Parameter Cleanup: A fix has been implemented to ensure complete cleanup of search parameters in the database when triggered with delete API calls, addressing issues related to incomplete deletions. [Reference #4623]
-
+- Descending Sort Issue: Resolved an issue where descending sort operations returned no resources if the sorted field had no data in the database, even when relevant resources existed. [Reference #4661]
+- Authentication Failure Handling: Added a new catch block to manage authentication failures when import requests are executed with managed identity turned off. [Reference #4255]
 
 ## September 2024