Duplicate Work in Healthcare

One of my favorite stories is the time we implemented an EHR in the UNLV health center. At first, we decided to do a phased implementation in order to replace some legacy bubble sheet software that was no longer being supported. So, we just implemented enough of the PM system to handle the patient scheduling and to capture the charge data in the EHR. Of course, we were also a bit afraid if we implemented the full EHR, the staff would revolt.

A week or two into the partial implementation, something really amazing happened. First, some of the providers started to document the patient visit in the EHR even though they still had to document it in the paper chart as well. I asked them why and they just said, “It was there and I thought it would be good to have my info in the note.”

Second, some of the providers started asking me why they had to do duplicate work. They really hated having to enter the diagnosis and charge codes into the EHR and then document them again in the paper chart. Plus, they followed up that they could see the other section of the notes in the EHR and “why couldn’t they just use that instead of the paper chart.” The reality was: Doctors hated doing duplicate work!

Once I heard this, I ran to the director of the Health Center’s office and told her what they’d said. We both agreed, why wait? A week or so later we’d moved from paper charts to a full EHR implementation.

There were a lot of lessons learned from this experience. First, it’s amazing how people want to use the new system when they can see that it’s possible. They basically drove the EHR implementation forward. However, what was interesting to me was the power of “duplicate work.” We all hate it and it was a driving force for using technology the right way.

While we used the concept of duplicate work for good, there’s a lot of duplicate work in healthcare which drives patients and healthcare staff totally nuts. However, we don’t do anything about it. This was highlighted perfectly in a recent e-Patient update from Anne Zieger. Go and read her full account. We’ll be here when you get back.

What’s astounding from her account is how even though doctors hate duplicate work for themselves, we’re happy to let our patients and support staff do duplicate work all the time. I’ve seen some form of Anne’s experience over and over. Technology can and should solve this. This is true across multiple clinics but is absolutely true in the same clinic where you handle the workflow.

I get that there are reasons why you may want a staff to verify a patient’s record to ensure it was entered correctly and is complete. That’s absolutely understandable and would not have likely been an issue for Anne. However, to disregard the work a patient had done on their intake paperwork is messed up. Let alone not tapping into a patient’s history that may have been entered at another clinic owned by the same organization or collecting/updating the info electronically through a patient portal. I’m reminded of @cancergeek’s recent comment about the excuse that “it’s how we’ve always done it.”

In the past this might not have mattered too much. Patients would keep coming back. However, the tides of consumerism in healthcare are changing. Do you enjoy doing duplicate work? Of course not! It’s time to purge duplicate work for patients and healthcare staff as well!

About the author

John Lynn

John Lynn

John Lynn is the Founder of HealthcareScene.com, a network of leading Healthcare IT resources. The flagship blog, Healthcare IT Today, contains over 13,000 articles with over half of the articles written by John. These EMR and Healthcare IT related articles have been viewed over 20 million times.

John manages Healthcare IT Central, the leading career Health IT job board. He also organizes the first of its kind conference and community focused on healthcare marketing, Healthcare and IT Marketing Conference, and a healthcare IT conference, EXPO.health, focused on practical healthcare IT innovation. John is an advisor to multiple healthcare IT companies. John is highly involved in social media, and in addition to his blogs can be found on Twitter: @techguy.