Merge pull request #203029 from msjasteppe/iot-add-deploy

Adding Deploy to Azure button.

Author: v-stsavell

articles/healthcare-apis/get-started-with-health-data-services.md

@@ -37,7 +37,7 @@ After the Azure Health Data Services resource group is deployed, you can enter t
 
 To be guided through these steps, see [Deploy Azure Health Data Services workspace using Azure portal](healthcare-apis-quickstart.md).
 
-> [!Note] 
+> [!NOTE] 
 > You can provision multiple data services within a workspace, and by design, they work seamlessly with one another. With the workspace, you can organize all your Azure Health Data Services instances and manage certain configuration settings that are shared among all the underlying datasets and services where it's applicable. 
 
 [![Screenshot of the Azure Health Data Services workspace.](media/health-data-services-workspace.png)](media/health-data-services-workspace.png#lightbox)
@@ -88,13 +88,13 @@ For more information, see [Get started with the DICOM service](./../healthcare-a
 
 MedTech service transforms device data into FHIR-based observation resources and then persists the transformed messages into Azure Health Data Services FHIR service. This allows for a unified approach to health data access, standardization, and trend capture enabling the discovery of operational and clinical insights, connecting new device applications, and enabling new research projects. 
 
-To ensure that your MedTech service works properly, it must have granted access permissions to the Azure Event Hub and FHIR service. The Azure Event Hubs Data Receiver role allows the MedTech service that's being assigned this role to receive data from this Event Hub. For more information about application roles, see [Authentication & Authorization for Azure Health Data Services](./../healthcare-apis/authentication-authorization.md)
+To ensure that your MedTech service works properly, it must have granted access permissions to the Azure Event Hubs and FHIR service. The Azure Event Hubs Data Receiver role allows the MedTech service that's being assigned this role to receive data from this event hub. For more information about application roles, see [Authentication & Authorization for Azure Health Data Services](./../healthcare-apis/authentication-authorization.md)
 
 You can also do the following:
 - Create a new FHIR service or use an existing one in the same or different workspace 
-- Create a new Event Hub or use an existing one 
-- Assign roles to allow the MedTech service to access [Event Hub](./../healthcare-apis/iot/deploy-iot-connector-in-azure.md#granting-medtech-service-access) and [FHIR service](./../healthcare-apis/iot/deploy-iot-connector-in-azure.md#accessing-the-medtech-service-from-the-fhir-service)
-- Send data to the Event Hub, which is associated with the MedTech service 
+- Create a new event hub or use an existing one 
+- Assign roles to allow the MedTech service to access [Event Hubs](./../healthcare-apis/iot/deploy-iot-connector-in-azure.md#granting-the-medtech-service-access) and [FHIR service](./../healthcare-apis/iot/deploy-iot-connector-in-azure.md#accessing-the-medtech-service-from-the-fhir-service)
+- Send data to the event hub, which is associated with the MedTech service 
 
 For more information, see [Get started with the MedTech service](./../healthcare-apis/iot/get-started-with-iot.md).
 
@@ -112,4 +112,3 @@ This article described the basic steps to get started using Azure Health Data Se
 >[Frequently asked questions about Azure Health Data Services](healthcare-apis-faqs.md)
 
 FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
-

articles/healthcare-apis/iot/deploy-iot-connector-in-azure.md

@@ -5,12 +5,12 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 04/07/2022
+ms.date: 06/28/2022
 ms.author: jasteppe
 ms.custom: mode-api
 ---
 
-# Deploy MedTech service in the Azure portal
+# Deploy the MedTech service in the Azure portal
 
 In this quickstart, you'll learn how to deploy MedTech service in the Azure portal. The MedTech service will enable you to ingest data from Internet of Things (IoT) into your Fast Healthcare Interoperability Resources (FHIR®) service.
 
@@ -33,7 +33,38 @@ It's important that you have the following prerequisites completed before you be
 >* Two MedTech services accessing the same device message event hub.
 >* A MedTech service and a storage writer application accessing the same device message event hub.
 
-## Deploy MedTech service 
+If you already have an active Azure account, you can use the ![Deploy to Azure](https://aka.ms/deploytoazurebutton) button below to deploy a MedTech service that will include the following resources and permissions:
+ * An Azure Event Hubs Namespace and device message event hub (the event hub is named: **devicedata**).
+ * An Azure event hub sender role (the sender role is named: **devicedatasender**).
+ * An Azure Health Data Services workspace.
+ * An Azure Health Data Services FHIR service.
+ * An Azure Health Data Services MedTech service including the necessary system managed identity permissions to the device message event hub and FHIR service.
+
+When the Azure portal launches, the following fields must be filled out:
+ * **Subscription** - Chose the Azure subscription you would like to use for the deployment.
+ * **Resource Group** - Chose an existing Resource Group or create a new Resource Group.
+ * **Region** - The Azure region of the Resource Group used for the deployment. This field will auto-fill based on the Resource Group region.
+ * **Basename** - Will be used to append the name the Azure services to be deployed.
+ * **Location** - Use the drop-down list to select a supported Azure region for the Azure Health Data Services (could be the same or different region than your Resource Group). 
+
+Leave the **Device Mapping** and **Destination Mapping** fields with their default values.
+
+Select the **Review + create** button once the fields are filled out.
+
+:::image type="content" source="media\iot-deploy-arm-in-portal\iot-connector-arm-deploy-options.png" alt-text="Azure portal page displaying deployment options for the Azure Health Data Service MedTech service." lightbox="media\iot-deploy-arm-in-portal\iot-connector-arm-deploy-options.png"::: 
+
+After the validation has passed, select the **Create** button to begin the deployment.
+
+:::image type="content" source="media\iot-deploy-arm-in-portal\iot-connector-arm-deploy-create.png" alt-text="Azure portal page displaying validation box and Create button for the Azure Health Data Service MedTech service." lightbox="media\iot-deploy-arm-in-portal\iot-connector-arm-deploy-create.png"::: 
+
+After a successful deployment, there will be remaining configurations that will need to be completed by you for a fully functional MedTech service:
+ * Provide a working device mapping file. For more information, see [How to use device mappings](how-to-use-device-mappings.md).
+ * Provide a working destination mapping file. For more information, see [How to use FHIR destination mappings](how-to-use-fhir-mappings.md).
+ * Use the Shared access policies (SAS) key (**devicedatasender**) for connecting your device or application to the MedTech service device message event hub (**devicedata**). For more information, see [Connection string for a specific event hub in a namespace](../../event-hubs/event-hubs-get-connection-string.md#connection-string-for-a-specific-event-hub-in-a-namespace).
+
+[![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%2Fazuredeploy.json) 
+
+## Deploy the MedTech service 
 
 1. Sign in the [Azure portal](https://portal.azure.com), and then enter your Health Data Services workspace resource name in the **Search** bar field.
 
@@ -47,7 +78,7 @@ It's important that you have the following prerequisites completed before you be
 
    ![Screenshot of add MedTech services.](media/add-iot-connector.png#lightbox)
 
-## Configure MedTech service to ingest data
+## Configure the MedTech service to ingest data
 
 Under the **Basics** tab, complete the required fields under **Instance details**.
 
@@ -81,7 +112,7 @@ Under the **Basics** tab, complete the required fields under **Instance details*
 
 5. Select **Next: Device mapping**. 
 
-## Configure Device mapping properties
+## Configure the Device mapping properties
 
 > [!TIP]
 > The IoMT Connector Data Mapper is an open source tool to visualize the mapping configuration for normalizing a device's input data, and then transform it to FHIR resources. Developers can use this tool to edit and test Devices and FHIR destination mappings, and to export the data to upload to an MedTech service in the Azure portal. This tool also helps developers understand their device's Device and FHIR destination mapping configurations.
@@ -98,7 +129,7 @@ Under the **Basics** tab, complete the required fields under **Instance details*
 
 2. Select **Next: Destination >** to configure the destination properties associated with your MedTech service.
 
-## Configure FHIR destination mapping properties
+## Configure the FHIR destination mapping properties
 
 Under the **Destination** tab, enter the destination properties associated with the MedTech service.
 
@@ -162,7 +193,7 @@ Under the **Tags** tab, enter the tag properties associated with the MedTech ser
 
     Now that your MedTech service has been deployed, we're going to walk through the steps of assigning permissions to access the event hub and FHIR service. 
 
-## Granting MedTech service access
+## Granting the MedTech service access
 
 To ensure that your MedTech service works properly, it must have granted access permissions to the event hub and FHIR service. 
 
@@ -226,13 +257,15 @@ For more information about authoring access to Event Hubs resources, see [Author
 
    ![Screenshot of FHIR service added role assignment message.](media/fhir-service-added-role-assignment.png#lightbox)
 
-   For more information about assigning roles to the FHIR service, see [Configure Azure RBAC](.././configure-azure-rbac.md).
+   For more information about assigning roles to the FHIR service, see [Configure Azure Role-based Access Control (RBAC)](.././configure-azure-rbac.md).
 
 ## Next steps
 
-In this article, you've learned how to deploy a MedTech service in the Azure portal. For an overview of MedTech service, see
+In this article, you've learned how to deploy a MedTech service in the Azure portal. To learn more about the device and FHIR destination mapping files for the MedTech service, see
 
 >[!div class="nextstepaction"]
->[MedTech service overview](iot-connector-overview.md)
+>[How to use Device mappings](how-to-use-device-mappings.md)
+>
+>[How to use FHIR destination mappings](how-to-use-fhir-mappings.md)
 
-FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+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/get-started-with-iot.md

@@ -27,27 +27,27 @@ You can create a workspace from the [Azure portal](../healthcare-apis-quickstart
 > [!NOTE]
 > There are limits to the number of workspaces and the number of MedTech service instances you can create in each Azure subscription.
 
-## Create the FHIR service and an Event Hub
+## Create the FHIR service and an event hub
 
-The MedTech service works with the Azure Event Hub and the FHIR service. You can create a new [FHIR service](../fhir/get-started-with-fhir.md) or use an existing one in the same or different workspace. Similarly, you can create a new [Event Hub](../../event-hubs/event-hubs-create.md) or use an existing one.
+The MedTech service works with Azure Event Hubs and the FHIR service. You can create a new [FHIR service](../fhir/get-started-with-fhir.md) or use an existing one in the same or different workspace. Similarly, you can create a new [Event Hub](../../event-hubs/event-hubs-create.md) or use an existing one.
 
 ## Create a MedTech service in the workspace
 
 You can create a MedTech service from the [Azure portal](deploy-iot-connector-in-azure.md) or using PowerShell, Azure CLI, or REST API. You can find scripts from the [Azure Health Data Services samples](https://github.com/microsoft/healthcare-apis-samples/tree/main/src/scripts).
 
 Optionally, you can create a [FHIR service](../fhir/fhir-portal-quickstart.md) and [DICOM service](../dicom/deploy-dicom-services-in-azure.md) in the workspace.
 
-## Assign roles to allow MedTech service to access Event Hub
+## Assign roles to allow MedTech service to access Event Hubs
 
-By design, the MedTech service retrieves data from the specified Event Hub using the system-managed identity. For more information on how to assign the role to the MedTech service from [Event Hub](../../healthcare-apis/iot/deploy-iot-connector-in-azure.md#granting-medtech-service-access).
+By design, the MedTech service retrieves data from the specified event hub using the system-managed identity. For more information on how to assign the role to the MedTech service from [Event Hubs](../../healthcare-apis/iot/deploy-iot-connector-in-azure.md#granting-the-medtech-service-access).
 
 ## Assign roles to allow MedTech service to access FHIR service
 
 The MedTech service persists the data to the FHIR store using the system-managed identity. See details on how to assign the role to the MedTech service from the [FHIR service](../../healthcare-apis/iot/deploy-iot-connector-in-azure.md#accessing-the-medtech-service-from-the-fhir-service).
 
 ## Sending data to the MedTech service
 
-You can send data to the Event Hub, which is associated with the MedTech service. If you don't see any data in the FHIR service, check the mappings and role assignments for the MedTech service.
+You can send data to the event hub, which is associated with the MedTech service. If you don't see any data in the FHIR service, check the mappings and role assignments for the MedTech service.
 
 ## MedTech service mappings, data flow, ML, Power BI, and Teams notifications