Related GitHub Projects


Azure API for FHIR will be retired on September 30, 2026. Follow the migration strategies to transition to Azure Health Data Services FHIR service by that date. Due to the retirement of Azure API for FHIR, new deployments won't be allowed beginning April 1, 2025. Azure Health Data Services FHIR service is the evolved version of Azure API for FHIR that enables customers to manage FHIR, DICOM, and MedTech services with integrations into other Azure services.

We have many open-source projects on GitHub that provide you the source code and instructions to deploy services for various uses. You're always welcome to visit our GitHub repositories to learn and experiment with our features and products.

FHIR Server

Data Conversion & Anonymization

FHIR Converter

  • microsoft/FHIR-Converter: a data conversion project that uses CLI tool and $convert-data FHIR endpoint to translate healthcare legacy data formats into FHIR
  • Integrated with the FHIR service and FHIR server for Azure in the form of $convert-data operation
  • Ongoing improvements in OSS, and continual integration to the FHIR servers

FHIR Converter - VS Code Extension

FHIR Tools for Anonymization

  • microsoft/Tools-for-Health-Data-Anonymization: a data anonymization project that provides tools for de-identifying FHIR data and DICOM data
  • Integrated with the FHIR service and FHIR server for Azure in the form of de-identified $export operation
  • For FHIR data, it can also be used with Azure Data Factory (ADF) pipeline by reading FHIR data from Azure blob storage and writing back the anonymized data

MedTech service

Integration with IoT Hub and IoT Central

  • microsoft/iomt-fhir: integration with IoT Hub or IoT Central to FHIR with data normalization and FHIR conversion of the normalized data
  • Normalization: device data information is extracted into a common format for further processing
  • FHIR Conversion: normalized and grouped data is mapped to FHIR. Observations are created or updated according to configured templates and linked to the device and patient.
  • Tools to help build the conversation map: visualize the mapping configuration for normalizing the device input data and transform it to the FHIR resources. Developers can use this tool to edit and test the mappings, device mapping and FHIR mapping, and export them for uploading to the MedTech service in the Azure portal.

HealthKit and FHIR Integration

Next steps

In this article, you've learned about the related GitHub Projects for Azure API for FHIR that provide source code and instructions to let you experiment and deploy services for various uses. For more information about Azure API for FHIR, see

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