Skip to content

Commit e98e599

Browse files
committed
Minor edit.
1 parent af3f2af commit e98e599

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ In order to begin the deployment and complete this tutorial, you'll need to have
3535

3636
When you've fulfilled these prerequisites, you're ready to use the **Deploy to Azure** button.
3737

38-
## Deploy to Azure button
38+
## Use the Deploy to Azure button
3939

4040
1. Select the **Deploy to Azure** button below to begin the deployment within the Azure portal.
4141

@@ -172,16 +172,16 @@ Now that your deployment has successfully completed, we'll connect to your IoT H
172172
>
173173
> To learn more about IotJsonPathContentTemplate mappings usage with the MedTech service device mappings, see [How to use IotJsonPathContentTemplate mappings](how-to-use-iot-jsonpath-content-mappings.md).
174174
175-
## Review test message metrics
175+
## Review test message MedTech service metrics
176176

177-
Now that you've successfully sent a test message to your IoT Hub, you can now review your MedTech service metrics to verify that the MedTech service transformed and persisted the test message into your FHIR service. To learn more about how display and use the MedTech service metrics, see [How to use the MedTech service monitoring tab](how-to-use-monitoring-tab.md).
177+
Now that you've successfully sent a test message to your IoT Hub, you can now review your MedTech service metrics to verify that the MedTech service received,transformed, and persisted the test message into your FHIR service. To learn more about how display the MedTech service monitoring tab metrics and the different metrics types, see [How to display the MedTech service monitoring tab metrics](how-to-use-monitoring-tab.md).
178178

179-
For your MedTech service metrics, see can see that:
179+
For your MedTech service metrics, see can see that your MedTech service performed the following steps with the test message:
180180

181-
* **Number of Incoming Messages** - The test message was received.
182-
* **Number of Normalized Messages** - The test message had five normalized messages.
183-
* **Number of Measurements** - The test message had five measurements.
184-
* **Number of FHIR resources** - The test message created five FHIR resources that will be persisted on your FHIR service.
181+
* **Number of Incoming Messages** - Received the incoming test message from the device message event hub.
182+
* **Number of Normalized Messages** - Created five normalized messages.
183+
* **Number of Measurements** - Created five measurements.
184+
* **Number of FHIR resources** - Created five FHIR resources that will be persisted on your FHIR service.
185185

186186
:::image type="content" source="media\iot-hub-to-iot-connector\iot-metrics-tile-one.png" alt-text="Screenshot of MedTech service first metrics tile showing the test data metrics." lightbox="media\iot-hub-to-iot-connector\iot-metrics-tile-one.png":::
187187

0 commit comments

Comments
 (0)