Quickstart: Choose a deployment method for the MedTech service

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.

In this quickstart, you'll 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.
  • Manually in the Azure portal.

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

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 Fast Healthcare Interoperability Resources (FHIR®) destination mappings. Use the Azure IoT Hub to create devices and send device messages to the MedTech service.

Deploy to Azure

To learn more about deploying the MedTech service including an Azure IoT Hub using an ARM template and the Deploy to Azure button, see Receive device messages through Azure IoT Hub.

ARM template using the Deploy to Azure button

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 will still require conforming and valid device and FHIR destination mappings to be fully functional.

Deploy to Azure.

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.

ARM template using Azure PowerShell or the Azure CLI

Using an ARM template with Azure PowerShell or the Azure CLI 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. The deployed MedTech service will still require conforming and valid device and FHIR destination mappings to be fully functional.

To learn more about deploying the MedTech service using an ARM template and Azure PowerShell or the Azure CLI, see Deploy the MedTech service using an Azure Resource Manager template and Azure PowerShell or the Azure CLI.

Manually in the Azure portal

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.

To learn more about deploying the MedTech service manually using the Azure portal, see Deploy the MedTech service manually using the Azure portal.

Deployment architecture overview

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.

Diagram showing MedTech service architecture overview.

Important

If you're going to allow access from multiple services to the device message event hub, it is highly recommended that each service has its own event hub consumer group.

Consumer groups enable multiple consuming applications to have a separate view of the event stream, and to read the stream independently at their own pace and with their own offsets. For more information, see Consumer groups.

Examples:

  • 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.

Next steps

In this quickstart, you learned about the different types of deployment methods for the MedTech service.

To learn more about the MedTech service, see

FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.