Free EMR 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 EMR and EHR for FREE!

Ebola and EHR Workflow

Posted on November 20, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com 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 InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

Earlier this month, the EHR Workflow fanatic addict expert, Charles Webster, MD, put together a webinar on EHR workflow (imagine that). However, he decided to piggyback the Ebola headline and talk about EHR workflow and a bit about how it applied to the Ebola incident. I love the marketing behind it.

EHR workflow is a topic of interest to me and so this summer I had Charles Webster, MD do an EHR workflow series over on EMR and HIPAA. Turns out, he covers a number of the same EHR workflow topics in the webinar embedded below:
-What it workflow?
-What is workflow technology?
-What is a workflow engine?
-What is a workflow editor?
-What is workflow visibility?

If you have an interest in EHR workflow, here’s Chuck’s webinar:

Karen DeSalvo Remains as National Coordinator of ONC Along with New Position

Posted on October 31, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com 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 InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

In case you missed it, last week it was announced that Karen DeSalvo had been appointed Assistant Secretary of Health focused on Ebola by HHS Secretary Burwell. In that same announcement Jacob Reider also announced his departure from ONC.

While the news was true that DeSalvo was taking on a new role at HHS as Assistant Secretary of Health, ONC also published a blog post that DeSalvo would stay on as National Coordinator of Health IT as well:

Dr. DeSalvo will serve as Acting ASH while maintaining her leadership of ONC. Importantly, she will continue to work on high level policy issues at ONC, and ONC will follow the policy direction that she has set. She will remain the chair of the Health IT Policy Committee; she will continue to lead on the development and finalization of the Interoperability Roadmap; and she will remain involved in meaningful use policymaking. She will also continue to co-chair the HHS cross-departmental work on delivery system reform.

Lisa Lewis will provide day to day leadership at ONC. Lewis served as Acting Principal Deputy National Coordinator before Dr. DeSalvo joined ONC, so she has had experience with all parts of our work. She will lead our extremely talented and very strong team during Dr. DeSalvo’s deployment to the Office of the Assistant Secretary for Health.

But most importantly, the team that is ONC is far more than one or two leaders. The team of ONC is personified in each and every individual – all part of a steady ship and a strong and important part of HHS’ path toward delivery system reform and overall health improvement.

Seems like an awkward arrangement if you ask me. DeSalvo will be providing high level leadership on policy direction, but Lisa Lewis will handle the day to day leadership. That job description for DeSalvo sounds like something an Assistant Secretary of Health might do and Lisa Lewis’ job sounds like something the National Coordinator would do.

I’m sure there’s more to this story. Maybe moving DeSalvo to Assistant Secretary was a way for ONC to save money and keep DeSalvo on board working on healthcare IT. If ONC’s budget gets cut, then HHS still has a way to pay for DeSalvo. Maybe that’s why Lisa Lewis can’t be promoted to full National Coordinator. Then again, maybe it’s like I mentioned when we first heard the DeSalvo news, DeSalvo is more of a public health person than she is a healthcare IT person.

The fact that DeSalvo is remaining as National Coordinator is interesting. However, I just came back from CHIME (healthcare CIO conference) where DeSalvo was scheduled as one of the plenary session speakers. However, she didn’t show and so the whole session was cancelled. I guess you could make the case that she’s got Ebola to deal with right now, but it also illustrates how health IT will be playing second fiddle for her going forward. Likely says something about the future of ONC.

ICD-10 Ebola Infographic

Posted on October 21, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com 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 InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

In my post on funny ICD-10 codes ruining the ICD-10 brand, I briefly commented how there’s no ICD-9 code for Ebola, but that there is one for ICD-10.

Beth Friedman from Agency Ten22 shared a link to this ICD-10 Ebola Infographic that I thought readers would find really interesting.

Ebola ICD-10 Infographic

One more reason to finally implement ICD-10 in the US.

Ebola Lapse in Dallas Offers Few Lessons, Except About Our Over-reliance on Technology

Posted on October 8, 2014 I Written By

Andy Oram is an editor at O'Reilly Media, a highly respected book publisher and technology information provider. An employee of the company since 1992, Andy currently specializes in open source, software engineering, and health IT, but his editorial output has ranged from a legal guide covering intellectual property to a graphic novel about teenage hackers. His articles have appeared often on EMR & EHR and other blogs in the health IT space. Andy also writes often for O'Reilly's Radar site (http://oreilly.com/) and other publications on policy issues related to the Internet and on trends affecting technical innovation and its effects on society. Print publications where his work has appeared include The Economist, Communications of the ACM, Copyright World, the Journal of Information Technology & Politics, Vanguardia Dossier, and Internet Law and Business. Conferences where he has presented talks include O'Reilly's Open Source Convention, FISL (Brazil), FOSDEM, and DebConf.

