Big Data. Big Decisions
InformationWeek
Special Coverage Series


Stage 3 Meaningful Use Proposals: Too Ambitious?

Most objectives merely build on stage 2 -- but some new criteria might generate pushback, consultants say.

6 Healthcare Revenue Cycle Management Systems To Watch
6 Healthcare Revenue Cycle Management Systems To Watch
(click image for larger view and for slideshow)
The Health IT Policy Committee (HITPC), which advises the government on its electronic health record incentive program, released its preliminary recommendations for Meaningful Use stage 3 requirements that will go into effect in 2016. After the recommendations are published in the Federal Register, possibly this month, there will be a 45-day public comment period.

The bulk of the stage 3 objectives in the 44-page document reiterate stage 2 goals, with higher thresholds for showing Meaningful Use. This should please hospitals and eligible professionals, Chris Giancola, a principal consultant at CSC, told InformationWeek Healthcare. "They're going to be grateful that these are mostly increase-of-adoption sort of changes, where you ratchet up the percentages you have to comply with to meet the objectives."

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Michelle Holmes, a senior manager with ECG Management Consultants in Seattle, agreed. "The stage 3 proposal is a lot about coordination between different provider organizations, whether practices or hospitals," she said. "It's about more extensive use of decision support at the point of care, and more patient engagement. There isn't anything new in those three areas; they've just taken them further."

[ To see how patient engagement can help transform medical care, check out 5 Healthcare Tools To Boost Patient Involvement. ]

There are new objectives, however, and some of them are quite ambitious. For example, one new item would require providers to give 10% of patients the ability to submit patient-generated health information to improve performance on high-priority health conditions; to increase patient engagement in care; or both. HITPC suggests this could be accomplished through "semi-structured questionnaires."

Physicians are likely to push back against this requirement because they don't have control over patient behavior, Holmes said. She said the recommendation will probably make it into the stage 3 final rule, but with exclusions for physicians who would have trouble meeting this objective. For example, she noted, a geriatrician might have difficulty finding 10% of elderly patients willing to fill out a Web-based questionnaire.

Another proposal would expand the information that eligible clinicians and hospitals would have to provide at transitions of care to include a care synopsis, setting-specific goals, and instructions for care during the transition. If EHRs could be programmed to extract this additional data automatically, it would be no big deal, Giancola said.

Even if that's the case, it could lead to a change in workflow, Holmes said. Today, primary care physicians often have a staff member assemble information -- the latest visit note and lab results, for example -- to send along with a referral to a specialist, she said. "The idea here is that everything needed to support that referral is being generated [in the EHR] as the provider orders the referral. When he does that, the material is packaged in electronic format, and the patient could walk out the door with it. It puts the burden on the provider to complete the relevant information sooner and not be as reliant on someone else to do it."

Beyond transitions of care, Giancola was surprised that HITPC proposed requiring that certified EHRs be able to query other systems and respond to queries. "'Push' has been hard enough to achieve -- just getting people to send information from one place to another," he noted. "But the ability to ask another system for information or to answer a request for information -- that's gigantic."

On the other hand, Giancola pointed out, HITPC is still not talking about having providers use their EHRs to exchange data with disparate EHRs in separate business entities. This was originally proposed as a Meaningful Use stage 2 criterion, but that was later watered down, he noted.

Holmes was also a little surprised that the policy committee hasn't yet required this kind of data interchange. "That part seems a little bit soft to me," she said. She suggested that there might be some changes in the final stage 3 proposal.

What HITPC does propose, however, is that hospitals be required to electronically inform a care team member, such as a primary-care physician or a care coordinator, when a patient visits the ER or is admitted to or discharged from the hospital. Although the mechanism isn't specified -- it could be via pager, text, secure email, or a clinical summary sent to another EHR -- the mere fact of requiring such an event to trigger a message to the patient's care team would be a major change, Giancola said.

Another big step is to require that providers implement 15 clinical decision support interventions, compared with just five in stage 2. Certified EHRs would also need more clinical decision support capabilities under the stage 3 proposal.

In Holmes' view, providers could use patient registries capable of generating alerts to meet this requirement. Although EHRs have not had good registry capabilities up to now, they're improving, she said. Third-party registries connected to EHRs might enable providers to satisfy this objective in the meantime, she said.

Clinical, patient engagement, and consumer apps promise to re-energize healthcare. Also in the new, all-digital Mobile Power issue of InformationWeek Healthcare: Comparative effectiveness research taps the IT toolbox to compare treatments to determine which ones are most effective. (Free registration required.)



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.