This article details the technical specifications of the 'FHIR Destination,' designed for sending resources to a FHIR server. It natively supports resource creation, updates, and transaction bundle operations, providing structured error handling and validation based on FHIR semantics.
AIRIS introduces a gamified approach to physical therapy and rehabilitation. It utilizes AI-supported 3D movement recognition to make the patient's body the control mechanism, combining movement and learning through visual tasks to support motivation and functional recovery.
WHO released the WHO GDHCN Key Usage ValueSet (DEV - Testing) as part of the SMART Trust v1.7.2 release. This experimental ValueSet is defined using FHIR v5.0.0, providing definitions for specific usage keys crucial for global health data exchange.
This paper proposes two complementary pattern languages to address inconsistent outcomes in FHIR-based health information exchange (HIE). These languages guide both the authoring of FHIR artifacts (profiles, terminology, IGs) and the implementation of large-scale distributed FHIR systems, promoting reuse and making trade-offs explicit.
MedX offers a platform built on a single FHIR data store. It integrates four core pillars—Automation, Assistant, Registry, and Workspace—to ensure data flows seamlessly from devices and labs to clinical intelligence and analytics systems.
Apple has published comprehensive guidelines for healthcare organizations to provide verifiable health records to the Apple Health app via FHIR API. This includes registration processes, technical requirements, and procedures for data sharing opt-in/opt-out.
WHO released the SMART Trust Implementation Guide (IG) v1.7.2. This update continues the continuous evolution of the guide, which is based on FHIR 5.0.0, ensuring the standardization of digital health interoperability across various domains.
mcp-fhir is an implementation that applies the Model Context Protocol (MCP) to the FHIR standard. This allows developers to programmatically access FHIR data through the MCP, simplifying system integration.
When hospitals process high volumes of clinical data (HL7/FHIR), API delays can cause significant issues like delayed lab results or message queue backlogs. This guide details technical strategies for stabilizing and accelerating API endpoints under heavy load.
Cambio Healthcare Systems has published its COSMIC clinical data as an open API based on the FHIR R4 standard. This API covers over 24 FHIR resource types, including Patient, Condition, and Medication, aiming to enhance healthcare data interoperability.
eMicro aims to build data interconnection infrastructure based on the international standard HL7 FHIR to solve data fragmentation between medical equipment and systems. This eliminates manual transcription at the clinical site, establishing a real-time data flow that supports care.
eMicro offers the "DRIVE Gateway," a data hub for medical equipment, based on the international HL7 FHIR standard. It integrates data from various bedside devices—including ventilators, ICU monitors, and dialysis machines—into electronic health records, aiming to accelerate clinical decision-making and improve care accuracy.
Regenstrief Institute and West Coast Informatics announced a partnership to support LOINC development and distribution. WCI will utilize its TermHub platform to deliver LOINC content via FHIR services, making the standard more accessible to the global implementer community.
As FHIR adoption accelerates, the workforce needed to implement and govern it is not scaling fast enough. Estimates suggest a massive capability gap, requiring hundreds of thousands of new skilled professionals globally by 2031.
Health Gorilla has published an open collection for the DocumentReference API based on the FHIR R4 standard. This API supports interoperability in the healthcare sector, specifically aiding in the management of clinical data and lab results.
A FHIR Bundle resource was retrieved, defining the history of the 'OMOP Concepts - Visit Type vocabulary' ValueSet. This vocabulary set is active and managed under version v5.0-27-FEB-26.
This tool allows users to visualize FHIR resources. Users can paste or upload FHIR JSON and view the data in multiple formats, including a human-readable Clinical View, summaries, and resource graphs.
FHIR R4 conformance is a closed specification limited to the functionality described in the CapabilityStatement and is claimed, not awarded. The article details technical requirements for developers, including resource maturity markers (FMM 0-3) and version management considerations.
BritonOne Technology provides comprehensive healthcare software solutions, including EHR integration, clinical AI, and population health data management. They support standards like FHIR R4 and HL7 v2, demonstrating capabilities across multiple jurisdictions (UK, US, EU).
Research efforts include OjasRaksha, which built a synthetic, privacy-preserving decentralized healthcare dataset using HL7 FHIR R4 and ICD-10-CM. Additionally, ArogyaLake presented a serverless lakehouse architecture for resource-constrained areas, natively emitting ABDM-conformant HL7 FHIR R4 payloads.