Merge pull request #215477 from msjasteppe/events-logic-app-updates

Updates to Events Logic Apps article.

Author: JamesJBarnett

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

@@ -6,13 +6,13 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 07/06/2022
-ms.author: v-smcevoy
+ms.date: 10/21/2022
+ms.author: jasteppe
 ---
 
 # Consume 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 create and run automated workflows to process event data from other applications. You will learn how to register a FHIR event with your Logic App, meet a specified event criteria, and perform a service operation.
+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.
 
 Here's an example of a Logic App workflow:
 
@@ -30,7 +30,7 @@ Follow these steps to create a Logic App workflow to consume FHIR events:
 
 ## Prerequisites
 
-Before you begin this tutorial, you need to have deployed a FHIR service and enabled events. For more information about deploying events, see [Deploy Events in the Azure portal](./events-deploy-portal.md).
+Before you begin this tutorial, you need to have deployed a FHIR service and enabled events. For more information about deploying events, see [Deploy Events in the Azure portal](events-deploy-portal.md).
 
 ## Creating a Logic App
 
@@ -42,7 +42,7 @@ Follow these steps:
 
 1. Go to the Azure portal.
 2. Search for "Logic App".
-3. Click "Add".
+3. Select "Add".
 4. Specify Basic details.
 5. Specify Hosting.
 6. Specify Monitoring.
@@ -51,7 +51,7 @@ Follow these steps:
 
 You now need to fill out the details of your Logic App. Specify information for these five categories. They are in separate tabs:
 
-:::image type="content" source="media/events-logic-apps/events-logic-tabs.png" alt-text="Screenshot of the five tabs for specifying your Logic App." lightbox="./media/events-logic-apps/events-logic-tabs.png":::
+:::image type="content" source="media/events-logic-apps/events-logic-tabs.png" alt-text="Screenshot of the five tabs for specifying your Logic App." lightbox="media/events-logic-apps/events-logic-tabs.png":::
 
 - Tab 1 - Basics
 - Tab 2 - Hosting
@@ -123,7 +123,7 @@ Continue specifying your Logic App by clicking "Next: Tags".
 
 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 will not use tagging.
+This example won't use tagging.
 
 ### Review + create - Tab 5
 
@@ -142,21 +142,21 @@ Your proposed Logic app will display the following details:
 - Plan
 - Monitoring
 
-If you're satisfied with the proposed configuration, click "Create". If not, click "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.
 
-:::image type="content" source="media/events-logic-apps/events-logic-progress.png" alt-text="Screenshot of the notification telling you your deployment is in progress." lightbox="./media/events-logic-apps/events-logic-progress.png":::
+:::image type="content" source="media/events-logic-apps/events-logic-progress.png" alt-text="Screenshot of the notification telling you your deployment is in progress." lightbox="media/events-logic-apps/events-logic-progress.png":::
 
-If there are no errors, you will finally see a notification telling you that your deployment is complete.
+If there are no errors, you'll finally see a notification telling you that your deployment is complete.
 
-:::image type="content" source="media/events-logic-apps/events-logic-complete.png" alt-text="Screenshot of the notification telling you your deployment is complete." lightbox="./media/events-logic-apps/events-logic-complete.png":::
+:::image type="content" source="media/events-logic-apps/events-logic-complete.png" alt-text="Screenshot of the notification telling you your deployment is complete." lightbox="media/events-logic-apps/events-logic-complete.png":::
 
 #### 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:
 
-:::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":::
+:::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":::
 
 You can do the following activities from your dashboard.
 
@@ -189,16 +189,16 @@ 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. Click "Logic Apps" in Azure services.
+2. Select "Logic Apps" in Azure services.
 3. Select the Logic App you created.
-4. Click "Workflows" in the Workflow menu on the left.
-5. Click "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
 
-You will see a new panel on the right for creating a workflow.
+You'll see a new panel on the right for creating a workflow.
 
