Merge pull request #271153 from EXPEkesheth/patch-fhir-release-91

v-ccolin · web-flow · commit 20c01dfa565b · 2024-04-04T09:21:53.000+01:00
FHIR Release 4.0.91 notes
diff --git a/articles/healthcare-apis/azure-api-for-fhir/fhir-rest-api-capabilities.md b/articles/healthcare-apis/azure-api-for-fhir/fhir-rest-api-capabilities.md
@@ -13,7 +13,7 @@ ms.author: kesheth
 
 [!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
 
-In this article, we'll cover some of the nuances of the RESTful interactions of Azure API for FHIR.
+In this article, we cover some of the nuances of the RESTful interactions of Azure API for FHIR.
 
 ## Conditional create/update
 
@@ -27,7 +27,7 @@ Azure API for FHIR offers two delete types. There's [Delete](https://www.hl7.org
 
 ### Delete (Hard + Soft Delete)
 
-Delete defined by the FHIR specification requires that after deleting a resource, subsequent non-version specific reads of a resource returns a 410 HTTP status code. Therefore, the resource is no longer found through searching. Additionally, Azure API for FHIR enables you to fully delete (including all history) the resource. To fully delete the resource, you can pass a parameter settings `hardDelete` to true `(DELETE {{FHIR_URL}}/{resource}/{id}?hardDelete=true)`. If you don't pass this parameter or set `hardDelete` to false, the historic versions of the resource will still be available.
+Delete defined by the FHIR specification requires that after deleting a resource, subsequent nonversion specific reads of a resource returns a 410 HTTP status code. Therefore, the resource is no longer found through searching. Additionally, Azure API for FHIR enables you to fully delete (including all history) the resource. To fully delete the resource, you can pass a parameter settings `hardDelete` to true `(DELETE {{FHIR_URL}}/{resource}/{id}?hardDelete=true)`. If you don't pass this parameter or set `hardDelete` to false, the historic versions of the resource will still be available.
 
 > [!NOTE]
 > If you only want to delete the history, Azure API for FHIR supports a custom operation called `$purge-history`. This operation allows you to delete the history off of a resource.
@@ -44,13 +44,13 @@ You can do the same search but include `hardDelete=true` to also delete all hist
 
 `DELETE https://{{FHIR_URL}}/Patient?identifier=1032704&hardDelete=true`
 
-To delete multiple resources, include `_count=100` parameter. This parameter will delete up to 100 resources that match the search criteria.
+To delete multiple resources, include `_count=100` parameter. This parameter deletes up to 100 resources that match the search criteria.
 
 `DELETE https://{{FHIR_URL}}/Patient?identifier=1032704&_count=100`
  
 ### Recovery of deleted files
 
-If you don't use the hard delete parameter, then the record(s) in Azure API for FHIR should still exist. The record(s) can be found by doing a history search on the resource and looking for the last version with data.
+If you don't use the hard delete parameter, then the records in Azure API for FHIR should still exist. The records can be found by doing a history search on the resource and looking for the last version with data.
  
 If the ID of the resource that was deleted is known, use the following URL pattern:
 
@@ -67,7 +67,7 @@ For example: `https://myworkspace-myfhirserver.fhir.azurehealthcareapis.com/Pati
 After you've found the record you want to restore, use the `PUT` operation to recreate the resource with the same ID, or use the `POST` operation to make a new resource with the same information.
  
 > [!NOTE]
-> There is no time-based expiration for history/soft delete data. The only way to remove history/soft deleted data is with a hard delete or the purge history operation.\
+> There is no time-based expiration for history/soft delete data. The only way to remove history/soft deleted data is with a hard delete or the purge history operation.
 
 ## Batch Bundles 
 In FHIR, bundles can be considered as a container that holds multiple resources. Batch bundles enable users to submit a set of actions to be performed on a server in single HTTP request/response.
@@ -124,15 +124,12 @@ 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 
+* 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.
 
 ## Patch and Conditional Patch
 
diff --git a/articles/healthcare-apis/azure-api-for-fhir/release-notes.md b/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**
+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](././../azure-api-for-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).
@@ -74,7 +86,7 @@ For more details, visit [#3222](https://github.com/microsoft/fhir-server/pull/32
 
 **Fixed the Error generated when resource is updated using if-match header and PATCH**
 
-Bug is now fixed and Resource will be updated if matches the Etag header. For details , see [#2877](https://github.com/microsoft/fhir-server/issues/2877)|
+Bug is now fixed and Resource will be updated if matches the Etag header. For details , see [#2877](https://github.com/microsoft/fhir-server/issues/2877)|.
 
 ## May 2022
 
@@ -124,7 +136,7 @@ Bug is now fixed and Resource will be updated if matches the Etag header. For de
 |Enhancements  |Related information |
 | :----------------------------------- | :--------------- |
 |Added 429 retry and logging in BundleHandler |We sometimes encounter 429 errors when processing a bundle. If the FHIR service receives a 429 at the BundleHandler layer, we abort processing of the bundle and skip the remaining resources. We've added another retry (in addition to the retry present in the data store layer) that will execute one time per resource that encounters a 429. For more about this feature enhancement, see [PR #2400](https://github.com/microsoft/fhir-server/pull/2400).|
-|Billing for `$convert-data` and `$de-id` |Azure API for FHIR's data conversion and de-identified export features are now Generally Available. Billing for `$convert-data` and `$de-id` operations in Azure API for FHIR has been enabled. Billing meters were turned on March 1, 2022. |
+|Billing for `$convert-data` and `$de-id` |Azure API for FHIR's data conversion and deidentified export features are now Generally Available. Billing for `$convert-data` and `$de-id` operations in Azure API for FHIR has been enabled. Billing meters were turned on March 1, 2022. |
 
 ### **Bug fixes**
 
@@ -146,7 +158,7 @@ Bug is now fixed and Resource will be updated if matches the Etag header. For de
 
 |Bug fixes |Related information |
 | :----------------------------------- | :--------------- |
-|Fixed 500 error when `SearchParameter` Code is null |Fixed an issue with `SearchParameter` if it had a null value for Code, the result would be a 500. Now it will result in an  `InvalidResourceException` like the other values do. [#2343](https://github.com/microsoft/fhir-server/pull/2343) |
+|Fixed 500 error when `SearchParameter` Code is null |Fixed an issue with `SearchParameter` if it had a null value for Code, the result would be a 500. Now it results in an  `InvalidResourceException` like the other values do. [#2343](https://github.com/microsoft/fhir-server/pull/2343) |
 |Returned `BadRequestException` with valid message when input JSON body is invalid |For invalid JSON body requests, the FHIR server was returning a 500 error. Now we'll return a `BadRequestException` with a valid message instead of 500. [#2239](https://github.com/microsoft/fhir-server/pull/2239) |
 |`_sort` can cause `ChainedSearch` to return incorrect results |Previously, the sort options from the chained search's `SearchOption` object wasn't cleared, causing the sorting options to be passed through to the chained subsearch, which aren't valid. This could result in no results when there should be results. This bug is now fixed  [#2347](https://github.com/microsoft/fhir-server/pull/2347). It addressed GitHub bug [#2344](https://github.com/microsoft/fhir-server/issues/2344). |
 
diff --git a/articles/healthcare-apis/fhir/fhir-features-supported.md b/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
 
diff --git a/articles/healthcare-apis/release-notes-2024.md b/articles/healthcare-apis/release-notes-2024.md
@@ -50,6 +50,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
diff --git a/includes/fhir-rest-api-bundle.md b/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 
