Skip to content

Commit e2f1fbc

Browse files
authored
Merge pull request #224327 from msjasteppe/minor-updates
Minor updates
2 parents 7dc4b84 + fe8077a commit e2f1fbc

17 files changed

+32
-28
lines changed

.openpublishing.redirection.healthcare-apis.json

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -489,37 +489,37 @@
489489
},
490490
{
491491
"source_path_from_root": "/articles/healthcare-apis/azure-api-for-fhir/iot-azure-resource-manager-template-quickstart.md",
492-
"redirect_url": "/azure/healthcare-apis/iot/iot-connector-overview",
492+
"redirect_url": "/azure/healthcare-apis/iot/overview",
493493
"redirect_document_id": false
494494
},
495495
{
496496
"source_path_from_root": "/articles/healthcare-apis/azure-api-for-fhir/iot-data-flow.md",
497-
"redirect_url": "/azure/healthcare-apis/iot/iot-connector-overview",
497+
"redirect_url": "/azure/healthcare-apis/iot/overview",
498498
"redirect_document_id": false
499499
},
500500
{
501501
"source_path_from_root": "/articles/healthcare-apis/azure-api-for-fhir/iot-fhir-portal-quickstart.md",
502-
"redirect_url": "/azure/healthcare-apis/iot/iot-connector-overview",
502+
"redirect_url": "/azure/healthcare-apis/iot/overview",
503503
"redirect_document_id": false
504504
},
505505
{
506506
"source_path_from_root": "/articles/healthcare-apis/azure-api-for-fhir/iot-mapping-templates.md",
507-
"redirect_url": "/azure/healthcare-apis/iot/iot-connector-overview",
507+
"redirect_url": "/azure/healthcare-apis/iot/overview",
508508
"redirect_document_id": false
509509
},
510510
{
511511
"source_path_from_root": "/articles/healthcare-apis/azure-api-for-fhir/iot-metrics-diagnostics-export.md",
512-
"redirect_url": "/azure/healthcare-apis/iot/iot-connector-overview",
512+
"redirect_url": "/azure/healthcare-apis/iot/overview",
513513
"redirect_document_id": false
514514
},
515515
{
516516
"source_path_from_root": "/articles/healthcare-apis/azure-api-for-fhir/iot-metrics-display.md",
517-
"redirect_url": "/azure/healthcare-apis/iot/iot-connector-overview",
517+
"redirect_url": "/azure/healthcare-apis/iot/overview",
518518
"redirect_document_id": false
519519
},
520520
{
521521
"source_path_from_root": "/articles/healthcare-apis/azure-api-for-fhir/iot-troubleshoot-guide.md",
522-
"redirect_url": "/azure/healthcare-apis/iot/iot-connector-overview",
522+
"redirect_url": "/azure/healthcare-apis/iot/overview",
523523
"redirect_document_id": false
524524
},
525525
{
@@ -645,6 +645,10 @@
645645
"redirect_url": "/azure/healthcare-apis/iot/troubleshoot-errors",
646646
"redirect_document_id": false
647647
},
648+
{ "source_path_from_root": "/articles/healthcare-apis/iot/device-data-through-iot-hub.md",
649+
"redirect_url": "/azure/healthcare-apis/iot/device-messages-through-iot-hub",
650+
"redirect_document_id": false
651+
},
648652
{ "source_path_from_root": "/articles/healthcare-apis/events/events-display-metrics.md",
649653
"redirect_url": "/azure/healthcare-apis/events/events-use-metrics",
650654
"redirect_document_id": false

articles/healthcare-apis/iot/deploy-new-choose.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: msjasteppe
55
ms.service: healthcare-apis
66
ms.subservice: fhir
77
ms.topic: quickstart
8-
ms.date: 1/10/2023
8+
ms.date: 1/18/2023
99
ms.author: jasteppe
1010
---
1111

@@ -27,7 +27,7 @@ In this quickstart, you'll learn about these deployment methods:
2727

2828
[![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.healthcareapis%2Fworkspaces%2Fiotconnectors-with-iothub%2Fazuredeploy.json)
2929

30-
To learn more about deploying the MedTech service including an Azure IoT Hub using an ARM template and the **Deploy to Azure** button, see [Receive device messages through Azure IoT Hub](device-data-through-iot-hub.md).
30+
To learn more about deploying the MedTech service including an Azure IoT Hub using an ARM template and the **Deploy to Azure** button, see [Receive device messages through Azure IoT Hub](device-messages-through-iot-hub.md).
3131

3232
## ARM template using the Deploy to Azure button
3333

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

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,15 @@ author: msjasteppe
66
ms.service: healthcare-apis
77
ms.subservice: iomt
88
ms.topic: tutorial
9-
ms.date: 12/27/2022
9+
ms.date: 1/18/2023
1010
ms.author: jasteppe
1111
---
1212

1313
# Tutorial: Receive device messages through Azure IoT Hub
1414

1515
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.
1616

17-
:::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":::
17+
:::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]
2020
> 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).
@@ -82,23 +82,23 @@ To begin deployment in the Azure portal, select the **Deploy to Azure** button:
8282

