Big Data. Big Decisions
InformationWeek
Special Coverage Series


Electronic Records May Increase Malpractice Lawsuit Risk

EHRs may reduce medical liability for some errors, but could create new forms of medical liability and expose existing liability issues, says report.

17 Leading EHR Vendors
(click image for larger view)
Slideshow: 17 Leading EHR Vendors
The rapid movement toward electronic health records (EHRs) may unwittingly raise physician risk for malpractice lawsuits and push liability insurers to raise their premiums, a new report suggests.

EHRs may reduce the medical liability for certain errors, but it appears they "both create new forms of medical liability and expose existing liability issues in the healthcare environment that might otherwise remain unknown," says a white paper published by the AC Group, a Montgomery, Texas, health IT research and consulting firm.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

The paper calls on federal officials to slow the pace of the federal Meaningful Use incentive program to get medical practices and hospitals to use EHRs. Co-authors Mark Anderson, CEO of the AC Group, and veteran clinical informatics professional Dr. Larry Ozeran say the "artificially short deadlines" for implementation could raise malpractice risks by spurring vendors to cut corners on developing products and rushing users through training.

[ there are other concerns about EHRs. Read GE Admits Inaccuracies With EHR Reporting. ]

Anderson and Ozeran reviewed 65 ambulatory EHRs that were certified to meet federal 2011 Meaningful Use standards and found that more than 90% didn't offer "adequate medico-legal training" and that 95% raised specific legal issues.

"Either could increase the potential risk of a liability claim and would hamper its defense," they wrote. "As is often the case, technology is advancing more rapidly than our ability to identify and address the medico-legal issues. The result of this uneven progression is that physicians and other stakeholders may be unknowingly exposed to medical liability risk."

Shortfalls in EHR functionality also could contribute to increased liability risk, since the Office of the National Coordinator for Health Information Technology's (ONC) certification criteria doesn't require EHRs to check drug orders against laboratory results or take into account social and family medical history in creating alerts.

"Everyone thinks ONC covers everything," Anderson told InformationWeek Healthcare at the annual Medical Group Management Association conference, now underway in Las Vegas. But most commercial EHRs that have ONC certification don't, for example, create alerts for more frequent mammograms if a female patient has indicated that her mother has had breast cancer, he explained.

Also, clinical notes provide too many "normal" indicators, according to Anderson and Ozeran. EHRs often are too focused on recording billing codes and don't do a good job of documenting what doctors are really thinking.

AC Group further investigated the specific functionality of 42 ambulatory EHRs and found that nearly 90% couldn't provide drug-lab alerts. More than 80% didn't run interaction checking during the prescription refill process, and about 60% didn't automatically update clinical decision support to reflect changes in recommended treatments. In many cases, Anderson added, drugs ordered by other physicians don't always show up in medication lists, so the EHR could miss critical safety alerts.

"It creates a gigantic risk," Anderson said. He said his review actually found two deaths that could be traced to EHRs missing alerts for medications patients shouldn't have been given.

In addition, poorly designed and implemented EHRs could make it far easier for malpractice attorneys to press their cases by mining the metadata embedded in patient records. "During the discovery process of a malpractice claim, the printed record shows the current information but not the information that was available to the provider at the time the care was rendered," the report says. "Time synchronization between different electronic charting systems is lacking--for example, one time sequence might indicate that a child was born before the C-section was performed."

Anderson and Ozeran recommended that EHR vendors "strongly consider" external reviews of their products for potential medical malpractice concerns their customers could face. Vendors so far have resisted, since their software offerings do meet federal standards, Anderson says. But vendors and providers should act to head off potential problems, he adds.

Anderson says he's talking separately with five malpractice insurance carriers on developing policies to mitigate EHR-related risk, which could include higher premiums for using certain products. "Carriers may want to clarify their coverage with their clients, both the circumstances and the limits of liability protection, if different from their standard liability policy," the report says.

A spokesman for the Physician Insurers Association of America (PIAA), the trade group for medical malpractice insurers, said he wasn't aware of any discussions between malpractice insurers and EHR vendors. The HIMSS EHR Association, an affiliate of the Healthcare Information and Management Systems Society, also didn't comment for this story.



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.