This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
The Health and Life Sciences Data Platform team recently released an update to the FHIRlink connector introducing support for EPIC® on FHIR® connectivity. This is our initial release of connectivity for EPIC® on FHIR® application registrations configured with an application audience of Patient or Clinicians/Administrative Users.
Epic® on FHIR®
Epic® is a cloud-based Electronic Health Record (EHR) solution widely used in the healthcare industry and across the globe. Epic® on FHIR® is the integration of Epic's electronic health record (EHR) system with the Fast Healthcare Interoperability Resources (FHIR®) standard. These REST endpoints enable Epic customers to exchange data with FHIR enabled systems. Healthcare organizations can then build targeted, interoperable applications while preserving Epic as the system of source critical healthcare data.
With FHIRlink’s additional support for Epic® on FHIR®, it means building low code Canvas Apps and Power Automate Flows on Power Platform or Azure Logic Apps that connect directly to Epic®, extending capabilities not readily available in the current solution.
Connecting to Epic
With the latest update, the FHIRlink connection options includes an additional item for connectivity under the Authentication Type dropdown.
Once selected, the new connection dialog prompts for Epic® on FHIR® specific parameters that are defined when setting up the application registration. For example, you will provide the URL to your Epic® on FHIR® endpoint. Once these settings are provided, you will provide consent for your user that has access to the Epic® on FHIR® APIs. This consent will align with your application registration and resources available to the Epic® on FHIR® user.
You can find the full connection details on the Microsoft Learn site at Bring your own EPIC® on FHIR® application
Available Operations
The FHIRlink connector operations conform to the HL7 FHIR specifications. This means the available operations are the same across all Authentication Types. Although FHIRlink makes the same call for each operation, each system to which you connect may implement these endpoints a bit differently.
The EPIC® on FHIR® APIs support access to a large set of FHIR resources. However, some FHIR resources may offer 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 the detailed documentation available online and test the FHIRlink connector using the sandbox available at EPIC® on FHIR®.
More to come
The latest updates are our first investment in providing connectivity to Epic® on FHIR® but not the last. In future releases, we are investigating support for shareable connections and additional connectivity options with Epic on FHIR, such as application registrations with Backend Systems application audience types.
As we continue to invest in FHIRlink, we will continue to provide learning opportunities for our customers and partners via the Health and Life Sciences blog. In the meantime, we welcome any feedback through the comments section.
FHIR®, Google and Epic® are registered trademarks owned, respectively, by Health Level Seven International and Epic Systems Corporation. The use of these trademarks on this page does not constitute endorsement by Health Level Seven International or Epic Systems.