Remove eHealth Remove Examples Remove FHIR
article thumbnail

FDA FHIR Pilot Automates Adverse Events Reporting and Validation with Cedars-Sinai and the VA Through eHealth Exchange

Healthcare IT Today

The following is a guest article by Jay Nakashima, President at eHealth Exchange An FDA project aims to make it as easy as possible for clinicians to report adverse drug events and share important clinical data with public health agencies to investigate the event.

eHealth 123
article thumbnail

TEFCA Is Live – Clarifying Common Misperceptions

Healthcare IT Today

The following is a guest article by Jay Nakashima, President at eHealth Exchange Change is scary. At eHealth Exchange, which is one of the first Qualified Health Information Networks™ (QHINs™) under TEFCA, we have a front-row seat to the framework’s ongoing implementation. eHealth Exchange is embracing both use cases.

eHealth 80
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Enhancing Interoperability and Data Sharing with Innovative Technologies and Standards

Healthcare IT Today

The ONC Cures Act APIs and the companion CMS Access APIs all require these modern FHIR-based technologies and are fundamentally designed to grow a vibrant digital health economy providing choice and value to consumers. These API protocols are known and used by hundreds of thousands of developers.

article thumbnail

The Role of the Trusted Exchange Framework and Common Agreement (TEFCA) in Facilitating Seamless Data Sharing Among Healthcare Entities

Healthcare IT Today

Jay Nakashima, President at eHealth Exchange We continue to move closer to realizing the dream of complete interoperability, and TEFCA is a big part of that. eHealth Exchange is proud to be one of the first Designated QHINs. Policies like the 21st Century Cures Act and ONC/CMS rules enhance data access and prevent information blocking.

article thumbnail

The Balance Between Promoting Data Sharing and Ensuring the Privacy and Security of Sensitive Health Information

Healthcare IT Today

A great example of this is de-identified patient data sets, where we’re able to take a large volume of data and determine trends. Jay Nakashima, President at eHealth Exchange Keeping patient data safe and private is our top priority. TEFCA proposes that the adoption of FHIR access with OAuth2.0

article thumbnail

Redox unwraps interoperability in 2024

Redox

Here are some specific reflections: FHIR adoption: We missed the mark on our HL7® Fast Healthcare Interoperability Resources (FHIR®) growth prediction. It certainly is growing, but FHIR has not picked up the steam we had hoped for in 2023. We reflected on that in our recap of 2023 FHIR DevDays. Sadly, he was wrong.

article thumbnail

Improving Document Exchange Response with Asynchronous FHIR API

Healthcare Exchange Standards

In the last article I show how PDQm can be made Asynchronous by using the FHIR Subscription. In the example from 200 partners, only 10 of them know of the patient of interest. For example the eHealth Exchange and CareQuality don't have any use of asynchronous while they have required everyone to support it.

FHIR 40