Merge pull request #220817 from msjasteppe/choose-edits

Choose edits

Author: Stacyrch140

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

@@ -5,91 +5,52 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 11/29/2022
+ms.date: 12/08/2022
 ms.author: jasteppe
 ---
 
 # Quickstart: Choose a deployment method for the MedTech service
 
-The MedTech service provides multiple methods for deployment into an Azure Platform as a Service (PaaS) configuration. Each method has different advantages that will allow you to customize your development environment to suit your needs.
+The MedTech service provides multiple methods for deployment into Azure. Each deployment method has different advantages that will allow you to customize your deployment to suit your needs and use cases.
 
-The different deployment methods are:
+In this quickstart, you'll learn about these deployment methods:
 
-- Azure Resource Manager (ARM) template with Deploy to Azure button
-- Azure PowerShell or Azure CLI automation
-- Azure portal manual deployment
+> [!div class="checklist"]
+> - Azure Resource Manager template (ARM template) with the **Deploy to Azure** button.
+> - Azure PowerShell or the Azure CLI.
+> - Azure portal manual deployment. 
 
-## Azure Resource Manager template with Deploy to Azure button
+## Azure Resource Manager template with the Deploy to Azure button
 
-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.
+Using an ARM template with the **Deploy to Azure** button is an easy and fast deployment method because it automates the deployment, most configuration steps, and uses the Azure portal.
 
-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).
+To learn more about using an 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
+## Azure PowerShell or the Azure CLI
 
-Azure provides Azure PowerShell and Azure CLI to speed up your configurations when used in enterprise environments. Deploying MedTech service with Azure PowerShell or Azure CLI can be useful for adding automation so that you can scale your deployment for a large number of developers. This method is more detailed but provides extra speed and efficiency because it allows you to automate your deployment.
+Using Azure PowerShell or the Azure CLI to deploy an ARM template is a more advanced deployment method. This deployment method can be useful for adding automation and repeatability so that you can scale and customize your deployments.
 
-For more information about Using an ARM template with Azure PowerShell or Azure CLI, see [Deploy the MedTech service using an Azure Resource Manager template and Azure PowerShell or the Azure CLI](deploy-new-powershell-cli.md).
+To learn more about using an ARM template with Azure PowerShell or the Azure CLI, see [Deploy the MedTech service using an Azure Resource Manager template and Azure PowerShell or the Azure CLI](deploy-new-powershell-cli.md).
 
 ## Azure portal manual deployment
 
-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.
+Using the Azure portal manual deployment will allow you to see the details of each deployment step. The manual deployment has many steps, but it provides valuable technical information that may be useful for customizing and troubleshooting your MedTech service.
 
-For more information about manual deployment with Azure portal, see [Deploy the MedTech service manually using the Azure portal](deploy-new-manual.md).
+To learn more about using a manual deployment with the Azure portal, see [Deploy the MedTech service manually using the Azure portal](deploy-new-manual.md).
 
 ## Deployment architecture overview
 
-The following data-flow diagram outlines the basic steps of MedTech service deployment and shows how these steps fit together with its data processing procedures. These basic steps may help you analyze the options and determine which deployment method is best for you.
+The following diagram outlines the basic steps of the MedTech service deployment and shows how these steps fit together with its data processing procedures. These basic steps may help you analyze the deployment options and determine which deployment method is best for you.
 
 :::image type="content" source="media/iot-get-started/get-started-with-iot.png" alt-text="Diagram showing MedTech service architecture overview." lightbox="media/iot-get-started/get-started-with-iot.png":::
 
-There are six different steps of the MedTech service PaaS. Only the first four apply to deployment. All the methods of deployment will implement each of these four steps. However, the QuickStart template method will automatically implement part of step 1 and all of step 2. The other two methods will have to implement all of the steps individually. Here's a summary of each of the four deployment steps:
-
-### Step 1: Prerequisites
-
-- Have an Azure subscription
-- Create RBAC roles contributor and user access administrator or owner. This feature is automatically done in the ARM template method with the Deploy to Azure button. It isn't included in the manual or PowerShell/CLI methods and needs to be implemented individually.
-
-### Step 2: Provision
-
-The ARM template method with the Deploy to Azure button automatically provides all these steps, but they aren't included in the manual or the PowerShell/CLI method and must be completed individually.
-
-- Create a resource group and workspace for Event Hubs, FHIR, and MedTech services.
-- Provision an Event Hubs instance to a namespace.
-- Provision a FHIR service instance to the same workspace.
-- Provision a MedTech service instance in the same workspace.
-
-### Step 3: Configure
-
-Each method needs to provide **all** these configuration details. They include: 
-
-- Configure MedTech service to ingest data from an event hub.
-- Configure device mapping properties.
-- Configure destination mappings to an Observation resource in the FHIR service.
-- When the prerequisites, provisioning, and configuration are complete, create and deploy MedTech service.
-
-### Step 4: Post-Deployment
-
-Each method must add **all** these post-deployment tasks:
-
-- Connect to services using device and destination mapping.
-- Use managed identity to grant access to the device message event hub.
-- Use managed identity to grant access to the FHIR service, enabling FHIR to receive data from the MedTech service.
-- Note: only the ARM template method requires a shared access key for post-deployment.
-
-### 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-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-new-deploy.md#grant-access-to-the-fhir-service).
-
 ## Next steps
 
