AGENTS.md - microsoft/fhir-server · GitHub
Microsoft FHIR ServerリポジトリにAGENTS.mdが追加（Azure Cosmos DB・SQL Server対応、FHIR R4/R5/STU3準拠）。
News
Search results for "Azure": 48 articles
「自分の病院アカウントにAIエージェントのOAuthアクセスを許可してみた」— SMART on FHIR連携が一発成功
Paul J. Swider氏が、自分自身の病院ポータルに対してAIエージェントにOAuthアクセスを与え、SMART on FHIRハンドシェイクを実行させた個人実験を報告した。エージェントは患者プル形式の暗号化ペイロードを復号し、医療履歴一式をAzure上のLinux環境へ取得することに初回試行で成功したという。
FHIR Integration Services for Azure Health Data - QServices
exchange time and reduce compliance risk. See how .
PQT Health and Serene Intelligence Announce Strategic Partnership to bring AI-Powered Prior Authorization to Dyvine EHR®
米国のDyvine EHR開発企業PQTヘルスと、AI医療収益サイクル管理企業セリーン・インテリジェンスが戦略的提携を発表。Microsoft AzureのFHIR対応インフラ上に構築されたDyvine EHR®に、AI主導の事前承認管理および否認対応機能を直接統合し、地方・医療資源不足地域の医療機関向けに自律型収益サイクル管理を実現する。
PQT Health and Serene Intelligence Announce Strategic Partnership to bring AI-Powered Prior Authorization to Dyvine EHR®
米PQT Healthと医療AI企業Serene Intelligenceが提携し、電子カルテ「Dyvine EHR」に自律型の事前承認・請求拒否対応機能を統合すると発表した。FHIRに対応したAzure基盤上で動作し、地域の診療所や病院向けにAI主導の収益サイクル管理を提供する。
Microsoft introduces Azure IoT Connector for FHIR to enhance RPM security.
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.
MicrosoftFHIRAzure IoT
Microsoft supports US core profiles within Azure FHIR service
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.
MicrosoftAzure
Microsoft enables FHIR data export from Azure Health Data Services to Fabric OneLake
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 FabricAzure Health Data ServicesFHIR
Microsoft plans to enable FHIR R5 support within Azure services.
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.
MicrosoftAzure
Securing FHIR Access Using Azure Role-Based Access Control (RBAC)
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).
AzureFHIR
Guidance on securing healthcare applications using Azure API for FHIR.
Guidance is available on securing healthcare applications using Azure API for FHIR. This process involves registering a confidential client to safely access healthcare data.
Azure API for FHIR
TBO Health manages FHIR CDR using Azure Health Data Services
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.
Azure Health Data Services
Pueblo Chieftain implements FHIR-ready EHR using Azure for rural healthcare.
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.
PQT HealthMicrosoft Azure
IntuitionLabs implements HL7 FHIR standard on Microsoft Azure.
IntuitionLabs developed an implementation of the HL7 FHIR standard. This solution is optimized for deployment within the Microsoft Azure cloud environment.
HL7Microsoft Azure
Sonata Health and Life Sciences assesses data interoperability using FHIR standards.
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.
Sonata Health and Life SciencesMicrosoft
API Management routing issue observed when integrating with FHIR backend
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.
Azure API Management (APIM)FHIR
Microsoft reports Azure FHIR Service transaction failure error.
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.
AzureFHIR
Assessment of FHIR Interoperability using Azure Health Data Services
The assessment focused on achieving compliant healthcare data interoperability. This utilized Azure Health Data Services and involved FHIR standards.
Sonata Health and Life Sciences conducts FHIR data interoperability POC using Azure Health.
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.
Sonata Health and Life SciencesMicrosoft
Demonstration of Smart Patient Risk Scoring using FHIR R4 and Azure OpenAI
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.
.NET 8FHIR R4Azure OpenAISQLite