Microsoft announces FHIR server for Azure to facilitate healthcare data exchange
One of the world’s biggest technology company, Microsoft Corporation has announced that Azure will be able to have access to FHR servers to have the improved data exchange in the healthcare industry.
Recently, Microsoft declared that Azure will have access to FHIR Server, which is Microsoft’s cloud computing service. Azure is an open source project on GitHub, and its main goal is to enable the exchange and organization of healthcare information in the cloud system. FHIR Server for Azure sells support set-up, for instance, the ability for role-based access controls and mapping to Azure Active Directory. In the first release of FHIR Server, Azure will have access to FHIR STU3, which is the present version of the FHIR API.
Cloud computing platforms and fast healthcare interoperability resources (FHIR) have begun to play a bigger role in removing the obstructions from the acceptance and implementation of technologies that can provide a good support for healthcare interoperability, mainly those that are supported by the cloud and AI.
For that reason, in August 2018, Microsoft joined hands with Amazon, IBM, Google, and other companies working on the goal to eliminate barriers for the adoption of technologies in healthcare.
In almost every aspect of the healthcare sector, the drive to build and deliver AI go beyond the tools accessible to deliver it. FHIR Server for Azure works as a solution to that problem. It offers a basis to manage that problem. While working with data in the FHIR format, developers can utilize the server to swiftly embrace and manage FHIR databases in a cloud setting, track and handle data access, and begin to standardize data for machine learning assignments.
FHIR Layers
As an open source project, FHIR Server for Azure has been built on logical separation, allowing the developers to have the flexibility to amend how it is applied, and spread its competencies as required. The logical layers of the FHIR Server are:
- Hosting Layer – It supports hosting services in different types of settings, with the help of custom structuring of Inversion of Control (IoC) containers.
- REST API Layer – It supports the application of the APIs which are defined by the HL7 FHIR specification.
- Core Logic Layer – It includes the application of the core logic of FHIR.
- Persistence Layer – It is a data persistence provider and allows the FHIR server to connect with virtually any data persistence function.
FHR Implementation
According to Microsoft, they want to have some exploration with FHIR. The future scenarios for cloud settings with FHIR are unlimited, and some of the top cloud scenarios for execution are:
- Scientific Research – Having data in FHIR formats can really help to speed up the normalization of data for scientists and researchers, and allow them to have much better control of data that will be needing to be shared across various groups. By facilitating RBAC and audit records, the use of an FHIR service allows data owners to enjoy more control over the sharing of data.
- Interoperability –Using FHIR APIs and FHIR services, the healthcare systems can enable interoperability and standardization of data between different systems to achieve compatibility.
- Internet of Medical Things (IoMT) – Start-ups and new device or application developers can store and share data with others in the FHIR format, assisting with quicker integration with provider and payer systems, for example transferring data to EHRs using FHIR APIs.
Image credit: www.cloudblogs.microsoft.com
