Merge pull request #309798 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-20 06:00 UTC

Author: learn-build-service-prod[bot]

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

@@ -15,7 +15,7 @@ ms.custom:
 
 # Release notes 2025: Azure Health Data Services
 
-This article describes features, enhancements, and bug fixes released in 2025 for the FHIR® service, Azure API for FHIR, DICOM® service, and MedTech service in Azure Health Data Services.
+Release notes describe features, enhancements, and bug fixes released in 2025 for the FHIR® service, Azure API for FHIR, DICOM® service, and MedTech service in Azure Health Data Services.
 
 ## December 2025
 ### FHIR service
@@ -26,13 +26,25 @@ This article describes features, enhancements, and bug fixes released in 2025 fo
 
 #### Bug fixes:
 
-**Bug fix for PUT request with new search parameters**: Resolved issue where PUT requests for new search parameters were failing due to validation. This issue has been resolved, and PUT requests for search parameters should now properly work as upserts, allowing new search parameters to be inserted using PUT if  the search parameter doesn't already exist in the system.
+**Bug fix for PUT request with new search parameters**: Resolved issue where PUT requests for new search parameters were failing due to validation. This issue is resolved. PUT requests for search parameters should now properly work as upserts, allowing new search parameters to be inserted using PUT if the search parameter doesn't already exist in the system.
 
 **Bug fix for PUT regression with metadata-only updates**: Resolved issue where metadata-only updates made via PATCH incremented the resource version without preserving the previous version. This issue was resolved on November 28, 2025.
 
+**Bug fix for $import with relative URL error**: Previously, using $import with a relative URL could return a 500 Internal Server Error stating `This operation is not supported for a relative URI`. This issue is fixed, and now, a relative URL can be used as the input URL.
+
+**Bug fixes for search with `_include`/`_revinclude` and `_sort`**: When executing a [search request with _include or _revinclude](./fhir/overview-of-search.md#request-parameters), if there are more than the `_includesCount` number of matched items, an include continuation link is provided, allowing you to navigate the complete result set. Previously, this particular functionality had some bugs when it was used with `_sort`. The following issues are fixed:
+- Sorting by `lastUpdated` (descending): Included resources were missing from the bundle, and no include continuation token was returned. This issue is fixed; included resources and the include continuation token are now returned correctly.
+- Sorting by any other field: If enough results existed to fill a page, it triggered a 500 error. This issue is fixed, and all results are returned correctly.
+- Partial page with sort value: If matched results didn't fill a page but generated an include continuation token, that token was lost during the second search for non-sort matches. This issue is fixed, and the include continuation token is returned correctly.
+- Include continuation link with `_sort`: The search retrieved data for both matches with and without the sort field, regardless of which type generated the token. This issue is fixed, and data is retrieved for the correct match.
+
 ## November 2025
 ### FHIR service
 
+#### Support for SMART on FHIR v2
+SMART on FHIR v2.0.0 sample is available now on the Azure Health Data and AI Samples open source repo. For more information, visit [`SMART on FHIR`](./fhir/smart-on-fhir.md).
+
+
 **Metadata-only updates and versioning configuration**: Introduced new query parameter "_meta-history" for PUT updates when versioning policy is set to either "versioned" or "version-update" to configure whether or not the old version is saved as a historical record. "_meta-history = true" is the default. By default, the resource version is incremented, a new version is created, and the old version is saved as a historical record. "_meta-history=false" can be configured so that the resource version is incremented, a new version is created, but the old version is not saved as a historical record. For more information, visit [metadata-only updates and versioning](./fhir/fhir-versioning-policy-and-history-management.md#metadata-only-updates-and-versioning).
 
 **Composite search parameter collation fix**:  Corrected inconsistent collation handling for Token-String composite search parameters.