Events
Power BI DataViz World Championships
Feb 14, 4 PM - Mar 31, 4 PM
With 4 chances to enter, you could win a conference package and make it to the LIVE Grand Finale in Las Vegas
Learn moreThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
The healthcare industry is rapidly moving to adopt the emerging HL7 FHIR® standard. The Fast Healthcare Interoperability Resources (FHIR) standard defines an extensible data model with standardized semantics and data exchange that enables interoperability and rapid exchange of data in applications. Microsoft Health and Life Science's FHIRlink connector is a first-party Power Platform FHIR connector that enables Power App developers to build low-code, no-code applications that interact directly with FHIR data. The connector supports multiple authentication methods for enhanced security. It simplifies FHIR service authentication, query construction, and handling FHIR data, eliminating the need for custom single-use integration solutions.
The feature includes the following key benefits:
This article provides an overview and instructions for accessing and setting up your connections for FHIRlink. To learn more about other first party connectors that you can use with FHIRlink when building complex healthcare applications on Power Platform, see Connector reference overview.
Ensure you have the following prerequisites in place:
The connector supports the following authentication methods:
After you create the connection, you can use it in one or more of your Canvas Apps, Power Automate Flows, or Azure Logic Apps.
Note
FHIR® (owned by Health Level Seven International), Google™ (owned by Google LLC), and Epic® (owned by Epic Systems Corporation) are registered trademarks. The usage of these trademarks on this page doesn't constitute endorsement by Health Level Seven International, Google, or Epic Systems.
This option can be used when you connect to the Azure Health Data Services Azure API for FHIR. The authentication method needs the following two values:
https://{{fhirservicename}}.fhir.azurehealthcareapis.com
.https://{{fhirservicename}}.fhir.azurehealthcareapis.com
.This connectivity option requires the following setup:
Microsoft Entra user account.
Appropriate role permissions granted to the user account over the Azure Health Data Services FHIR service. For example, the FHIR Data Reader role.
For more information about access configuration, see Configure Azure RBAC for FHIR.
Note
Subsequent FHIRlink connector releases will include the ability to connect to Azure Health Data Services FHIR service using a registered service client applications and OAuth, supporting a shared connection.
This option can be used when you connect to Google™ Cloud Healthcare API. The authentication needs the following three values:
https://healthcare.googleapis.com/{{fhirservicepath}}/fhir
.For more information on setting up OAuth in Google™ Healthcare Cloud, see Create an OAuth Client Application in Google™.
This option can be used when you connect to Epic® on FHIR® FHIR APIs. The authentication needs the following values:
https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4
.Note
The current FHIRlink connector release supports Epic® on FHIR® application registrations configured with an application audience of the type Patient, Clinicians, or Administrative Users. We haven't yet implemented support for application audiences of the type Backend Systems.
The Epic® on FHIR® APIs support access to a select set of FHIR resources. However, each FHIR resource may support different operations and FHIR versions. For example, some FHIR resources may support read and search operations, while others may support read, search, and create operations.
Invoking unsupported operations results in errors from the Epic® on FHIR® services, with the appropriate OperationOutcome values returned that can be handled by the caller.
For a full list of supported FHIR resources, versions, and operations, you can explore Epic® on FHIR®.
When you create your Epic® on FHIR® app registration, include the following Redirect URI entry: https://global.consent.azure-apim.net/redirect/fhirlink
For detailed guidance on setting up an Epic® on FHIR® app registration and the available options, see App Creation & Request Process.
Subsequent FHIRlink connector releases will include expanded support for Epic® on FHIR® connectivity.
To learn more about the connector reference and how to use it, see FHIRlink connector. For a list of supported operations, go to FHIRlink connector actions.
The FHIRlink connector release provides samples for how to use the connector within a simple Power Platform canvas app. These examples explained step-by-step are intended to build on each previous sample. However, you can also use them individually as needed.
Each sample provides a downloadable completed solution. To review the samples, go to:
The samples provided assume completion of the following steps:
Events
Power BI DataViz World Championships
Feb 14, 4 PM - Mar 31, 4 PM
With 4 chances to enter, you could win a conference package and make it to the LIVE Grand Finale in Las Vegas
Learn moreTraining
Module
Build an app by using the FHIRlink connector - Training
Learn how to build an app from Power Apps by using the FHIRlink connector in Microsoft Cloud for Healthcare.
Certification
Microsoft Certified: Power Platform Functional Consultant Associate - Certifications
Demonstrate the use of Microsoft Power Platform solutions to simplify, automate, and empower business processes for organizations in the role of a Functional Consultant.
Documentation
Overview of data integration toolkit - Microsoft Cloud for Healthcare
Learn how the data integration toolkit connects patient-consented EHR data to Dataverse.
Overview of virtual health data tables - Microsoft Cloud for Healthcare
Learn what the virtual health data tables are and how they enable interoperability between different data sources.
Manage FHIR data using data integration toolkit - Microsoft Cloud for Healthcare
Learn how the data integration toolkit components simplify managing and working with FHIR data.