Skip to content

Commit b087f49

Browse files
committed
Content updates as needed
1 parent b87e52b commit b087f49

File tree

3 files changed

+16
-22
lines changed

3 files changed

+16
-22
lines changed

articles/healthcare-apis/events/events-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,21 +6,21 @@ author: chachachachami
66
ms.service: azure-health-data-services
77
ms.subservice: events
88
ms.topic: overview
9-
ms.date: 01/29/2024
9+
ms.date: 11/26/2024
1010
ms.author: chrupa
1111
---
1212

1313
# What are events?
1414

15-
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.
15+
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 services based changes or other actions to health data, such as starting workflows, sending email, text messages, or alerts.
1616

1717
Events are:
1818

1919
- **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).
2020

2121
- **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.
2222

23-
- **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.
23+
- **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.
2424

2525
- **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.
2626

articles/healthcare-apis/events/events-troubleshooting-guide.md

Lines changed: 8 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -6,18 +6,15 @@ author: chachachachami
66
ms.service: azure-health-data-services
77
ms.subservice: fhir
88
ms.topic: troubleshooting
9-
ms.date: 07/12/2023
9+
ms.date: 11/26/2024
1010
ms.author: chrupa
1111
---
1212
# Troubleshoot events
1313

14-
> [!NOTE]
15-
> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
16-
1714
This article provides resources to troubleshoot events.
1815

1916
> [!IMPORTANT]
20-
> 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.
17+
> The Events feature must be turned on for FHIR® resource and DICOM® image change data to be written, and event messages sent. The event feature doesn't send messages on past FHIR resource or DICOM image changes, or when the feature is turned off.
2118
2219
:::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":::
2320

@@ -42,21 +39,21 @@ This article provides resources to troubleshoot events.
4239
4340
### Events message structures
4441

45-
Use this resource to learn about the events message structures, required and nonrequired elements, and see sample Events messages:
42+
Use the following resource to learn about the events message structures, required and nonrequired elements, and to see sample Events messages.
4643
* [Events message structures](events-message-structure.md)
4744

4845
### How to's
4946

50-
Use this resource to learn how to deploy events in the Azure portal:
47+
Use the following resource to learn how to deploy events in the Azure portal.
5148
* [Deploy events by using the Azure portal](events-deploy-portal.md)
5249

5350
> [!IMPORTANT]
54-
> The event subscription requires access to the endpoint you chose to send events messages to. For more information, see [Enable managed identity for a system topic](../../event-grid/enable-identity-system-topics.md).
51+
> The event subscription requires access to the endpoint you chose to receive events messages. For more information, see [Enable managed identity for a system topic](../../event-grid/enable-identity-system-topics.md).
5552
56-
Use this resource to learn how to use events metrics:
53+
Use the following resource to learn how to use events metrics.
5754
* [How to use events metrics](events-display-metrics.md)
5855

59-
Use this resource to learn how to enable diagnostic settings for events:
56+
Use the following resource to learn how to enable diagnostic settings for events.
6057
* [How to enable diagnostic settings for events](events-export-logs-metrics.md)
6158

6259
## Contact support
@@ -71,4 +68,4 @@ To learn about the frequently asked questions (FAQs) about events, see
7168
> [!div class="nextstepaction"]
7269
> [Frequently asked questions about events](events-faqs.md)
7370
74-
FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
71+
[!INCLUDE [FHIR DICOM trademark statement](../includes/healthcare-apis-fhir-dicom-trademark.md)]

articles/healthcare-apis/events/events-use-metrics.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,12 @@ author: chachachachami
66
ms.service: azure-health-data-services
77
ms.subservice: fhir
88
ms.topic: how-to
9-
ms.date: 07/11/2023
9+
ms.date: 11/26/2024
1010
ms.author: chrupa
1111
---
1212

1313
# How to use events metrics
1414

15-
> [!NOTE]
16-
> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
17-
1815
In this article, learn how to use events metrics using the Azure portal.
1916

2017
> [!TIP]
@@ -29,15 +26,15 @@ In this article, learn how to use events metrics using the Azure portal.
2926

3027
:::image type="content" source="media\events-display-metrics\events-metrics-workspace-select.png" alt-text="Screenshot of select the events button from the Azure Health Data Services workspace." lightbox="media\events-display-metrics\events-metrics-workspace-select.png":::
3128

32-
2. The Events page displays the combined metrics for all Events Subscriptions. For example, we have one subscription named **fhir-events** and one processed message. To view the metrics for that subscription, select the subscription in the lower left-hand corner of the page.
29+
2. The Events page displays the combined metrics for all Events Subscriptions. In this example, we have one subscription named **fhir-events** and one processed message. To view the metrics for that subscription, select the subscription in the lower left-hand corner of the page.
3330

3431
:::image type="content" source="media\events-display-metrics\events-metrics-main.png" alt-text="Screenshot of events you would like to display metrics for." lightbox="media\events-display-metrics\events-metrics-main.png":::
3532

36-
3. From this page, notice that the subscription named **fhir-events** has one processed message. To view the Event Hubs metrics, select the name of the Event Hubs (for this example, **azuredocsfhirservice**) from the lower right-hand corner of the page.
33+
3. On this page, notice that the subscription named **fhir-events** has one processed message. To view the Event Hubs metrics, select the name of the Event Hubs (in this example, **azuredocsfhirservice**) from the lower right-hand corner of the page.
3734

3835
:::image type="content" source="media\events-display-metrics\events-metrics-subscription.png" alt-text="Screenshot of select the metrics button." lightbox="media\events-display-metrics\events-metrics-subscription.png":::
3936

40-
4. From this page, notice that the Event Hubs received the incoming message presented in the previous Events Subscription metrics pages.
37+
4. On this page, notice that the Event Hubs received the incoming message presented in the previous Events Subscription metrics pages.
4138

4239
:::image type="content" source="media\events-display-metrics\events-metrics-event-hub.png" alt-text="Screenshot of displaying event hubs metrics." lightbox="media\events-display-metrics\events-metrics-event-hub.png":::
4340

@@ -50,4 +47,4 @@ To learn how to enable events diagnostic settings, see:
5047
> [!div class="nextstepaction"]
5148
> [Enable diagnostic settings for events](events-enable-diagnostic-settings.md)
5249
53-
FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
50+
[!INCLUDE [FHIR DICOM trademark statement](../includes/healthcare-apis-fhir-dicom-trademark.md)]

0 commit comments

Comments
 (0)