Skip to content

Commit ff6b3f0

Browse files
authored
Apply suggestions from code review
Acro edits.
1 parent adc1c8b commit ff6b3f0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/healthcare-apis/get-started-with-health-data-services.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,12 +88,12 @@ For more information, see [Get started with the DICOM service](./../healthcare-a
8888

8989
MedTech service transforms device data into FHIR-based observation resources and then persists the transformed messages into Azure Health Data Services FHIR service. This allows for a unified approach to health data access, standardization, and trend capture enabling the discovery of operational and clinical insights, connecting new device applications, and enabling new research projects.
9090

91-
To ensure that your MedTech service works properly, it must have granted access permissions to the Azure Event Hub and FHIR service. 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](./../healthcare-apis/authentication-authorization.md)
91+
To ensure that your MedTech service works properly, it must have granted access permissions to the Azure Event Hubs and FHIR service. 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](./../healthcare-apis/authentication-authorization.md)
9292

9393
You can also do the following:
9494
- Create a new FHIR service or use an existing one in the same or different workspace
9595
- Create a new event hub or use an existing one
96-
- Assign roles to allow the MedTech service to access [Event Hub](./../healthcare-apis/iot/deploy-iot-connector-in-azure.md#granting-the-medtech-service-access) and [FHIR service](./../healthcare-apis/iot/deploy-iot-connector-in-azure.md#accessing-the-medtech-service-from-the-fhir-service)
96+
- Assign roles to allow the MedTech service to access [Event Hubs](./../healthcare-apis/iot/deploy-iot-connector-in-azure.md#granting-the-medtech-service-access) and [FHIR service](./../healthcare-apis/iot/deploy-iot-connector-in-azure.md#accessing-the-medtech-service-from-the-fhir-service)
9797
- Send data to the event hub, which is associated with the MedTech service
9898

9999
For more information, see [Get started with the MedTech service](./../healthcare-apis/iot/get-started-with-iot.md).

0 commit comments

Comments
 (0)