Tutorial: Receive device data through Azure IoT Hub

Članak
03/28/2022
2 min. za čitanje

MedTech service may be used with devices created and managed through Azure IoT Hub for enhanced workflows and ease of use.

This tutorial provides the steps to connect and route device data from IoT Hub to MedTech service.

Prerequisites

An active Azure subscription - Create one for free
FHIR service resource with at least one MedTech service - Deploy MedTech service using Azure portal
Azure IoT Hub resource connected with real or simulated device(s) - Create an IoT Hub using the Azure portal

Tip

If you are using an Azure IoT Hub simulated device application, feel free to pick the application of your choice amongst different supported languages and systems.

Below is a diagram of the IoT device message flow from IoT Hub into MedTech service:

Create a managed identity for IoT Hub

For this tutorial, we'll be using an IoT Hub with a system-assigned managed identity to provide access from the IoT Hub to the MedTech service device message event hub.

For more information about how to create a system-assigned managed identity with your IoT Hub, see IoT Hub support for managed identities.

For more information on Azure role-based access control, see Azure role-based access control (Azure RBAC).

Connect IoT Hub with the MedTech service

Azure IoT Hub supports a feature called message routing. 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.

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.

Send device message to IoT Hub

Use your device (real or simulated) to send the sample heart rate message shown below to the IoT Hub.

This message will get routed to MedTech service, where the message will be transformed into a FHIR Observation resource and stored into FHIR service.

{
  "HeartRate": 80,
  "RespiratoryRate": 12,
  "HeartRateVariability": 64,
  "BodyTemperature": 99.08839032397609,
  "BloodPressure": {
    "Systolic": 23,
    "Diastolic": 34
  },
  "Activity": "walking"
}

Important

Make sure to send the device message that conforms to the Device mappings and FHIR destinations mappings configured with your MedTech service.

View device data in FHIR service

You can view the FHIR Observation resource(s) created by the MedTech service on the FHIR service using Postman. For information, see Access the FHIR service using Postman, and make a GET request to https://your-fhir-server-url/Observation?code=http://loinc.org|8867-4 to view Observation FHIR resources with heart rate value submitted in the above sample message.

Tip

Ensure that your user has appropriate access to FHIR service data plane. Use Azure role-based access control (Azure RBAC) to assign required data plane roles.

Next steps

In this tutorial, you set up an Azure IoT Hub to route device data to MedTech service.

To learn about the different stages of data flow within MedTech service, see

MedTech service data flow

(FHIR®) is a registered trademark of HL7 and is used with the permission of HL7.