You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/iot/device-data-through-iot-hub.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ In order to begin the deployment and complete this tutorial, you'll need to have
35
35
36
36
When you've fulfilled these prerequisites, you're ready to use the **Deploy to Azure** button.
37
37
38
-
## Deploy to Azure button
38
+
## Use the Deploy to Azure button
39
39
40
40
1. Select the **Deploy to Azure** button below to begin the deployment within the Azure portal.
41
41
@@ -172,16 +172,16 @@ Now that your deployment has successfully completed, we'll connect to your IoT H
172
172
>
173
173
> 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).
174
174
175
-
## Review test message metrics
175
+
## Review test message MedTech service metrics
176
176
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).
178
178
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:
180
180
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.
185
185
186
186
:::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":::
0 commit comments