Merge pull request #264584 from shellyhaverkamp/smh-events-FAQ-TOC

FAQ + TOC updates

Author: v-regandowner

articles/healthcare-apis/events/events-disable-delete-workspace.md

@@ -1,56 +1,56 @@
 ---
-title: How to disable events and delete events enabled workspaces - Azure Health Data Services
-description: Learn how to disable events and delete events enabled workspaces.
+title: Disable events for the FHIR or DICOM service in Azure Health Data Services
+description: Disable events for the FHIR or DICOM service in Azure Health Services by deleting an event subscription. Learn why and how to stop sending notifications from your data and resources.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
-ms.subservice: fhir
+ms.subservice: events
 ms.topic: how-to
-ms.date: 09/26/2023
+ms.date: 01/31/2024
 ms.author: jasteppe
 ---
 
-# How to disable events and delete event enabled workspaces
+# Disable events
 
-> [!NOTE]
-> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
+**Applies to:** [!INCLUDE [Yes icon](../includes/applies-to.md)][!INCLUDE [FHIR service](../includes/fhir-service.md)], [!INCLUDE [DICOM service](../includes/DICOM-service.md)]
 
-In this article, learn how to disable events and delete events enabled workspaces.
+Events in Azure Health Services allow you to monitor and respond to changes in your data and resources. By creating an event subscription, you can specify the conditions and actions for sending notifications to various endpoints.
 
-## Disable events
+However, there may be situations where you want to temporarily or permanently stop receiving notifications from an event subscription. For example, you might want to pause notifications during maintenance or testing, or delete the event subscription if you no longer need it. 
 
-To disable events from sending event messages for a single **Event Subscription**, the **Event Subscription** must be deleted.
+To disable events from sending notifications for an **Event Subscription**, you need to delete the subscription.
 
-1. Select the **Event Subscription** to be deleted. In this example, we're selecting an Event Subscription named **fhir-events**.
+1. In the Azure portal on the left pane, select **Events**. 
 
-   :::image type="content" source="media/disable-delete-workspaces/select-event-subscription.png" alt-text="Screenshot of Events Subscriptions and select event subscription to be deleted." lightbox="media/disable-delete-workspaces/select-event-subscription.png":::
+1. Select **Event Subscriptions**. 
 
-2. Select **Delete** and confirm the **Event Subscription** deletion.
+1. Select the **Event Subscription** you want to disable notifications for. In the example, the event subscription is named **azuredocsdemo-fhir-events-subscription**.
 
-   :::image type="content" source="media/disable-delete-workspaces/select-subscription-delete.png" alt-text="Screenshot of events subscriptions and select delete and confirm the event subscription to be deleted." lightbox="media/disable-delete-workspaces/select-subscription-delete.png":::
+   :::image type="content" source="media/disable-delete-workspaces/select-event-subscription.png" alt-text="Screenshot showing selection of event subscription to be deleted." lightbox="media/disable-delete-workspaces/select-event-subscription.png":::
 
-3. If you have multiple **Event Subscriptions**, follow the steps to delete the **Event Subscriptions** so that no **Event Subscriptions** remain.
+1. Choose **Delete**.
 
-   :::image type="content" source="media/disable-delete-workspaces/no-event-subscriptions-found.png" alt-text="Screenshot of Event Subscriptions and delete all event subscriptions to disable events." lightbox="media/disable-delete-workspaces/no-event-subscriptions-found.png":::
+   :::image type="content" source="media/disable-delete-workspaces/select-subscription-delete-sml.png" alt-text="Screenshot showing confirmation of the event subscription to be deleted." lightbox="media/disable-delete-workspaces/select-subscription-delete-lrg.png":::
 
-> [!NOTE]
-> The FHIR service will automatically go into an **Updating** status to disable events when a full delete of **Event Subscriptions** is executed. The FHIR service will remain online while the operation is completing, however, you won't be able to make any further configuration changes to the FHIR service until the updating has completed.
+1. If there are multiple event subscriptions, repeat these steps to delete each one until the message **No Event Subscriptions Found** is displayed in the **Name** field.
 
-## Delete events enabled workspaces
+   :::image type="content" source="media/disable-delete-workspaces/no-event-subscriptions-found-sml.png" alt-text="Screenshot showing deletion of all event subscriptions to disable events." lightbox="media/disable-delete-workspaces/no-event-subscriptions-found-lrg.png":::
 
-To avoid errors and successfully delete events enabled workspaces, follow these steps and in this specific order:
+> [!NOTE] 
+> When you delete all event subscriptions, the FHIR or DICOM service disables events and goes into **Updating** status. The FHIR or DICOM service stays online during the update, but you can’t change the configuration until it completes.
 
-1. Delete all workspace associated child resources (for example: DICOM services, FHIR services, and MedTech services).
-2. Delete all workspace associated **Event Subscriptions**.
-3. Delete workspace.
+## Delete events-enabled workspaces
 
