|
| 1 | +--- |
| 2 | +title: Release notes for 2025 Azure Health Data Services monthly releases |
| 3 | +description: 2025 - Stay updated with the latest features and improvements for the FHIR, DICOM, and MedTech services in Azure Health Data Services in 2024. Read the monthly release notes and learn how to get the most out of healthcare data. |
| 4 | +services: healthcare-apis |
| 5 | +author: KendalBond007 |
| 6 | +ms.service: azure-health-data-services |
| 7 | +ms.subservice: workspace |
| 8 | +ms.topic: reference |
| 9 | +ms.date: 07/29/2024 |
| 10 | +ms.author: kesheth |
| 11 | +ms.custom: references_regions |
| 12 | +--- |
| 13 | + |
| 14 | +# Release notes 2025: Azure Health Data Services |
| 15 | + |
| 16 | +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. |
| 17 | + |
| 18 | +## October 2024 |
| 19 | + |
| 20 | +### Azure Health Data Services |
| 21 | + |
| 22 | +### FHIR service |
| 23 | + |
| 24 | +#### Enhancement: Improved error handling and validation |
| 25 | + |
| 26 | +HTTP Method Validation for Transaction Bundle Requests: |
| 27 | +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. |
| 28 | + |
| 29 | +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](https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/configure-customer-managed-keys) if issues occur related to CMK. |
| 30 | + |
| 31 | +### Azure API for FHIR |
| 32 | + |
| 33 | +#### Enhancement: Improved error handling and validation |
| 34 | + |
| 35 | +HTTP Method Validation for Transaction Bundle Requests: |
| 36 | +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. |
| 37 | + |
| 38 | +Partition Size Error Handling: When a partition exceeds 20GB, a `PreconditionFailedException` is raised, replacing the previous HTTP 500 errors with HTTP 400 errors. This indicates to customers that the failure is due to an issue on their end (partition size). |
| 39 | + |
| 40 | +Transaction Failure Exception: A new FHIR-specific exception type has been introduced to handle Cosmos DB transaction failures, replacing the generic `InvalidOperationExceptions`. |
| 41 | + |
| 42 | +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](https://learn.microsoft.com/en-us/azure/healthcare-apis/fhir/configure-customer-managed-keys) if issues occur related to CMK. |
0 commit comments