Of all the EHR problems encountered daily across the country, the only one to hit the major news outlets was a non-story about a missed Ebola diagnosis in Dallas, Texas. Before being retracted, the hospital’s claim of an Epic failure launched a slew of commentary in the health IT field. These swirled through my head last night as I tried to find a lesson in the incident.

The facts seem to be as follows. A 42-year-old man named Thomas Eric Duncan arrived from Liberia and checked in to the emergency room at Texas Health Presbyterian Hospital Dallas complaining of symptoms consistent with an Ebola diagnosis. He told the admitting nurse he had come from Liberia, and the nurse entered the data into the Epic EHR.

The purpose of recording the patient’s travel history, however, seemed to be simply to determine the need for immunizations, so the EHR kept it within a nurse’s section of the data (which the hospital called a “workflow”) and did not display it to the doctor. The doctor sent Duncan home, where he came into contact with about 100 people who were potentially infected. His symptoms worsened and he returned to the hospital two days later, where he was finally diagnosed correctly and admitted.

Late night musing #1: If Texas Health Presbyterian Hospital Dallas can’t diagnose a case of Ebola, why do they think they can treat one? The hospital has won numerous awards, including one for patient safety–I guess you’re safe once you’re admitted.

Meanwhile, the city of Dallas waited several extra days to clean up infected sheets and other belongings from the Duncan home. In Africa, such detritis are recognized as a major source of new Ebola infections.

Late night musing #2: Does this reflect the competence of public health officials in this country? Maybe we should turn the job over to the Secret Service.

It’s really a shame that the national press jumped on the hospital’s announcement that the EHR was the source of the problem. Commenters criticized the hospital right away, asking why the nurse didn’t simply tell the doctor, and why the doctor didn’t ask on his own.

Finally, the hospital backed off from blaming Epic, thus making the hospital look even stupider and more guilty than it already appeared. Nevertheless, EHRs at some hospitals may be designed to flag warning signals.

Clearly, there are many layers to this health care failure. I don’t blame the nurse, or even the doctor. ERs are always busy, and the nurse might never have known who would see the patient or even be in the ER when the doctor finally saw him.

But I do find a small lesson in the brief appearance of the EHR as a pivotal character in the story. The nurse thought he or she was doing their job just by entering the data into the EHR, and the doctor thought he was doing his job by reading it. The EHR had loomed as a magical solution to health care workflow–in the minds of hospital administrators, if not the ER staff.

Maybe if the nurse knew that the travel history was for the purpose of immunizations, he or she would not have relied on the EHR to use that information for diagnosis. Besides showing the need for training, some of my colleagues suggest that this problem calls for FDA regulation of EHR interfaces. They also suggest that systems use good user interface design to highlight important information (which would require a definition of what’s “important”) or at least allow searches for critical elements of the record.

Late night musing #3: Behind this also lies the mindlessness of much data collected by EHRs. I’m sure the nurse knew whether the unfortunate Mr. Duncan was a smoker and whether he suffered from depression, because regulations require these things to be recorded. Travel history became just another one of these automatic requirements to be tossed into the EHR and forgotten.

My story also concerns the musings of other health IT commentators, who suggested that EHRs be better integrated into “workflows”–as if every clinician follows a mechanical path of treatment and the EHR can figure out what it is.

Another thoughtful posting calls for integrating infectious diseaess into clinical decision support. But as my colleague Sandra Raup (R.D., J.D., M.P.H.) points out, CDS depends on a long history of clinical data collection. One can’t instantly add a new disease.

It might have been useful for some international health organization to realize, when the Ebola outbreak began to spread, that it would eventually break out of central Africa, and then to provide an app to hospitals around the world for checking symptoms and travel history. There is certainly a creative role for health IT to play.

I think the messiness of the Texas Health Presbyterian Hospital Dallas story shows why EHR failures, numerous as they are, don’t get reported in the press. There are just too many complicating factors. The EHR is partly configured by the clinic’s staff, who thereby become responsible for some of its decisions. The EHR failure usually comes when the staff is under stress, when they have communication problems, when the patient’s condition is rare. Ascribing blame becomes a tangled mess; one must start designing systems with multiple, redundant points to catch failures that can fall through the cracks.

So one level, this is just another sad story of humanity’s tendency to trust too much in its technology, a story that ranges from the flight of Icarus to the sail of the Titanic and the failure of the Fukushima Daiichi nuclear power plant. On other, it’s a familiar story of a systemic problem leading to what’s sometimes called a “normal failure.” Not much new to learn, but lots of work to do. Clinicians have to evaluate EHRs and know how the data is used, a more open system in all directions.