The Regional Open Digital Health Summit (RODHS) 2025 was held in New Delhi, gathering leaders from South-East Asian nations, governments, and international bodies. The focus was on establishing collaborative governance and interoperable platforms to achieve Universal Health Coverage.
This article explains how to configure 'expansion maps' used to transform hierarchical JSON data into Dataverse's relational model. This allows complex JSON attributes to be mapped to multiple, related Dataverse attributes.
Appian and Ignyte Group announced their win at the global HL7 AI Challenge for their "Bring AI to Work(flow)" solution. This platform aims to transform clinical and operational workflows within public health agencies and healthcare systems by embedding multiple types of AI.
True Electronic Health Record (EHR) integration requires 'semantic interoperability,' not just basic data connectivity. This article explains the characteristics and appropriate use cases of technologies ranging from legacy HL7 v2 to modern FHIR, demonstrating how to effectively utilize medical data.
This paper addresses the interoperability challenges between openEHR and HL7 FHIR due to fundamental differences in their data modeling. It proposes FHIRconnect, a novel domain-specific language (DSL) and open-source transformation engine that enables standardized, bidirectional data exchange. This framework aims to bridge critical interoperability gaps by leveraging international archetypes.
A data structure for collaborative teleconsultation (teleconsult) has been defined based on the HL7 FHIR standard. This 'BundleRelazioneCollaborativaTeleconsultoTransaction' resource profile aims to streamline medical information sharing between electronic health record systems and standardize remote diagnosis and collaboration processes.
This article provides a technical guide on the structure and usage of medical terminologies based on HL7 FHIR. It comprehensively covers fundamental concepts like CodeSystem and ValueSet, as well as advanced data retrieval methods using videos and multiple API endpoints.
Extensive efforts are underway to move electronic product information (ePI) onto FHIR, a transition expected to become mandatory. This shift promises substantial advantages not only for regulators and industry but also, critically, for end users like patients and healthcare providers. However, successful implementation requires careful steps, stakeholder communication, and alignment on phasing.
This article introduces the 'RareLink' framework, designed to solve the problem of interoperability among international rare disease registries. It aims to accelerate research by utilizing standardized data models like FHIR and Phenopackets for large-scale data sharing.
Tenasol offers solutions to convert various healthcare data formats into FHIR, the latest standard. This conversion is possible from a wide range of formats, including unstructured data such as images and PDFs, in addition to structured ones like X12/EDI, HL7v2, and HL7v3.
Trisotech announced that it can provide reliable, AI-powered clinical orchestration by combining the creativity of AI with governance based on BPM+ and HL7 standards. This utilizes industry standards like FHIR.
Healthcare data interoperability is the ability for different systems to seamlessly exchange and utilize patient data. This article explains FHIR, a next-generation standard that is key to solving this challenge.
A resource profile called PractitionerTeleconsulto has been published based on the HL7 FHIR standard. This defines data structures related to teleconsultation (remote care), providing concrete implementation guidelines for healthcare information exchange.
This article provides a technical guide on how to set up FHIR integration within the Cline tool. Users must use the provided JSON configuration example, tailored for operating systems like macOS, Windows, or Linux, and input it via the 'Add MCP Server' function. Crucially, restarting Cline is required after completing this setup.
The definition for a ValueSet titled 'Opiate Antagonists' has been published by NCQA PHEMUR. This ValueSet includes multiple drug codes related to opioid antagonists, such as buprenorphine and naltrexone, which aids in standardizing medical information.
The article compares Kong, a comprehensive API gateway, with Runbeam (Harmony), a secure data integration platform. Both platforms have distinct design philosophies and offer optimal solutions depending on the use case.
Google Cloud has enabled the centralized processing of electronic health records (FHIR), diagnostic images (DICOM), and clinical messages (HL7v2) through the Cloud Healthcare API. This allows healthcare institutions to manage and utilize diverse data formats in an efficient environment.
This guide explains how to export messages from an HL7v2 data store within Google Cloud Healthcare API to a Pub/Sub topic. This method addresses the lack of automatic notification mechanism when new HL7v2 messages are imported into a data warehouse.
This article provides detailed instructions and code samples for updating the configuration (Pub/sub topic name) of a DICOM store using the Google Cloud Healthcare API. Developers can modify the notification settings of a DICOM store via API calls using major languages like Go, Java, and Node.js.