updates per ADO130496

Author: KendalBond007

articles/healthcare-apis/includes/rest-api-bundle-common.md

@@ -76,5 +76,5 @@ Transaction bundles don't support:
 Batch and transaction bundles are executed serially in the FHIR service. To improve performance and throughput, we enabled parallel processing of bundles.
 
 To use parallel batch bundle processing:
-- Set header `x-bundle-processing-logic` value to 1parallel`.
+- Set header `x-bundle-processing-logic` value to `parallel`.
 - Ensure there's no overlapping resource ID that executes on DELETE, POST, PUT, or PATCH operations in the same bundle.

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

@@ -15,14 +15,61 @@ ms.custom: references_regions
 
 This article describes features, enhancements, and bug fixes released in 2024 for the FHIR® service, DICOM® service, and MedTech service in Azure Health Data Services.
 
+## October 2024
+
+### 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]
+
+- 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]
+
+
 ## September 2024
 
 ### Azure Health Data Services
 
 ### FHIR service
 
 #### Enhanced Export Efficiency
-The export functionality has been improved to optimize memory usage. With this change the  export process now pushes data to blob storage one resource at a time, reducing memory consumption. 
+The export functionality has been improved to optimize memory usage. With this change, the export process now pushes data to blob storage one resource at a time, reducing memory consumption. 
 
 ## August 2024
 
@@ -31,8 +78,8 @@ The export functionality has been improved to optimize memory usage. With this c
 ### FHIR service
 
 #### Import operation error handling
-1. The import operation returns a HTTP 400 error when a search parameter resource is ingested via the import process. This change is intended to prevent search parameters from being placed in an invalid state when ingested with an import operation.
-2. The import operation will return a HTTP 400 status code, as opposed to the previous HTTP 500 status code, in cases where configuration issues with the storage account occur. This update aims to improve error handling associated with managed identities during import operations. 
+1. The import operation returns an HTTP 400 error when a search parameter resource is ingested via the import process. This change is intended to prevent search parameters from being placed in an invalid state when ingested with an import operation.
+2. The import operation returns an HTTP 400 status code, as opposed to the previous HTTP 500 status code, in cases where configuration issues with the storage account occur. This update aims to improve error handling associated with managed identities during import operations. 
 
 ## July 2024
 
@@ -59,7 +106,7 @@ Updating Status Code from HTTP 500 to HTTP 400
 During a patch operation, if the payload requested an update for a resource type other than parameter, an internal server error (HTTP 500) was initially thrown. This has been updated to throw an HTTP 400 error instead.
 
 #### Performance enhancement
-Query optimization is added when searching FHIR resources with a data range. This query optimization will help with efficient querying as one combined CTE is generated.
+Query optimization is added when searching FHIR resources with a data range. This query optimization helps with efficient querying as one combined CTE is generated.
 
 ## May 2024
 
@@ -73,7 +120,7 @@ The scaling logic for import operations is improved, enabling multiple jobs to b
 
 #### Bug fixes
 - **Fixed: HTTP status code for long-running requests**. FHIR requests that take longer than 100 seconds to execute return an HTTP 408 status code instead of HTTP 500. 
-- **Fixed: History request in bundle**. Prior to the fix, history request in a bundle returned HTTP status code 404.
+- **Fixed: History request in bundle**. Before the fix, history request in a bundle returned HTTP status code 404.
 
 #### Stand-alone FHIR converter (preview)