This post has been republished via RSS; it originally appeared at: Healthcare and Life Sciences Blog articles.
As Healthcare organizations look to modernize legacy applications, they face many barriers such as conforming to complex industry standards and adopting new cloud-based technologies. By leveraging the power of the Microsoft Cloud for Healthcare and the Microsoft Power Platform, you can rapidly innovate your application estate. We have released updates to our Virtual Health Data Tables, which enables customers to leverage no-code and low-code to build health applications while also simplifying the complexities of the Health Level 7 (HL7) Fast Healthcare Interoperability Resources (FHIR) standard.
Dataverse solutions often require complex integrations between systems. For example, Microsoft Cloud for Healthcare provides integration capabilities via our Dataverse Healthcare APIs. Virtual health data tables in Microsoft Cloud for Healthcare also provides an option for customers not wanting to move data between systems, or only selectively sync some of these records.
Dataverse includes the Virtual tables feature that enables surfacing records within Dataverse from external sources like Azure Health Data Services. Virtual health data tables extend this feature via a custom virtual table provider for FHIR-based data. This custom provider includes additional capabilities for dynamically switching the data source between FHIR endpoints and Dataverse, via a capability called Data routes.
Until recently, Virtual health data tables only supported read-only access to the external FHIR services. While you could retrieve Encounters related to a Patient in Microsoft Cloud for Healthcare from a remote FHIR service, you could not update the data back into the Azure FHIR services.
With the latest release of Microsoft Cloud for Healthcare, Virtual health data tables supports Create, Update and Delete events for both root level FHIR resource tables and expansion tables (nested elements within the FHIR resource). For example, you can update both an Allergy/Sensitivity (Allergy Intolerance) record and a related Allergy Sensitivity Reaction record and these values will be saved back to the Azure FHIR services.
As with standard virtual tables, security roles allow you to control which operation is permitted on a virtualized table, meaning you can restrict Create, Update, or Delete operations on one or more tables as your solution requires. Our Attribute Maps include an additional field named FHIR Required Attribute that ensures the update conforms with the HL7 FHIR specification.
Watch this feature in action:
This update adds another tool to the Microsoft Cloud for Healthcare platform that enables Microsoft, our partners, and our customers to build enterprise scale healthcare business applications.
Learn more about Microsoft Cloud for Healthcare and Virtual health data tables: