Del via

What is the MedTech service?

The MedTech service is a Platform as a Service (PaaS) within the Azure Health Data Services. The MedTech service enables you to ingest device data, transform it into a unified FHIR® format, and store it in an enterprise-scale, secure, and compliant cloud environment. 

The MedTech service is built to help customers that are dealing with the challenge of gaining relevant insights from device data coming in from multiple and diverse sources. No matter the device or structure, the MedTech service normalizes that device data into a common format, allowing the end user to then easily capture trends, run analytics, and build Artificial Intelligence (AI) models. In the enterprise healthcare setting, the MedTech service is used in the context of remote patient monitoring, virtual health, and clinical trials.

The following video presents an overview of the MedTech service:

How the MedTech service works

The following diagram outlines the basic elements of how the MedTech service transforms device data into standardized FHIR Observations for persistence in the FHIR service.

Simple diagram showing the MedTech service.

The MedTech service processes device data in five stages:

  1. Ingest - The MedTech service asynchronously reads the device message from the event hub at high speed.

  2. Normalize - After the device message has been ingested, the MedTech service uses the device mapping to streamline and convert the device data into a normalized schema format.

  3. Group - The normalized data is then grouped by parameters to prepare it for the next stage of processing. The parameters are: device identity, measurement type, time period, and (optionally) correlation ID.

  4. Transform - When the normalized data is grouped, it's transformed through the FHIR destination mapping and is ready to become FHIR Observations.

  5. Persist - After the transformation is done, the newly transformed data is sent to the FHIR service and persisted as FHIR Observations.

Key features of the MedTech service

The MedTech service has many features that make it secure, configurable, scalable, and extensible.


The MedTech service delivers your device data into FHIR service, ensuring that your data has unparalleled security and advanced threat protection. The FHIR service isolates your data in a unique database per API instance and protects it with multi-region failover. In addition, the MedTech service uses Azure role-based access control (Azure RBAC) and a system-assigned managed identity for extra security and control of your MedTech service assets.


The MedTech service can be customized and configured by using device and FHIR destination mappings to define the filtering and transformation of your data into FHIR Observations.

Useful options could include:

  • Link devices and consumers together for enhanced insights, trend captures, interoperability between systems, and proactive and remote monitoring.

  • Update or create FHIR Observations according to existing or new mapping template types.

  • Choose data terms that work best for your organization and provide consistency in device data ingestion.

  • Customize, edit, test, and troubleshoot MedTech service device and FHIR destination mappings with the Mapping debugger.


The MedTech service enables you to easily modify and extend the capabilities of the MedTech service to support new device mapping template types and FHIR resources.


The MedTech service can also be integrated for ingesting device data from these wearables using our open-source projects:

  • Fitbit®

  • Apple®

  • Google®

The following Microsoft solutions can use MedTech service for extra functionality:

Next steps

Overview of the MedTech service device data processing stages

Choose a deployment method for the MedTech service

Frequently asked questions about the MedTech service


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