The core mission in healthcare is to deliver better health outcomes, and the data standard fueling the future of that mission is FHIR. The Fast Healthcare Interoperability Resource (FHIR) has revolutionized the industry in the last several years and has become established as the preferred standard for exchanging and managing healthcare information in electronic format. Particularly, with the ONC’s Cures Act Final Rule requiring the use of FHIR to enable data interoperability. Microsoft understands the unique value FHIR offers to enable management of Protected Health Information (PHI) in the cloud, so we’re advancing Azure technology to enable our health customers the ability to ingest, manage, and persist PHI data across the Azure environment in the native FHIR format.
FHIR Server for Azure is an open-source implementation of the emerging HL7 Fast Healthcare Interoperability Resources (FHIR) specification designed for the Microsoft cloud.
Health Architectures is a collection of reference architectures and, when appropriate, implementations. They illustrate end-to-end best practices for using the Azure API for FHIR and related technologies. Below is the holistic conceptual end to end architecture for Azure API for FHIR.
Microsoft has expanded its portfolio with new open-source software (OSS) and connectors which will help customers at different stages of their journey to advance interoperability and secure exchange of protected health information (PHI):
The FHIR Converter is an open source project that enables the conversion of legacy formatted health data to FHIR, expanding the use cases for health data and enabling interoperability.
The FHIR Converter transforms HL7 v2 messages and C-CDA documents into FHIR bundles using templates that define the mappings between the two data formats. Leveraging the FHIR Converter, organizations can customize or create their own mapping templates based on their HL7 v2 or C-CDA implementation and transform them into FHIR bundles. These FHIR bundles are returned for further data manipulation or can be immediately persisted into a FHIR server.
FHIR Tools for Anonymization is an open-source project that helps de-identify healthcare FHIR data, on-premises or in the cloud, for secondary usage such as research, public health, and more.
The core engine allows for the use of a configuration file specifying the de-identification settings to help anonymize the data. The project includes a command-line tool that can be used on-premises or in the cloud to anonymize data. It also comes with a tutorial and script to create an ADF pipeline that reads data from Azure blob store and writes anonymized data back to a specified blob store.
The Internet of Medical Things (IoMT) is the subset of IoT devices that capture and help to securely transmit patient health data. It represents one of the largest technology revolutions changing the way we deliver healthcare. The IoMT FHIR Connector for Azure is an open-source project for ingesting data from IoMT devices and persisting the PHI data in a FHIR server. The goal of this Microsoft Healthcare project is to enable developers to Ingest, normalize, and transform data from health devices into FHIR.
Connect FHIR APIs to the Power BI platform for analytics and visualization. With the Power BI FHIR Connector, you can pull data from any FHIR server and ingest it into Power BI and start leveraging it in your research teams, to support decision making, for alerting or dashboards or embedded in mobile tools.
Power BI Dashboard created using FHIR Data
Azure API for FHIR offers exchange of data via a FHIR API and a managed Platform as a Service (PaaS) offering in Azure, designed for management and persistence of PHI data in the native FHIR format.
Access to Diagnostic Logs is essential for any healthcare service where being compliant with regulatory requirements (like HIPAA) is a must. The feature in Azure API for FHIR that supports this is Diagnostic settings in the Azure Portal UI.
The open source FHIR Server for Azure supports both Azure Cosmos DB and SQL backed persistence providers. With the SQL persistence provider, developers will be able to perform complex search queries that join information across multiple FHIR resource types and leverage transactions.
FHIR® is the registered trademark of HL7 and is used with the permission of HL7.