Commentary

Marianne Kolbasuk McGee
Senior Writer, InformationWeek  

Meaningful Use Rules Make Sense To Patients

I'm not a doctor or nurse. Nor am I a hospital administrator, CIO or health IT worker. However, I am a patient. So while the government's long-awaited, meaningful use, stage 1 "core objectives" could very well entail a lot of process changes and costly technology to implement for healthcare providers, from a patient perspective--my perspective--many of the requirements sound reasonable, even commonsensible.

I'm not a doctor or nurse. Nor am I a hospital administrator, CIO or health IT worker. However, I am a patient. So while the government's long-awaited, meaningful use, stage 1 "core objectives" could very well entail a lot of process changes and costly technology to implement for healthcare providers, from a patient perspective--my perspective--many of the requirements sound reasonable, even commonsensible.For instance, among core objectives for healthcare providers in stage 1 is supplying more than 50% of patients with an electronic copy of the patient's health information within three business days of patients asking.

Patient's health information just that--the patient's information. An individual expecting to get a copy of his or her medical information within three days of asking sounds rational to me. Granted, waiting three days isn't exactly the same as real time access to data. But in some states today, rules say patients should be able to receive copies of their medical information "within a reasonable amount of time." That wait could last weeks.


More Healthcare Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

So, by comparison, waiting no more than three days for getting an electronic copy is reasonable, unless a patient is in urgent need of these records sooner. Of course for healthcare providers who don't already have some kind of e-health record system plans in place, fulfilling those requests might sound impossible now. (Then again, isn't the chore of making photocopies of paper records for patients even more work for providers?)

Once a patient's health information becomes routinely digitized, it's also reasonable to expect that many records could be available to patients (via a portal, for instance) much sooner than three days--maybe immediately (as long as sensitive data, like important lab results, for instance, are vetted first by clinicians.)

Among other core requirements are maintaining active lists for health problems, diagnoses, drug allergies and medications for 80% of patients. Again, that's basic--but important information--that can help improve the safety and quality of care that patients receive, especially when patients receive care from multiple providers. Sounds like a no-brainer.

The next wave of meaningful use requirements that come in stages 2 and 3 will likely be tougher to meet, since health department officials admit that many of the original and more challenging stage 1 goals set out in the proposed rules released earlier this year are just being deferred to later.

And while the core requirements aren't perfect, from a patient's perspective, many appear very practical.

As time goes on, the government won't be the only one raising the bar in its meaningful use requirements. Patients' expectations in the quality and safety of care they receive--and timely, easy, secure access to their own health information--will continue to rise, too.



InformationWeek has published an in-depth report on this year's Healthcare Information and Management Systems Society conference. This report offers the best healthcare IT advice, insight, and analysis coming out of that conference. Download the report here (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

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek 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. InformationWeek 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.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links