Edit

Frequently asked questions (FAQs) about Events

  • Article
  • 3 minutes to read

The following are some of the frequently asked questions about Events.

Events: The basics

Can I use Events with a different FHIR/DICOM service other than the Azure Health Data Services FHIR/DICOM service?

No. The Azure Health Data Services Events feature only currently supports the Azure Health Data Services Fast Healthcare Interoperability Resources (FHIR®) and DICOM services.

What FHIR resource events does Events support?

Events are generated from the following FHIR service types:

  • 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.

For more information about the FHIR service delete types, see FHIR REST API capabilities for Azure Health Data Services FHIR service

What DICOM image events does Events support?

Events are generated from the following DICOM service types:

  • DicomImageCreated - The event emitted after a DICOM image gets created successfully.

  • DicomImageDeleted - The event emitted after a DICOM image gets deleted successfully.

What is the payload of an Events message?

For a detailed description of the Events message structure and both required and non-required elements, see Events troubleshooting guide.

What is the throughput for the Events messages?

The throughput of FHIR and DICOM events is governed by the throughput of the FHIR or DICOM service and the Event Grid. When a request made to the FHIR service is successful, it will return a 2xx HTTP status code. It will also generate a FHIR resource or DICOM image changing event. The current limitation is 5,000 events/second per a workspace for all FHIR or DICOM service instances in it.

How am I charged for using Events?

There are no extra charges for using Azure Health Data Services Events. However, applicable charges for the Event Grid will be assessed against your Azure subscription.

How do I subscribe to multiple FHIR and/or DICOM services in the same workspace separately?

You can use the Event Grid filtering feature. There are unique identifiers in the event message payload to differentiate different accounts and workspaces. You can find a global unique identifier for workspace in the source field, which is the Azure Resource ID. You can locate the unique FHIR account name in that workspace in the data.resourceFhirAccount field. You can locate the unique DICOM account name in that workspace in the data.serviceHostName field. When you create a subscription, you can use the filtering operators to select the events you want to get in that subscription.

Screenshot of the Event Grid filters tab.

Can I use the same subscriber for multiple workspaces, FHIR accounts, or DICOM accounts?

Yes. We recommend that you use different subscribers for each individual FHIR or DICOM account to process in isolated scopes.

Is Event Grid compatible with HIPAA and HITRUST compliance obligations?

Yes. Event Grid supports customer's Health Insurance Portability and Accountability Act (HIPAA) and Health Information Trust Alliance (HITRUST) obligations. For more information, see Microsoft Azure Compliance Offerings.

What is the expected time to receive an Events message?

On average, you should receive your event message within one second after a successful HTTP request. 99.99% of the event messages should be delivered within five seconds unless the limitation of either the FHIR service, DICOM service, or Event Grid has been met.

Is it possible to receive duplicate Events message?

Yes. The Event Grid guarantees at least one Events message delivery with its push mode. There may be chances that the event delivery request returns with a transient failure status code for random reasons. In this situation, the Event Grid will consider that as a delivery failure and will resend the Events message. For more information, see Azure Event Grid delivery and retry.

Generally, we recommend that developers ensure idempotency for the event subscriber. The event ID or the combination of all fields in the data property of the message content are unique per each event. The developer can rely on them to de-duplicate.

More frequently asked questions

FAQs about the Azure Health Data Services

FAQs about Azure Health Data Services FHIR service

FAQs about Azure Health Data Services DICOM service

FAQs about Azure Health Data Services MedTech service

FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.