Known issues: Azure Health Data Services
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 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. | -- |
| 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 9:00 am PST |
| 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 9:00 am PST |
| 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 9:00 am PST |
| 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 9:00am PST |
| 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 9:00 am PST |
| FHIR Applications were down in EUS2 region | January 8, 2024 2 pm PST | -- | January 8,2024 4:15 pm PST |
| API queries to FHIR service returned Internal Server error in UK south region | August 10,2023 9:53 am PST | -- | August 10,2023 10:43 am PST |