Related GitHub Projects
Important
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.
There are many open-source projects on GitHub that provide source code and instructions to deploy services for various uses. You're always welcome to visit our GitHub repositories to learn about and experiment with our features and products.
FHIR Server GitHub projects
- microsoft/fhir-server: an open-source FHIR Server, which is the basis for Azure API for FHIR
- microsoft/fhir-server-samples: a sample environment
- To see the latest releases, refer to the Release Notes
Data Conversion & Anonymization
FHIR Converter
- microsoft/FHIR-Converter is a data conversion project that uses the CLI tool and the
$convert-dataFHIR endpoint to translate healthcare legacy data formats into FHIR. - Integrated with the FHIR service and FHIR server for Azure in the form of
$convert-dataoperation - Ongoing improvements in OSS, and continual integration to the FHIR servers
FHIR Converter - VS Code Extension
- microsoft/vscode-azurehealthcareapis-tools is a VS Code extension that contains a collection of tools to work with FHIR Converter.
- Released to Visual Studio Marketplace, you can install it here: FHIR Converter VS Code extension.
- Used for authoring Liquid conversion templates and managing templates on Azure Container Registry
FHIR Tools for Anonymization
- microsoft/Tools-for-Health-Data-Anonymization is 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 $exportoperation - 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 device input data and transform it to FHIR resources. Developers can use this tool to edit and test mappings, device mapping and FHIR mapping, and export mappings for uploading to the MedTech service in the Azure portal.
HealthKit and FHIR Integration
- microsoft/healthkit-on-fhir: A Swift library that automates the export of Apple HealthKit Data to a FHIR Server.
Next steps
In this article, you 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
Note
FHIR® is a registered trademark of HL7 and is used with the permission of HL7.