Merge pull request #277072 from EXPEkesheth/releasenotes-2024-fhirservice

Release notes 2024 FHIR service

Author: prmerger-automator[bot]

articles/healthcare-apis/azure-api-for-fhir/purge-history.md

@@ -33,6 +33,8 @@ The `$purge-history` operation was created to help with the management of resour
 
 Since `$purge-history` is a resource level operation versus a type level or system level operation, you'll need to run the operation for every resource that you want remove the history from.
 
+By default, the purge history operation waits for successful completion before deleting resources. However, if any errors occur during the execution of the purge-history operation, the deletion of resources is rolled back. To prevent this rollback behavior, use the optional query parameter ‘allowPartialSuccess’ and set it to true during the purge-history call. This step ensures that the transaction isn't rolled back in case of an error.
+
 ## Examples of purge history
 
 To use `$purge-history`, you must add `/$purge-history` to the end of a standard delete request. The template of the request is:
@@ -46,6 +48,12 @@ For example:
 ```http
 DELETE https://workspace-fhir.fhir.azurehealthcareapis.com/Observation/123/$purge-history
 ```
+
+To use the 'allowPartialSuccess' parameter, you need to set it to true. The template of request is:
+```http
+DELETE <FHIR-Service-Url>/<Resource-Type>/<Resource-Id>/$purge-history?allowPartialSuccess=true
+```
+
 ## Next steps
 
 In this article, you learned how to purge the history for resources in Azure API for FHIR. For more information about Azure API for FHIR, see

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

@@ -17,6 +17,17 @@ 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.
 
+## **May 2024**
+
+### FHIR service
+**Enhancements to the purge-history operation**
+The purge-history operation allows you to perform a partial delete by using the query parameter ‘allowPartialSuccess’. By default, the purge-history operation waits for successful completion before deleting resources. However, if an error occurs during execution, the deletion of resources is rolled back. By using the ‘allowPartialSuccess’ query parameter, you can prevent the transaction from being rolled back in case of an error.
+
+**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, a history request in a bundle returned HTTP status code 404.
+
 ## **March 2024**
 **Batch-bundle parallelization**
 Batch bundles are executed serially in FHIR service by default. To improve throughput with bundle calls, we enabled parallel processing of batch bundles.

articles/healthcare-apis/fhir/import-data.md

@@ -60,7 +60,7 @@ To achieve the best performance with the `import` operation, consider these fact
 
 - **Import FHIR resource files as a single batch**. For optimal performance, import all the FHIR resource files that you want to ingest in the FHIR server in one `import` operation. Importing all the files in one operation reduces the overhead of creating and managing multiple import jobs. The combined total size of all the files in a single import should be greater than 100 GB or 100 M resources. 
 
-- **Limit the number of parallel import jobs**. You can run multiple `import` jobs at the same time, but running multiple jobs might affect the overall throughput of the `import` operation. The FHIR server can handle up to five parallel `import` jobs. If you exceed this limit, the FHIR server might throttle or reject your requests.
+- **Limit the number of parallel import jobs**. You can run multiple `import` jobs at the same time, but running multiple jobs might affect the overall throughput of the `import` operation. 
 
 ## Perform the import operation
 

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

@@ -19,6 +19,16 @@ This article describes features, enhancements, and bug fixes released in 2024 fo
 
 ### Azure Health Data Services
 
+### FHIR service
+
+#### Scaling enhancement to Import operation
+
+The scaling logic for import operations has been improved enabling multiple jobs to be executed in parallel. This change has an impact on audit logs for import operation. Audit logs for individual import jobs will now have multiple rows, with each row corresponding to an internal processing job. 
+
+#### Bug Fixes
+- **Fixed: HTTP Status Code for Long-Running Requests** FHIR requests that take longer than 100 seconds to execute will now 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.
+
 #### Stand-alone FHIR converter (preview)
 
 The stand-alone FHIR converter API available for preview is decoupled from the FHIR service and packaged as a container (Docker) image. In addition to enabling you to convert data from the source of record to FHIR R4 bundles, the FHIR converter offers: