Skip to content

Commit 498f9d0

Browse files
committed
Additional edits
1 parent 0ca81c1 commit 498f9d0

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

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

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,24 +15,25 @@ ms.author: jasteppe
1515
> [!NOTE]
1616
> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
1717
18-
The MedTech service provides multiple methods for deployment into Azure. Each deployment method has different advantages allow you to customize your deployment to suit your needs and use cases.
18+
The MedTech service provides multiple methods for deployment into Azure. Each deployment method has different advantages that allow you to customize your deployment to suit your needs and use cases.
1919

2020
In this quickstart, learn about these deployment methods:
2121

2222
* Azure Resource Manager template (ARM template) including an Azure Iot Hub using the **Deploy to Azure** button.
2323
* ARM template using the **Deploy to Azure** button.
2424
* ARM template using Azure PowerShell or the Azure CLI.
25+
* Bicep file using Azure PowerShell or the Azure CLI.
2526
* Manually in the Azure portal.
2627

2728
## Deployment overview
2829

29-
The following diagram outlines the basic steps of the MedTech service deployment. These basic steps may help you analyze the deployment options and determine which deployment method is best for you.
30+
The following diagram outlines the basic steps of the MedTech service deployment. These steps may help you analyze the deployment options and determine which deployment method is best for you.
3031

3132
:::image type="content" source="media/get-started/get-started-with-medtech-service.png" alt-text="Diagram showing MedTech service deployment overview." lightbox="media/get-started/get-started-with-medtech-service.png":::
3233

3334
## ARM template including an Azure Iot Hub using the Deploy to Azure button
3435

35-
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. The deployed MedTech service and Azure IoT Hub are fully functional including conforming and valid device and FHIR destination mappings. Use the Azure IoT Hub to create devices and send device messages to the MedTech service.
36+
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. The deployed MedTech service and Azure IoT Hub are fully functional including conforming and valid device and FHIR destination mappings. Use the Azure IoT Hub to create devices and send device messages to the MedTech service.
3637

3738
[![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-with-iothub%2Fazuredeploy.json)
3839

@@ -42,7 +43,7 @@ To learn more about deploying the MedTech service including an Azure IoT Hub usi
4243

4344
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. The deployed MedTech service requires conforming and valid device and FHIR destination mappings to be fully functional.
4445

45-
[![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).
46+
[![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).
4647

4748
To learn more about deploying the MedTech service using an ARM template and the **Deploy to Azure** button, see [Deploy the MedTech service using an Azure Resource Manager template](deploy-arm-template.md).
4849

@@ -71,9 +72,9 @@ To learn more about deploying the MedTech service manually using the Azure porta
7172
>
7273
> Examples:
7374
>
74-
> - Two MedTech services accessing the same device message event hub.
75+
> * Two MedTech services accessing the same device message event hub.
7576
>
76-
> - A MedTech service and a storage writer application accessing the same device message event hub.
77+
> * A MedTech service and a storage writer application accessing the same device message event hub.
7778
7879
## Next steps
7980

0 commit comments

Comments
 (0)