Remove Article 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

Bonus Features – October 13, 2024 – 85% of clinicians waste at least an hour a day on admin tasks, 82% of healthcare organizations hit with a cyberattack experience a disruption to patient care, plus 20 more stories

Healthcare IT Today

This article will be a weekly roundup of interesting stories, product announcements, new hires, partnerships, research studies, awards, sales, and more. Another ASTP/ONC post found only 20% of HIE organizations are using HL7 FHIR APIs to send and receive data. Welcome to the weekly edition of Healthcare IT Today Bonus Features.

FHIR 94
Insiders

Sign Up for our Newsletter

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

article thumbnail

HHS STAR HIE Program Funds 5 Organizations To Improve Interoperability

Electronic Health Reporter

This article is copyrighted strictly for Electronic Health Reporter. The article HHS STAR HIE Program Funds 5 Organizations To Improve Interoperability appeared first on electronichealthreporter.com. Illegal copying is prohibited.

HIE 91
article thumbnail

FHIR data in existing Nationwide Health Information Exchange

Healthcare Exchange Standards

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. Just add FHIR FHIR is a content format. By Just adding FHIR, the whole nationwide exchange that is functioning today just works.

FHIR 105
article thumbnail

Agile improvements toward #FHIR

Healthcare Exchange Standards

This article is where I muse about getting to that beautiful future based on #FHIR. Break Everything One possibly that some advocate is turn off what we have today, and everyone and everything switch to using http RESTful FHIR. This pair of transports now has a third FHIR mode, so Karen's Cross is now three dimensional.

FHIR 72
article thumbnail

Why use current Exchange infrastructure rather than starting over?

Healthcare Exchange Standards

Does that mean we don't move to nationwide http RESTful FHIR? I expect, as I have said before, that the green-fields will/should use http RESTful FHIR. My main concern is that we are trying to apply http RESTful FHIR to the hardest problem (Treatment, Payment, and Operations) when we already have a solution there.

FHIR 118
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