Skip to content

Commit 3a2e44c

Browse files
authored
Update known-issues.md
1 parent 1955496 commit 3a2e44c

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/healthcare-apis/known-issues.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,7 @@ Refer to the table for details about resolution dates or possible workarounds.
2020

2121
|Issue | Date discovered | Workaround | Date resolved |
2222
| :------------------------------------- | :------------ | :------------- | :------------- |
23+
| 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. | |
2324
|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 |
2425
|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 |
2526
|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 |

0 commit comments

Comments
 (0)