Merge pull request #219959 from msjasteppe/fixing-file-names

Fixing file names/index/toc

Author: v-stsavell

.openpublishing.redirection.healthcare-apis.json

@@ -554,10 +554,34 @@
         "redirect_url": "/azure/healthcare-apis/iot/how-to-use-iot-jsonpath-content-mappings",
         "redirect_document_id": false
     },
+    {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-iot-connector-in-azure.md",
+        "redirect_url": "/azure/healthcare-apis/iot/deploy-new-choose",
+        "redirect_document_id": false
+    },
+    {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-02-new-button.md",
+        "redirect_url": "/azure/healthcare-apis/iot/deploy-new-button",
+        "redirect_document_id": false
+    },
+    {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-03-new-manual.md",
+        "redirect_url": "/azure/healthcare-apis/iot/deploy-new-manual",
+        "redirect_document_id": false
+    },
+    {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-05-new-config.md",
+        "redirect_url": "/azure/healthcare-apis/iot/deploy-new-config",
+        "redirect_document_id": false
+    },
+    {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-06-new-deploy.md",
+        "redirect_url": "/azure/healthcare-apis/iot/deploy-new-deploy",
+        "redirect_document_id": false
+    },
     {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-08-new-ps-cli.md",
         "redirect_url": "/azure/healthcare-apis/iot/deploy-new-powershell-cli",
         "redirect_document_id": false
     },
