Merge pull request #244033 from msjasteppe/minor-updates

prmerger-automator[bot] · web-flow · commit 14761b621fd4 · 2023-07-06T00:20:57.000Z
Editing for standardization
diff --git a/articles/healthcare-apis/iot/deploy-arm-template.md b/articles/healthcare-apis/iot/deploy-arm-template.md
@@ -6,7 +6,7 @@ ms.service: healthcare-apis
 ms.subservice: fhir
 ms.custom: devx-track-arm-template
 ms.topic: quickstart
-ms.date: 05/16/2023
+ms.date: 07/05/2023
 ms.author: jasteppe
 ---
 
@@ -30,11 +30,11 @@ In this quickstart, learn how to:
 
 To begin your deployment and complete the quickstart, you must have the following prerequisites:
 
-- An active Azure subscription account. If you don't have an Azure subscription, see [Subscription decision guide](/azure/cloud-adoption-framework/decision-guides/subscriptions/).
+* An active Azure subscription account. If you don't have an Azure subscription, see [Subscription decision guide](/azure/cloud-adoption-framework/decision-guides/subscriptions/).
 
-- **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)
+* **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)
 
-- The Microsoft.HealthcareApis and Microsoft.EventHub resource providers registered with your Azure subscription. To learn more about registering resource providers, see [Azure resource providers and types](../../azure-resource-manager/management/resource-providers-and-types.md).
+* The Microsoft.HealthcareApis and Microsoft.EventHub resource providers registered with your Azure subscription. To learn more about registering resource providers, see [Azure resource providers and types](../../azure-resource-manager/management/resource-providers-and-types.md).
 
 When you have these prerequisites, you're ready to configure the ARM template by using the **Deploy to Azure** button.
 
@@ -124,17 +124,27 @@ When deployment is completed, the following resources and access roles are creat
 
 After you have successfully deployed an instance of the MedTech service, you'll still need to provide conforming and valid device and FHIR destination mappings.
 
- * To learn about the device mapping, see [Overview of the MedTech service device mapping](overview-of-device-mapping.md).
+* To learn about the device mapping, see [Overview of the MedTech service device mapping](overview-of-device-mapping.md).
 
- * To learn about the FHIR destination mapping, see [Overview of the MedTech service FHIR destination mapping](overview-of-fhir-destination-mapping.md).
+* To learn about the FHIR destination mapping, see [Overview of the MedTech service FHIR destination mapping](overview-of-fhir-destination-mapping.md).
 
 ## Next steps
 
 In this quickstart, you learned how to deploy the MedTech service in the Azure portal using an ARM template with the **Deploy to Azure** button. 
 
-To learn about other methods for deploying the MedTech service, see
+To learn about other methods of deploying the MedTech service, see
 
 > [!div class="nextstepaction"]
