Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Marianne Kolbasuk McGee

Marianne Kolbasuk McGee

Senior Writer, InformationWeek

Compromise On Health Data Access May Be Ugly

Some hospitals and doctors oppose giving patients electronic data as quickly as required by proposed Meaningful Use Stage 2 regulations. Consumer groups want more speed--and the compromise likely won't please either side.

9 Health IT Tools Patients Should Understand
9 Health IT Tools Patients Should Understand
(click image for larger view and for slideshow)
The government's proposed rule for Meaningful Use Stage 2 and the comment period that ended earlier this week kicked off a battle between patients and providers. At the heart of the war is the Centers for Medicare and Medicaid Services proposal that patient information be available to the individuals within 36 hours of discharge from a hospital and within 24 hours of an office visit.

Understandably, patient and consumer rights groups want individuals able to access their medical information as soon as possible so they can act on it swiftly, while healthcare providers want more time to gather data and make it available to patients. Providers fear they'll be forced to rush complex data to patients before it's complete, accurate, and secure.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

On the provider end of the battlefield is the American Hospital Association, which says 36 hours is not enough time to provide discharged patients with information about their hospital stay. The proposed CMS requirement is technically "unfeasible" and riddled with potential conflicts with current HIPAA privacy and security regulations, says the AHA. The AHA has requested CMS to modify its proposed rule and give hospitals 30 days to make information available to patients upon discharge.

[ Read More Patient Data Risks, Lawsuits Predicted In 2012. ]

The AHA says it's not possible for hospitals to gather and deliver the proposed patient information within 36 hours. That information includes:

--Admittance and discharge date and location.

--Reason for hospitalization.

--Names of care providers during hospitalization.

--Problem list maintained by the hospital on the patient, verified to be up-to-date.

--Relevant past diagnoses known by the hospital.

--Medication list maintained by the hospital on the patient, both current admission and historical, and verified to be up-to-date.

--Medication allergy list maintained by the hospital on the patient, both current admission and historical, and verified to be up-to-date.

--Vital signs at discharge.

--Laboratory test results that are available at time of discharge.

--Care transition summary and plan for next care provider for transitions other than home.

-- Discharge instructions for patient.

-- Demographics maintained by hospital on gender, race, ethnicity, date of birth, preferred language, and smoking status.

In addition, the CMS proposal requires all of this information to be available for patients to: 1) view online; 2) download, in both a "human readable form" and coded to the specific vocabulary, document, and other standards adopted by the Office of National Coordinator for Health IT; and 3) request that the hospital transmit it to them.

"Thirty days are necessary to make determinations about how to respond to a request no matter the format of the protected health information," said the AHA in its comments to CMS.

"While providing an electronic copy of protected health information maintained in an e-health record eventually may be facilitated more easily by technology, the process of determining which records are relevant and appropriate takes the same amount of time as it does for evaluating paper records," wrote the AHA.

 1 | 23  | Next Page »


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.