Skip to content

Latest commit

 

History

History
57 lines (41 loc) · 6.9 KB

Challenge06.md

File metadata and controls

57 lines (41 loc) · 6.9 KB

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.

  • Deploy Azure Event Hubs for MedTech service to ingest medical IoT device data

    Hint: An Event Hubs namespace provides a unique scoping container, in which you create one or more event hubs.

  • Deploy a new instance of the MedTech service in your Azure Health Data Services workspace (deployed in challenge 1) and configure it to ingest IoT data from the above Event Hubs instance

  • Deploy the IoT mapper tool

    • Import sample IoT messages into tool to customize device mapping to FHIR
      • You can also find the sample IoT message files (devicecontent.json and fhirmapping.json) in the /MedTech-service/SampleData folder of the Resources.zip file provided by your coach.
    • Export customized mapping in tool to generate the new Device Mapping and FHIR Mapping files

  • Import the newly generated FHIR mapping into your MedTech service

    • Configure and save the Device mapping JSON in the MedTech service (Device Mapping setting)
    • Configure and save the Destination mapping JSON to in the MedTech service (Destination setting)

  • Send sample device data to persist in the FHIR service using Postman via MedTech service Event Hub service

Success Criteria

  • You have successfully configured device mapping to FHIR using the data mapper tool
  • You have successfully generated a custom FHIR mapping for medical IoT device data
  • You have successfully configured MedTech service for mapping IoT device data to FHIR
  • You have successfully ingested sample medical IoT device data into the FHIR services as Observation resources.

Learning Resources