Merge pull request #222269 from msjasteppe/receive-edit

Receive edit

Author: 19BMG00

articles/healthcare-apis/iot/device-data-through-iot-hub.md

@@ -6,14 +6,20 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: iomt
 ms.topic: tutorial 
-ms.date: 12/15/2022
+ms.date: 12/22/2022
 ms.author: jasteppe
 ---
 
 # Tutorial: Receive device messages through Azure IoT Hub
 
 For enhanced workflows and ease of use, you can use the MedTech service to receive messages from devices you create and manage through an IoT hub in [Azure IoT Hub](../../iot-hub/iot-concepts-and-iot-hub.md). This tutorial uses an Azure Resource Manager template (ARM template) and a **Deploy to Azure** button to deploy a MedTech service. The template creates an IoT hub to create and manage devices, and then routes device messages to an event hub in Azure Event Hubs for the MedTech service to pick up.
 
+:::image type="content" source="media\device-data-through-iot-hub\data-flow-diagram.png" border="false" alt-text="Diagram of the IoT message data flow through an IoT hub and event hub, and then into the MedTech service." lightbox="media\device-data-through-iot-hub\data-flow-diagram.png":::
+
+> [!TIP]
+> To learn more about how the MedTech service transforms and persists device messages into the Fast Healthcare Interoperability Resources (FHIR®) service as FHIR Observations, see [The MedTech service data flow](data-flow.md). 
+
+
 In this tutorial, you learn how to:
 
 > [!div class="checklist"]
@@ -26,12 +32,6 @@ In this tutorial, you learn how to:
 > [!TIP]
 > To learn more about ARM templates, see [What are ARM templates?](./../../azure-resource-manager/templates/overview.md)
 
-## Device message flow
-
-The following diagram demonstrates the IoT device message flow when you use an IoT hub in Azure IoT Hub with the MedTech service in Azure Health Data Services. Devices send messages to your IoT hub. Your IoT hub routes the device messages to the device message event hub in Azure Event Hubs for the MedTech service to pick up. The MedTech service transforms the device messages and persists them in the Fast Healthcare Interoperability Resources (FHIR®) service as FHIR observations. For more information, see [MedTech service data flow](data-flow.md).
-
-:::image type="content" source="media\iot-hub-to-iot-connector\iot-hub-to-iot-connector.png" border="false" alt-text="Diagram of the IoT message data flow through an IoT hub and event hub, and then into the MedTech service." lightbox="media\iot-hub-to-iot-connector\iot-hub-to-iot-connector.png":::
-
 ## Prerequisites
 
 To begin your deployment and complete the tutorial, you must have the following prerequisites:
@@ -82,23 +82,23 @@ To begin deployment in the Azure portal, select the **Deploy to Azure** button:
 
    - **Destination Mapping**: Don't change the default values for this tutorial. The mappings are set in the template to send a device message to your IoT hub later in the tutorial.
 
-   :::image type="content" source="media\iot-hub-to-iot-connector\iot-deploy-template-options.png" alt-text="Screenshot that shows deployment options for the MedTech service for Health Data Services in the Azure portal." lightbox="media\iot-hub-to-iot-connector\iot-deploy-template-options.png":::
+   :::image type="content" source="media\device-data-through-iot-hub\deploy-template-options.png" alt-text="Screenshot that shows deployment options for the MedTech service for Health Data Services in the Azure portal." lightbox="media\device-data-through-iot-hub\deploy-template-options.png":::
 
 2. To validate your configuration, select **Review + create**.
 
-   :::image type="content" source="media\iot-hub-to-iot-connector\iot-review-and-create-button.png" alt-text="Screenshot that shows the Review + create button selected in the Azure portal.":::
+   :::image type="content" source="media\device-data-through-iot-hub\review-and-create-button.png" alt-text="Screenshot that shows the Review + create button selected in the Azure portal.":::
 
 3. In **Review + create**, check the template validation status. If validation is successful, the template displays **Validation Passed**. If validation fails, fix the detail that's indicated in the error message, and then select **Review + create** again.
 
-   :::image type="content" source="media\iot-hub-to-iot-connector\iot-validation-completed.png" alt-text="Screenshot that shows the Review + create pane displaying the Validation Passed message.":::
+   :::image type="content" source="media\device-data-through-iot-hub\validation-complete.png" alt-text="Screenshot that shows the Review + create pane displaying the Validation Passed message.":::
 
 4. After a successful validation, to begin the deployment, select **Create**.
 
