iClinic LLC attended a meeting and discussed their ongoing development of FHIR and openEHR. This collaboration was noted during an event involving iKon.MN and the openEHR International Community.
A new LOINC code, 85276-4, has been defined to specify the status of the closest surgical margin when all margins are uninvolved. This standard helps standardize the reporting of surgical pathology data within FHIR systems.
HL7 updated the FHIR specification to include a new extension for tracking the degree of polymerization in substances. This update enhances the ability of healthcare systems to model complex chemical or material data using FHIR standards.
The Office of the National Coordinator (ONC) is focusing on integrating FHIR standards for health data exchange. This effort aims to navigate the future landscape of health data interoperability.
The FHIR R4 Core Package Registry package was published, providing a structured set of resources. This package outlines the core components and dependencies for FHIR R4 implementation.
openFHIR released version 1.2.5 of its engine. This update implements the FHIR Connect specification and enables bidirectional data mapping between openEHR and FHIR standards.
The presentation detailed how the HL7 FHIR IG Publisher utilizes SQL on FHIR ViewDefinitions. This capability enhances the functionality of the FHIR IG Publisher.
Taction Software is expanding its development services for healthcare applications that meet HIPAA compliance requirements. The expansion includes specialized expertise across multiple high-demand areas, focusing on FHIR compliance.
The discussion covered multiple interoperability methods, ranging from manual workflows and email to blockchain and Fast Healthcare Interoperability. The focus was on setting the future standards and best practices for FHIR adoption.
HL7 provided information regarding LOINC content for FHIR Server. This update specifically addresses the deprecation of the LOINC code 27506-5, which relates to alcohol-substance abuse rehabilitation treatment plans.
The content reviewed the first year of FHIR Schema results, covering ecosystem evolution and developer experience. It also addressed inconsistencies in FHIR validation across different engines.
A session was presented at FHIR DevDays 2025 focusing on implementing SQL queries against FHIR data. The session covered advanced techniques, including flattening FHIR resources using ViewDefinitions DSL.
Opala hosted a webinar detailing how they scaled their FHIR implementation. The session focused on strategies to avoid a costly and disruptive 'rip and replace' process.
A synthetic data API was developed using Synthea to generate realistic, FHIR-compliant patient health records. This approach allows for testing and development without compromising patient privacy.
A cross-version extension for MonetaryComponent.type has been defined for FHIR R5. This update addresses version compatibility for monetary component types within the FHIR standard.
Google Cloud updated the MedGemma toolkit to support native DICOMweb integration. This enhancement simplifies the process of integrating MedGemma into clinical workflows.
An information session was conducted concerning the use of FHIR for the PLM portal web-based electronic application form (eAF). This session was related to the European Commission's PLM portal.