A .NET Core implementation of the FHIR standard.
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.
- Open Source Deployment: Describes how to deploy FHIR Server for Azure.
- PaaS Service Deployment: Describes how to deploy Azure API for FHIR.
- FHIR Postman tutorial: Describes how to access a FHIR API using Postman.
- Azure Active Directory Application Registrations: Describes how to configure Azure Active Directory (AAD) for use with FHIR Server for Azure.
- Authentication: Describes the authentication settings for the FHIR server and how to make use of it in development and test scenarios.
- Roles: Describes how the FHIR Server for Azure role-based access control (RBAC) system works.
- Search: Describes how search is implemented for the FHIR Server for Azure.
- Debugging: Describes how to debug FHIR Server for Azure using Visual Studio.
- Testing with Postman: Describes how to use Postman for testing FHIR Server for Azure.
- Azure API for FHIR documentation
- FHIR Server Samples Repo: A demo sandbox using the Azure API for FHIR.
- Features: This document lists the main features of the FHIR Server for Azure and Azure API for FHIR.
- Roadmap: This document provides a list of features that are planned or in development.
- Blog: FHIR Server for Azure, an open source project for modern healthcare
- Twitter: Health_IT
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 https://cla.microsoft.com.
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.
- Submit bugs and help us verify fixes as they are checked in.
- Review the source code changes.
- Engage with FHIR Server for Azure users and developers on StackOverflow.
- Join the #fhirforazure discussion on Twitter.
- Contribute bug fixes.
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 [email protected] with any additional questions or comments.
FHIR® is the registered trademark of HL7 and is used with the permission of HL7.