-   :::image type="content" source="media\iot-hub-to-iot-connector\iot-create-button.png" alt-text="Screenshot that shows the highlighted Create button.":::
+   :::image type="content" source="media\device-data-through-iot-hub\create-button.png" alt-text="Screenshot that shows the highlighted Create button.":::
 
 5. In a few minutes, the Azure portal displays the message that your deployment is completed.
 
-   :::image type="content" source="media\iot-hub-to-iot-connector\iot-deployment-complete-banner.png" alt-text="Screenshot that shows a green checkmark and the message Your deployment is complete.":::
+   :::image type="content" source="media\device-data-through-iot-hub\deployment-complete-banner.png" alt-text="Screenshot that shows a green checkmark and the message Your deployment is complete.":::
 
    > [!IMPORTANT]
    > If you're going to allow access from multiple services to the device message event hub, it is highly recommended that each service has its own event hub consumer group.
@@ -119,17 +119,17 @@ When deployment is completed, the following resources and access roles are creat
 
 - An event hub consumer group. In this deployment, the consumer group is named *$Default*.
 
-- The Azure Event Hubs Data Sender role. In this deployment, the role is named *devicedatasender*. The Azure Event Hubs Data Sender role isn't used in this tutorial. To learn more about the role, see [Review of deployed resources and access permissions](deploy-02-new-button.md#required-post-deployment-tasks).
+- An Azure Event Hubs Data Sender role. In this deployment, the role is named *devicedatasender*. The Azure Event Hubs Data Sender role isn't used in this tutorial.
 
-- An instance of Azure IoT Hub with [message routing](../../iot-hub/iot-hub-devguide-messages-d2c.md) configured to send device messages to the device message event hub.
+- An Azure IoT Hub with [message routing](../../iot-hub/iot-hub-devguide-messages-d2c.md) configured to send device messages to the device message event hub.
 
 - A [user-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) that provides send access from the IoT hub to the device message event hub. The managed identity has the Azure Event Hubs Data Sender role in the [Access control section (IAM)](../../role-based-access-control/overview.md) of the device message event hub.  
 
 - A Health Data Services workspace.
 
 - A Health Data Services FHIR service.
 
-- An instance of the MedTech service for Health Data Services, with the required [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) roles:
+- A Health Data Services MedTech service with the required [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) access roles:
 
   - For the device message event hub, the Azure Events Hubs Data Receiver role is assigned in the [Access control section (IAM)](../../role-based-access-control/overview.md) of the device message event hub.
 
@@ -156,22 +156,22 @@ You complete the steps by using Visual Studio Code with the Azure IoT Hub extens
 
 2. In Explorer, in **Azure IoT Hub**, select **…** and choose **Select IoT Hub**.
 
-   :::image type="content" source="media\iot-hub-to-iot-connector\iot-select-iot-hub.png" alt-text="Screenshot of Visual Studio Code with the Azure IoT Hub extension with the deployed IoT hub selected." lightbox="media\iot-hub-to-iot-connector\iot-select-iot-hub.png":::
+   :::image type="content" source="media\device-data-through-iot-hub\select-iot-hub.png" alt-text="Screenshot of Visual Studio Code with the Azure IoT Hub extension with the deployed IoT hub selected." lightbox="media\device-data-through-iot-hub\select-iot-hub.png":::
 
 3. Select the Azure subscription where your IoT hub was provisioned.
 
 4. Select your IoT hub. The name of your IoT hub is the *basename* you provided when you provisioned the resources prefixed with **ih-**. An example hub name is *ih-azuredocsdemo*.
 
 5. In Explorer, in **Azure IoT Hub**, select **…** and choose **Create Device**. An example device name is *iot-001*.
 
-   :::image type="content" source="media\iot-hub-to-iot-connector\iot-create-device.png" alt-text="Screenshot that shows Visual Studio Code with the Azure IoT Hub extension with Create device selected." lightbox="media\iot-hub-to-iot-connector\iot-create-device.png":::
+   :::image type="content" source="media\device-data-through-iot-hub\create-device.png" alt-text="Screenshot that shows Visual Studio Code with the Azure IoT Hub extension with Create device selected." lightbox="media\device-data-through-iot-hub\create-device.png":::
 
 6. To send a test message from the device to your IoT hub, right-click the device and select **Send D2C Message to IoT Hub**.
 
    > [!NOTE]
