InterSystems has launched FHIR Agent Studio, a developer portal for building AI agents into FHIR workflows. This tool allows users to build and run small clinical workflows—from trigger to action—on a single backend while tracing every step of the process.
To address the challenges of medical information sharing, HL7 standards have continuously evolved. This article compares and explains the evolution from message-based HL7 v2, through HL7 v3 with a more advanced semantic structure, to FHIR's web-based approach using RESTful APIs.
This article analyzes the importance of 'production readiness' for developing AI-powered telehealth products. It argues that success in enterprise adoption hinges not merely on adding features, but on foundational design elements like data infrastructure, compliance, and AI governance.
eHealth Infrastructure published the FHIR-based code system 'Publication Status'. This system defines the lifecycle status (draft, active, retired, etc.) of medical resources or concept maps, aiming to enhance data reliability during exchange.
This article provides technical instructions for setting up an International Patient Summary (IPS) node. It details a comprehensive system architecture including a FHIR R4 server, a PostgreSQL database, and multiple gateway services.
This guide outlines the implementation guidelines for the xShare Yellow Button, based on FHIR R4. Implementers must first 'claim' their conformance by specifying supported features and roles, and then 'prove' it by meeting detailed technical requirements.
The World Health Organization (WHO) has released version 1.6.0 of the 'WHORegionalOffices' code system. Built on the FHIR standard, this aims to standardize regional identifiers and enhance interoperability for global healthcare data.
As healthcare data utilization increases, FHIR and OMOP are often compared. However, this article argues that the true challenge is not choosing between them, but establishing a robust strategy for 'semantic normalization.' Long-term success depends on strategic approaches like terminology governance and concept normalization.
The 'FHIR Converter' provided by ms-azuretools is a tool that enables the conversion of legacy formatted health data into FHIR, expanding the use cases and interoperability of health data. The security assessment confirms its vulnerability status and malware presence.
InterSystems announced a demo for FHIR Agent Studio. This tool integrates AI agents with the FHIR standard, Large Language Models (LLM), and Vector Search to demonstrate how developers can explore, build, and test agent-driven healthcare workflows.
EasyPA offers a stateless API service that converts modern FHIR R4 data into legacy HL7v2 messages. The service uses AI assistance to rapidly generate mapping templates, significantly shortening the time required for developing integrations for downstream systems.
This document defines the FHIR resource structure (Profile) for handling a specific clinical scenario, 'Observation - Embarazo: Fecha Estimada de Parto'. This profile aims to standardize and exchange pregnancy-related data, such as fetal monitoring and estimated due dates, thereby enhancing interoperability in healthcare information exchange.
Sean Connelly introduces 'FHIR Agent Studio,' a platform for building AI agents using reusable building blocks, applicable to real FHIR workflows. This enables developers to build and validate reliable decision support tools without complex system integration.
Elimu provides comprehensive IT solutions across various domains, including Knowledge/Clinical Decision Support (CDS), FHIR development, and Social Determinants of Health (SDOH) integration. They support full-stack EHR embedding and data structuring compliant with CMS 1151.
This article provides a technical overview of the 'EU Digital Green Certificate FHIR Implementation Guide' designed for COVID-19 vaccination certificates. It details how immunization records and clinical documents are structured using specific resources and code definitions.
JondaX is a data transformation engine that processes diverse real-world inputs—such as PDFs, images, HL7/FHIR—and converts them into clean, coded, and regulation-ready structured output. It offers advanced functions based on clinical context while adhering to international regulations like HIPAA and GDPR.
This specification introduces the 'ehealth-trigger-enablement-code' extension to the FHIR ServiceRequest resource. It allows setting whether a service will react to trigger conditions expressed in other activities within a care plan.
The article addresses critical issues in healthcare platform development, such as duplicate patient records and data inconsistencies across modules. It advocates that the FHIR 'Patient' resource must be treated not merely as metadata, but as the central, unifying identifier for all clinical encounters.