Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Rebecca Armato

Rebecca Armato



Is IT Innovation Driving Physicians Out The Door?

Recent health IT initiatives are forcing many frustrated clinicians to take early retirement. IT leaders need to realize that our national treasure is becoming an endangered species.

Rather than face the perfect storm of decreasing reimbursement, increasing costs, legislative mandates, and penalties around technology adoption, information exchange, and Meaningful Use, an alarming number of physicians are making the decision to "go quietly into the night" and retire early from practice.

Some are leaving the profession as many as 10 years earlier than they had anticipated. Rather than consider change, physicians are placing a DNR on their practices, saying no to investing in tools necessary to efficiently manage their businesses. For some physicians, the hospital's own IT transformation activities are the tipping point driving them to retire. We need to do something about this problem before it's too late.

Physicians are trained to make decisions, not ask questions--except of patients. The noble personality that gives them the confidence to heal also causes them to feel they have to be all-knowing and all-seeing on all topics. Many physicians are not comfortable publicly sharing their questions about technology selection, adoption, or optimization--fearing it will expose ignorance about topics on which they believe their peers have all the answers. Yet with so little time just to keep up with clinical research in their own specialties, when do physicians have time to become IT experts as well?

Consider what happens when physicians experience an adverse outcome. Unless they're residents or are in a behind-closed-doors peer review, they're not encouraged to expose the troubling issue so they can brainstorm with their peers to improve their clinical decision-making. For fear of retribution by attorneys representing patients or grieving families, they have been trained to suffer in silence and guess at what might have happened and/or what they might do differently next time.

Unfortunately, many physicians apply that same learned response to their selection, implementation, and adoption of EHRs. They don't openly discuss their questions, concerns, thought processes, and experiences as they evaluate technology. Nor do they share best practices or lessons learned while adopting and utilizing new health record tools and processes. Instead, they kick into "fight or flight" mode during EMR implementation, too often letting their practices quietly flat-line.

[ Looking for a PACS platform to replace an outdated system? See 9 Must-See Picture Archiving/Communication Systems. ]

In my view, physicians fall somewhere between a national treasure and natural resource, and one that's becoming an endangered species. Fewer physicians are encouraging their children to go into medicine, unsure of the future reward for all the risk. Physicians are deciding to retire early, afraid to change, unwilling to learn something new, and unsure if they can. While your first instinct as an IT manager may be to push forward with your hospital's EHR implementation without them--don't. You may not realize exactly how much impact on care they are providing in your community.

Hospitals have a license to house patients; physicians have the license to treat them. It is only by working together that we can continue to provide care in our community. If physicians go, who will step in to provide care to those patients? With empathy and the right engagement, these physicians will ensure the successful adoption and utilization of the technology needed to ensure your organization not only survives but also thrives during these turbulent times.

Huntington Hospital, where I serve as executive director, physician & interoperability services, is working with physicians in our community to help them consider their options, share their experiences, best practices, challenges, and missteps, and figure out how to create efficient workflows.

 1 | 2  | Next Page »


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.