-In this article, you learned about the different types of deployment for MedTech service. To learn more about MedTech service, see
+In this quickstart, you learned about the different types of deployment methods for the MedTech service. 
+
+To learn more about the MedTech service, see
 
 > [!div class="nextstepaction"]
-> [What is MedTech service?](iot-connector-overview.md)
+> [What is the MedTech service?](iot-connector-overview.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/iot-connector-faqs.md

@@ -1,18 +1,18 @@
 ---
-title: FAQs about the MedTech service - Azure Health Data Services
-description: This document provides answers to the frequently asked questions about the MedTech service.
+title: Frequently asked questions (FAQs) about the MedTech service - Azure Health Data Services
+description: This document provides answers to the frequently asked questions (FAQs) about the MedTech service.
 services: healthcare-apis
 author: msjasteppe
 ms.custom: references_regions
 ms.service: healthcare-apis
 ms.topic: reference
-ms.date: 12/06/2022
+ms.date: 12/08/2022
 ms.author: jasteppe
 ---
 
 # Frequently asked questions about the MedTech service
 
-Here are some of the frequently asked questions about the MedTech service.
+Here are some of the frequently asked questions (FAQs) about the MedTech service.
 
 ## The MedTech service: The basics
 
@@ -24,15 +24,17 @@ The MedTech service is available in these regions: [Products available by region
 
 No. The Azure Health Data Services MedTech service currently only supports the Azure Health Data Services Fast Healthcare Interoperability Resources (FHIR®) service for the persistence of data. The open-source version of the MedTech service supports the use of different FHIR services. 
 
-For more information, see the [Open-source projects](iot-git-projects.md) section of our documentation.  
+To learn more about the MedTech service open-source projects, see [Open-source projects](iot-git-projects.md). 
 
 ### What versions of FHIR does the MedTech service support?
 
 The MedTech service currently only supports the persistence of [HL7 FHIR® R4](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=491). 
 
 ### Does the MedTech service perform backups of device messages?
 
-No. The MedTech service doesn't back up the device messages that come into the customer's event hub. The customer controls the device message retention period within their event hub, which can be from 1-7 days. If the device message data is successfully processed by the MedTech service, it's persisted in the FHIR service, and the backup policy applies. To learn more about event hub message retention, see [What is the maximum retention period for events?](/azure/event-hubs/event-hubs-faq#what-is-the-maximum-retention-period-for-events-) 
+No. The MedTech service doesn't back up the device messages that come into the customer's event hub. The customer controls the device message retention period within their event hub, which can be from 1-7 days. If the device message data is successfully processed by the MedTech service, it's persisted in the FHIR service, and the FHIR service backup policy applies. 
+
+To learn more about event hub message retention, see [What is the maximum retention period for events?](/azure/event-hubs/event-hubs-faq#what-is-the-maximum-retention-period-for-events-) 
 
 ### What are the subscription quota limits for the MedTech service?
 
@@ -44,11 +46,12 @@ No. The MedTech service doesn't back up the device messages that come into the c
 
 ### Can I use the MedTech service with device messages from Apple®, Google®, or Fitbit® devices?
 
-Yes. The MedTech service supports device messages from all these vendors through the open-source version. 
+Yes. The MedTech service supports device messages from all these vendors through the open-source version of the MedTech service. 
 
-For more information, see the [Open-source projects](iot-git-projects.md) section of our documentation.
+To learn more about the MedTech service open-source projects, see [Open-source projects](iot-git-projects.md). 
 
 ## More frequently asked questions
+
 [FAQs about the Azure Health Data Services](../healthcare-apis-faqs.md)
 
 [FAQs about Azure Health Data Services FHIR service](../fhir/fhir-faq.md)