Microsoft released a specific build (20190926-1) of the FHIR server. This update includes improvements such as better handling of API notification errors and an upgrade to the .NET Core SDK.
Microsoft released fhir-server version 2.0.13. This version includes several key improvements related to search functionality and data synchronization, such as support for the $member-match operation required by the CMS Interoperability and Patient Access Rule, and enhanced logging for reindexing processes.
Microsoft released FHIR server build 20200723-1. This version includes multiple significant fixes and feature additions, such as enabling pod identity for AKS deployments and updating health check code references.
AirGate Technologies offers an integrated data analytics solution utilizing Azure Synapse and FHIR Store. This enables healthcare providers and payers to centralize analysis of data scattered across different systems, aiming for personalized care delivery and cost reduction.
DataArt offers a proprietary accelerator approach to extend existing EHR solutions with SMART on FHIR capabilities and FHIR API, helping healthcare companies comply quickly with new regulations. This solution is built on Azure cloud to accelerate development.
Microsoft provides an overview detailing the regional availability of services and features within Azure Health Data Services. The availability of interoperability resources like FHIR varies by region, and users are warned that Azure API for FHIR will be retired on September 30, 2026, necessitating proactive migration.
This article defines the `IotFhirDestinationCollection` interface, which handles FHIR-based destinations for IoT Connectors within an Azure environment. This interface provides a structure to manage multiple FHIR destinations for IoT data linkage, offering developers a technical reference point necessary for implementation.
This page provides a practice test for the "HL7 FHIR STU3 Proficiency," offered by HL7. The test is designed to assess proficiency in knowledge based on a specific version (v2025-03-10).
This article explains how to manage the linkage settings between an IoT Connector and a FHIR target in a Microsoft Azure environment using PowerShell cmdlets. Developers can use the `Get-AzHealthcareIotConnectorFhirDestination` command to retrieve existing FHIR destination properties based on details like resource group or workspace name.
This article reviews various API platforms utilizing FHIR, a standard for fast healthcare data exchange. It introduces solutions from major cloud vendors like Google Cloud, Microsoft Azure, and AWS, which aim to improve interoperability and enable patient-centric care.
This article introduces ten essential open-source tools for 2025, built upon the FHIR standard. These tools provide developers with robust foundations necessary to implement and manage scalable FHIR solutions.
Microsoft is promoting seamless interoperability of medical data using FHIR and DICOM services. This enhances patient care, improves operational efficiency, and enables advanced analytics, accelerating the transformation toward digital healthcare.
This document describes the `FhirServiceCollection interface` for Azure environments. It outlines a structure used to access multiple FHIR services through a single collection.
This guide details the technical process of collecting, transforming, and storing Internet of Medical Things (IoMT) device data into a FHIR format destination using Microsoft Azure. It serves as a technical reference for achieving standardized medical data storage and system interoperability.
Sonata Health offers a data interoperability assessment service leveraging Azure Health Data Services based on FHIR standards. This solution aims to support the integration of diverse systems within the healthcare and life sciences sectors.
This article explains how to manage FHIR services within the Microsoft Azure environment. Specifically, it provides procedures and syntax for safely deleting deployed FHIR services using the PowerShell cmdlet `Remove-AzHealthcareFhirService`.
Microsoft Azure's FHIR servers are forgiving regarding non-conforming data because resource creation and update validation is off by default. However, some validation still occurs for specific elements, and enabling profile validation requires explicit header settings, necessitating caution about potential operational surprises.
This article explains how companies can utilize DrapCode to integrate Microsoft FHIR APIs, enabling real-time healthcare data exchange and workflow streamlining. It facilitates the construction of secure systems compliant with FHIR standards.