Merge pull request #242795 from msjasteppe/events-faqs-updates

Working on incrementally increasing Acrolinx score

Author: JamesJBarnett

articles/healthcare-apis/events/events-consume-logic-apps.md

@@ -1,18 +1,21 @@
 ---
 title: Consume events with Logic Apps - Azure Health Data Services
-description: This tutorial provides resources on how to consume events with Logic Apps.
+description: Learn how to consume FHIR events with Logic Apps.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: tutorial
-ms.date: 12/21/2022
+ms.date: 06/23/2022
 ms.author: jasteppe
 ---
 
-# Tutorial: Consume events with Logic Apps
+# Tutorial: Consume FHIR events with Logic Apps
 
-This tutorial shows how to use Azure Logic Apps to process Azure Health Data Services Fast Healthcare Interoperability Resources (FHIR®) events. Logic Apps creates and runs automated workflows to process event data from other applications. You'll learn how to register a FHIR event with your Logic App, meet a specified event criteria, and perform a service operation.
+> [!NOTE]
+> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
+
+This tutorial shows how to use Azure Logic Apps to process Azure Health Data Services FHIR events. Logic Apps creates and runs automated workflows to process event data from other applications. Learn how to register a FHIR event with your Logic App, meet a specified event criteria, and perform a service operation.
 
 Here's an example of a Logic App workflow:
 
@@ -41,13 +44,13 @@ To set up an automated workflow, you must first create a Logic App. For more inf
 Follow these steps:
 
 1. Go to the Azure portal.
-2. Search for "Logic App".
-3. Select "Add".
-4. Specify Basic details.
-5. Specify Hosting.
-6. Specify Monitoring.
-7. Specify Tags.
-8. Review and create your Logic App.
+2. Search for **Logic App**.
+3. Select **Add**.
+4. Specify **Basic details**.
+5. Specify **Hosting**.
+6. Specify **Monitoring**.
+7. Specify **Tags**.
+8. **Review and create** your Logic App.
 
 You now need to fill out the details of your Logic App. Specify information for these five categories. They are in separate tabs:
 
@@ -90,7 +93,7 @@ Choose a plan type (Standard or Consumption). Create a new Windows Plan name and
 
 - Zone redundancy deployment
 
-Enabling your plan will make it zone redundant.
+Enabling your plan makes it zone redundant.
 
 ### Hosting - Tab 2
 
@@ -117,21 +120,21 @@ Enable Azure Monitor Application Insights to automatically monitor your applicat
 
 ### Tags - Tab 4
 
-Continue specifying your Logic App by clicking "Next: Tags".
+Continue specifying your Logic App by clicking **Next: Tags**.
 
 #### Use tags to categorize resources
 
 Tags are name/value pairs that enable you to categorize resources and view consolidated billing by applying the same tag to multiple resources and resource groups.
 
-This example won't use tagging.
+This example doesn't use tagging.
 
 ### Review + create - Tab 5
 
-Finish specifying your Logic App by clicking "Next: Review + create".
+Finish specifying your Logic App by clicking **Next: Review + create**.
 
 #### Review your Logic App
 
-Your proposed Logic app will display the following details:
+Your proposed Logic app displays the following details:
 
 - Subscription
 - Resource Group
@@ -142,7 +145,7 @@ Your proposed Logic app will display the following details:
 - Plan
 - Monitoring
 
-If you're satisfied with the proposed configuration, select "Create". If not, select "Previous" to go back and specify new details.
+If you're satisfied with the proposed configuration, select **Create**. If not, select **Previous** to go back and specify new details.
 
 First you'll see an alert telling you that deployment is initializing. Next you'll see a new page telling you that the deployment is in progress.
 
@@ -154,7 +157,7 @@ If there are no errors, you'll finally see a notification telling you that your
 
 #### Your Logic App dashboard
 
-Azure creates a dashboard when your Logic App is complete. The dashboard will show you the status of your app. You can return to your dashboard by clicking Overview in the Logic App menu. Here's a Logic App dashboard:
+Azure creates a dashboard when your Logic App is complete. The dashboard shows you the status of your app. You can return to your dashboard by clicking Overview in the Logic App menu. Here's a Logic App dashboard:
 
 :::image type="content" source="media/events-logic-apps/events-logic-overview.png" alt-text="Screenshot of your Logic Apps overview dashboard." lightbox="media/events-logic-apps/events-logic-overview.png":::
 
@@ -189,10 +192,10 @@ Before you begin, you'll need to have a Logic App configured and running correct
 Once your Logic App is running, you can create and configure a workflow. To initialize a workflow, follow these steps:
 
 1. Start at the Azure portal.
-2. Select "Logic Apps" in Azure services.
+2. Select **Logic Apps** in Azure services.
 3. Select the Logic App you created.
-4. Select "Workflows" in the Workflow menu on the left.
-5. Select "Add" to add a workflow.
+4. Select **Workflows** in the Workflow menu on the left.
+5. Select **Add** to add a workflow.
 
 ### Configuring a new workflow
 
