Skip to content

Commit b4b45ac

Browse files
committed
Minor updates.
1 parent 454ee41 commit b4b45ac

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

articles/healthcare-apis/iot/device-data-through-iot-hub.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,9 +39,9 @@ For more information on Azure role-based access control, see [Azure role-based a
3939

4040
## Connect IoT Hub with the MedTech service
4141

42-
Azure IoT Hub supports a feature called [message routing](../../iot-hub/iot-hub-devguide-messages-d2c.md). Message routing provides the capability to send device data to various Azure services (for example: event hub, Storage Accounts, and Service Buses). MedTech service uses this feature to allow an IoT Hub to connect and send device messages to the MedTech service device message event hub endpoint.
42+
Azure IoT Hub supports a feature called [message routing](/azure/iot-hub/iot-hub-devguide-messages-d2c.md). Message routing provides the capability to send device data to various Azure services (for example: event hub, Storage Accounts, and Service Buses). MedTech service uses this feature to allow an IoT Hub to connect and send device messages to the MedTech service device message event hub endpoint.
4343

44-
Follow these directions to grant access to the IoT Hub user-assigned managed identity to your MedTech service device message event hub and set up message routing: [Configure message routing with managed identities](../../iot-hub/iot-hub-managed-identity.md#egress-connectivity-from-iot-hub-to-other-azure-resources).
44+
Follow these directions to grant access to the IoT Hub system-assigned managed identity to your MedTech service device message event hub and set up message routing: [Configure message routing with managed identities](/azure-pipelines.yml/iot-hub/iot-hub-managed-identitymd#egress-connectivity-from-iot-hub-to-other-azure-resources)
4545

4646
## Send device message to IoT Hub
4747

@@ -56,6 +56,7 @@ This message will get routed to MedTech service, where the message will be trans
5656
> To learn about IoT Hub device message enrichment and IotJsonPathContentTemplate mappings usage with the MedTech service device mapping, see [How to use IotJsonPathContentTemplate mappings](how-to-use-iot-jsonpath-content-mappings.md)
5757
5858
```json
59+
5960
{
6061
"HeartRate": 80,
6162
"RespiratoryRate": 12,
@@ -67,7 +68,9 @@ This message will get routed to MedTech service, where the message will be trans
6768
},
6869
"Activity": "walking"
6970
}
71+
7072
```
73+
7174
> [!IMPORTANT]
7275
> Make sure to send the device message that conforms to the [Device mappings](how-to-use-device-mappings.md) and [FHIR destinations mappings](how-to-use-fhir-mappings.md) configured with your MedTech service.
7376

0 commit comments

Comments
 (0)