Free Hospital EMR and EHR Newsletter Want to receive the latest news on EMR, Meaningful Use, ARRA and Healthcare IT sent straight to your email? Join thousands of healthcare pros who subscribe to Hospital EMR and EHR for FREE!

Hospitals That Share Patients Don’t Share Patient Data

Posted on August 7, 2018 I Written By

Anne Zieger is veteran healthcare branding and communications expert with more than 25 years of industry experience. and her commentaries have appeared in dozens of international business publications, including Forbes, Business Week and Information Week. She has also worked extensively healthcare and health IT organizations, including several Fortune 500 companies. She can be reached at @ziegerhealth or

If anyone in healthcare needs to catch up on your records, it’s another provider who is treating mutual patients. In this day and age, there’s no good reason why clinicians at one hospital should be guessing what the other would get (or not get as the case is far too often).

Over the last few years, we’ve certainly seen signs of data sharing progress. For example, in early August the marriage between health data sharing networks CommonWell and Carequality was consummated, with providers using Cerner and Greenway Health going live with their connections.

Still, health data exchange is far more difficult than it should be. Despite many years of trying, hospitals still don’t share data with each other routinely, even when they’re treating the same patient.

To learn more about this issue, researchers surveyed pairs of hospitals likely to share patients across the United States. The teams chose pairs which referred the largest volume of patients to each other in a given hospital referral region.

After reaching out to many facilities, the researchers ended up with 63 pairs of hospitals. Researchers then asked them how likely they were to share patient health information with nearby institutions with whom they share patients.

The results, which appeared in the Journal of the American Medical Informatics Association, suggest that while virtually all of the hospitals they studied could be classified as routinely sharing data by federal definitions, that didn’t tell the whole story.

For one thing, while 97% of respondents met the federal guidelines, only 63% shared data routinely with hospitals with the highest shared patient (HSP) volume.

In fact, 23% of respondents reported that information sharing with their HSP hospital was worse than with other hospitals, and 48% said there was no difference. Just 17% said they enjoyed better sharing of patient health data with their HSP volume hospital.

It’s not clear how to fix the problem highlighted in the JAMIA study. While HIEs have been lumbering along for well more than a decade, only a few regional players seem to have developed a trusted relationship with the providers in their area.

The techniques HIEs use to foster such loyalty, which include high-touch methods such as personal check-ins with end users, don’t seem to work as well for some HIE they do for others. Not only that, HIE funding models still vary, which can have a meaningful impact on how successful they’ll be overall.

Regardless, it would be churlish to gloss over the fact that almost two-thirds of hospitals are getting the right data to their peers. I don’t know about you, but this seems like a hopeful development.

Interoperability Challenges (VA, DOD, Epic, CommonWell) – Where Do We Go From Here?

Posted on November 16, 2015 I Written By

David Chou is the Vice President / Chief Information & Digital Officer for Children’s Mercy Kansas City. Children’s Mercy is the only free-standing children's hospital between St. Louis and Denver and provide comprehensive care for patients from birth to 21. They are consistently ranked among the leading children's hospitals in the nation and were the first hospital in Missouri or Kansas to earn the prestigious Magnet designation for excellence in patient care from the American Nurses Credentialing Center Prior to Children’s Mercy David held the CIO position at University of Mississippi Medical Center, the state’s only academic health science center. David also served as senior director of IT operations at Cleveland Clinic Abu Dhabi and CIO at AHMC Healthcare in California. His work has been recognized by several publications, and he has been interviewed by a number of media outlets. David is also one of the most mentioned CIOs on social media, and is an active member of both CHIME and HIMSS. Subscribe to David's latest CXO Scene posts here and follow me at Twitter Facebook.

The state of healthcare in the United States is fairly well known with the US healthcare spend between 17-18% of the GDP. It is one of the most expensive countries in the world for healthcare. America is also one of the few developed nations not to have a universal healthcare scheme, and one of the main barriers is interoperability challenges.

As we have just finished celebrating veteran’s day, one of the challenges in our federal system is interoperability. In order to provide these veterans with proper healthcare, the Veterans Association and the Department of Defense each proposed an update to the way medical records were stored. The proposed system involved purchasing or customizing an existing an EMR software, which would allow doctors to access patient files far more easily.

This would make it easier for veterans to switch doctors without having to worry about taking large amounts of paperwork along with them. It would also allow doctors to give their patients the best care possible without having to worry about red tape and legal hoops they have to jump through. While this makes sense to everyone, a decision has been made to have two separate systems.

We are also having the same discussion in the commercial EMR space recently where representatives from Cerner asked Epic to joing the CommonWell Health Alliance. Based on my experience Epic has done a great job at exchanging data with other Epic customers. At the request of the customer, Epic will work on creating interoperability with other non-Epic systems. The challenge is the need to create a special request for data sharing every time an Epic customer wants to communicate with a non Epic facility.

The House of Representatives have questioned the VA and DOD decisions to create these separate EHR systems. This makes perfect sense since I am also questioning the decision myself. What should have happened in this situation is the VA and DOD should have come together to collaborate on one EHR system. At the same time, the federal government should step in to create a standard for interoperability and mandate that we move towards collaboration.   If you think about the impact that meaningful use had on transforming the healthcare sector’s move towards digital, I believe the government could have the same impact on interoperability if they made it a requirement.

