Challenge 6: Ingest and Persist IoT Medical Device Data

< Previous Challenge - Home - Next Challenge>

Introduction

In this challenge, you will work with IoT medical device data using the MedTech service in Azure Health Data Services. You will use MedTech service toolkit to transform IoT medical device data into Fast Healthcare Interoperability Resources (FHIR®)-based Observation resources. You will deploy a MedTech service data pipeline to ingest medical IoT data, normalize and group these messages,transform the grouped-normalized messages into FHIR-based Observation resources, and then persist the transformed messages into the FHIR service (previously deployed in challenge 1).

The MedTech service in Azure Health Data Services uses an event hub to ingests streaming event data from IoT medical devices, transforms them into FHIR-based Observation resources, retrieves associated Patient resource from FHIR service, adds them as reference to the Observation resource created, and then persists the transformed messages to the FHIR service.

Azure IoMT Connector Data Mapper is the MedTech toolkit to visualize and configure normalize mapping between the medical IoT data and FHIR. Once you completed the FHIR mapping, you can export it and upload the mapping files to your MedTech service Device Mapping configuration in Azure Portal.

Below is the overview of the MedTech service data flow:

Description

You will deploy an instance of MedTech service in your Azure Health Data Service workspace, and configure it to receive and transform medical IoT data for persitence in your FHIR service (deployed in challenge 1) as Observation resources.

Success Criteria

Learning Resources