3,145 FHIR-related articles (latest first)
An enterprise interoperability platform was highlighted for its capabilities in HEDIS quality measure evaluation. This platform supports FHIR R4 compliance, facilitating advanced healthcare data exchange.
The news describes a hybrid architecture designed for a secured health information exchange. This architecture integrates FHIR standards with Blockchain and IPFS technologies to enhance interoperability and security.
HL7 International published a specification detailing the TTL representation for X12 Remittance Advice Remark Codes. This update integrates X12 standards into the FHIR Terminology Services, enhancing interoperability for financial transaction data.
A cross-version extension for MonetaryComponent.code has been defined for FHIR R5. This update allows for standardized handling of monetary component codes across different FHIR versions.
A cross-version extension for the Invoice line item price component code has been defined for FHIR R4. This extension updates the structure definition for billing and invoicing data.
The LOINC code 102832-3, related to Tea IgG Ab [Presence] in Serum, was documented on the FHIR Server. This documentation provides standardized terminology for allergy testing results within the FHIR framework.
A test case was developed for the CARIN BlueButton standard, focusing on basic FHIR Server Bundle operations. This demonstrates the capability to perform fundamental resource creation and testing using FHIR standards.
The paper describes the architecture and load testing methodology for a robust healthcare platform. This platform is built upon the established standards of HL7 FHIR.
Core health data, such as wishes regarding life-sustaining treatment and drinking/smoking status, are being included in medical records. This development aims to improve upon previous document-based exchange standards (CDA) by adopting a next-generation transmission standard applicable across various environments like apps and cloud.
FHIR.org has released a cross-version extension for the expectedSupplyDuration element in MedicationRequest.dispenseRequest. This update provides compatibility for the element across different FHIR versions, specifically addressing R2 and R3.
A FHIR Server SNOMED CT Browser was made available. This tool integrates FHIR standards with SNOMED CT terminology.
Information regarding LOINC Code 68524-8, which tracks past usage of illegal drugs, is available. This data is accessible through FHIR Server resources, indicating standardization efforts for substance use tracking.
A cross-version extension for Evidence.version was defined for use in FHIR R4. This update provides standardized support for versioning evidence data across different FHIR releases.
FHIR R6 is scheduled for release. Furthermore, CMS is reportedly preparing infrastructure to facilitate the push of health data.
The upgrade cycle for health IT across Europe is moving towards interoperability standards compatible with the European Health Data Space (EHDS). Many organizations are accelerating their adoption of FHIR APIs.
A cross-version extension for SupplyRequest.identifier has been defined for FHIR R4. This extension can be utilized within the SupplyRequest element context.
The FHIR Server SNOMED CT Browser was utilized to demonstrate the mapping of the code 128649001, which represents Hepatocellular carcinoma, clear cell type. This functionality supports the integration of SNOMED CT terminology within the FHIR standard.
A new cross-version extension for ResearchStudy.arm.code has been defined for use in FHIR R3. This extension can be utilized in various contexts requiring specific coding capabilities.
Infor announced a new data archival solution built upon the FHIR standard. This solution aims to manage and store healthcare data using modern interoperability standards.
A cross-version extension for Ingredient.substance.strength.measurementPoint was defined for FHIR R4B. This extension updates the structure definition for ingredient substance strength measurements.