Microsoft announced the development of an Azure IoT Connector for FHIR. This tool aims to improve the security and integration of Remote Patient Monitoring (RPM) data.
Microsoft has implemented support for US core profiles within its Azure FHIR service. This feature addresses the need to identify specific FHIR artifacts from the US core 6.1 Implementation Guide.
Microsoft has provided functionality to export FHIR resources from Azure Health Data Services into Microsoft Fabric OneLake. This integration allows for the seamless movement and utilization of healthcare interoperability data within the Fabric platform.
Microsoft is addressing the need to enable FHIR R5 within its Azure scripting environment. This update relates to the use of the FHIR Service instance under Healthdata services.
The news describes securing FHIR access within the Azure cloud environment. This is achieved by implementing Azure Role-Based Access Control (RBAC) and specific IAM role assignments to manage FHIR roles (Reader/Writer/Exporter).
Guidance is available on securing healthcare applications using Azure API for FHIR. This process involves registering a confidential client to safely access healthcare data.
TBO Health implemented a solution for managing a FHIR Clinical Data Repository (CDR). This solution was built using Azure Health Data Services to create a logical data fabric.
Pueblo Chieftain has rolled out a new Electronic Health Record (EHR) system. This system utilizes a secure, FHIR-ready Microsoft Azure setup to improve healthcare services in rural areas.
IntuitionLabs developed an implementation of the HL7 FHIR standard. This solution is optimized for deployment within the Microsoft Azure cloud environment.
Sonata Health and Life Sciences conducted a one-week assessment focused on data interoperability using FHIR standards. This initiative leveraged Microsoft's Azure platform to enhance data exchange within their ecosystem.
An issue was observed where Azure API Management (APIM) returned a 404 error while the backend FHIR service successfully returned a 201 status code. This issue relates to routing within the API Management system.
Microsoft encountered a transaction failure error when using its Azure FHIR Service. The issue relates to roles such as FHIR Data Contributor or FHIR Data Reader.
Sonata Health and Life Sciences performed a 12-week Proof of Concept (POC) focused on data interoperability. This initiative utilized FHIR standards and Microsoft Azure Health within their ecosystem.
The demonstration showcases the integration of FHIR R4 standards with modern technologies like .NET 8 and Azure OpenAI. This combination enables the development of advanced, intelligent patient risk scoring tools.
WaferWire Cloud Technologies announced its Patient 360° solution designed for FHIR transitions. This tool helps organizations move from using the Azure API for FHIR.
The Smile CDR HAPI-FHIR server has been updated to support the Patient/$everything operation. This feature allows for enhanced data retrieval capabilities using FHIR standards.
Microsoft Azure introduced an FHIR MCP server designed for AI agents. This service enables secure, authenticated retrieval and searching of data from Azure Health Data Services FHIR servers.