What is the MedTech service?
Overview
The MedTech service is an optional service of the Azure Health Data Services designed to ingest health data from multiple and disparate Internet of Medical Things (IoMT) devices and persisting the health data in a Fast Healthcare Interoperability Resources (FHIR®) service.
The MedTech service is important because health data collected from patients and health care consumers can be fragmented from access across multiple systems, device types, and formats. Managing healthcare data can be difficult, however, trying to gain insight from the data can be one of the biggest barriers to population and personal wellness understanding and sustaining health.
The MedTech service transforms device data into FHIR-based Observation resources and then persists the transformed messages into the Azure Health Data Services FHIR service. Allowing 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.
Below is an overview of what the MedTech service does after IoMT device data is received. Each step will be further explained in the The MedTech service data flows article.
Note
Learn more about Azure Event Hubs use cases, features and architectures.
Scalable
The MedTech service is designed out-of-the-box to support growth and adaptation to the changes and pace of healthcare by using autoscaling features. The service enables developers to modify and extend the capabilities to support more device mapping template types and FHIR resources.
Configurable
The MedTech service is configured by using Device and FHIR destination mappings. The mappings instruct the filtering and transformation of your IoMT device messages into the FHIR format.
The different points for extension are:
- Normalization: Health data from disparate devices can be aligned and standardized into a common format to make sense of the data from a unified lens and capture trends.
- FHIR conversion: Health data is normalized and grouped by mapping commonalities to FHIR. Observations can be created or updated according to chosen or configured templates. Devices and health care consumers can be linked for enhanced insights and trend capture.
Tip
Check out the IoMT Connector Data Mapper tool for editing, testing, and troubleshooting MedTech service Device and FHIR destination mappings. Export mappings for uploading to the MedTech service in the Azure portal or use with the open-source version of the MedTech service.
Extensible
The MedTech service may also be used with our open-source projects for ingesting IoMT device data from the following wearables:
- Fitbit®
- Apple®
- Google®
The MedTech service may also be used with the following Microsoft solutions to provide more functionalities and insights:
Secure
The MedTech service uses Azure role-based access control (Azure RBAC) and a system-assigned managed identity for granular security and access control of your MedTech service assets.
Next steps
In this article, you learned about the MedTech service. To learn about the MedTech service data flows and how to deploy the MedTech service in the Azure portal, see
FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
Povratne informacije
Pošalјite i prikažite povratne informacije za