-   > In this device-to-cloud (D2C) example, *cloud* is the IoT hub in Azure IoT Hub that receives the device message. Azure IoT Hub supports two-way communications. To set up a cloud-to-device (C2D) scenario, select **Send C2D Message to Device Cloud**.
+   > In this device-to-cloud (D2C) example, *cloud* is the IoT hub in the Azure IoT Hub that receives the device message. Azure IoT Hub supports two-way communications. To set up a cloud-to-device (C2D) scenario, select **Send C2D Message to Device Cloud**.
 
-   :::image type="content" source="media\iot-hub-to-iot-connector\iot-select-device-to-cloud-message.png" alt-text="Screenshot that shows Visual Studio Code with the Azure IoT Hub extension and the Send D2C Message to IoT Hub option selected." lightbox="media\iot-hub-to-iot-connector\iot-select-device-to-cloud-message.png":::
+   :::image type="content" source="media\device-data-through-iot-hub\select-device-to-cloud-message.png" alt-text="Screenshot that shows Visual Studio Code with the Azure IoT Hub extension and the Send D2C Message to IoT Hub option selected." lightbox="media\device-data-through-iot-hub\select-device-to-cloud-message.png":::
 
 7. In **Send D2C Messages**, select or enter the following values:
 
@@ -186,7 +186,7 @@ You complete the steps by using Visual Studio Code with the Azure IoT Hub extens
    - **Edit**: Clear any existing text, and then paste the following JSON.
 
      > [!TIP]
-     > You can use the **Copy** option in in the right corner of the test message, and then paste it in **Edit**.
+     > You can use the **Copy** option in in the right corner of the below test message, and then paste it within the **Edit** option.
 
      ```json
      {
@@ -203,7 +203,7 @@ You complete the steps by using Visual Studio Code with the Azure IoT Hub extens
 
 8. To begin the process of sending a test message to your IoT hub, select **Send**.
 
-   :::image type="content" source="media\iot-hub-to-iot-connector\iot-select-device-to-cloud-message-options.png" alt-text="Screenshot that shows Visual Studio code with the Azure IoT Hub extension with the device message options selected." lightbox="media\iot-hub-to-iot-connector\iot-select-device-to-cloud-message-options.png":::
+   :::image type="content" source="media\device-data-through-iot-hub\select-device-to-cloud-message-options.png" alt-text="Screenshot that shows Visual Studio code with the Azure IoT Hub extension with the device message options selected." lightbox="media\device-data-through-iot-hub\select-device-to-cloud-message-options.png":::
 
    After you select **Send**, it might take up to five minutes for the FHIR resources to be available in the FHIR service.
 
@@ -221,9 +221,9 @@ For your MedTech service metrics, you can see that your MedTech service complete
 - **Number of Measurements**: Created five measurements.
 - **Number of FHIR resources**: Created five FHIR resources that are persisted in your FHIR service.
 
-:::image type="content" source="media\iot-hub-to-iot-connector\iot-metrics-tile-one.png" alt-text="Screenshot that shows a MedTech service metrics tile and test data metrics." lightbox="media\iot-hub-to-iot-connector\iot-metrics-tile-one.png":::
+:::image type="content" source="media\device-data-through-iot-hub\metrics-tile-one.png" alt-text="Screenshot that shows a MedTech service metrics tile and test data metrics." lightbox="media\device-data-through-iot-hub\metrics-tile-one.png":::
 
-:::image type="content" source="media\iot-hub-to-iot-connector\iot-metrics-tile-two.png" alt-text="Screenshot that shows a second MedTech service metrics tile and test data metrics." lightbox="media\iot-hub-to-iot-connector\iot-metrics-tile-two.png":::
+:::image type="content" source="media\device-data-through-iot-hub\metrics-tile-two.png" alt-text="Screenshot that shows a second MedTech service metrics tile and test data metrics." lightbox="media\device-data-through-iot-hub\metrics-tile-two.png":::
 
 ## View test data in the FHIR service