@@ -244,7 +247,7 @@ Fill in the details for subscription, resource type, and resource name. Then you
 - Resource deleted
 - Resource updated
 
-For more information about event types, see [What FHIR resource events does Events support?](events-faqs.md).
+For more information about event types, see [What FHIR resource events does Events support?](events-faqs.md#what-fhir-resource-events-does-events-support).
 
 ### Adding an HTTP action
 
@@ -285,9 +288,9 @@ When the condition is ready, you can specify what actions happen if the conditio
 
 ### Choosing a condition criteria
 
-In order to specify whether you want to take action for the specific event, begin specifying the criteria by clicking on "Condition" in the workflow on the left. You'll then see a set of condition choices on the right.
+In order to specify whether you want to take action for the specific event, begin specifying the criteria by clicking on **Condition** in the workflow. A set of condition choices are then displayed.
 
-Under the "And" box, add these two conditions:
+Under the **And** box, add these two conditions:
 
 - resourceType
 - Event Type
@@ -331,19 +334,24 @@ To test your new workflow, do the following steps:
 1. Add a new Patient FHIR Resource to your FHIR Service.
 2. Wait a moment or two and then check the Overview webpage of your Logic App workflow.
 3. The event should be shaded in green if the action was successful.
-4. If it failed, the event will be shaded in red.
+4. If it failed, the event is shaded in red.
 
 Here's an example of a workflow trigger success operation:
 
 :::image type="content" source="media/events-logic-apps/events-logic-success.png" alt-text="Screenshot showing workflow success indicated by green highlighting of the workflow name." lightbox="./media/events-logic-apps/events-logic-success.png":::
 
 ## Next steps
 
-In this tutorial, you learned about how to use Logic Apps to process FHIR events.
+In this tutorial, you learned how to use Logic Apps to process FHIR events.
+
+To learn about Events, see
+
+> [!div class="nextstepaction"]
+> [What are Events?](events-overview.md)
 
-To learn more about FHIR events, see:
+To learn about the Events frequently asked questions (FAQs), see
 
 > [!div class="nextstepaction"]
-> [What are Events?](./events-overview.md)
+> [Frequently asked questions about Events](events-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.

articles/healthcare-apis/events/events-deploy-portal.md

@@ -1,18 +1,21 @@
 ---
 title: Deploy Events using the Azure portal - Azure Health Data Services
-description: This article describes how to deploy the Events feature in the Azure portal.
+description: Learn how to deploy the Events feature using the Azure portal.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 10/21/2022
+ms.date: 06/23/2022
 ms.author: jasteppe
 ---
 
 # Quickstart: Deploy Events using the Azure portal
 
-In this quickstart, you’ll learn how to deploy the Azure Health Data Services Events feature in the Azure portal to send Fast Healthcare Interoperability Resources (FHIR®) and DICOM event messages.
+> [!NOTE]
+> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
+
+In this quickstart, learn how to deploy the Azure Health Data Services Events feature in the Azure portal to send FHIR and DICOM event messages.
 
 ## Prerequisites
 
@@ -57,7 +60,7 @@ It's important that you have the following prerequisites completed before you be
 
 4. After the form is completed, select **Create** to begin the subscription creation. 
 
-5. Event messages won't be sent until the Event Grid System Topic deployment has successfully completed. Upon successful creation of the Event Grid System Topic, the status of the workspace will change from "Updating" to "Succeeded".
+5. Event message sending can't occur until the Event Grid System Topic deployment has successfully completed. Upon successful creation of the Event Grid System Topic, the status of the workspace changes from **Updating** to **Succeeded**.
 
    :::image type="content" source="media/events-deploy-in-portal/events-new-subscription-create.png" alt-text="Screenshot of an events subscription being deployed"  lightbox="media/events-deploy-in-portal/events-new-subscription-create.png":::
 
@@ -76,7 +79,7 @@ It's important that you have the following prerequisites completed before you be
 
 ## Next steps
 
-In this article, you've learned how to deploy events in the Azure portal. For details about supported events, see [Azure Health Data Services as an Event Grid source](../../event-grid/event-schema-azure-health-data-services.md).
+In this article, you learned how to deploy Events in the Azure portal. For details about supported events, see [Azure Health Data Services as an Event Grid source](../../event-grid/event-schema-azure-health-data-services.md).
 
 To learn how to enable the Events metrics, see
 

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

@@ -1,24 +1,27 @@
 ---
 title: Disable Events and delete workspaces - Azure Health Data Services
-description: This article provides resources on how to disable the Events service and delete workspaces.
+description: Learn how to disable the Events service and delete workspaces.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 10/21/2022
+ms.date: 06/23/2022
 ms.author: jasteppe
 ---
 
 # How to disable Events and delete workspaces
 
-In this article, you'll learn how to disable the Events feature and delete workspaces in the Azure Health Data Services.
+> [!NOTE]
+> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
+
+In this article, learn how to disable the Events feature and delete workspaces in the Azure Health Data Services.
 
 ## Disable Events
 
 To disable Events from sending event messages for a single **Event Subscription**, the **Event Subscription** must be deleted.
 
-1. Select the **Event Subscription** to be deleted. In this example, we'll be selecting an Event Subscription named **fhir-events**.
+1. Select the **Event Subscription** to be deleted. In this example, we select an Event Subscription named **fhir-events**.
 
    :::image type="content" source="media/disable-delete-workspaces/events-select-subscription.png" alt-text="Screenshot of Events subscriptions and select event subscription to be deleted." lightbox="media/disable-delete-workspaces/events-select-subscription.png":::
 
@@ -31,21 +34,21 @@ To disable Events from sending event messages for a single **Event Subscription*
    :::image type="content" source="media/disable-delete-workspaces/events-disable-no-subscriptions.png" alt-text="Screenshot of Events subscriptions and delete all event subscriptions to disable events." lightbox="media/disable-delete-workspaces/events-disable-no-subscriptions.png":::
 
 > [!NOTE]
-> The Fast Healthcare Interoperability Resources (FHIR®) service will automatically go into an **Updating** status to disable the Events extension when a full delete of Event Subscriptions is executed. The FHIR service will remain online while the operation is completing.
+> The FHIR service will automatically go into an **Updating** status to disable the Events extension when a full delete of Event Subscriptions is executed. The FHIR service will remain online while the operation is completing.
 
 ## Delete workspaces
 
-To successfully delete a workspace, delete all associated child resources first (for example: DICOM services, FHIR services and MedTech services), delete all Event Subscriptions, and then delete the workspace. Not deleting the child resources and Event Subscriptions first will cause an error when attempting to delete a workspace with child resources.
+To avoid errors and successfully delete workspaces, follow these steps and in this specific order:
 
-As an example:
-
- 1. Delete all workspaces associated child resources - for example: DICOM service(s), FHIR service(s), and MedTech service(s).
- 2. Delete all workspaces associated Event Subscriptions.
- 3. Delete workspace.
+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.
 
 ## Next steps
 
-For more information about troubleshooting Events, see the Events troubleshooting guide:
+In this article, you learned how to disable Events and delete workspaces.
+
+For more information about troubleshooting Events, see
 
 > [!div class="nextstepaction"]
 > [Troubleshoot Events](events-troubleshooting-guide.md)

articles/healthcare-apis/events/events-enable-diagnostic-settings.md

@@ -1,25 +1,26 @@
 ---
 title: Enable Events diagnostic settings for diagnostic logs and metrics export - Azure Health Data Services
-description: This article provides resources on how to enable Events diagnostic settings for diagnostic logs and metrics exporting.
+description: Learn how to enable Events diagnostic settings for diagnostic logs and metrics exporting.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 10/21/2022
+ms.date: 06/23/2022
 ms.author: jasteppe
 ---
 
 # How to enable diagnostic settings for Events
 
-In this article, you'll be provided resources to enable the Events diagnostic settings for Azure Event Grid system topics. 
+> [!NOTE]
+> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
 
-After they're enabled, Event Grid system topics diagnostic logs and metrics will be exported to the destination of your choosing for audit, analysis, troubleshooting, or backup.
+In this article, learn how to enable the Events diagnostic settings for Azure Event Grid system topics. 
 
 ## Resources
 
 |Description|Resource|
-|----------------|--------|
+|-----------|--------|
 |Learn how to enable the Event Grid system topics diagnostic logging and metrics export feature.|[Enable diagnostic logs for Event Grid system topics](../../event-grid/enable-diagnostic-logs-topic.md#enable-diagnostic-logs-for-event-grid-system-topics)|
 |View a list of currently captured Event Grid system topics diagnostic logs.|[Event Grid system topic diagnostic logs](../../azure-monitor/essentials/resource-logs-categories.md#microsofteventgridsystemtopics)|
 |View a list of currently captured Event Grid system topics metrics.|[Event Grid system topic metrics](../../azure-monitor/essentials/metrics-supported.md#microsofteventgridsystemtopics)| 

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

@@ -6,7 +6,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: reference
-ms.date: 06/16/2022
+ms.date: 06/23/2022
 ms.author: jasteppe
 ---
 
@@ -62,7 +62,7 @@ For a detailed description of the Events message structure and both required and
 
 ## What is the throughput for the 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 a workspace for all FHIR or DICOM service instances in it. 
+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. 
 
 ## How am I charged for using Events?
 
@@ -76,7 +76,7 @@ You can use the Event Grid filtering feature. There are unique identifiers in th
 
 ## 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.
+Yes. We recommend that you use different subscribers for each individual FHIR or DICOM service to process in isolated scopes.
 
 ## Is Event Grid compatible with HIPAA and HITRUST compliance obligations?