You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/events/events-overview.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,32 +8,31 @@ ms.subservice: events
8
8
ms.topic: overview
9
9
ms.date: 01/29/2024
10
10
ms.author: jasteppe
11
-
appliesto:
12
-
- FHIR service
13
-
- DICOM service
14
11
---
15
12
16
13
# What are events?
17
14
18
-
Events in Azure Health Data Services allow you to subscribe to and receive notifications of changes to health data in the FHIR® service or the DICOM® service. Events also enable you to trigger other actions or services based changes to health data, such as starting workflows, sending email or text messages, or triggering alerts.
Events in Azure Health Data Services allow you to subscribe to and receive notifications of changes to health data in the FHIR® service or the DICOM® service. Events also enable you to trigger other actions or services based changes to health data, such as starting workflows, sending email, text messages, or alerts.
19
18
20
19
Events are:
21
20
22
21
-**Scalable**. Events support growth and change in an organization's healthcare data needs by using the [Azure Event Grid service](../../event-grid/overview.md) and creating a [system topic](../../event-grid/system-topics.md) for Azure Health Data Services. For more information, see [Azure Event Grid event schema](../../event-grid/event-schema.md) and [Azure Health Data Services as an Event Grid source](../../event-grid/event-schema-azure-health-data-services.md).
23
22
24
23
-**Configurable**. Choose which FHIR and DICOM event types trigger event notifications. Use advanced features built into the Azure Event Grid service, such as filters, dead-lettering, and retry policies to tune message delivery options for events.
25
24
26
-
-**Extensible**. Use events to send FHIR resource and DICOM image change messages to [Azure Event Hubs](../../event-hubs/event-hubs-about.md) or [Azure Functions](../../azure-functions/functions-overview.md) to trigger downstream automated workflows that enhance operational data, data analysis, and visibility of the incoming data capturing in near real time.
25
+
-**Extensible**. Use events to send FHIR resource and DICOM image change messages to [Azure Event Hubs](../../event-hubs/event-hubs-about.md) or [Azure Functions](../../azure-functions/functions-overview.md). to trigger downstream automated workflows that enhance operational data, data analysis, and visibility of the incoming data capturing in near real time.
27
26
28
27
-**Secure**. Events are built on a platform that supports protected health information (PHI) compliance with privacy, safety, and security standards. Use [Azure managed identities](../../active-directory/managed-identities-azure-resources/overview.md) to provide secure access from the Event Grid system topic to the events message-receiving endpoints of your choice.
29
28
30
29
:::image type="content" source="media/events-overview/events-overview-flow.png" alt-text="Diagram of data flow from users to a FHIR service and then into the events pipeline." lightbox="media/events-overview/events-overview-flow.png":::
0 commit comments