Commentary

Mitch Wagner
Executive Editor, Community  

Blumenthal: Tear Down E-Health Barriers

The U.S.'s top e-health official urged healthcare organizations to tear down the barriers to effective exchange of e-health records in a message to healthcare providers.

The U.S.'s top e-health official urged healthcare organizations to tear down the barriers to effective exchange of e-health records in a message to healthcare providers.Dr. David Blumenthal, national coordinator for Health Information Technology, addressed healthcare providers in an electronic message Nov. 12. Blumenthal's office is charged with fleshing out the Health Information Technology for Economic and Clinical Health (HITECH) Act requirements of the U.S. American Recovery and Reinvestment Act (ARRA) of 2009. In one of a series of messages explaining the provisions of the legislation, he said:

A key premise: information should follow the patient, and artificial obstacles - technical, business related, bureaucratic - should not get in the way. As a doctor, I have many times wanted access to data that I knew were buried in the computers or paper records of another health system across town. Neither my care nor my patients were well served in those instances. That is what we must get beyond. That is the goal we will pursue, and it will inform all our policy choices now and going forward. This means that information exchange must cross institutional and business boundaries. Because that is what patients need. Exchange within business groups will not be sufficient - the goal is to have information flow seamlessly and effortlessly to every nook and cranny of our health system, when and where it is needed, just like the blood within our arteries and veins meets our bodies' vital needs.

More Healthcare Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The HITECH Act is "pretty specific about eliminating inappropriate barriers," he said. These include:

- Commercial barriers that "restrict the secure, private exchange of information required for patient care across provider or network boundaries. Some of these arrangments may improve care for those inside their walls. But ultimately, they have the potential to carve the nation up into disconnected silos of information.... Consumers, patients and their caretakers should never feel locked into a single health system or exchange arrangement because it does not permit or encourage the sharing of information."

- Economic barriers.

- Technical barriers which limit interoperability. Information must "follow patients wherever they go."

The HITECH Act also calls for building information exchanges across jurisdictions. Grants for states and state-designated entities totaling $564 million target information exchanges "not only within each state but explicitly as part of a nationwide framework" (italics Blumenthal's). HHS will start announcing awards this winter.

The message from Blumenthal was third in a series, according to HealthcareIT News.

Blumenthal's two previous e-mails, on Aug. 20 and Oct. 1, focused on how electronic health record systems could transform today's "antiquated paper-based system" and on the term "meaningful use." The final definition of meaningful use is expected in December.

The next e-mail is likely to address privacy and security issue, he said.



Blue Cross of Northeast Pennsylvania, the University of Louisville School of Medicine, and a range of large and small healthcare providers are using mobile apps to improve care and help patients manage their health. Find out how. Download the report here (registration required).

Follow InformationWeek on Twitter, Facebook, and LinkedIn:

Twitter: @InformationWeek @IWpremium @MitchWagner

Facebook: InformationWeek Mitch Wagner

LinkedIn: InformationWeek Mitch Wagner


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