Rhapsody Health Solutions Team

Interoperability form and function: Interview with AMIA CEO Dr. Doug Fridsma

February 7, 2016

From The Health Care Blog:

I’ve tried to maintain for the last six years a consistent definition of what interoperability is. The first thing I can describe is what interoperability is not. It is not a state of utopia in which there is this information liquidity. You will hear this all the time: we want ubiquitous information, and free-flow, data liquidity and all those things…

Interoperability cannot be achieved in the abstract. It can only be achieved, given a definition, in the concrete. Interoperability is the exchange and use forces us to ask ourselves “what do we want to try to accomplish?

Some great insights in the original article from Doug Frisdsma, who explains interoperability and the state of exchange in very understandable terms that cuts through so much of the noise that many bloggers and analysts publish on a daily basis. 

“Interoperability is defined operationally,” he wrote. 

We love to see so many Corepoint Health customers operationally using health data between systems and applications.

Related Blogs

Dan Rice

Six reasons to consider cloud migration

Learn what’s motivating healthcare organizations to migrate infrastructure to the cloud.

Read more

Rhapsody Health Solutions Team

How Michigan DHHS supports high quality data exchange with FHIR

Discover how Michigan's Department of Health and Human Services optimizes modern data exchange with Rhapsody

Read more

Rhapsody Health Solutions Team

Flexible deployment options: Why it matters

Learn the limitations of cloud only solutions and why you need a solution that meets you where you are for total interoperability in healthcare.

Read more