-:::image type="content" source="media/events-logic-apps/events-logic-panel.png" alt-text="Screenshot of the panel for creating a workflow." lightbox="./media/events-logic-apps/events-logic-panel.png":::
+:::image type="content" source="media/events-logic-apps/events-logic-panel.png" alt-text="Screenshot of the panel for creating a workflow." lightbox="media/events-logic-apps/events-logic-panel.png":::
 
 You can specify the details of the new workflow in the panel on the right.
 
@@ -211,21 +211,21 @@ To set up a new workflow, fill in these details:
 
 Specify a new name for your workflow. Indicate whether you want the workflow to be stateful or stateless. Stateful is for business processes and stateless is for processing IoT events.
 
-When you have specified the details, click "Create" to begin designing your workflow.
+When you've specified the details, select "Create" to begin designing your workflow.
 
 ### Designing the workflow
 
-In your new workflow, click the name of the enabled workflow.
+In your new workflow, select the name of the enabled workflow.
 
 You can write code to design a workflow for your application, but for this tutorial, choose the Designer option on the Developer menu.
 
-Next, click "Choose an operation" to display the "Add a Trigger" blade on the right. Then search for "Azure Event Grid" and click the "Azure" tab below. The Event Grid is not a Logic App Built-in.
+Next, select "Choose an operation" to display the "Add a Trigger" blade on the right. Then search for "Azure Event Grid" and select the "Azure" tab below. The Event Grid isn't a Logic App Built-in.
 
-:::image type="content" source="media/events-logic-apps/events-logic-grid.png" alt-text="Screenshot of the search results for Azure Event Grid." lightbox="./media/events-logic-apps/events-logic-grid.png":::
+:::image type="content" source="media/events-logic-apps/events-logic-grid.png" alt-text="Screenshot of the search results for Azure Event Grid." lightbox="media/events-logic-apps/events-logic-grid.png":::
 
-When you see the "Azure Event Grid" icon,  click on it to display the Triggers and Actions available from Event Grid. For more information about Event Grid, see [What is Azure Event Grid?](./../../event-grid/overview.md).
+When you see the "Azure Event Grid" icon,  select on it to display the Triggers and Actions available from Event Grid. For more information about Event Grid, see [What is Azure Event Grid?](./../../event-grid/overview.md).
 
-Click "When a resource event occurs" to set up a trigger for the Azure Event Grid.
+Select "When a resource event occurs" to set up a trigger for the Azure Event Grid.
 
 To tell Event Grid how to respond to the trigger, you must specify parameters and add actions.
 
@@ -244,48 +244,48 @@ 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).
 
 ### Adding an HTTP action
 
-Once you have specified the trigger events, you must add more details. Click the "+" below the "When a resource event occurs" button.
+Once you've specified the trigger events, you must add more details. Select the "+" below the "When a resource event occurs" button.
 
-You need to add a specific action. Click "Choose an operation" to continue. Then, for the operation, search for "HTTP" and click on "Built-in" to select an HTTP operation. The HTTP action will allow you to query the FHIR service.
+You need to add a specific action. Select "Choose an operation" to continue. Then, for the operation, search for "HTTP" and select on "Built-in" to select an HTTP operation. The HTTP action will allow you to query the FHIR service.
 
 The options in this example are:
 
 - Method is "Get"
-- URL is "concat('https://', triggerBody()?['subject'], '/_history/', triggerBody()?['dataVersion'])".
+- URL is `"concat('https://', triggerBody()?['subject'], '/_history/', triggerBody()?['dataVersion'])"`.
 - Authentication type is "Managed Identity".
-- Audience is "concat('https://', triggerBody()?['data']['resourceFhirAccount'])"
+- Audience is `"concat('https://', triggerBody()?['data']['resourceFhirAccount'])"`.
 
 ### Allow FHIR Reader access to your Logic App
 
 At this point, you need to give the FHIR Reader access to your app, so it can verify that the event details are correct. Follow these steps to give it access:
 