-> [Choose a deployment method for the MedTech service](deploy-choose-method.md)
+> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
+
+For an overview of the MedTech service device data processing stages, see
+
+> [!div class="nextstepaction"]
+> [Overview of the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
+
+For frequently asked questions (FAQs) about the MedTech service, see
+
+> [!div class="nextstepaction"]
+> [Frequently asked questions about the MedTech service](frequently-asked-questions.md)
 
 FHIR&#174; is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
diff --git a/articles/healthcare-apis/iot/deploy-bicep-powershell-cli.md b/articles/healthcare-apis/iot/deploy-bicep-powershell-cli.md
@@ -6,7 +6,7 @@ ms.service: healthcare-apis
 ms.subservice: fhir
 ms.custom: devx-track-bicep, devx-track-azurepowershell, devx-track-azurecli
 ms.topic: quickstart
-ms.date: 05/16/2023
+ms.date: 07/05/2023
 ms.author: jasteppe
 ---
 
@@ -165,7 +165,7 @@ Complete the following five steps to deploy the MedTech service using the Azure
 
 When deployment is completed, the following resources and access roles are created in the Bicep file deployment:
 
-* Azure Event Hubs namespace and device message event hub. In this deployment, the device message event hub is named *devicedata*.
+* Azure Event Hubs namespace and event hub. In this deployment, the event hub is named *devicedata*.
 
   * Event hub consumer group. In this deployment, the consumer group is named *$Default*.
 
@@ -219,11 +219,21 @@ For example: `az group delete --resource-group BicepTestDeployment`
 
 ## Next steps
 
-In this quickstart, you learned about how to use Azure PowerShell or the Azure CLI to deploy an instance of the MedTech service using a Bicep file. 
+In this quickstart, you learned how to use Azure PowerShell or the Azure CLI to deploy an instance of the MedTech service using a Bicep file. 
 
-To learn about other methods for deploying the MedTech service, see
+To learn about other methods of deploying the MedTech service, see
 
 > [!div class="nextstepaction"]
-> [Choose a deployment method for the MedTech service](deploy-choose-method.md)
+> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
+
+For an overview of the MedTech service device data processing stages, see
+
+> [!div class="nextstepaction"]
+> [Overview of the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
+
+For frequently asked questions (FAQs) about the MedTech service, see
+
+> [!div class="nextstepaction"]
+> [Frequently asked questions about the MedTech service](frequently-asked-questions.md)
 
 FHIR&#174; is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
diff --git a/articles/healthcare-apis/iot/deploy-choose-method.md b/articles/healthcare-apis/iot/deploy-choose-method.md
@@ -6,7 +6,7 @@ ms.service: healthcare-apis
 ms.subservice: fhir
 ms.custom: devx-track-azurecli, devx-track-azurepowershell, devx-track-arm-template, devx-track-bicep
 ms.topic: quickstart
-ms.date: 04/28/2023
+ms.date: 07/05/2023
 ms.author: jasteppe
 ---
 
@@ -20,10 +20,10 @@ The MedTech service provides multiple methods for deployment into Azure. Each de
 In this quickstart, learn about these deployment methods:
 
 * Azure Resource Manager template (ARM template) including an Azure Iot Hub using the **Deploy to Azure** button. 
-* ARM template using the **Deploy to Azure** button
-* ARM template using Azure PowerShell or the Azure CLI
-* Bicep file using Azure PowerShell or the Azure CLI
-* Azure portal 
+* ARM template using the **Deploy to Azure** button.
+* ARM template using Azure PowerShell or the Azure CLI.
+* Bicep file using Azure PowerShell or the Azure CLI.
+* Azure portal.
 
 ## Deployment overview
 
@@ -80,9 +80,19 @@ To learn more about deploying the MedTech service using the Azure portal, see [D
 
 In this quickstart, you learned about the different types of deployment methods for the MedTech service. 
 
-To learn about the MedTech service, see
+To learn about other methods of deploying the MedTech service, see
 
 > [!div class="nextstepaction"]
-> [What is the MedTech service?](overview.md)
+> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
+
+For an overview of the MedTech service device data processing stages, see
+
+> [!div class="nextstepaction"]
+> [Overview of the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
+
+For frequently asked questions (FAQs) about the MedTech service, see
+
+> [!div class="nextstepaction"]
+> [Frequently asked questions about the MedTech service](frequently-asked-questions.md)
 
 FHIR&#174; is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
diff --git a/articles/healthcare-apis/iot/deploy-json-powershell-cli.md b/articles/healthcare-apis/iot/deploy-json-powershell-cli.md
@@ -6,7 +6,7 @@ ms.service: healthcare-apis
 ms.subservice: fhir
 ms.custom: devx-track-arm-template, devx-track-azurepowershell, devx-track-azurecli
 ms.topic: quickstart
-ms.date: 05/16/2023
+ms.date: 07/05/2023
 ms.author: jasteppe
 ---
 
@@ -160,7 +160,7 @@ Complete the following five steps to deploy the MedTech service using the Azure
 
 When deployment is completed, the following resources and access roles are created in the ARM template deployment:
 
-* Azure Event Hubs namespace and device message event hub. In this deployment, the device message event hub is named *devicedata*.
+* Azure Event Hubs namespace and event hub. In this deployment, the event hub is named *devicedata*.
 
   * Event hub consumer group. In this deployment, the consumer group is named *$Default*.
 
@@ -216,9 +216,19 @@ For example: `az group delete --resource-group ArmTestDeployment`
 
 In this quickstart, you learned how to use Azure PowerShell or Azure CLI to deploy an instance of the MedTech service using an ARM template. 
 
-To learn about other methods for deploying the MedTech service, see
+To learn about other methods of deploying the MedTech service, see
 
 > [!div class="nextstepaction"]
-> [Choose a deployment method for the MedTech service](deploy-choose-method.md)
+> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
+
+For an overview of the MedTech service device data processing stages, see
+
+> [!div class="nextstepaction"]
+> [Overview of the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
+
+For frequently asked questions (FAQs) about the MedTech service, see
+
+> [!div class="nextstepaction"]
+> [Frequently asked questions about the MedTech service](frequently-asked-questions.md)
 
 FHIR&#174; is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
diff --git a/articles/healthcare-apis/iot/deploy-manual-portal.md b/articles/healthcare-apis/iot/deploy-manual-portal.md
@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 06/29/2023
+ms.date: 07/05/2023
 ms.author: jasteppe
 ---
 
@@ -14,12 +14,9 @@ ms.author: jasteppe
 > [!NOTE]
 > [Fast Healthcare Interoperability Resources (FHIR&#174;)](https://www.hl7.org/fhir/) is an open healthcare specification.
 
-You may prefer to deploy the MedTech service using the Azure portal if you:
+In this quickstart, learn how to deploy the MedTech service and required resources using the Azure portal.
 
-* Need to track every step of the provisioning process.
-* Want to customize or troubleshoot your deployment.
-
-In this quickstart, the MedTech service deployment using the Azure portal is divided into the following three sections:
+The MedTech service deployment using the Azure portal is divided into the following three sections:
 
 * [Deploy prerequisite resources](#deploy-prerequisite-resources)
 * [Configure and deploy the MedTech service](#configure-and-deploy-the-medtech-service)
@@ -36,14 +33,14 @@ As a prerequisite, you need an Azure subscription and have been granted the prop
 
 The first step is to deploy the MedTech service prerequisite resources:
 
-* Azure resource group.
-* Azure Event Hubs namespace and event hub.
-* Azure Health Data services workspace.
-* Azure Health Data Services FHIR service.
+* Azure resource group
+* Azure Event Hubs namespace and event hub
+* Azure Health Data services workspace
+* Azure Health Data Services FHIR service
 
 Once the prerequisite resources are available, deploy:
  
-* Azure Health Data Services MedTech service.
+* Azure Health Data Services MedTech service
 
 ### Deploy a resource group 
 
@@ -93,11 +90,11 @@ Follow these four steps to fill in the **Basics** tab configuration:
 
 2. Select the **Event Hubs Namespace**.
 
-   The **Event Hubs Namespace** is the name of the *Event Hubs namespace* that you previously deployed. For this example, we're using *eh-azuredocsdemo* for our MedTech service device messages.
+   The **Event Hubs Namespace** is the name of the *Event Hubs namespace* that you previously deployed. For this example, we're using the name *eh-azuredocsdemo*.
 
 3. Select the **Events Hubs name**.
 
-   The **Event Hubs name** is the name of the event hub that you previously deployed within the Event Hubs Namespace. For this example, we're using *devicedata* for our MedTech service device messages.  
+   The **Event Hubs name** is the name of the event hub that you previously deployed within the Event Hubs Namespace. For this example, we're using the name *devicedata*.  
 
 4. Select the **Consumer group**.
 
@@ -130,7 +127,7 @@ Under the **Destination** tab, use these values to enter the destination propert
 
 * Next, enter the **Destination name**.
 
-  The **Destination name** is a friendly name for the destination. Enter a unique name for your destination. In this example, the **Destination name** is
+  The **Destination name** is a friendly name for the destination. Enter a unique name for your destination. In this example, the **Destination name** name is
   *fs-azuredocsdemo*.
 
 * Next, select the **Resolution type**.
@@ -213,7 +210,7 @@ Valid and conforming device and FHIR destination mappings have to be provided to
 
 ## Next steps
 
-This article described the deployment steps needed to get started using the MedTech service. 
+In this article, you learned how to deploy the MedTech service and required resources using the Azure portal.  
 
 To learn about other methods of deploying the MedTech service, see
 
diff --git a/articles/healthcare-apis/iot/device-messages-through-iot-hub.md b/articles/healthcare-apis/iot/device-messages-through-iot-hub.md
@@ -6,7 +6,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: iomt
 ms.topic: tutorial
-ms.date: 06/19/2023
+ms.date: 07/05/2023
 ms.custom: devx-track-arm-template
 ms.author: jasteppe
 ---
@@ -246,9 +246,19 @@ To learn how to get an Azure AD access token and view FHIR resources in your FHI
 
 In this tutorial, you deployed an ARM template in the Azure portal, connected to your IoT hub, created a device, sent a test message, and reviewed your MedTech service metrics.
 
-To learn about other methods for deploying the MedTech service, see
+To learn about other methods of deploying the MedTech service, see
 
-> [!div class="nextstepaction"] 
-> [Choose a deployment method for the MedTech service](deploy-choose-method.md)
+> [!div class="nextstepaction"]
+> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
+
+For an overview of the MedTech service device data processing stages, see
+
+> [!div class="nextstepaction"]
+> [Overview of the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
+
+For frequently asked questions (FAQs) about the MedTech service, see
+
+> [!div class="nextstepaction"]
+> [Frequently asked questions about the MedTech service](frequently-asked-questions.md)
 
 FHIR&#174; is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