-## Next steps
+To delete events-enabled workspaces without errors, do these steps in this exact order:
+
+1. Delete all child resources associated with the workspace (for example, FHIR® services, DICOM® services, and MedTech services).
 
-In this article, you learned how to disable events and delete events enabled workspaces.
+1. [Delete all event subscriptions](#disable-events) associated with the workspace.
 
-To learn about how to troubleshoot events, see
+1. Delete the workspace.
+
+## Next steps
 
-> [!div class="nextstepaction"]
-> [Troubleshoot events](events-troubleshooting-guide.md)
+[Troubleshoot events](events-troubleshooting-guide.md)
 
-FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+[!INCLUDE [FHIR and DICOM trademark statement](../includes/healthcare-apis-fhir-dicom-trademark.md)]

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

@@ -1,105 +1,94 @@
 ---
-title: Frequently asked questions about events - Azure Health Data Services
-description: Learn about the frequently asked questions about events.
+title: Events FAQ for Azure Health Data Services
+description: Get answers to common questions about the events capability in the FHIR and DICOM services in Azure Health Data Services. Find out how events work, what types of events are supported, and how to subscribe to events by using Azure Event Grid.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
-ms.subservice: fhir
+ms.subservice: events
 ms.topic: reference
-ms.date: 07/11/2023
+ms.date: 01/31/2024
 ms.author: jasteppe
 ---
 
-# Frequently asked questions about events
+# Events FAQ
 
-> [!NOTE]
-> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
+**Applies to:** [!INCLUDE [Yes icon](../includes/applies-to.md)][!INCLUDE [FHIR service](../includes/fhir-service.md)], [!INCLUDE [DICOM service](../includes/DICOM-service.md)]
 
-## Events: The basics
+Events let you subscribe to data changes in the FHIR® or DICOM® service and get notified through Azure Event Grid. You can use events to trigger workflows, automate tasks, send alerts, and more. In this FAQ, you’ll find answers to some common questions about events.
 
-## Can I use events with a different FHIR/DICOM service other than the Azure Health Data Services FHIR/DICOM service?
+**Can I use events with a non-Microsoft FHIR or DICOM service?**
 
-No. The Azure Health Data Services events feature only currently supports the Azure Health Data Services FHIR and DICOM services.
+No. The Events capability only supports the Azure Health Data Services FHIR and DICOM services.
 
-## What FHIR resource changes does events support?
+**What FHIR resource changes are supported by events?**
 
-Events are generated from the following FHIR service types:
+Events are generated from these FHIR service types:
 
-* **FhirResourceCreated** - The event emitted after a FHIR resource gets created successfully.
+- **FhirResourceCreated**. The event emitted after a FHIR resource is created.
 
-* **FhirResourceUpdated** - The event emitted after a FHIR resource gets updated successfully.
+- **FhirResourceUpdated**. The event emitted after a FHIR resource is updated.
 
-* **FhirResourceDeleted** - The event emitted after a FHIR resource gets soft deleted successfully.
+- **FhirResourceDeleted**. The event emitted after a FHIR resource is soft deleted.
 
-For more information about the FHIR service delete types, see [FHIR REST API capabilities for Azure Health Data Services FHIR service](../../healthcare-apis/fhir/fhir-rest-api-capabilities.md).
+For more information about delete types in the FHIR service, see [FHIR REST API capabilities for Azure Health Data Services](../../healthcare-apis/fhir/fhir-rest-api-capabilities.md).
 
-## Does events support FHIR bundles?
+**Does events support FHIR bundles?**
 
-Yes. The events feature is designed to emit notifications of data changes at the FHIR resource level. 
+Yes. The events capability emits notifications of data changes at the FHIR resource level. 
 
-Events support these [FHIR bundle types](http://hl7.org/fhir/R4/valueset-bundle-type.html) in the following ways:
+Events support these [FHIR bundle types](http://hl7.org/fhir/R4/valueset-bundle-type.html):
 
-* **Batch**: An event is emitted for each successful data change operation in a bundle. If one of the operations generates an error, no event is emitted for that operation. For example: the batch bundle contains five operations, however, there's an error with one of the operations. Events are emitted for the four successful operations with no event emitted for the operation that generated an error.
+- **Batch**. An event is emitted for each successful data change operation in a bundle. If one of the operations generates an error, no event is emitted for that operation. For example: the batch bundle contains five operations, however, there's an error with one of the operations. Events are emitted for the four successful operations with no event emitted for the operation that generated an error.
 
-* **Transaction**: An event is emitted for each successful bundle operation as long as there are no errors. If there are any errors within a transaction bundle, then no events are emitted. For example: the transaction bundle contains five operations, however, there's an error with one of the operations. No events are emitted for that bundle.
+- **Transaction**. An event is emitted for each successful bundle operation as long as there are no errors. If there are any errors within a transaction bundle, then no events are emitted. For example: the transaction bundle contains five operations, however, there's an error with one of the operations. No events are emitted for that bundle.
 
 > [!NOTE]
-> Events are not sent in the sequence of the data operations in the FHIR bundle.
+> Events aren't sent in the sequence of the data operations in the FHIR bundle.
 
-## What DICOM image changes does events support?
+**What DICOM image changes does events support?**
 
 Events are generated from the following DICOM service types:
 
-* **DicomImageCreated** - The event emitted after a DICOM image gets created successfully.
+- **DicomImageCreated**. The event emitted after a DICOM image is created.
 
-* **DicomImageDeleted** - The event emitted after a DICOM image gets deleted successfully.
+- **DicomImageDeleted**. The event emitted after a DICOM image is deleted.
 
-* **DicomImageUpdated** - The event emitted after a DICOM image gets updated successfully.
+- **DicomImageUpdated**. The event emitted after a DICOM image is updated. For more information, see [Update DICOM files](../dicom/update-files.md).
 
-## What is the payload of an events message? 
+**What is the payload of an events message?**
 
-For a detailed description of the events message structure and both required and nonrequired elements, see [Events message structures](events-message-structure.md). 
+For a description of the events message structure and required and nonrequired elements, see [Events message structures](events-message-structure.md). 
 
-## What is the throughput for the events messages?
+**What is the throughput for events messages?**
 
-The throughput of the FHIR or DICOM service and the Event Grid govern the throughput of FHIR and DICOM events. When a request made to the FHIR service is successful, it returns a 2xx HTTP status code. It also generates a FHIR resource or DICOM image changing event. The current limitation is 5,000 events/second per workspace for all FHIR or DICOM service instances in the workspace. 
+The throughput of the FHIR or DICOM service and the Event Grid governs the throughput of FHIR and DICOM events. When a request made to the FHIR service is successful, it returns a 2xx HTTP status code. It also generates a FHIR resource or DICOM image changing event. The current limitation is 5,000 events/second per workspace for all FHIR or DICOM service instances in the workspace. 
 
-## How am I charged for using events?
+**How am I charged for using events?**
 
 There are no extra charges for using [Azure Health Data Services events](https://azure.microsoft.com/pricing/details/health-data-services/). However, applicable charges for the [Event Grid](https://azure.microsoft.com/pricing/details/event-grid/) are assessed against your Azure subscription.
 
-## How do I subscribe to multiple FHIR and/or DICOM services in the same workspace separately?
+**How do I subscribe separately to multiple FHIR or DICOM services in the same workspace?**
 
-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.
+Use the Event Grid filtering feature. There are unique identifiers in the event message payload to differentiate 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 the workspace in the `data.serviceHostName` field. When you create a subscription, use the filtering operators to select the events you want to include in the subscription.
 
 :::image type="content" source="media\event-grid\event-grid-filters.png" alt-text="Screenshot of the Event Grid filters tab." lightbox="media\event-grid\event-grid-filters.png":::
 
-## Can I use the same subscriber for multiple workspaces, FHIR accounts, or DICOM accounts?
+**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 service to process in isolated scopes.
+Yes. We recommend that you use different subscribers for each FHIR or DICOM service to enable processing in isolated scopes.
 
-## Is Event Grid compatible with HIPAA and HITRUST compliance obligations?
+**Is the Event Grid compatible with HIPAA and HITRUST compliance requirements?**
 
-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](https://azure.microsoft.com/resources/microsoft-azure-compliance-offerings/).
+Yes. Event Grid supports Health Insurance Portability and Accountability Act (HIPAA) and Health Information Trust Alliance (HITRUST) obligations. For more information, see [Microsoft Azure Compliance Offerings](https://azure.microsoft.com/resources/microsoft-azure-compliance-offerings/).
 
-## What is the expected time to receive an events message?
+**How long does it take 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](../../event-grid/quotas-limits.md) has been met.
+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](../../event-grid/quotas-limits.md) is reached.
 
-## Is it possible to receive duplicate events messages?
+**Is it possible to receive duplicate events messages?**
 
-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 considers that as a delivery failure and resends the events message. For more information, see [Azure Event Grid delivery and retry](../../event-grid/delivery-and-retry.md).
+Yes. The Event Grid guarantees at least one events message delivery with its push mode. There may be cases when the event delivery request returns with a transient failure status code for random reasons. In this situation, the Event Grid considers it a delivery failure and resends the events message. For more information, see [Azure Event Grid delivery and retry](../../event-grid/delivery-and-retry.md).
 
-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 deduplicate. 
+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 for each event. You can rely on them to deduplicate. 
 
-## More frequently asked questions
-
-[FAQs about the Azure Health Data Services](../healthcare-apis-faqs.md)
-
-[FAQs about Azure Health Data Services DICOM service](../dicom/dicom-services-faqs.yml)
-
-[FAQs about Azure Health Data Services FHIR service](../fhir/fhir-faq.md)
-
-[FAQs about Azure Health Data Services MedTech service](../iot/iot-connector-faqs.md)
-
-FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+[!INCLUDE [FHIR and DICOM trademark statement](../includes/healthcare-apis-fhir-dicom-trademark.md)]