This free half-day briefing discusses how to modernize existing healthcare applications quickly and flexibly by leveraging Microsoft Azure. The focus is placed on cloud migration and integration opportunities for industry standards like FHIR and HL7.
Onyx Technology offers OnyxOS, an HL7 FHIR-based interoperability platform. This enables health plans and Medicaid state agencies to comply with the CMS-9115 Patient Access Rule and related interoperability requirements.
Microsoft released FHIR Server version 1.0.822. This update includes several critical changes for the Azure API for FHIR, such as increasing search query limits and implementing standard headers.
MicrosoftใฏใFHIRใตใผใใผ๏ผmicrosoft/fhir-server๏ผใฎใใผใธใงใณ4.0.25ใใชใชใผในใใพใใใๆฌใขใใใใผใใงใฏใAzure API for FHIR (Cosmos) ใใใณ Azure Health Data Services (SQL) ใฎไธกๆนใงๆฉ่ฝๆนๅใ่กใใใพใใใ
Microsoft released build 20181031-1 of the fhir-server, implementing key improvements such as Role-Based Access Control (RBAC) and defining complex search parameters. These updates enhance the robustness and extensibility of the FHIR server, improving its utility in healthcare data interoperability.
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 object (`SmartIdentityProviderConfiguration interface`) used to configure the Identity Provider for SMART on FHIR authentication. This configuration allows specifying multiple applications and the token issuing authority.
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 article details the implementation process for data conversion using the $convert-data endpoint of Azure Health Data Services. It provides concrete API calling methods and sample code for converting non-FHIR data (e.g., HL7v2) into FHIR format.
This article introduces a sample application that utilizes the FHIRlink connector for Power Platform, integrating Dataverse, Epic on FHIR, and Azure OpenAI. This setup enables the provision of patient details and AI support to clinical users.
In data exchange, not all resource references are guaranteed to point to a valid FHIR resource. Specifically, when references are used as business identifiers or simple display strings across different systems, they can cause unexpected issues during query execution.
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.