8383
- **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.
8484

85-
:::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":::
85+
:::image type="content" source="media\device-messages-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-messages-through-iot-hub\deploy-template-options.png":::
8686

8787
2. To validate your configuration, select **Review + create**.
8888

89-
:::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.":::
89+
:::image type="content" source="media\device-messages-through-iot-hub\review-and-create-button.png" alt-text="Screenshot that shows the Review + create button selected in the Azure portal.":::
9090

9191
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.
9292

93-
:::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.":::
93+
:::image type="content" source="media\device-messages-through-iot-hub\validation-complete.png" alt-text="Screenshot that shows the Review + create pane displaying the Validation Passed message.":::
9494

9595
4. After a successful validation, to begin the deployment, select **Create**.
9696

97-
:::image type="content" source="media\device-data-through-iot-hub\create-button.png" alt-text="Screenshot that shows the highlighted Create button.":::
97+
:::image type="content" source="media\device-messages-through-iot-hub\create-button.png" alt-text="Screenshot that shows the highlighted Create button.":::
9898

9999
5. In a few minutes, the Azure portal displays the message that your deployment is completed.
100100

101-
:::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.":::
101+
:::image type="content" source="media\device-messages-through-iot-hub\deployment-complete-banner.png" alt-text="Screenshot that shows a green checkmark and the message Your deployment is complete.":::
102102

103103
> [!IMPORTANT]
104104
> 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.
@@ -156,22 +156,22 @@ You complete the steps by using Visual Studio Code with the Azure IoT Hub extens
156156

157157
2. In Explorer, in **Azure IoT Hub**, select **** and choose **Select IoT Hub**.
158158

159-
:::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":::
159+
:::image type="content" source="media\device-messages-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-messages-through-iot-hub\select-iot-hub.png":::
160160

161161
3. Select the Azure subscription where your IoT hub was provisioned.
162162

163163
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*.
164164

165165
5. In Explorer, in **Azure IoT Hub**, select **** and choose **Create Device**. An example device name is *iot-001*.
166166

167-
:::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":::
167+
:::image type="content" source="media\device-messages-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-messages-through-iot-hub\create-device.png":::
168168

169169
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**.
170170

171171
> [!NOTE]
172172
> 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**.
173173
174-
:::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":::
174+
:::image type="content" source="media\device-messages-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-messages-through-iot-hub\select-device-to-cloud-message.png":::
175175

176176
7. In **Send D2C Messages**, select or enter the following values:
177177

@@ -203,7 +203,7 @@ You complete the steps by using Visual Studio Code with the Azure IoT Hub extens
203203

204204
8. To begin the process of sending a test message to your IoT hub, select **Send**.
205205

206-
:::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":::
206+
:::image type="content" source="media\device-messages-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-messages-through-iot-hub\select-device-to-cloud-message-options.png":::
207207

208208
After you select **Send**, it might take up to five minutes for the FHIR resources to be available in the FHIR service.
209209

@@ -221,9 +221,9 @@ For your MedTech service metrics, you can see that your MedTech service complete
221221
- **Number of Measurements**: Created five measurements.
222222
- **Number of FHIR resources**: Created five FHIR resources that are persisted in your FHIR service.
223223

224-
:::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":::
224+
:::image type="content" source="media\device-messages-through-iot-hub\metrics-tile-one.png" alt-text="Screenshot that shows a MedTech service metrics tile and test data metrics." lightbox="media\device-messages-through-iot-hub\metrics-tile-one.png":::
225225

226-
:::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":::
226+
:::image type="content" source="media\device-messages-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-messages-through-iot-hub\metrics-tile-two.png":::
227227

228228
## View test data in the FHIR service
229229

@@ -240,4 +240,4 @@ To learn about other methods for deploying the MedTech service, see
240240
> [!div class="nextstepaction"]
241241
> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
242242

243-
FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
243+
FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.

articles/healthcare-apis/iot/index.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ metadata:
1313
ms.collection: collection
1414
author: msjasteppe
1515
ms.author: jasteppe
16-
ms.date: 1/5/2023
16+
ms.date: 1/18/2023
1717

1818
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
1919

@@ -53,8 +53,8 @@ landingContent:
5353
linkLists:
5454
- linkListType: tutorial
5555
links:
56-
- text: Receive device data through Azure IoT Hub
57-
url: device-data-through-iot-hub.md
56+
- text: Receive device messages through Azure IoT Hub
57+
url: device-messages-through-iot-hub.md
5858

5959
- title: Configure the MedTech service mappings
6060
linkLists:

0 commit comments

Comments
 (0)