Merge pull request #194423 from msjasteppe/medtech-deploy-updates

Adding section about Consumer Groups and edits.

Author: PRMerger14

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

@@ -5,24 +5,33 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 03/21/2022
+ms.date: 04/07/2022
 ms.author: jasteppe
 ms.custom: mode-api
 ---
 
 # Deploy MedTech service in the Azure portal
 
-In this quickstart, you'll learn how to deploy MedTech service in the Azure portal. Configuring the MedTech service will enable you to ingest data from Internet of Things (IoT) into your Fast Healthcare Interoperability Resources (FHIR®) service using an Azure Event Hub for device messages.
+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.
 
 ## Prerequisites
 
-It's important that you have the following prerequisites completed before you begin the steps of creating an MedTech service instance in Azure Health Data Services.
+It's important that you have the following prerequisites completed before you begin the steps of creating a MedTech service instance in Azure Health Data Services.
 
 * [Azure account](https://azure.microsoft.com/free/search/?OCID=AID2100131_SEM_c4b0772dc7df1f075552174a854fd4bc:G:s&ef_id=c4b0772dc7df1f075552174a854fd4bc:G:s&msclkid=c4b0772dc7df1f075552174a854fd4bc)
 * [Resource group deployed in the Azure portal](../../azure-resource-manager/management/manage-resource-groups-portal.md)
-* [Event Hubs namespace and Event Hub deployed in the Azure portal](../../event-hubs/event-hubs-create.md)
+* [Event Hubs namespace and event hub deployed in the Azure portal](../../event-hubs/event-hubs-create.md)
 * [Workspace deployed in Azure Health Data Services](../healthcare-apis-quickstart.md)  
-* [FHIR service deployed in Azure Health Data Services](../fhir/fhir-portal-quickstart.md) 
+* [FHIR service deployed in Azure Health Data Services](../fhir/fhir-portal-quickstart.md)
+
+> [!IMPORTANT]
+> If you're going to allow access from multiple services to the device message event hub, it is highly recommended that each service have its own event hub consumer group. 
+>
+> Consumer groups enable multiple consuming applications to each 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](../../event-hubs/event-hubs-features.md#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.
 
 ## Deploy MedTech service 
 
@@ -50,9 +59,9 @@ Under the **Basics** tab, complete the required fields under **Instance details*
 
 2. Enter the **Event Hub name**.
 
-   The Event Hub name is the name of the **Event Hubs Instance** that you've deployed. 
+   The event hub name is the name of the **Event Hubs Instance** that you've deployed. 
 
-   For information about Azure Event Hubs, see [Quickstart: Create an Event Hub using Azure portal](../../event-hubs/event-hubs-create.md#create-an-event-hubs-namespace).
+   For information about Azure Event Hubs, see [Quickstart: Create an event hub using Azure portal](../../event-hubs/event-hubs-create.md#create-an-event-hubs-namespace).
 
 3. Enter the **Consumer Group**.
 
@@ -112,11 +121,11 @@ Under the **Destination** tab, enter the destination properties associated with
 
    **Create**
 
-     The MedTech service destination attempts to retrieve a device resource from the FHIR Server using the device identifier included in the Event Hub message. It also attempts to retrieve a patient resource from the FHIR Server using the patient identifier included in the Event Hub message. If either resource isn't found, new resources will be created (device, patient, or both) containing just the identifier contained in the Event Hub message. When you use the **Create** option, both a device identifier and a patient identifier can be configured in the device mapping. In other words, when the IoT Connector destination is in **Create** mode, it can function normally **without** adding device and patient resources to the FHIR Server.
+     The MedTech service destination attempts to retrieve a device resource from the FHIR Server using the device identifier included in the event hub message. It also attempts to retrieve a patient resource from the FHIR Server using the patient identifier included in the event hub message. If either resource isn't found, new resources will be created (device, patient, or both) containing just the identifier contained in the event hub message. When you use the **Create** option, both a device identifier and a patient identifier can be configured in the device mapping. In other words, when the IoT Connector destination is in **Create** mode, it can function normally **without** adding device and patient resources to the FHIR Server.
 
    **Lookup**
 
-     The MedTech service destination attempts to retrieve a device resource from the FHIR Server using the device identifier included in the event hub message. If the device resource isn't found, this will cause an error, and the data won't be processed. For **Lookup** to function properly, a device resource with an identifier matching the device identifier included in the event hub message **must** exist and the device resource **must** have a reference to a patient resource that also exists. In other words, when the MedTech service destination is in the Lookup mode, device and patient resources **must** be added to the FHIR Server before data can be processed.
+     The MedTech service destination attempts to retrieve a device resource from the FHIR service using the device identifier included in the event hub message. If the device resource isn't found, an error will occur, and the data won't be processed. For **Lookup** to function properly, a device resource with an identifier matching the device identifier included in the event hub message **must** exist and the device resource **must** have a reference to a patient resource that also exists. In other words, when the MedTech service destination is in the Lookup mode, device and patient resources **must** be added to the FHIR Server before data can be processed.
 
    For more information, see the open source documentation [FHIR destination mapping](https://github.com/microsoft/iomt-fhir/blob/master/docs/Configuration.md#fhir-mapping).
 
@@ -151,13 +160,13 @@ Under the **Tags** tab, enter the tag properties associated with the MedTech ser
 
    ![Screenshot of Deployed MedTech service listed in the Azure Recent resources list.](media/azure-resources-iot-connector-deployed.png#lightbox)  
 
-    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. 
+    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
 
-To ensure that your MedTech service works properly, it must have granted access permissions to the Event Hub and FHIR service. 
+To ensure that your MedTech service works properly, it must have granted access permissions to the event hub and FHIR service. 
 
-### Accessing the MedTech service from the Event Hub
+### Accessing the MedTech service from the event hub
 
 1. In the **Azure Resource group** list, select the name of your **Event Hubs Namespace**.
 
@@ -173,7 +182,7 @@ To ensure that your MedTech service works properly, it must have granted access
 
    ![Screenshot of add role assignment required fields.](media/event-hub-add-role-assignment-fields.png#lightbox)
 
-   The Azure Event Hubs Data Receiver role allows the MedTech service that's being assigned this role to receive data from this Event Hub.
+   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](.././authentication-authorization.md).
 
@@ -183,11 +192,11 @@ To ensure that your MedTech service works properly, it must have granted access
 
    `<your workspace name>/iotconnectors/<your MedTech service name>`
 
-   When you deploy an MedTech service, it creates a managed identity. The managed identify name is a concatenation of the workspace name, resource type (that's the MedTech service), and the name of the MedTech service.
+   When you deploy a MedTech service, it creates a managed identity. The managed identify name is a concatenation of the workspace name, resource type (that's the MedTech service), and the name of the MedTech service.
 
 7. Select **Save**.
 
-   After the role assignment has been successfully added to the Event Hub, a notification will display a green check mark with the text "Add Role assignment."  This message indicates that the MedTech service can now read from the Event Hub.
+   After the role assignment has been successfully added to the event hub, a notification will display a green check mark with the text "Add Role assignment."  This message indicates that the MedTech service can now read from the event hub.
 
    ![Screenshot of added role assignment message.](media/event-hub-added-role-assignment.png#lightbox)
 
@@ -221,9 +230,9 @@ For more information about authoring access to Event Hubs resources, see [Author
 
 ## Next steps
 
-In this article, you've learned how to deploy an 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. For an overview of MedTech service, see
 
 >[!div class="nextstepaction"]
 >[MedTech service overview](iot-connector-overview.md)
 
-(FHIR&#174;) is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+FHIR&#174; is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.