FHIRlink Connector Support for EPIC® on FHIR®
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.FHIRlink Power Platform connector Public Preview Release
Microsoft FHIRlink creates a direct connection between healthcare apps built on Microsoft Azure services and FHIR’s servers, bypassing the need to duplicate data from Microsoft Dataverse. FHIRlink reduces the complexity and cost of building low code/no code applications on Power Platform and Azure because developers can build their apps directly against the FHIR services rather than having to duplicate data between systems. Connect Power Automate Flows, Power Platform Canvas Apps, and Azure Logic Apps to various FHIR services and perform create, retrieve, update and delete operations directly on FHIR resources.Virtual Health Data Tables Create Update and Delete Support
Health organizations are considering low-code development to improve productivity, gain faster time-to-market, experiment more easily, and overall, be more agile when responding to market changes. A key blocker has been the inability to pull health data from multiple sources and manage it in a secure and compliant way. Microsoft Cloud for Healthcare includes configurable solutions to exchange data between Dataverse and external systems using the FHIR standard. Microsoft's Virtual Health Data Tables provides the ability to connect directly to Azure Health Data Services FHIR service from within Dataverse. As part of the latest release, Virtual Health Data Tables has been updated to include support for the create, update, and delete FHIR operations.
FHIRlink Power Platform connector General Availability
Microsoft FHIRlink creates a direct connection between healthcare apps built on Microsoft Azure services and FHIR’s servers, bypassing the need to duplicate data from Microsoft Dataverse. FHIRlink reduces the complexity and cost of building low code/no code applications on Power Platform and Azure because developers can build their apps directly against the FHIR services rather than having to duplicate data between systems. Connect Power Automate Flows, Power Platform Canvas Apps, and Azure Logic Apps to various FHIR services and perform create, retrieve, update and delete operations directly on FHIR resources.FHIRlink connector and Epic on FHIR for Power Platform development
The FHIRlink connector for Power Platform enables direct access to FHIR based endpoints. In this post, we look at a working sample application that connects Dataverse with Epic on EPIC® on FHIR® and Azure OpenAI to provide patient details and AI support for clinical users.
Medical Device Management System
I have designed a Medical Device Management System that can be hosted as follows The Medical Device Management System can be used: BizTalk On-premise – only BizTalk On-premise – Azure Hybrid Azure only Open source On-premise – only Open source On-premise – Azure Hybrid BizTalk Server 2020 is able to receive device twins and transform them into HL7 FHIR Observation Resources. I have developed an MQTT adapter which allows BizTalk to become an Edge Device. In addition, I am developing PowerShell and SSH adapters. I am using the open-source Azure FHIR Server. The solution is in Alignment with the SDPi+FHIR Device Interoperability Project ➢ Application of IEEE 11073 Service-oriented Device Connectivity (SDC) standards with HL7 FHIR to support medical and health device interoperability across multiple use contexts and applications that interact with and consume information from devices. ➢This includes regulated (medical) and non-regulated (health) devices. ➢ Software as a Medical Device (SAMD) and health apps are to be supported. Device informatics/interoperability standardization has been progressing in parallel within HL7 Devices, IHE Devices, and IEEE 11073 Standards Committee. ➢ Although these efforts are generally well-coordinated, there is an increasing need to ensure strong linkages between the specifications, especially between FHIR and IEEE 11073 SDC. ➢The latter is tailored for the most acute, medical-grade device connectivity applications (e.g., operating room and ICU), including service-oriented plug-and-play and medical content reporting, alerting, and external control (including closed-loop clinical apps/SAMD). ➢ FHIR supports interoperability across the broad landscape of health information exchange, including the integration of device-sourced content and services. ➢This project ensures the coordinated and cohesive development of FHIR profiles, extensions and implementation guides, as well as SDC-based IHE profiles to enable the next generation of device interoperability standardization The following is a high-level diagram of the on-premise version.
