Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article describes known issues with Azure Health Data Services, which includes the FHIR®, DICOM®, and MedTech services.
Refer to the table for details about resolution dates or possible workarounds.
FHIR service
| Issue | Date discovered | Workaround | Date resolved |
|---|---|---|---|
| Customers are unable to select storage account in the FHIR instance export configuration. The issue is caused by throttling due to a large number of resource groups and storage accounts, leading to errors like "Storage account doesn't exist" on the Export blade. | May 15, 2025 2:05 pm PST | PowerShell commands to configure the storage account for export manually: Run this command to install the Az Module: Install-Module -Name AzIf Az module is already installed: Update-Module -Name AzConnect to Azure Account: Connect-AzAccountInitialize the variable resourceGroupName, fhirServiceName, and storageAccountName: $resourceGroupName = "YOUR_RESOURCEGROUP_NAME"$fhirServiceName = "YOUR_FHIRSERVICE_NAME"$exportConfig = @{ "storageAccountName" = "YOUR_STORAGEACCOUNT_NAME" }Run this command to set the storage account for export: Set-AzResource -ResourceGroupName $resourceGroupName -ResourceType "Microsoft.HealthcareApis/services" -ResourceName $fhirServiceName -ApiVersion "2021-11-01" -Properties @{ "exportConfiguration" = $exportConfig }Running this command confirms if the setting was successful: Get-AzResource -ResourceGroupName $resourceGroupName -ResourceType "Microsoft.HealthcareApis/services" -ResourceName $fhirServiceName \| Select-Object -ExpandProperty Properties \| Select-Object -ExpandProperty exportConfiguration |
-- |
| Patient-everything operation returns a 500 error when run using a SMART patient fhirUser token. | April 9, 2025 | A fix is being released in the upcoming FHIR release. | |
| Customers can't access FHIR, DICOM, or Medtech through the portal. | October 31, 2024 1:00 pm PST | ARM calls are still operational, and there's no disruption to existing services. | November 1, 2024 |
| For FHIR instances created after August 19, 2024, diagnostic logs aren't available in log analytics workspace. | September 19, 2024 9:00 am PST | -- | October 17, 2024 |
| For FHIR instances created after August 19, 2024, in metrics blade - Total requests, Total latency, and Total errors metrics are not being populated. | September 19, 2024 9:00 am PST | -- | October 28, 2024 |
| For FHIR instances created after August 19, 2024, changes in private link configuration at the workspace level causes FHIR service to be stuck in 'Updating' state. | September 24, 2024 9:00 am PST | Accounts deployed prior to September 27, 2024 and facing this issue can follow the steps: 1. Remove private endpoint from the Azure Health Data Services workspace having this issue. On Azure blade, go to Workspace and then click on Networking blade. In networking blade, select existing private link connection and click on 'Remove' 2. Create new private connection to link to the workspace. |
September 27, 2024 |
| Changes in private link configuration at the workspace level don't propagate to the child services. | September 4, 2024 9:00 am PST | To fix this issue a service reprovisioning is required. To reprovision the service, reach out to FHIR service team | September 17, 2024 |
| Customers accessing the FHIR Service via a private endpoint are experiencing difficulties, specifically receiving a 403 error when making API calls from within the vNet. This problem affects FHIR instances provisioned after August 19 that utilize private link. | August 22, 2024 11:00 am PST | -- | September 3, 2024 |
| FHIR Applications were down in EUS2 region | January 8, 2024 2 pm PST | -- | January 8, 2024 |
| API queries to FHIR service returned Internal Server error in UK south region | August 10, 2023 9:53 am PST | -- | August 10, 2023 |