Azure FHIR Service

Introduction: This article is a continuation of the series of articles starting with the description of SignalR service which was followed by a discussion on Azure Gateway service, Azure Private Link, and Azure Private Endpoint and the benefit of diverting traffic to the Azure Backbone network. Then we started reviewing a more public internet-facing service such as the Bing API. and the benefits it provided when used together with Azure Cognitive Services. We then discussed infrastructure API such as Provider API, ARM resources, and Azure Pipeline and followed it up with a brief overview of the Azure services support for Kubernetes Control Plane via the OSBA and Azure operator. Then we followed it with an example of Azure integration service for Host Integration Server (HIS). We now discuss Azure FHIR service.

Description: 

The Azure Integration Service consisted of four components: – namely, APIs, Orchestrations, Messaging, and Events.  They are represented by Azure resource such as API management, Logic Apps, Service Bus, and Event Grid. There is also a fifth component when it comes to healthcare. This is the Fast Healthcare Interoperability resource or the FHIR service, which is a managed, standards-based compliant API for clinical health data. It powers solutions and analytics and makes it easy for anyone working with health data to ingest, manage, and persist protected health information (PHI) in the cloud. It is enterprise grade and demonstrates high performance with low latency. It is accessible by mobile and web applications and has sufficient role based-access control to secure all accesses universally. Audit log has significant emphasis and this service and tracks all activities per data store.

As with any data access layer, this service provides a flexible data model for the PHI data with standardized semantics and data exchange that enables easy interoperability with other applications. Data transfer to FHIR enable universal connectivity and exchange because of the standard definitions. The exchange is rapid due to the power of Azure.

The FHIR service allows the exchange of data via its APIs. As with all Azure APIs, the programmability can be exercised via REST based services, PowerShell, CLI and SDKs.  In addition to data access, FHIR service focuses on all industry compliance requirements for PHI data. 

The data is secured with unparalleled intelligence and customer’s data are isolated by databases providing all controls at the database level. The security features are provided by a layered, in-depth defense and advanced threat protection system.

This service is used by startups, devices such as IoT and application development simply because it is a fully managed data management service for PHI data. Healthcare ecosystems can be built on this service as the source of truth. The FHIR data model is not only suitable for conventional, transactional and analytical purposes but also for deep learning. As part of the PaaS offerings, it becomes invaluable for turn-key production ready solutions.