Skip to content

Commit 35e6bf5

Browse files
authored
Update get-started-with-iot.md
Acro edits: "Event Hub" to "Event Hubs."
1 parent b159828 commit 35e6bf5

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/healthcare-apis/iot/get-started-with-iot.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -27,27 +27,27 @@ You can create a workspace from the [Azure portal](../healthcare-apis-quickstart
2727
> [!NOTE]
2828
> There are limits to the number of workspaces and the number of MedTech service instances you can create in each Azure subscription.
2929
30-
## Create the FHIR service and an Event Hub
30+
## Create the FHIR service and an event hub
3131

32-
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.
32+
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.
3333

3434
## Create a MedTech service in the workspace
3535

3636
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).
3737

3838
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.
3939

40-
## Assign roles to allow MedTech service to access Event Hub
40+
## Assign roles to allow MedTech service to access Event Hubs
4141

42-
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-the-medtech-service-access).
42+
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).
4343

4444
## Assign roles to allow MedTech service to access FHIR service
4545

4646
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).
4747

4848
## Sending data to the MedTech service
4949

50-
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.
50+
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.
5151

5252
## MedTech service mappings, data flow, ML, Power BI, and Teams notifications
5353

0 commit comments

Comments
 (0)