Edit

Share via

What is the FHIR service?

  • Article

The FHIR® service in Azure Health Data Services enables rapid exchange of health data using the Fast Healthcare Interoperability Resources (FHIR) data standard. As part of a managed Platform-as-a-Service (PaaS), the FHIR service makes it easy for anyone working with health data to securely store and exchange Protected Health Information (PHI) in the cloud.

The FHIR service offers:

  • Managed FHIR-compliant server, provisioned in the cloud in minutes
  • Enterprise-grade FHIR API endpoint for FHIR data access and storage
  • High performance, low latency
  • Secure management of Protected Health Information (PHI) in a compliant cloud environment
  • SMART on FHIR for mobile and web clients
  • Controlled access to FHIR data at scale with Microsoft Entra role-Based Access Control (RBAC)
  • Audit log tracking for access, creation, and modification events within the FHIR service data store

The FHIR service allows you to quickly create and deploy a FHIR server to the cloud for ingesting, persisting, and querying FHIR data. The Azure services that power the FHIR service are designed for high performance no matter how much data you're working with.

The FHIR API in the FHIR service enables any FHIR-compliant system to securely connect and interact with FHIR data. As a PaaS offering, Microsoft takes on the operations, maintenance, update, and compliance requirements for the FHIR service so you can free up your own operational and development resources.

Leverage the power of health data

The healthcare industry is rapidly adopting FHIR® as the industry-wide standard for health data storage, querying, and exchange. FHIR provides a robust, extensible data model with standardized semantics that all FHIR-compliant systems can use interchangeably. With FHIR, organizations can unify disparate electronic health record systems (EHRs) and other health data repositories – allowing all data to be persisted and exchanged in a single, universal format. With the addition of SMART on FHIR, user-facing mobile and web-based applications can securely interact with FHIR data – opening a new range of possibilities for patient and provider access to PHI. Most of all, FHIR simplifies the process of assembling large health datasets for research – enabling researchers and clinicians to apply machine learning and analytics at scale for gaining new health insights.

Securely manage health data in the cloud

The FHIR service in Azure Health Data Services makes FHIR data available to clients through a RESTful API. This API is an implementation of the HL7 FHIR API specification. As a managed PaaS offering in Azure, the FHIR service gives organizations a scalable and secure environment for the storage and exchange of PHI in the native FHIR format.

Free up resources to innovate

You can build and maintain your own FHIR server. However, with the FHIR service in Azure Health Data Services, Microsoft handles setting up server components, and ensuring all compliance requirements are met, so you can focus on building innovative solutions.

Enable interoperability

The FHIR service enables connection with any health data system or application capable of sending FHIR API requests. Along with other parts of the Azure ecosystem, the FHIR service forms a link between electronic health records systems (EHRs) and Azure's suite of data analytics and machine learning tools, enabling organizations to build patient and provider applications that harness the full power of the Microsoft cloud.

Control data access at scale

With the FHIR service, you control health data at scale. The FHIR service's role-based access control (RBAC) is based on Microsoft Entra identities management. You can grant or deny access to health data based on the roles given to individuals in your organization. The RBAC settings for the FHIR service are configurable in Azure Health Data Services at the workspace level. Workspaces simplify system management and help ensure your organization's PHI is safe within a HIPAA and HITRUST-compliant environment.

Secure healthcare data

Because it belongs to the Azure family of services, the FHIR service protects your organization's PHI with an unparalleled level of security. In Azure Health Data Services, FHIR data is isolated to a unique database per FHIR service instance and protected with multi-region failover. Plus, the FHIR service implements a layered, in-depth defense and advanced threat detection for health data.

Use cases for the FHIR service

FHIR servers are essential for interoperability of health data. The FHIR service is designed as a managed FHIR server with a RESTful API for connecting to a broad range of client systems and applications. Some of the key use cases for the FHIR service are as follows.

  • Startup app development: Customers developing a patient- or provider-centric app (mobile or web) can use the FHIR service as a fully managed backend for health data transactions. The FHIR service enables secure transfer of PHI. With SMART on FHIR, app developers can take advantage of the robust identities management in Microsoft Entra ID for authorization of FHIR RESTful API actions.

  • Healthcare ecosystems: Although EHRs are the primary source of truth in many clinical settings, it's common for providers to have multiple databases that aren’t connected to each other (often because the data is stored in different formats). Using the FHIR service as a conversion layer between these systems, organizations can standardize data in the FHIR format. Ingesting and persisting in FHIR format enables health data querying and exchange across multiple disparate systems.

  • Research: Health researchers use the FHIR standard because it gives the community a shared data model and removes barriers to assembling large datasets for machine learning and analytics. With the data conversion and PHI de-identification capabilities in the FHIR service, researchers can prepare HIPAA-compliant data for secondary use before sending the data to Azure Machine Learning and analytics pipelines. The FHIR service's audit logging and alert mechanisms also play an important role in research workflows.

FHIR platforms from Microsoft

FHIR capabilities from Microsoft are available in three configurations:

  • The FHIR service is a managed PaaS that operates as part of Azure Health Data Services. In addition to the FHIR service, Azure Health Data Services includes managed services for other types of health data, such as the DICOM service for medical imaging data, and the MedTech service for medical IoT data. All services (FHIR service, DICOM service, and MedTech service) can be connected and administered within an Azure Health Data Services workspace.

  • Azure API for FHIR is a managed FHIR server offered as a PaaS in Azure and is easily deployed in the Azure portal. Azure API for FHIR isn't part of Azure Health Data Services and lacks some of the features of the FHIR service.

  • FHIR server for Azure is an open-source FHIR server that can be deployed into your Azure subscription. It's available on GitHub at https://github.com/Microsoft/fhir-server.

For use cases that require customizing a FHIR server with admin access to the underlying services (for example, access to the database without going through the FHIR API), developers should choose the open-source FHIR Server for Azure. For implementation of a turnkey, production-ready FHIR API with a provisioned database backend (data can only be accessed through the FHIR API, not the database directly), developers should choose the FHIR service.

Next steps

Deploy the FHIR service

Note

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