Skip to content
A service that implements the FHIR standard
C# Other
  1. C# 98.6%
  2. Other 1.4%
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Create user story template (#207) Jan 2, 2019
build publish global.json (#609) Aug 12, 2019
docs Fix spelling in Sep 3, 2019
release/scripts/PowerShell Add auth secrets to keyvault (#555) Jun 25, 2019
samples Package R4 Web project in build (#513) Jun 1, 2019
src Updates package 'IdentityServer4' to version '2.5.3' (#652) Sep 16, 2019
test Add batch/transaction route (#646) Sep 11, 2019
tools Updates package 'Microsoft.Azure.DocumentDB.Core' to version '2.5.1' (#… Aug 16, 2019
.editorconfig Initial code commit Sep 11, 2018
.gitattributes Initial code commit Sep 11, 2018
.gitignore Introduces testauthenvironment.json for defining roles, users, apps, … Oct 12, 2018 Initial draft of the contributing guideline. (#57) Sep 25, 2018
CustomAnalysisRules.Test.ruleset Initial code commit Sep 11, 2018
CustomAnalysisRules.ruleset Basic SQL CRUD operations (#444) May 4, 2019
Directory.Build.props Fixes references/versions of analyzers (#554) Jun 20, 2019
GeoPol.xml GeoPolitical Update: Fix for GeoPolExclude into master branch Jul 2, 2019
LICENSE Initial commit Aug 23, 2018
Microsoft.Health.Fhir.sln Add _include support to SQL server (#564) Sep 5, 2019 Create (#231) Jan 2, 2019 Update (#546) Jun 19, 2019 Updates package 'Polly' to version '7.1.1' (#634) Sep 4, 2019
global.json Changes to 2.2.107 (#570) Jul 8, 2019
nuget.config Packages source for pre-release fhir-net-api versions (#404) Apr 9, 2019
stylecop.json Initial code commit Sep 11, 2018
testauthenvironment.json Added permission support for export operation. (#437) May 1, 2019

FHIR Server for Azure

A .NET Core implementation of the FHIR standard.

CI Status

FHIR Server for Azure is an open-source implementation of the emerging HL7 Fast Healthcare Interoperability Resources (FHIR) specification designed for the Microsoft cloud. The FHIR specification defines how clinical health data can be made interoperable across systems, and the FHIR Server for Azure helps facilitate that interoperability in the cloud. The goal of this Microsoft Healthcare project is to enable developers to rapidly deploy a FHIR service.

With data in the FHIR format, the FHIR Server for Azure enables developers to quickly ingest and manage FHIR datasets in the cloud, track and manage data access and normalize data for machine learning workloads. FHIR Server for Azure is optimized for the Azure ecosystem:

  • Scripts and ARM templates are available for immediate provisioning in the Microsoft Cloud
  • Scripts are available to map to Azure AAD and enable role-based access control (RBAC)

FHIR Server for Azure is built with logical separation, enabling developers with flexibility to modify how it is implemented, and extend its capabilities as needed. The logic layers of the FHIR server are:

  • Hosting Layer – Supports hosting in different environments, with custom configuration of Inversion of Control (IoC) containers.
  • RESTful API Layer – The implementation of the APIs defined by the HL7 FHIR specification.
  • Core Logic Layer – The implementation of the core FHIR logic.
  • Persistence Layer – A pluggable persistence provider enabling the FHIR server to connect to virtually any data persistence utility. FHIR Server for Azure includes a ready-to-use data persistence provider for Azure Cosmos DB (a globally replicated database service that offers rich querying over data).

FHIR Server for Azure empowers developers – saving time when they need to quickly integrate a FHIR server into their own applications or providing them with a foundation on which they can customize their own FHIR service. As an open source project, contributions and feedback from the FHIR developer community will continue to improve this project.

Privacy and security are top priorities and the FHIR Server for Azure has been developed in support of requirements for Protected Health Information (PHI). All the Azure services used in FHIR Server for Azure meet the compliance requirements for Protected Health Information.

This open source project is fully backed by the Microsoft Healthcare team, but we know that this project will only get better with your feedback and contributions. We are leading the development of this code base, and test builds and deployments daily.

There is also a managed offering in Azure called the Azure API for FHIR. This Platform as a Service (PaaS) FHIR server is backed by the open source project in this repository and it offers a turn key solution to provisioning a compliant, secure FHIR service.


More Information


This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

There are many other ways to contribute to FHIR Server for Azure.

See Contributing to FHIR Server for Azure for more information.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.

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

You can’t perform that action at this time.