Big Data. Big Decisions
InformationWeek
Special Coverage Series


Healthcare Experts Propose EHR Safety Guidelines

Framework aims to reduce electronic health records system errors that obstruct patient safety.

6 Healthcare Revenue Cycle Management Systems To Watch
6 Healthcare Revenue Cycle Management Systems To Watch
(click image for larger view and for slideshow)
A pair of health IT experts has proposed a framework for national patient safety guidelines that the industry could apply to electronic health records (EHR) systems. Their article appears in the New England Journal of Medicine as the drumbeat of concern about potential hazards of EHRs grows ever louder.

"Recent evidence has highlighted substantial and often unexpected risks resulting from the use of EHRs and other forms of health information technology," note Dean F. Sittig, a professor at the University of Texas Health Sciences Center in Houston, and his co-author Hardeep Singh, MD. But in their view, the problem is not in the technology, but in how it is being used. They propose guidelines to reduce the danger.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Sittig and Singh's framework consists of three consecutive phases:

1. Make sure that hardware and software work properly. This is especially important because "a malfunction can rapidly affect not only a single department or institution but possibly an entire community," the authors note.

2. Make sure EHRs are used appropriately. This applies not only to human factors such as "alert fatigue," but also to organizational policies such as not requiring that all physicians use computerized physician order entry (CPOE). "For example, if CPOE systems were to be used on some nursing units but not others, clinicians would need to check for orders and test results in multiple locations, increasing the likelihood that some information would be overlooked," the paper notes.

3. Use EHRs to monitor and improve patient safety. For instance, the authors point out, current methods used to measure safety events rely too heavily on incident reports, which cover only a small portion of incidents. "In contrast, [EHR] systems can be programmed to automatically detect easily overlooked and underreported errors of omission, such as patients who are overdue for medication monitoring, patients who lack appropriate surveillance after treatment and patients who are not provided with follow-up care after receiving abnormal laboratory or radiologic test results."

[ For more on the role of EHRs in clinical research, see Health IT's Next Big Challenge: Comparative Effectiveness Research. ]

Some of the proposed guidelines would place a heavy burden on institutions that currently struggle just to achieve the much lower criteria of Meaningful Use. For example, Sittig and Hadeep suggest that hospitals enter all orders through CPOE for safety reasons. In stage 1 of Meaningful Use, hospitals must attest that 30% of medication orders go through CPOE. In stage 2, beginning in 2014, 60% of medication, lab and radiology orders must go through CPOE.

Similarly, the authors observe that, "many institutions are not currently coding some of the critical data needed to maximize safety." As a result, their EHRs cannot provide feedback or interpretation to clinicians based on the data, such as alerts on drug-drug interactions or reminders to read test results. So the paper suggests that "critical data on medications, allergies, diagnostic test results and clinical problems are entered as structured or coded data in the EHR."

In both CPOE and structured data entry, staff resistance can hamper hospitals' efforts to expand the use of health IT, even for patient safety reasons. But Sittig told InformationWeek Healthcare that physicians do not have to enter the safety-critical data themselves. Lab data can flow into the EHR automatically in coded form, and staff members can update allergy, medication and problem lists. Nevertheless, hospitals don't often do that now.

Sittig emphasized that despite reports like the recent one from ECRI Insttitue on EHR safety hazards, "The EHR is a critical piece of the patient safety solution. I realize we're having trouble getting our computers to work correctly, and to get people using them right, but I don't think they're inherently dangerous. They're inherently safe."

He also pointed out that healthcare organizations need to be cognizant of how safety issues related to EHR usage differ from other safety problems.

"When you rely on a computer, the scale and the size of the errors can be much bigger than they were before. The analogy in the car field is when you have a freeway, you have multi-car pileups, which you didn't have before there were freeways." He pointed out: "With EHRs, you're building highly interconnected systems that can cause problems very quickly and get out of hand very quickly. That's why we need to make sure they're as safe and effective as can be so we don't have these widespread problems."



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.