FHIRlink connector and Epic on FHIR for Power Platform development

This post has been republished via RSS; it originally appeared at: Healthcare and Life Sciences Blog articles.

In a recent Healthcare and Life Sciences Blog post, the Health and Life Sciences Data Platform team announced our first release for support for EPIC® on FHIR® connectivity in the to the FHIRlink Power Platform connector.  This post covered the basics of our first release, and in this post, we dive into an example built by our colleagues in the Business Applications team in Australia. 

Jarrod Huang and Daniel Xu developed an example Canvas app using the FHIRlink connector to interact with the EPIC® on FHIR® rest endpoints to provide direct access to Patient data from Power Platform.

Extend EMR with Low Code

Enterprise EHR systems offer a wide range of capabilities, but they can be challenging to extend for targeted experiences.  The Power Platform offers a variety of low code/no code platform tools to build line of business applications.  The FHIRlink connector helps bridge the gap by enabling our customers to build business applications that connect directly to their FHIR endpoints, reducing the need for data duplication and other complex integration solutions. 

Connecting Power Platform and your EHR addresses unique operational challenges by leveraging your EMR data and customized apps.  For example, your Power Platform business application may equip care teams with simplified, digitized task management as an extension of EMR.

The Sample Application

The example developed by Jarrod and Daniel includes a Canvas app using the FHIRlink connector and the Epic on FHIR sandbox.

 

jimnovakms_0-1726238951958.png

 

As a Power App, you have access to over 1000 existing connectors and the ability to develop your own custom connectors for proprietary systems.  In the example scenario, the application connects a list of patients in Dataverse with their corresponding Epic on FHIR record.

Once you have the correct patient identifier, you can then retrieve related patient data using the Epic on FHIR endpoints.  In the sample application, this means selecting a patient from the list invokes a call to the Epic on FHIR rest endpoint, offering a near real time view of the patient record in the EHR.

FHIR data and AI

Once you have the patient record, you can leverage Microsoft’s OpenAI capabilities using the Azure OpenAI connector.  A patient record can include large amounts of complex data, even formatted for end users, as seen in the sample application. This complex FHIR data can be summarized using the OpenAI’s capabilities, highlighting key elements for a simplified view for the clinician.

Check out the video below for a demonstration of Jarrod and Daniel’s example application in action.

As we continue to invest in FHIRlink, we will provide ongoing learning opportunities for our customers and partners through the Health and Life Sciences blog. In the meantime, we welcome your feedback in the comments section.

FHIR®, Google and Epic® are registered trademarks owned, respectively, by Health Level Seven International, Google LLC, and Epic Systems Corporation. The use of these trademarks on this page does not constitute endorsement by Health Level Seven International, Google, 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.