Search results for "Azure": 109 articles
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.
Microsoft Azure has published the `HealthcareFhirResourceUpdatedEventData` interface for handling event data when a FHIR resource is updated. This enables standardized tracking and interoperability of medical data change history across systems.
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 details the usage of the `Get-AzHealthcareIotConnectorFhirDestination` cmdlet in a Microsoft Azure environment. This function allows users to retrieve properties for a specified IoT Connector's FHIR destination.
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.
Microsoft updated the domain name for the FHIR resource account.
ๅฐ้ๅฎถใฏใๅธ่ฒฉใฎFHIRใตใผใใผใฏใใใพใงๅบ็บ็นใซ้ใใใๅฎ้ใฎ่จๅบใใผใฟๅฆ็ใ่กใใใใซใฏ็ฌ่ชใฎ่ฟฝๅ ้็บใๅฟ ่ฆใ ใจๆๆใ็นใซ้ซๅบฆใชใใธใในใญใธใใฏใใปใญใฅใชใใฃๆฉ่ฝใฎๅฎ่ฃ ใ่ชฒ้กใจใชใใ
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.
GetTech offers a solution for managing and exchanging healthcare data, including medical images, in the cloud using global standards like FHIR and DICOM. This enables faster diagnosis and support for advanced workflows.
Microsoft has published the latest technical information regarding its FHIR API. As the API is scheduled for deprecation on September 30, 2026, users are advised to migrate to the FHIRยฎ service within Azure Data Services Integrity. Furthermore, multiple bug fixes and performance enhancements were implemented in 2025, including improvements to $expand and re-indexing processes.