-1. The first step is to go back to your Logic App and click the Identity menu item.
+1. The first step is to go back to your Logic App and select the Identity menu item.
 
 2. In the System assigned tab, make sure the Status is "On".
 
-3. Click on Azure role assignments. Click "Add role assignment".
+3. Select on Azure role assignments. Select "Add role assignment".
 
-4. Specify the following:
+4. Specify the following options:
 
    - Scope = Subscription
    - Subscription = your subscription
    - Role = FHIR Data Reader.
 
-When you have specified the first four steps, add the role assignment by Managed identity, using Subscription, Managed identity (Logic App Standard), and select your Logic App by clicking the name and then clicking the Select button. Finally, click "Review + assign" to assign the role.
+When you've specified the first four steps, add the role assignment by Managed identity, using Subscription, Managed identity (Logic App Standard), and select your Logic App by clicking the name and then clicking the Select button. Finally, select "Review + assign" to assign the role.
 
 ### Add a condition
 
-After you have given FHIR Reader access to your app, go back to the Logic App workflow Designer. Then add a condition to determine whether the event is one you want to process. Click the "+" below HTTP to "Choose an operation". On the right, search for the word "condition". Click on "Built-in" to display the Control icon. Next click Actions and choose Condition.
+After you have given FHIR Reader access to your app, go back to the Logic App workflow Designer. Then add a condition to determine whether the event is one you want to process. Select the "+" below HTTP to "Choose an operation". On the right, search for the word "condition". Select on "Built-in" to display the Control icon. Next select Actions and choose Condition.
 
 When the condition is ready, you can specify what actions happen if the condition is true or false.
 
 ### 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 will 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 on the left. You'll then see a set of condition choices on the right.
 
 Under the "And" box, add these two conditions:
 
@@ -300,19 +300,19 @@ The expression for getting the resourceType is `body('HTTP')?['resourceType']`.
 
 You can select Event Type from the Dynamic Content.
 
-Here is an example of the Condition criteria:
+Here's an example of the Condition criteria:
 
-:::image type="content" source="media/events-logic-apps/events-logic-condition.png" alt-text="Screenshot of the condition criteria for your workflow." lightbox="./media/events-logic-apps/events-logic-condition.png":::
+:::image type="content" source="media/events-logic-apps/events-logic-condition.png" alt-text="Screenshot of the condition criteria for your workflow." lightbox="media/events-logic-apps/events-logic-condition.png":::
 
 #### Save your workflow
 
-When you have entered the condition criteria, save your workflow.
+When you've entered the condition criteria, save your workflow.
 
 #### Workflow dashboard
 
-To check the status of your workflow, click Overview in the workflow menu. Here is a dashboard for a workflow:
+To check the status of your workflow, select Overview in the workflow menu. Here's a dashboard for a workflow:
 
-:::image type="content" source="media/events-logic-apps/events-logic-dashboard.png" alt-text="Screenshot of the Logic App workflow dashboard." lightbox="./media/events-logic-apps/events-logic-dashboard.png":::
+:::image type="content" source="media/events-logic-apps/events-logic-dashboard.png" alt-text="Screenshot of the Logic App workflow dashboard." lightbox="media/events-logic-apps/events-logic-dashboard.png":::
 
 You can do the following operations from your workflow dashboard:
 
@@ -333,15 +333,15 @@ To test your new workflow, do the following steps:
 3. The event should be shaded in green if the action was successful.
 4. If it failed, the event will be shaded in red.
 
-Here is an example of a workflow trigger success operation:
+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
 
-For more information about FHIR events, see
+For more information about FHIR events, see:
 
->[!div class="nextstepaction"]
->[What are Events?](./events-overview.md)
+> [!div class="nextstepaction"]
+> [What are Events?](./events-overview.md)
 
 FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.