Remove Data Remove FHIR Remove HIE
article thumbnail

Transitioning Federated HIE from XCA to FHIR Query

Healthcare Exchange Standards

I already have one proposal for the transition from the current Federated Health Information Exchange to supporting FHIR, that is based on a transition from CDA to FHIR-Documents. Federated FHIR Resource Servers In this article I am going to add another step to the smooth transition. I will get to those later.

FHIR 112
article thumbnail

FHIR data in existing Nationwide Health Information Exchange

Healthcare Exchange Standards

They have security models, privacy models, patient identification models, record location models, and data format models. The solution is to leverage this existing solution, and just add FHIR. My point in this article is that this does not need to be a restriction on those that do want to move on to FHIR.

FHIR 105
Insiders

Sign Up for our Newsletter

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

article thumbnail

Scaling #FHIR authorization in a multiple organization HIE

Healthcare Exchange Standards

In my last article on Controlled Exchange Architecture Models for Scale on #FHIR. One issue I ran into is the question of how OAuth at healthcare scale works when an HIE is made up of multiple organizations in a federation. This is an important part of how HIE scale. We don't address how an HIE might switch to user level.,

HIE 40
article thumbnail

HIE future bright -- FHIR API to Document Sharing

Healthcare Exchange Standards

I think the most useful value-add that an HIE can add is an API that is based on FHIR. This is true of an XDS based HIE, Regional Exchange (XCA), Vendor based EHR, nationwide Exchange, and Direct HISP. At an HIE level: Initially I would focus on enabling Apps to query for and read the data available in the HIE.

HIE 40
article thumbnail

TEFCA Is Live – Clarifying Common Misperceptions

Healthcare IT Today

The First Step Is To Decide Access to data via TEFCA is not always automatic. Most of these QHINs operated as health information networks (HINs) prior to the launch of TEFCA last year, and they continue to share data among and between their participants through their existing frameworks and legal structures.

eHealth 80
article thumbnail

Just Get Connected Already

Healthcare IT Today

The optometrist printed his report that I would bring to my next PCP exam, because otherwise my optometrist had no reliable way to transfer the data. The alliance was a bold gesture made ten years ago by leading EHR vendors to demonstrate their commitment to data sharing. This is the burden still faced by three quarters of U.S.

FHIR 130
article thumbnail

IHE IT-Infrastructure Spring 2023

Healthcare Exchange Standards

The IHE IT-Infrastructure committee continues to produce new and improved specifications for HIE interoperability. Cross-Community Patient Discovery (XCPD) Health Data Locator and Revoke Option - Rev. This spring we are publishing a supplement that was out for public-comment, a whitepaper that was out for public-comment.

FHIR 119