Remove Examples Remove FHIR Remove Health Information
article thumbnail

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

Healthcare IT Today

To make this happen, the FDA partnered with eHealth Exchange, a non-profit health information network, and multiple health systems. The decision to leverage HL7’s FHIR Release 4 is important for the long-term viability of this project as it expands to include reporting for other drugs and use cases.

eHealth 123
article thumbnail

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

Healthcare IT Today

Most of the data that we are looking to share is highly sensitive health information, the kind of information that cybercriminals love to hold for ransom. 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.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Simple definition of ABAC and #FHIR

Healthcare Exchange Standards

Users are grouped into "clearances" (aka roles); this might be a FHIR PractitionerRole, CareTeam, RelatedPerson, and Group; but might be something non-FHIR (aka OAuth, LDAP, etc). A good example is Observation.category code of 'vital-signs' -- indicates vital signs that are normal health information of no stigmatizing sensitivity.

FHIR 52
article thumbnail

VIP Patients in #FHIR

Healthcare Exchange Standards

The FHIR security tag `VIP` is used to indicate that a patient's health information is considered to be highly confidential and requires heightened security measures. To use the VIP security tag, simply add it to the security tag of any FHIR resource that contains the patient's health information.

FHIR 45
article thumbnail

TEFCA Is Live – Clarifying Common Misperceptions

Healthcare IT Today

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. Currently, eHealth Exchange is one of seven Designated QHINs exchanging health information via TEFCA. But we believe that is a mistake.

eHealth 80
article thumbnail

IHE IT-Infrastructure Spring 2023

Healthcare Exchange Standards

The first is the ability to exchange a list of health data locations, which enables Record Locator Services to interoperate with consumers wishing to discover the location of patient records within a health information exchange. This Provenance definition is now in mXDE along with examples and requirements CapabilityStatement.

FHIR 119
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.