3,748 FHIR-related articles (latest first)
This article addresses the problem of 'Interface Drift' in healthcare data flows, explaining an AI-driven approach for continuous monitoring and self-remediation. This capability detects semantic failures caused by changes in EHRs or interconnected systems, enabling safe and auditable corrections.
This document provides the FHIR profile mapping specification to support the EHR/KTC MVP Workflow (Phase 0 & Phase 1). It outlines implementation guidelines based on standards like US Core and IPS, targeting interoperability engineers and integration architects.
マット・フード氏が、ヘルスケア業界における大きな課題と、その解決策としてのFHIRについて講演した。本発表では、FHIRとは何か、どのような機能を持つのか、そしてそれが提供する可能性のある革新的な展望が紹介された。
ONCは、画像診断データの相互運用性確保のためRFI（情報提供依頼）を発行した。これは、従来のEHR中心の記録から脱却し、包括的な長期健康記録を実現するための重要な動きである。
Patient logistics platform VectorCare announced the launch of its Open API 2.0 and a strategic integration with Bambi, an NEMT platform. This allows clinicians to order transportation directly from their EHR, creating seamless data exchange and aiming to accelerate patient care.
This study developed and validated bidirectional data transformation rules between FHIR (Fast Healthcare Interoperability Resources) and OMOP Common Data Model (CDM) using the open-source platform TermX. This demonstrates a methodology supporting the secondary use of real-world health data within a patient-centered digital health paradigm.
VectorCare launched an Open API 2.0 and implemented a strategic integration with Bambi to enhance in-EHR capabilities.
Transcure is deploying medical billing experts to help meet the requirements of the 2026 HIPAA transition.
NHS Wales has published the definition of a ValueSet titled 'Cancer Staging TNM V8 Tumour Head and Neck Lip and Oral Cavity'. This resource provides standardized definitions based on FHIR for the TNM classification (Version 8) specific to certain tumour sites.
SL Core has published an Implementation Guide (IG) for 'SL Example' based on FHIR 4.0.1. This version is v0.1.0 and provides comprehensive definitions including various core resources and code systems.
FAH submitted comments to CMS regarding the draft proposal to transition from electronic clinical quality measures (eCQMs) to Fast Healthcare Interoperability Resources (FHIR)-based digital quality measures (dQMs). The organization stressed that this major redesign of hospital reporting infrastructure requires a careful and phased implementation.
Researchers emphasize that systematic data modeling is crucial for efficient, future-proof healthcare information sharing. They recommend that while HL7 FHIR excels in data exchange and interoperability, the appropriate standard must be chosen based on specific goals, such as analysis or organizational structure.
The French Agency for Digital Health (ANS) is holding two consultation sessions to establish FHIR implementation guides to ensure interoperability of medical devices. These focus on 'health measurements' and 'telemonitoring.'
ASCO recommended that the HHS adopt minimal Common Oncology Data Elements (mCODE) and Fast Healthcare FHIR standards.
This article explains the versioning process for FHIR Questionnaires, emphasizing its critical role in maintaining data integrity. Since Questionnaires are used to collect structured healthcare data, proper version control is essential for tracking changes and ensuring compatibility.
The core challenge in healthcare data is that clinical and administrative data remain separated across different systems, speaking different digital languages. Multiple mandates, such as CMS requiring FHIR APIs and the enforcement against information blocking, are driving integration. However, providers must guard against replacing two existing data silos with several new ones.
Small medical practices struggle to share information as patients move between multiple facilities. This article points out the problems of traditional HIEs and faxing, explaining how structured data exchange becomes possible using FHIR and SMART on FHIR.
This article explains how 'Practitioner' information—including healthcare providers, clinicians, and care team members—is structured and made available through an API based on the FHIR standard. It details how specific fields like names, identifiers (such as NPI), and qualifications enable the identification of practitioners and tracking of care teams.
Despite standards like FHIR, EHR interoperability often fails. The article argues that the failure is not due to missing standards but rather structural, economic, and operational challenges overlooked by vendors. These issues hinder data exchange and undermine care delivery.
Firely provides an official support SDK for HL7 FHIR on the Microsoft .NET (dotnet) platform. The article explains how to implement and select the appropriate SDK version, supporting multiple FHIR versions including R5 and R4B.