Skip to content

Commit fe55a6e

Browse files
Merge pull request #225944 from msjasteppe/quick-edits
Minor edits
2 parents fa7736c + 2297ecc commit fe55a6e

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: msjasteppe
66
ms.service: healthcare-apis
77
ms.subservice: iomt
88
ms.topic: tutorial
9-
ms.date: 1/20/2023
9+
ms.date: 02/01/2023
1010
ms.author: jasteppe
1111
---
1212

@@ -17,7 +17,7 @@ For enhanced workflows and ease of use, you can use the MedTech service to recei
1717
:::image type="content" source="media\device-messages-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-messages-through-iot-hub\data-flow-diagram.png":::
1818

1919
> [!TIP]
20-
> To learn more about how the MedTech service transforms and persists device message data into the Fast Healthcare Interoperability Resources (FHIR®) service as FHIR Observations, see [Understand the MedTech service device message data transformation](understand-service.md).
20+
> To learn how the MedTech service transforms and persists device message data into the Fast Healthcare Interoperability Resources (FHIR®) service as FHIR Observation resource, see [Understand the MedTech service device message data transformation](understand-service.md).
2121
2222

2323
In this tutorial, you learn how to:
@@ -30,7 +30,7 @@ In this tutorial, you learn how to:
3030
> - Review metrics for the test message.
3131
3232
> [!TIP]
33-
> To learn more about ARM templates, see [What are ARM templates?](./../../azure-resource-manager/templates/overview.md)
33+
> To learn about ARM templates, see [What are ARM templates?](./../../azure-resource-manager/templates/overview.md)
3434
3535
## Prerequisites
3636

@@ -40,7 +40,7 @@ To begin your deployment and complete the tutorial, you must have the following
4040

4141
- Owner or Contributor and User Access Administrator role assignments in the Azure subscription. For more information, see [What is Azure role-based access control (Azure RBAC)?](../../role-based-access-control/overview.md)
4242

43-
- The Microsoft.HealthcareApis, Microsoft.EventHub, and Microsoft.Devices resource providers registered with your Azure subscription. To learn more, see [Azure resource providers and types](../../azure-resource-manager/management/resource-providers-and-types.md).
43+
- The `Microsoft.HealthcareApis`, `Microsoft.EventHub`, and `Microsoft.Devices` resource providers registered with your Azure subscription. To learn more, see [Azure resource providers and types](../../azure-resource-manager/management/resource-providers-and-types.md).
4444

4545
- [Visual Studio Code](https://code.visualstudio.com/Download) installed locally.
4646

@@ -144,7 +144,7 @@ When deployment is completed, the following resources and access roles are creat
144144
145145
## Create a device and send a test message
146146

147-
With your resources successfully deployed, next, you connect to your IoT hub, create a device, and send a test message to the IoT hub. After you complete these steps, your MedTech service can:
147+
With your resources successfully deployed, you next connect to your IoT hub, create a device, and send a test message to the IoT hub. After you complete these steps, your MedTech service can:
148148

149149
- Pick up the IoT hub-routed test message from the device message event hub.
150150
- Transform the test message into five FHIR observations.

0 commit comments

Comments
 (0)