2013 Hospital EHR and Health IT Trends

Posted on December 31, 2013 I Written By

John Lynn is the Founder of the blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of and John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

There are a number of amazing milestones and trends happening with EHR and Healthcare IT. I think as we look back on 2013, we’ll remember it for a number of important changes that impact us for many years to come. Here are a few of the top trends and milestones that I’ll remember in 2013.

Epic and Cerner Separate Themselves – This has certainly been happening for a couple of years, but 2013 is the year I’ll remember that everyone agreed that for big hospitals it’s a two horse race between Cerner and Epic. There’s still an amazing battle brewing for the small hospital with no clear winner yet. However, in the large hospital race the battle between Cerner and Epic is on. Epic had been winning most of the deals, but Cerner just gave them a big left hook when Intermountain chose Cerner.

I expect we’re living in an Epic and Cerner world until at least a few years post meaningful use. The job listings on Healthcare IT Central illustrate Cerner and Epic dominance as well.

Near Universal EHR Adoption in Hospitals – I can’t find the latest EHR adoption (meaningful use) numbers from ONC, but the last ones I saw were in the high 80’s. That basically leaves a number of small rural hospitals that likely don’t have much tech infrastructure at all, let alone an EHR. Every major hospital institution now has an EHR. I guess we can now stop talking about hospital EHR adoption and start talking about hospital EHR use?

The Cracks in the Healthcare Interoperability Damn Appear – Interoperability has always been a hard nut to crack in healthcare. Everyone knew it was the right thing to do, but there were some real systemic reasons organizations didn’t go that direction. Not to mention, there was little financial motivation to do it (and often financial disincentive to do it).

With that background, I think in 2013 we’ve started to see the cracks in the damn that was holding up interoperability. They are still just cracks, but once water starts seeping through the crack the whole structure of the damn will break and the water will start flowing freely. Watch for the same with interoperability. Some of this year’s cracks were started with the announcement of CommonWell. I think in response to being left out of CommonWell, Epic has chosen to start being more interoperable as well.

Skinny Data Happens – I was first introduced to the concept of skinny data vs big data at HIMSS 2013 by Encore Health Resources. While I’m not sure if the skinny data branding will stick, the concept of doing a data project with a slice of data that has meaningful (excuse the use of the word) outcomes is the trend in data analytics and it’s going to dominate the conversations going forward.

As I posted on EMR and EHR, Big Data is Like Teenage Sex, but skinny data is very different. Skinny data is about doing something valuable with the data. Sadly, not enough people are doing skinny data, but they all will in 2014.

Hospitals Ignore Consumer Health Devices – Consumer health devices are popping up everywhere in healthcare. We’re quickly reaching the point that consumers can monitor all of their vital information at near hospital grade quality using their smartphone and sometimes an external device. This is a real revolution in medical devices. Many are still making their way through FDA approval, but some have passed and are starting to work on traction.

With all of this innovation, hospitals seemed to have mostly ignored what’s happening. Sure, the larger ones have a few pilot projects going. However, most hospitals have no idea what’s about to hit them upside the head. Gone will be the days of patients going to the hospital to be “monitored.” I don’t think most hospitals are ready for this shift.

Only Incentives Will Make EHR Interoperability Happen

Posted on April 26, 2013 I Written By

John Lynn is the Founder of the blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of and John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

Today we had a really interesting #HITsm chat about interoperability, data hoarding, and sharing healthcare data. Tomorrow we’ll have a post on EMR and EHR that summarizes some of the key tweets from the chat. Although, there was one theme that really struck home to me during the chat.

The biggest barrier to EHR interoperability and data sharing is incentives.

During the chat multiple people including myself made the observation that the reason EHR vendors don’t share data is that there’s no incentive to share data. I can’t say I’ve ever seen a hospital choose to not go with an EHR because it couldn’t interoperate with another EHR vendor. The incentive isn’t there for the hospital and therefore the EHR vendor.

Think about the EHR interoeprability announcement of CommonWell. While the CEO’s of the five EHR vendors can sit there and say that they’re doing it because it’s the right thing to do for healthcare, these public company CEOs also have a legal responsibility to do what’s best for the shareholders of their company.

The reality is that CommonWell would have never happened if there wasn’t an incentive for these companies to put CommonWell together. Rather than beat around the bush, these EHR companies came together to stick it to Epic and to give them a strategic advantage over other companies that can’t or won’t share data. You can certainly make an argument for why doing this is good for healthcare as well, but if there was no outside business incentive to CommonWell then the healthcare benefit wouldn’t have been enough.

As one person tweeted during the Twitter chat, If there were money paid for sharing data, all the fear and issues would suddenly disappear and solutions provided.

When thinking about incentivizing EHR interoperability, Farzad Mostashari’s words at The Breakaway Group event at TEDMED come ringing into my ears, “Incentives and money aren’t always the same.” Cash or otherwise, EHR interoperability needs some incentive.