Health Blawg

AUGUST 20, 2018

Following the announcement of implementation of the Carequality-CommonWell interoperability collaboration, I was fortunate enough to catch up with Micky Tripathi ( @mickytripathi1 ) to discuss this development and put it in context. Micky is bullish on interoperability, both over the near term (the next 12-18 months) and the long term.

Interoperability 60

Interoperability EHR FHIR HIE 60

Health Blawg

AUGUST 20, 2018

Following the announcement of implementation of the Carequality-CommonWell interoperability collaboration, I was fortunate enough to catch up with Micky Tripathi ( @mickytripathi1 ) to discuss this development and put it in context. Micky is bullish on interoperability, both over the near term (the next 12-18 months) and the long term.

Interoperability 60

Interoperability EHR FHIR HIE 60

Health Blawg

AUGUST 20, 2018

Following the announcement of implementation of the Carequality-CommonWell interoperability collaboration, I was fortunate enough to catch up with Micky Tripathi ( @mickytripathi1 ) to discuss this development and put it in context. Micky is bullish on interoperability, both over the near term (the next 12-18 months) and the long term.

Interoperability 60

Interoperability EHR FHIR HIE 60

Health Blawg

AUGUST 20, 2018

Following the announcement of implementation of the Carequality-CommonWell interoperability collaboration, I was fortunate enough to catch up with Micky Tripathi ( @mickytripathi1 ) to discuss this development and put it in context. Micky is bullish on interoperability, both over the near term (the next 12-18 months) and the long term.

Interoperability 60

Interoperability EHR FHIR HIE 60

Health Blawg

AUGUST 20, 2018

Following the announcement of implementation of the Carequality-CommonWell interoperability collaboration, I was fortunate enough to catch up with Micky Tripathi ( @mickytripathi1 ) to discuss this development and put it in context. Micky is bullish on interoperability, both over the near term (the next 12-18 months) and the long term.

Interoperability 60

Interoperability EHR FHIR eHealth 60

Health Blawg

AUGUST 20, 2018

Following the announcement of implementation of the Carequality-CommonWell interoperability collaboration, I was fortunate enough to catch up with Micky Tripathi ( @mickytripathi1 ) to discuss this development and put it in context. Micky is bullish on interoperability, both over the near term (the next 12-18 months) and the long term.

Interoperability 60

Interoperability EHR FHIR eHealth 60

Healthcare Exchange Standards

FEBRUARY 25, 2016

Two independent projects this week sent to the FHIR mailing list their diagrams of how they are using FHIR as an API to classic XDS environments. The power of using FHIR as a simplifying API to classic environments. Our project will use FHIR as an abstraction layer for the application. privacy consent). Well done!

FHIR 40

FHIR HIE EHR Interoperability 40

Healthcare IT Today

AUGUST 20, 2023

Partnerships eHealth Exchange added C3HIE , a Texas-based HIE, to its network of partners under its anticipated QHIN. Health Plan Alliance selected 1upHealth as its preferred health data interoperability vendor. MedArrive and Heartbeat Health are collaborating to provide on-demand cardiovascular services to Medicaid beneficiaries.

Digital Health 92

Digital Health HIE eHealth Life Science 92

Healthcare Exchange Standards

MARCH 16, 2015

The Mobile Health Documents (MHD) profile was born to provide a more simple API to an XDS environment. This happened to be the same timeframe that Grahame was fanning the FHIR flames. So we joined forces and brought the concepts needed for XDS into FHIR®. So now, I take those FHIR based Resources and re-write the profile.

FHIR 40

FHIR Mobile Health mHealth Meaningful Use 40

Healthcare Exchange Standards

APRIL 4, 2018

Mostly they keep trying because the most basic query is just asking for all documents available for a given Patient. These are useful, just not very primary for a general purpose Document Consumer. Where these classifications are useful to a Document Consumer. Thus one can ask for documents covering treatment prior to 1998.

HIE 45

HIE FHIR Health Information Interoperability 45

Healthcare Exchange Standards

DECEMBER 30, 2017

It happens that the framework for explaining why the future is bright for HIE comes from the Wisconsin HIE (WISHIN) fall summit. They used the following diagram to show what they viewed as the HIE future. These historic events need to have the full context of them, which is what a Document model provides.

HIE 40

HIE FHIR Meaningful Use Leadership 40

Redox

NOVEMBER 21, 2023

Is this just another HIE? Of note, the XCPD, XCA, and XDR profiles do not currently support FHIR natively. A few features of the CA DxF set it apart from traditional health information exchanges (HIEs) and networks (HINs). Required data format requirements are also notable.

HIE 59

HIE FHIR Health Information Nursing 59

Healthcare Exchange Standards

MAY 13, 2016

There is renewed discussion, much like back in January, around the need to go beyond testing just the FHIR Resource 'interoperability'. Testing Interoperability is not easy, and there are struggles with getting this first level testing done right. This is more than just a selection of FHIR Resources. A complete system.

FHIR 40

FHIR Interoperability HIE Leadership 40

Healthcare Exchange Standards

AUGUST 31, 2020

Most important, this is not an interoperability problem Nationwide Patient Identity Management, especially in a federation like the USA, is a balance between quality, privacy, and safety. Architectures IHE includes two distinct architectures at the interoperability level. Here are the IHE relevant works on the topic of Patient.

Interoperability 45

Interoperability HIE FHIR Health Information 45