FHIR Release 4.0.91 notes

Author: EXPEkesheth

articles/healthcare-apis/azure-api-for-fhir/fhir-rest-api-capabilities.md

@@ -124,16 +124,13 @@ In the case of a batch, each entry is treated as an individual interaction or op
 > [!NOTE]
 > For batch bundles there should be no interdependencies between different entries in FHIR bundle. The success or failure of one entry should not impact the success or failure of another entry.
 
-### Batch bundle parallel processing in public preview 
+### Batch bundle parallel processing
 
 Currently batch bundles are executed serially in FHIR service. To improve performance and throughput, we're enabling parallel processing of batch bundles in public preview.  
 To use the capability of parallel batch bundle processing-
 * Set header “x-bundle-processing-logic” value to “parallel”. 
 * Ensure there's no overlapping resource ID that is executing on DELETE, POST, PUT or PATCH operations in the same bundle.
 
-> [!IMPORTANT]
-> Bundle parallel processing is currently in public preview. Preview APIs and SDKs are provided without a service-level agreement. We recommend that you don't use them for production workloads. Some features might not be supported, or they might have constrained capabilities. For more information, review Supplemental Terms of Use for Microsoft Azure Previews 
-
 ## Patch and Conditional Patch
 
 Patch is a valuable RESTful operation when you need to update only a portion of the FHIR resource. Using patch allows you to specify the element(s) that you want to update in the resource without having to update the entire record. FHIR defines three ways to Patch resources: JSON Patch, XML Patch, and FHIRPath Patch. The FHIR Service support both JSON Patch and FHIRPath Patch along with Conditional JSON Patch and Conditional FHIRPath Patch (which allows you to Patch a resource based on a search criteria instead of a resource ID). To walk through some examples, refer to the sample [FHIRPath Patch REST file](https://github.com/microsoft/fhir-server/blob/main/docs/rest/FhirPatchRequests.http) and the [JSON Patch REST file](https://github.com/microsoft/fhir-server/blob/main/docs/rest/JsonPatchRequests.http) for each approach. For additional details, read the [HL7 documentation for patch operations with FHIR](https://www.hl7.org/fhir/http.html#patch).

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.
 
+## **March 2024**
+**Batch-bundle parallelization (GA)**
+Batch bundles are executed serially in FHIR service by default. To improve throughput with bundle calls, we enabled parallel processing of batch bundles.
+
+Learn more:
+- [Batch bundle parallelization](./../healthcare-apis/fhir/fhir-rest-api-capabilities.md)
+
+**Bug Fixes**
+
+- **Fixed: Improve performance for bundle processing**. Updates are made to the task execution method, leading to bundle processing performance improvement. See [PR#3727](https://github.com/microsoft/fhir-server/pull/3727).
+
+
 ## **February 2024**
 **Enables counting all versions (historical and soft deleted) of resources**
 The query parameter _summary=count and _count=0 can be added to _history endpoint to get count of all versioned resources. This count includes soft deleted resources. For more information, see [history management](././../azure-api-for-fhir/purge-history.md).

articles/healthcare-apis/fhir/fhir-features-supported.md

@@ -57,6 +57,7 @@ All the operations that are supported that extend the REST API.
 | [$patient-everything](patient-everything.md)    | Yes       | Yes       |         |
 | [$purge-history](purge-history.md)         | Yes       | Yes       |         |
 | [$import](import-data.md) |No |Yes | |
+| [$bulk-delete](fhir-bulk-delete.md)|Yes   |Yes   |   |
 
 ## Role-based access control
 

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

@@ -33,6 +33,26 @@ Learn more:
 - [Manage medical imaging data with the DICOM service and Azure Data Lake Storage](./dicom/dicom-data-lake.md)
 - [Deploy the DICOM service with Azure Data Lake Storage](./dicom/deploy-dicom-services-in-azure-data-lake.md)
 
+### FHIR Service 
+
+#### Bundle parallelization (GA)
+Bundles are executed serially in FHIR service by default. To improve throughput with bundle calls, we enabled parallel processing.
+
+Learn more:
+- [Bundle parallelization](./../healthcare-apis/fhir/fhir-rest-api-capabilities.md)
+
+#### Import operation accepts multiple resource types in single file
+
+Import operation allowed to have resource type per input file in the request parameters. With this enhance capability, you can pass multiple resource types in single file.
+
+#### Bug Fixes
+
+- **Fixed: Import operation ingest resources with same resource type and lastUpdated field value**. Before this change, resources executed in a batch with same type and lastUpdated field value were not ingested into the FHIR service. This bug fix addresses the issue. See [PR#3768](https://github.com/microsoft/fhir-server/pull/3768).
+
+- **Fixed: FHIR search with 3 or more custom search parameters**. Before this fix, FHIR search query at the root with three or more custom search parameters resulted in HTTP status code 504. See [PR#3701](https://github.com/microsoft/fhir-server/pull/3701).
+
+- **Fixed: Improve performance for bundle processing**. Updates are made to the task execution method, leading to bundle processing performance improvement. See [PR#3727](https://github.com/microsoft/fhir-server/pull/3727).
+
 ## February 2024
 
 ### FHIR service

includes/fhir-rest-api-bundle.md

@@ -70,12 +70,9 @@ Transaction bundle currently does not support
 1. Conditional Delete operation.
 2. Search operations using _search. 
 
-### Batch bundle parallel processing in public preview 
+### Bundle parallel processing 
 
-Currently Batch and transaction bundles are executed serially in FHIR service. To improve performance and throughput, we're enabling parallel processing of batch bundles in public preview.  
+Currently Batch and transaction bundles are executed serially in FHIR service. To improve performance and throughput, we're enabling parallel processing of bundles.
 To use the capability of parallel batch bundle processing-
 * Set header “x-bundle-processing-logic” value to “parallel”. 
 * Ensure there's no overlapping resource ID that is executing on DELETE, POST, PUT or PATCH operations in the same bundle.
-
-> [!IMPORTANT]
-> Bundle parallel processing is currently in public preview. Preview APIs and SDKs are provided without a service-level agreement. We recommend that you don't use them for production workloads. Some features might not be supported, or they might have constrained capabilities. For more information, review Supplemental Terms of Use for Microsoft Azure Previews