Update release-notes-2025.md

Updating per ADO145036.
Awaiting input on edits to the "Incremental Import Enhancement" content.

Author: KendalBond007

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

@@ -15,24 +15,36 @@ ms.custom: references_regions
 
 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.
 
+## February 2025
+
+**Selectable Search Parameters**: Customers can tune search parameters using the [selectable search parameters](fhir/selectable-search-parameters) capability. The capability provides a `$status` endpoint to validate the status of the search parameter. To avoid conflicts, the change now prevents updates to the search parameter status when a reindex job is in progress.
+ 
+**Schema Upgrade Changes**: To improve customer experience during schema upgrades, the service now ensures that instances are initialized up to the minimum supported schema version. If a schema upgrade is in progress, the service will continue to respond while initializing the instance in parallel.
+ 
+**Incremental Import Enhancement**: There is added protection from incorrect input values in last update pointing far in future, which causes incorrect versions to be generated by the FHIR server in subsequent resource updates. To prevent this behavior, check if the last updated input is set to more than 10 seconds in the future, and rejects input resources with such dates.
+
+**Date Search Logic Update**: When searching for a date, the logic now ensures that any date range containing the searched date is included in the results. Previously, it only matched a date if the entire range was inside the searched date. 
+ 
+**Health Checks for Improved Resiliency**: Added health checks to enhance the resilience of the service such as retriable exceptions, enhanced diagnostic logging and catching time out exceptions.
+
 ## January 2025
 
 ### FHIR service
 
 #### Enhancement: Improved error handling and validation
 
-HTTP Method Validation for Transaction Bundle Requests:
+**HTTP Method Validation for Transaction Bundle Requests**:
 Added validation to ensure the HTTP method in the Request component of the transaction bundle is a valid HTTPVerb enum value. If the HTTP method is invalid or null, a `RequestNotValidException` is thrown with a `400 Bad Request` status, providing a clearer error message to users.
 
-CMK Error Handling: Improved error handling for operations dependent on customer-managed keys. Users will now see a more specific error message and a link to [Microsoft's troubleshooting guide](fhir/configure-customer-managed-keys.md) if issues occur related to CMK.
+**CMK Error Handling**: Improved error handling for operations dependent on customer-managed keys. Users will now see a more specific error message and a link to [Microsoft's troubleshooting guide](fhir/configure-customer-managed-keys.md) if issues occur related to CMK.
 
 #### 100 items limit on include and revinclude searches
 
 The FHIR® server has a limit of 100 items on `include` and `revinclude` searches. A recent update fixed an issue where this limit was not being applied in specific conditions. Customers will receive a warning and truncated results if the limit is exceeded. Details on limits can be found in the [Overview of FHIR search](./fhir/overview-of-search.md#search-result-parameters). To manage this, use the `_count` parameter to reduce the number of returned results. In the short term, we plan to increase the limit to 1000
 
 ### Bug Fixes
 
-Billing in Sweden Central region: An issue was discovered where subscriptions in the Sweden Central region were not being billed correctly. We corrected the error, and billing has now been enabled in Sweden Central region. If you were affected by this error, you will not be responsible for any missed charged prior to your January bill.
+**Billing in Sweden Central region**: An issue was discovered where subscriptions in the Sweden Central region were not being billed correctly. We corrected the error, and billing has now been enabled in Sweden Central region. If you were affected by this error, you will not be responsible for any missed charged prior to your January bill.
 
 ## Related content