Big Data. Big Decisions
InformationWeek
Special Coverage Series


EHRs May Shortchange Depression Patients

Electronic health records may focus a doctor's attention on certain medical conditions, leading to undertreatment for depression, researchers suggest.

12 EHR Vendors That Stand Out
12 EHR Vendors That Stand Out
(click image for larger view and for slideshow)
Patients with three or more chronic conditions are half as likely to receive treatment for their depression during a visit to a doctor's office that uses electronic health records (EHRs) when compared with patients who visited paper-based practices. At least that's the conclusion of an investigation recently published in the Journal of General Internal Medicine.

The study, conducted by researchers at the University of Florida and the University of South Florida, analyzed the odds of receiving treatment for depression during a doctor's visit by examining data from the National Ambulatory Medical Care Surveys (NAMCS) of 3,467 physician office visits by patients from 2006 to 2008. Researchers focused on visits to primary care providers by patients ages 18 and older with physician-identified depression. The 3,467 visits were divided into two groups: 2,584 visits to practices without EHRs, and 883 visits to practices with EHRs.

The EHRs showed that patients were receiving either mental health counseling or one or more antidepressants, such as amitriptyline, amoxapine, and bupropion. The study revealed that 1,092 patients had one chronic condition, 916 had two, and 1,459 had three or more chronic conditions, including arthritis, asthma, cancer, and congestive heart failure.

[ Practice management software keeps the medical office running smoothly. For a closer look at KLAS' top-ranked systems, see 10 Top Medical Practice Management Software Systems. ]

The report found that for patients with three or more chronic conditions, EHRs "appear to have an unintended negative association with depression care provided during visits made by primary care patients with multiple chronic conditions." On the other hand, researchers also found that patients with depression combined with two or fewer chronic conditions who visited a physician with an EHR had the same probability of being treated for depression as those patients whose physician practice operated without an EHR.

Dr. Jeffrey Harman and his colleagues can't explain why patients who have three or more chronic conditions and visited a physician using an EHR were significantly less likely to be treated for their depression, but in an interview with InformationWeek Healthcare, he said that the study does offer a warning for EHR-enabled physicians.

"The study suggests two things ... when physicians are working with an EHR they may end up being engaged with the computer instead of the patient," Harman said. "Second, EHRs are often designed to focus physicians' attention on biomedical conditions, and the more medical conditions that exist, the greater the attention is toward addressing, for example, diabetes, high blood pressure, or congestive heart failure" rather than depression.

According to Harman, whatever the underlying cause, EHR vendors need to address how they design these systems in the future.

"EHRs are tools meant to assist physicians in the delivery of care and to improve patient outcomes," Harman said. "Primary care physicians only have about 15 minutes per patient. Therefore vendors need to think about workflow--how the physician works with these computers, and how to make EHRs easier to access and enter information related to mental illness and other chronic conditions."

InformationWeek Healthcare brought together eight top IT execs to discuss BYOD, Meaningful Use, accountable care, and other contentious issues. Also in the new, all-digital CIO Roundtable issue: Why use IT systems to help cut medical costs if physicians ignore the cost of the care they provide? (Free with registration.)



Related Reading


More Insights




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.