Merge pull request #300637 from v-rachitsh/v-rachitsh-mayreleasenotes

FHIR release notes for May 2025

Author: prmerger-automator[bot]

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

@@ -6,7 +6,7 @@ author: KendalBond007
 ms.service: azure-health-data-services
 ms.subservice: fhir
 ms.topic: reference
-ms.date: 5/14/2025
+ms.date: 5/30/2025
 ms.custom:
   - references_regions
   - build-2025
@@ -22,9 +22,15 @@ Azure API for FHIR® provides a fully managed deployment of the Microsoft FHI
 ## May 2025
 **Enhanced error handling for $export**: Previously, 409 and 412 errors from Cosmos DB weren't retried, and would be surfaced as 500 InternalServerError. The issue is fixed, and these requests are now retried. 
 
+**Improved error handling for exports or imports that have missing Managed Identity**: Previously, export or import jobs with a missing Managed Identity would result in an unknown server error (HTTP status code 500). We have improved error handling for this case, expect message—'Failed to get access token'—to be shown. 
+
+**Support multiple pages of include results in bulk delete**: Previously, bulk deletes with _include and _revinclude couldn't delete more than 100 included resources. We have made a fix to lift that limit by supporting multiple pages of include results, and bulk delete will be able to delete more than 100 included resources.
+
 #### Bug fixes:
 **Creation after deletion of search parameters fix**: Previously, creating the same search parameter that was deleted in the past could fail due to an issue in updating the cache for Search Parameter definition manager. The issue is fixed, and now, the cache is synced before validating a search parameter in an incoming request.
 
+**Export duplicates fix**: Previously, there was a bug where exports with _isParallel = on and _maxCount set to 1000 or lower could result in duplication of exported resources. This issue has been fixed. 
+
 ## April 2025
 **Enhanced error handling for READ operations with wrong cases on resource types**: Added validation on the resource type with wrong casing for READ operations (for example, GET /patient/ instead of GET /Patient/). In the past, a request with the wrong casing resource type was causing 500 status code (InternalServerError). After this change, a request with the wrong casing resource type will be rejected with 400 status code (ResourceNotSupported) as the resource type in any request should be validated in the case-sensitive manner.
 

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

@@ -25,6 +25,13 @@ This article describes features, enhancements, and bug fixes released in 2025 fo
 
 **Transaction handling improvement**: Fixed invisible transaction watchdog to limit number of transactions to process in a single batch to 10000 to avoid timeouts and improve transaction handling.
 
+**Improved error handling for exports or imports that have missing Managed Identity**: Previously, exports or imports with missing Managed Identity would result in a 500 Unknown Server Error. We have added improved error handling for this case, and now, a more descriptive error message "Failed to get access token" will be shown. 
+
+**Support multiple pages of include results in bulk delete**: Previously, bulk deletes with _include and _revinclude couldn't delete more than 100 included resources. We have made a fix to lift that limit by supporting multiple pages of include results, and bulk delete will be able to delete more than 100 included resources.
+
+**Added ID in CapabilityStatement**: Previously, when retrieving the server's CapabilityStatement from the /metadata endpoint, the returned resource did not contain an ID. We have now added a dynamic ID to the CapabilityStatement 
+
+Added validation on resource ID for import. Previously, the import process was not validating IDs, allowing unsupported characters, for example, "#", to cause errors. Now, we have added validation on resource ID for import, and have included the error message "Invalid resource ID".
 
 #### Bug fixes:
 **Creation after deletion of search parameters fix**: Previously, creating the same search parameter that was deleted in the past could fail due to an issue in updating the cache for Search Parameter definition manager. The issue is fixed, and now, the cache is synced before validating a search parameter in an incoming request.