+    {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-bicep-ps-cli.md",
+        "redirect_url": "/azure/healthcare-apis/iot/deploy-new-bicep-powershell-cli",
+        "redirect_document_id": false
+    }, 
     {   "source_path_from_root": "/articles/healthcare-apis/events/events-display-metrics.md",
         "redirect_url": "/azure/healthcare-apis/events/events-use-metrics",
         "redirect_document_id": false

articles/healthcare-apis/iot/deploy-new-bicep-ps-cli.md renamed to articles/healthcare-apis/iot/deploy-new-bicep-powershell-cli.md

@@ -193,12 +193,12 @@ For example: `az group delete --resource-group BicepTestDeployment`
 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 more about other methods of deploying the MedTech service, see
 
 > [!div class="nextstepaction"]
-> [Choose a deployment method for the MedTech service](deploy-iot-connector-in-azure.md)
+> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
 
 > [!div class="nextstepaction"]
-> [Deploy the MedTech service using an Azure Resource Manager template](deploy-02-new-button.md)
+> [Deploy the MedTech service using an Azure Resource Manager template](deploy-new-button.md)
 
 > [!div class="nextstepaction"]
-> [Deploy the MedTech service manually using the Azure portal](deploy-03-new-manual.md)
+> [Deploy the MedTech service manually using the Azure portal](deploy-new-manual.md)
 
 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/deploy-02-new-button.md renamed to articles/healthcare-apis/iot/deploy-new-button.md

@@ -17,7 +17,7 @@ For more information about ARM templates, see [What are ARM templates?](../../az
 
 The ARM template used in this article is available from the [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/iotconnectors/) site using the *azuredeploy.json* file located on [GitHub](https://github.com/azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors/).
 
-If you need to see a diagram with information on the MedTech service deployment, there's an architecture overview at [Choose a deployment method](deploy-iot-connector-in-azure.md#deployment-architecture-overview). This diagram shows the data flow steps of deployment and how MedTech service processes data into a Fast Healthcare Interoperability Resources (FHIR®) Observation.
+If you need to see a diagram with information on the MedTech service deployment, there's an architecture overview at [Choose a deployment method](deploy-new-choose.md#deployment-architecture-overview). This diagram shows the data flow steps of deployment and how MedTech service processes data into a Fast Healthcare Interoperability Resources (FHIR®) Observation.
 
 There are four simple tasks you need to complete in order to deploy MedTech service with the ARM template **Deploy to Azure** button. They are:
 
@@ -105,12 +105,12 @@ Now that the MedTech service is successfully deployed, there are three post-depl
 In this article, you learned how to deploy the MedTech service in the Azure portal using an ARM template with a **Deploy to Azure** button. To learn more about other methods of deployment, see
 
 > [!div class="nextstepaction"]
-> [Choose a deployment method for the MedTech service](deploy-iot-connector-in-azure.md)
+> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
 
 > [!div class="nextstepaction"]
 > [Deploy the MedTech service using an ARM template and Azure PowerShell or the Azure CLI](deploy-new-powershell-cli.md)
 
 > [!div class="nextstepaction"]
-> [Deploy the MedTech service manually using Azure portal](deploy-03-new-manual.md)
+> [Deploy the MedTech service manually using Azure portal](deploy-new-manual.md)
 
 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/deploy-iot-connector-in-azure.md renamed to articles/healthcare-apis/iot/deploy-new-choose.md

@@ -23,7 +23,7 @@ The different deployment methods are:
 
 Using an ARM template with Azure portal is the easiest and fastest deployment method because it automates most of your configuration with the touch of a **Deploy to Azure** button. This button automatically generates the following configurations and resources: managed identity Azure role-based access (RBAC) roles, a provisioned workspace and namespace, an Event Hubs instance, a Fast Healthcare Interoperability Resources (FHIR®) service instance, and a MedTech service instance. All you need to add are post-deployment device mapping, destination mapping, and a shared access policy key. This method simplifies your deployment, but doesn't allow for much customization.
 
-For more information about the ARM template and the Deploy to Azure button, see [Deploy the MedTech service using an Azure Resource Manager template](deploy-02-new-button.md).
+For more information about the ARM template and the Deploy to Azure button, see [Deploy the MedTech service using an Azure Resource Manager template](deploy-new-button.md).
 
 ## Azure PowerShell and Azure CLI automation
 
@@ -35,7 +35,7 @@ For more information about Using an ARM template with Azure PowerShell or Azure
 
 The manual deployment method uses the Azure portal to implement each deployment task individually. Using the manual deployment method will allow you to see all the details of how to complete the sequence of each deployment task. The manual deployment method can be beneficial if you need to customize or troubleshoot your deployment process. The manual deployment is the most complex method, but it provides valuable technical information and developmental options that will enable you to fine-tune your deployment precisely.
 
-For more information about manual deployment with Azure portal, see [Deploy the MedTech service manually using the Azure portal](deploy-03-new-manual.md).
+For more information about manual deployment with Azure portal, see [Deploy the MedTech service manually using the Azure portal](deploy-new-manual.md).
 
 ## Deployment architecture overview
 
@@ -79,11 +79,11 @@ Each method must add **all** these post-deployment tasks:
 
 ### Granting access to the device message event hub
 
-For information about granting access to the device message event hub, see [Granting access to the device message event hub](deploy-06-new-deploy.md#grant-access-to-the-device-message-event-hub).
+For information about granting access to the device message event hub, see [Granting access to the device message event hub](deploy-new-deploy.md#grant-access-to-the-device-message-event-hub).
 
 ### Granting access to the FHIR service
 
-For information about granting access to the FHIR service, see [Granting access to the FHIR service](deploy-06-new-deploy.md#grant-access-to-the-fhir-service).
+For information about granting access to the FHIR service, see [Granting access to the FHIR service](deploy-new-deploy.md#grant-access-to-the-fhir-service).
 
 ## Next steps
 

articles/healthcare-apis/iot/deploy-05-new-config.md renamed to articles/healthcare-apis/iot/deploy-new-config.md

@@ -17,7 +17,7 @@ Before you can manually deploy the MedTech service, you must complete the follow
 
 Start with these three steps to begin configuring the MedTech service so it will be ready to accept your tabbed configuration input:
 
-1. Start by going to the Health Data Services workspace you created in the manual deployment [Prerequisites](deploy-03-new-manual.md#part-1-prerequisites) section. Select the **Create MedTech service** box.
+1. Start by going to the Health Data Services workspace you created in the manual deployment [Prerequisites](deploy-new-manual.md#part-1-prerequisites) section. Select the **Create MedTech service** box.
 
 2. This step will take you to the **Add MedTech service** button. Select the button.
 
@@ -112,7 +112,7 @@ Under the **Destination** tab, use these values to enter the destination propert
 - First, enter the name of your **Fast Healthcare Interoperability Resources (FHIR®) server** using the following four steps:
 
   1. The **FHIR Server** name (also known as the **FHIR service**) can be located by using the **Search** bar at the top of the screen. 
-  1. To connect to your FHIR service instance, enter the name of the FHIR service you used in the manual deploy configuration article at [Deploy the FHIR service](deploy-03-new-manual.md#deploy-the-fhir-service).
+  1. To connect to your FHIR service instance, enter the name of the FHIR service you used in the manual deploy configuration article at [Deploy the FHIR service](deploy-new-manual.md#deploy-the-fhir-service).
   1. Then select the **Properties** button. 
   1. Next, Copy and paste the **Name** string into the **FHIR Server** text field. In this example, the **FHIR Server** name is `fs-azuredocsdemo`.
 
@@ -196,6 +196,6 @@ After your configuration is successfully completed, you can go on to Part 3: Dep
 When you're ready to begin Part 3 of Manual Deployment, see
 
 > [!div class="nextstepaction"]
-> [Part 3: Manual deployment and post-deployment of MedTech service](deploy-06-new-deploy.md)
+> [Part 3: Manual deployment and post-deployment of MedTech service](deploy-new-deploy.md)
 
 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/deploy-06-new-deploy.md renamed to articles/healthcare-apis/iot/deploy-new-deploy.md

@@ -97,10 +97,10 @@ Now that you have granted access to the device message event hub and the FHIR se
 In this article, you learned how to perform the manual deployment and post-deployment steps to implement your MedTech service. To learn more about other methods of deployment, see
 
 > [!div class="nextstepaction"]
-> [Choosing a method of deployment for MedTech service in Azure](deploy-iot-connector-in-azure.md)
+> [Choosing a method of deployment for MedTech service in Azure](deploy-new-choose.md)
 
 > [!div class="nextstepaction"]
-> [Deploy the MedTech service with an Azure Resource Manager template](deploy-02-new-button.md)
+> [Deploy the MedTech service with an Azure Resource Manager template](deploy-new-button.md)
 
 > [!div class="nextstepaction"]
 > [Deploy the MedTech service using an Azure Resource Manager template and Azure PowerShell or the Azure CLI](deploy-new-powershell-cli.md)

articles/healthcare-apis/iot/deploy-03-new-manual.md renamed to articles/healthcare-apis/iot/deploy-new-manual.md

@@ -16,10 +16,10 @@ You may prefer to manually deploy MedTech service if you need to track every ste
 The explanation of MedTech service manual deployment using the Azure portal is divided into three parts that cover each of key tasks required:
 
 - Part 1: Prerequisites (see Prerequisites below)
-- Part 2: Configuration (see [Configure for manual deployment](deploy-05-new-config.md))
-- Part 3: Deployment and Post Deployment (see [Manual deployment and post-deployment](deploy-06-new-deploy.md))
+- Part 2: Configuration (see [Configure for manual deployment](deploy-new-config.md))
+- Part 3: Deployment and Post Deployment (see [Manual deployment and post-deployment](deploy-new-deploy.md))
 
-If you need a diagram with information on the MedTech service deployment, there's an architecture overview at [Choose a deployment method](deploy-iot-connector-in-azure.md#deployment-architecture-overview). This diagram shows the data flow steps of deployment and how MedTech service processes data into a Fast Healthcare Interoperability Resources (FHIR®) Observation.
+If you need a diagram with information on the MedTech service deployment, there's an architecture overview at [Choose a deployment method](deploy-new-choose.md#deployment-architecture-overview). This diagram shows the data flow steps of deployment and how MedTech service processes data into a Fast Healthcare Interoperability Resources (FHIR®) Observation.
 
 ## Part 1: Prerequisites
 
@@ -95,6 +95,6 @@ After your prerequisites are successfully completed, you can go on to Part 2: Co
 When you're ready to begin Part 2 of Manual Deployment, see
 
 > [!div class="nextstepaction"]
-> [Part 2: Configure the MedTech service for manual deployment using the Azure portal](deploy-05-new-config.md)
+> [Part 2: Configure the MedTech service for manual deployment using the Azure portal](deploy-new-config.md)
 
 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/deploy-new-powershell-cli.md

@@ -85,7 +85,7 @@ Complete the following five steps to deploy the MedTech service using Azure Powe
 
    For example: `New-AzResourceGroupDeployment -ResourceGroupName ArmTestDeployment -TemplateUri https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.healthcareapis/workspaces/iotconnectors/azuredeploy.json -basename abc123 -location southcentralus`
 
-## Deploy the MedTech service with the Azure Resource Manager template and Azure CLI
+## Deploy the MedTech service with the Azure Resource Manager template and the Azure CLI
 
 Complete the following five steps to deploy the MedTech service using the Azure CLI:
 

articles/healthcare-apis/iot/how-to-use-iot-jsonpath-content-mappings.md

@@ -1,11 +1,11 @@
 ---
-title: IotJsonPathContentTemplate mappings in MedTech service device mapping - Azure Health Data Services
-description: This article describes how to use IotJsonPathContentTemplate mappings with MedTech service device mapping. 
+title: How to use IotJsonPathContentTemplate mappings in the MedTech service device mapping - Azure Health Data Services
+description: This article describes how to use IotJsonPathContentTemplate mappings with the MedTech service device mapping. 
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 10/25/2022
+ms.date: 11/30/2022
 ms.author: jasteppe
 ---
 
@@ -272,6 +272,6 @@ With each of these examples, you're provided with:
 In this article, you learned how to use IotJsonPathContentTemplate mappings with the MedTech service device mapping. To learn how to use MedTech service FHIR destination mapping, see
 
 > [!div class="nextstepaction"]
-> [How to use the FHIR destination mapping](how-to-use-fhir-mappings.md)
+> [How to configure FHIR destination mappings](how-to-use-fhir-mappings.md)
 
-FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+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

@@ -13,7 +13,7 @@ metadata:
   ms.collection: collection
   author: msjasteppe
   ms.author: jasteppe
-  ms.date: 11/29/2022
+  ms.date: 11/20/2022
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 
@@ -37,17 +37,17 @@ landingContent:
       - linkListType: overview
         links:
           - text: Choose a deployment method
-            url: deploy-iot-connector-in-azure.md
+            url: deploy-new-choose.md
       - linkListType: quickstart
         links:     
           - text: Azure Resource Manager template
-            url: deploy-02-new-button.md
-          - text: Azure PowerShell or the Azure CLI
+            url: deploy-new-button.md
+          - text: Azure PowerShell or Azure CLI
             url: deploy-new-powershell-cli.md
           - text: Azure Bicep
-            url: deploy-new-bicep-ps-cli.md
+            url: deploy-new-bicep-powershell-cli.md
           - text: Azure portal
-            url: deploy-03-new-manual.md
+            url: deploy-new-manual.md
 
   - title: MedTech service with Azure IoT Hub 
     linkLists: