This event, titled 'From Policy to FHIR: Co-Designing Across Sectors,' focuses on the transition from policy decision-making processes to the FHIR standard. Participants will learn about the potential for data standardization through collaboration across different sectors.
WHO has published the mapping specifications for the 'TestScenarioSource' logical model, which is based on FHIR R4. This provides up-to-date technical information regarding smart health data structures and contributes to improving healthcare data interoperability.
Daseka has expanded its business scope from GPUs to encompass entire infrastructure, including data centers, power, cooling, and security. In the healthcare sector specifically, it is deploying services such as remote medical care and system integration using FHIR.
Technology architect Aditya Swaprakash Gadepalli is advancing predictive healthcare by leveraging machine learning, cloud technology, and data interoperability. He has focused on building systems that use standardized data (FHIR) and advanced AI (GenAI/LLM) to analyze potential health risks.
eHealth Infrastructure in Denmark published a mapping definition for 'Device type to MedCom device type' based on FHIR. This map uses standard codes like SNOMED CT to link medical device classifications (e.g., oxygen analyzer, blood pressure monitor) to common MedCom device types.
This guide explains how to retrieve patient data using the mock.health API, based on the FHIR R4 standard. It covers everything from obtaining an API key to retrieving specific patient information and comprehensive clinical records (episodes) through concrete steps and search parameters.
This project implemented an end-to-end, secure, and scalable healthcare data pipeline using Microsoft Fabric and Azure Health Data Services (FHIR R4). The platform ensures that medical data can be managed consistently from ingestion to analytics preparation, adhering to the HL7 FHIR R4 standard.
The Danish eHealth Infrastructure released version 10.0.0 based on FHIR R4, publishing technical specifications regarding mappings for a specific extension. This document details structured data handling for medical data exchange.
Oracle Health provides REST APIs based on the HL7 FHIR standard through its AI Application Suite. This allows developers to utilize medical data within SMART applications, achieving system interoperability.
The CDC's NHSN has published the 'ACH Monthly Encounter Initial Population Type ValueSet' as part of its Digital Quality Measures (dQM) Content Package. This specification defines a set of codes indicating encounter types for acute care hospitals, based on FHIR R4 standards.
Vitagroup has selected Alliance SIH as the distribution partner for its Health Intelligence Platform (HIP) in France. This brings an open, vendor-neutral health data platform into a major European market.
The eHealth Infrastructure in Denmark has published a code system for 'Device Use Reason' based on FHIR. This aims to standardize the purpose of medical device usage, thereby enhancing consistency in electronic health records and data exchange.
The Australian Digital Health Agency has selected a provider for Application Support and Maintenance (ASM) services, ensuring the continued security and modernization of the My Health Record. This establishes a foundation for transitioning to an FHIR-based ecosystem.
Cantina offers a free vulnerability scan to investigate authorization, PHI exposure, and API risks within the FHIR workflow. This service aims to identify potential security issues during the development phase and support the entire remediation process.
Interoperability leader 1upHealth launched '1up Clinical Connect,' a solution for payers that automatically acquires and unifies clinical data from provider EHRs with claims data. This aims to close care gaps, sharpen risk adjustment accuracy, and improve overall outcomes.
The Centers for Medicare & Medicaid Services (CMS) published the 2020 CMS Interoperability and Patient Access final rule, aiming to give patients access to their health information when needed. The regulation mandates or encourages payers to implement APIs to improve electronic data exchange.
CUBE OneCare compares itself against legacy EHR vendors and point-solution providers, demonstrating that it offers full FHIR R4 interoperability, extensive compliance frameworks, and clinical AI features within a single platform. This allows healthcare organizations to ensure unified interoperability and high security standards.