Troubleshoot Events
This article provides guides and resources to troubleshoot Events.
Important
Fast Healthcare Interoperability Resources (FHIR®) resource and DICOM image change data is only written and event messages are sent when the Events feature is turned on. The Event feature doesn't send messages on past FHIR resource or DICOM image changes or when the feature is turned off.
Events resources for troubleshooting
Important
Events currently supports only the following operations:
FhirResourceCreated - The event emitted after a FHIR resource gets created successfully.
FhirResourceUpdated - The event emitted after a FHIR resource gets updated successfully.
FhirResourceDeleted - The event emitted after a FHIR resource gets soft deleted successfully.
DicomImageCreated - The event emitted after a DICOM image gets created successfully.
DicomImageDeleted - The event emitted after a DICOM image gets deleted successfully.
For more information about the FHIR service delete types, see FHIR REST API capabilities for Azure Health Data Services FHIR service
Events message structure
Use this resource to learn about the Events message structure, required and non-required elements, and sample messages:
How to
Use this resource to learn how to deploy Events in the Azure portal:
Important
The Event Subscription requires access to whichever endpoint you chose to send Events messages to. For more information, see Enable managed identity for a system topic.
Use this resource to learn how to display Events metrics:
Use this resource to learn how to export Event Grid system topics diagnostic logs and metrics:
Contacting support
If you have a technical question about Events or if you have a support related issue, see Create a support request and complete the required fields under the Problem description tab. For more information about Azure support options, see Azure support plans.
Next steps
To learn about frequently asked questions (FAQs) about Events, see
FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
Feedback
Submit and view feedback for