FHIRlink Power Platform connector General Availability

This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .


Microsoft’s FHIRlink Power Platform connector is now rolling out General Availability (GA) to all regions.  FHIRlink is a first-party Power Platform connector that enables Power App developers to build low-code, no-code applications that interact directly with HL7 Fast Healthcare Interoperability Resources® compliant REST APIs.

With the GA release, Power App developers can now build production ready healthcare applications on Microsoft Power Platform without the requirement of complex synchronization and transformation of FHIR data across multiple systems.

FHIRlink’s GA release supports multiple FHIR service authentication options for flexibility and enhanced security:

In the coming weeks, we will be providing another update to support additional connectivity to FHIR services supporting OpenID.  This update will assist FHIRlink developers in connecting to Epic® on FHIR services from their Power Platform and Azure applications.

Key Benefits

Power Platform offers both professional developers and app makers a place for building enterprise scale line of business applications.  FHIRlink offers another tool for Power App developers to build healthcare focused applications for their users.  Some of the benefits that come with using FHIRlink:

  • Microsoft first party supported connector for use with Canvas Apps, Power Automate Flows, and Azure Logic Apps.
  • Direct FHIR services access from Power Platform and Azure.
  • Reduces complexity working with FHIR services APIs and resulting FHIR data.
  • Simplifies managing connectivity details for Power Platform applications.

FHIRlink can be used in conjunction with the more than 1000 existing first party connectors to build targeted experiences for their users.

Because FHIRlink is a first party Power Platform Connector, customers also benefit from the Microsoft Power Platform Connector infrastructure such as governance through automated DLP polices, access control with Azure Active Directory, and monitoring from the Power Platform admin console.

Supported Operations

FHIRlink aims to simplify working with FHIR services within Power Platform applications.  This means assisting Power App developers in constructing operations against the FHIR compliant REST APIs.  Some key operation examples available for building Power Automate Flows, Canvas Apps, or Azure Logic Apps:

  • List Resources – retrieve a full list of available records for a particular FHIR resource type.  For example, you may want to retrieve a list of Appointment records for a given Patient.
  • Get a Resource – Get a single record for a type of FHIR resource using the FHIR Id. This will return the full FHIR JSON.
  • Create a Resource – post a JSON payload to the FHIR service that represents a new FHIR record in the target service.

You can review the full list of available operations and connectivity details at the FHIRlink landing page.

We welcome your feedback on the FHIRlink connector in the comments below and look forward to hearing more real world use cases.  Watch for upcoming posts over the next few months diving into some real examples on how to leverage FHIRlink to build healthcare applications on the Power Platform.


“FHIR®, Google and EPIC® are registered trademarks owned, respectively, by Health Level Seven International and Epic Systems Corporation. Use of these trademarks on this page does not constitute endorsement by Health Level Seven International or Epic Systems.”

Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.