Skip to content

Commit eea6998

Browse files
authored
Merge pull request #223077 from msjasteppe/media-folder-rename
Renaming media folder and necessary article edits
2 parents 3202a23 + c2899bb commit eea6998

File tree

7 files changed

+8
-8
lines changed

7 files changed

+8
-8
lines changed

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

Lines changed: 6 additions & 6 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: 12/27/2022
8+
ms.date: 1/5/2023
99
ms.author: jasteppe
1010
---
1111

@@ -63,23 +63,23 @@ To begin deployment in the Azure portal, select the **Deploy to Azure** button:
6363

6464
- **Destination Mapping** - Don't change the default values for this quickstart.
6565

66-
:::image type="content" source="media\deploy-new-button\iot-deploy-quickstart-options.png" alt-text="Screenshot of Azure portal page displaying deployment options for the Azure Health Data Service MedTech service." lightbox="media\deploy-new-button\iot-deploy-quickstart-options.png":::
66+
:::image type="content" source="media\deploy-new-arm\iot-deploy-quickstart-options.png" alt-text="Screenshot of Azure portal page displaying deployment options for the Azure Health Data Service MedTech service." lightbox="media\deploy-new-arm\iot-deploy-quickstart-options.png":::
6767

6868
2. To validate your configuration, select **Review + create**.
6969

70-
:::image type="content" source="media\deploy-new-button\iot-review-and-create-button.png" alt-text="Screenshot that shows the Review + create button selected in the Azure portal.":::
70+
:::image type="content" source="media\deploy-new-arm\iot-review-and-create-button.png" alt-text="Screenshot that shows the Review + create button selected in the Azure portal.":::
7171

7272
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.
7373

74-
:::image type="content" source="media\deploy-new-button\iot-validation-completed.png" alt-text="Screenshot that shows the Review + create pane displaying the Validation Passed message.":::
74+
:::image type="content" source="media\deploy-new-arm\iot-validation-completed.png" alt-text="Screenshot that shows the Review + create pane displaying the Validation Passed message.":::
7575

7676
4. After a successful validation, to begin the deployment, select **Create**.
7777

78-
:::image type="content" source="media\deploy-new-button\iot-create-button.png" alt-text="Screenshot that shows the highlighted Create button.":::
78+
:::image type="content" source="media\deploy-new-arm\iot-create-button.png" alt-text="Screenshot that shows the highlighted Create button.":::
7979

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

82-
:::image type="content" source="media\deploy-new-button\iot-deployment-complete-banner.png" alt-text="Screenshot that shows a green checkmark and the message Your deployment is complete.":::
82+
:::image type="content" source="media\deploy-new-arm\iot-deployment-complete-banner.png" alt-text="Screenshot that shows a green checkmark and the message Your deployment is complete.":::
8383

8484
> [!IMPORTANT]
8585
> 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.

articles/healthcare-apis/workspace-overview.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: overview
8-
ms.date: 1/3/2023
8+
ms.date: 1/5/2023
99
ms.author: jasteppe
1010
---
1111

@@ -50,7 +50,7 @@ Deploy a DICOM service to bring medical imaging data into the cloud from any DIC
5050

5151
## MedTech service
5252

53-
The MedTech service enables you to ingest high-frequency IoT device data into the FHIR Service in a scalable, secure, and compliant manner. For more information, see [Overview of the MedTech service](../healthcare-apis/iot/overview.md).
53+
The MedTech service enables you to ingest high-frequency IoT device data into the FHIR service in a scalable, secure, and compliant manner. For more information, see [Overview of the MedTech service](../healthcare-apis/iot/overview.md).
5454

5555
## Workspace configuration settings
5656

0 commit comments

Comments
 (0)