The US Department of Health and Human Services (HHS) issued the final HTI-5 rule, reducing several health IT certification measures to ease administrative burdens on developers. While the rule streamlines compliance, it notably delayed changes to information blocking rules for providers.
While many healthcare organizations are piloting agentic AI, the primary bottleneck for implementation lies in the underlying EMR system. This guide provides a comprehensive readiness checklist for CIOs, covering data quality, interoperability (FHIR/HL7), security, and workflow fit for AI agent adoption.
For US EHR integrations, the article advises building on FHIR R4. This is because the declared version governs the entire interactionβincluding MIME types and search behaviorβand R4 maintains compatibility with existing certified APIs and payer contracts.
While data exchange volume is rapidly growing, the core challenge lies in clinical data usability. Even if standards like FHIR and HL7 v2 standardize the structure, whether the data carries the usable 'meaning' depends on mapping and terminology validation. Reliable data pipelines must expose failures rather than hiding them.
The ONC released the HTI-5 final rule, simplifying the Health IT Certification Program by removing 14 criteria and revising others. This significantly changes compliance requirements for ISVs, particularly regarding interoperability and AI documentation.
HealthEx announced that ten emerging digital health companies are building on its platform. These companies use the HealthEx health records API and MCP server to integrate consented medical records from 90% of U.S. care sites, enabling personalized experiences in areas like AI coaching and rare disease care.
AI agents can book appointments directly into an EHR, but this requires the EHR vendor's explicit write access. The article compares HL7 v2 and FHIR, explaining the technical differences in scheduling data exchange. HL7 v2 only reports activity, while FHIR can execute booking operations if the vendor allows it.
Security researcher Abhinav Agarwal identified four vulnerabilities in HAPI FHIR, the open-source Java library implementing HL7 FHIR. These flaws affect Smile Digital Healthβs Smile CDR, potentially allowing cross-tenant data access and unauthorized patient record disclosure.
This article details how medical data must be securely transmitted beyond local hospital interfaces to reach diverse destinations, including public health agencies and patient apps. It introduces comprehensive data linkage mechanisms utilizing standards like FHIR, HL7, and DICOM, covering electronic case reporting (eCR), state-level record exchange (TEFCA), image processing, and document sharing.
A comprehensive checklist was provided to audit the security posture of open-source FHIR servers. It addresses critical vulnerabilities, such as those related to multi-tenant partitioning, authorization checks, and resource exhaustion, ensuring compliance before deployment.
Haste Health has published the results of its automated conformance testing for its FHIR implementation. The report details test results across major interoperability standards, including FHIR R4 core, US Core, ONC (g)(10) Standardized API, and SMART scopes, highlighting passing checks and known gaps.
Taction provides healthcare data integration services connecting disparate systems such as EHRs, labs, and imaging systems. Utilizing standards like HL7 and FHIR APIs, the service addresses the technical challenges required for accurate and secure data movement.
This article provides a guide for healthcare institutions considering AI adoption, focusing on selecting reliable development partners. Since AI implementation affects regulatory safety, data privacy, and long-term system performance, understanding strict health standards like HL7 and FHIR is crucial.
A new viewer tool allows users to read complex health records (FHIR/Blue Button JSON) by laying out nested data into simple, readable tables (e.g., lab results, claims, medications). It runs entirely in the browser, ensuring data privacy.
Connecting applications to Electronic Health Records (EHRs) cannot be achieved by implementing FHIR standards alone. This guide explains the necessity of a hybrid approach, utilizing multiple standards such as FHIR R4, HL7 v2, SMART on FHIR, and CDS Hooks.
A researcher identified four vulnerabilities in HAPI FHIR, an open-source interoperability software. These flaws could enable attackers to improperly access sensitive patient records or potentially disrupt services in multi-tenant environments.
Amazon, Google, Meta, and other major employers have joined a government-led pledge to reform prior authorization processes for self-funded health plans. They commit to implementing electronic prior authorizations to speed up care and improve data sharing, aligning with federal efforts to modernize healthcare processes.
Security researchers found four high-severity vulnerabilities in HAPI FHIR, a widely used open-source interoperability software. These flaws could allow attackers to improperly access sensitive patient records or disrupt services across multi-tenant healthcare systems.
This guide details the technical process of transforming raw CMS files (Marketplace and PBP) into a standardized FHIR InsurancePlan resource. The data is first imported into the Benefit Plan Standard schema, then converted using dedicated scripts, and finally validated against FHIR standards.
The service provides scalable integrations connecting EMR systems and the healthcare ecosystem using FHIR, HL7 v2, and proprietary APIs. Services cover comprehensive connectivity, including FHIR server setup, SMART on FHIR app development, and data transformation from legacy formats to FHIR resources.