Big Data. Big Decisions
InformationWeek
Special Coverage Series


Healthcare Experts Confront EHR-Related Medical Errors

AMIA task force calls on vendors, clinicians, academics and policy-makers to rethink poorly designed health IT systems.

 7 Portals Powering Patient Engagement
7 Portals Powering Patient Engagement
(click image for larger view and for slideshow)
Though questions about the efficacy of electronic health records (EHRs) seem to have increased recently, usability and safety of health IT systems have been on the minds of medical informaticists for a while.

The American Medical Informatics Association (AMIA), which convened an EHR usability task force in late 2011, this week released a position paper on EHR usability in which the group called on multiple stakeholders to act in order to lessen the chance of patient harm from poorly designed and implemented technology.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

In a position paper published online in the Journal of the American Medical Informatics Association (JAMIA), Bethesda, Md.-based AMIA spelled out 10 recommendations in four areas: research into health IT-related human factors; health IT policy; vendors; and clinician end users.

"These AMIA recommendations are intended to stimulate informed debate, provide a plan to increase understanding of the impact of usability on the effective use of health IT, and lead to safer and higher quality care with the adoption of useful and usable EHR systems," the paper said.

[ Is government throwing our money away on health IT? See Healthcare IT: Savior Or Sinkhole? ]

"The fundamental approach to health IT needs to change," lead author Dr. Blackford Middleton, corporate director of clinical informatics research and development at Partners Healthcare System and 2013 AMIA chair-elect, told InformationWeek Healthcare. "We've been installing it and not measuring it like we would any other intervention."

It is time, Middleton said, to take a step back and assess the direction of health IT, EHRs and the federal Meaningful Use incentive program. "We were motivated by the mounting evidence that there were unintended and untoward consequences with using health IT," Middleton explained.

Middleton gave a preview of the report at the 2012 AMIA annual meeting in November, but AMIA would not allow the authors to grant interviews until the paper's publication. He noted that the U.S. government's Office of the National Coordinator for Health Information Technology (ONC) has since issued a draft national patient safety plan based on a 2011 Institute of Medicine (IOM) report about the role of health IT in delivering safer care. ONC is taking public comments on the plan through Feb. 4.

AMIA called on the academic community to accelerate research into usability and human factors by standardizing use cases, developing a core set of measures for health IT-related adverse events and defining best practices for safe EHR implementation and usage.

On the policy front, the AMIA panel said ONC's policy framework should consider usability in the context of standardization and interoperability. Federal officials also should establish a reporting system for adverse events related to health IT, as the IOM called for in 2011, and create an educational program about safe and effective EHR use, the paper said.

For vendors, AMIA recommended that an industry coalition develop a common style guide for certain EHR functions related to patient safety to streamline training, much like all automobiles have similar information sources such as odometers and fuel gauges. Vendors also should conduct formal usability assessments on key EHR functions, AMIA said.

End users have responsibilities, too, according to AMIA. They should adopt best practices for EHR implementation and management, as well as monitor how clinicians use health IT systems and report any adverse events, the informatics group said.

"Following best practices for EHR implementation is essential to safe and effective use," the AMIA task force wrote. "User error may result in untoward outcomes and unintended negative consequences. These may also occur as a result of poor usability, and may also be an emergent property only demonstrated after system implementation or widespread use. User errors may occur without adverse events, and some may not even be apparent to the user, analyzed by hospital or clinic review boards, or reported to the vendor."

The AMIA usability task force included a diverse group from vendor companies, healthcare provider organizations, and academia. One of the members was University of Pennsylvania sociologist Ross Koppel, a longtime critic of major health IT vendors, which he considers barriers to true interoperability of health information. "The idea was to have a balanced number of industry people and academics," Middleton explained.

The policy statement concentrates on EHR usability, without considering medical devices, mobile devices, personal health records and other forms of health IT. Nor does the AMIA paper address potential EHR regulation by the U.S. Food and Drug Administration (FDA), as had been discussed in the formative days of the Meaningful Use program.

Middleton said the FDA's interest in health IT would lie in clinical decision support for medical devices. But the FDA probably has not stepped in because there is a "learned intermediary" such as a physician or nurse, not devices, making actual clinical judgments.



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.