Commentary

Bob Evans
Senior VP, Global CIO  

Google Health Records Reveal Grossly Inaccurate Info

Google Health users are finding stunning inaccuracies in medical records imported from primary-care physicians and hospitals because Google takes some information from insurance billing records that use broad and imprecise codes to describe patient treatment. One electronic health-records expert says "this kind of information should never be used clinically." Feeling better?

Google Health users are finding stunning inaccuracies in medical records imported from primary-care physicians and hospitals because Google takes some information from insurance billing records that use broad and imprecise codes to describe patient treatment. One electronic health-records expert says "this kind of information should never be used clinically." Feeling better?The comment above is from Dr. Daniel Z. Sands in describing how a kidney-cancer patient's Google Health record indicated - erroneously - that the patient's cancer had spread to his brain or his spine, and also that he had a number of other life-threatening conditions he never knew about.

As these types of frightening incidents come to light, more physicians and EHR experts are expressing deep concerns about populating patient-controlled systems, such as Google Health, with information from insurance billing records. That concern reflects the dilemma the medical industry faces today: while insurance billing records offer the richest source of ready-to-go computerized healthcare information, they are also the source of a wide range of grossly inaccurate medical information, according to a Boston Globe article.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Personal health records, such as those offered by Google Health, are a promising tool for patients' empowerment - but inaccuracies could be "a huge problem," said Dr. Paul Tang, the chief medical information officer for the Palo Alto Medical Foundation, who chairs a health technology panel for the National Quality Forum. For example, he said, an inaccurate diagnosis of gastrointestinal bleeding on a heart attack patient's personal health record could stop an emergency room doctor from administering a life-saving drug.

And according to Dr. David Kibbe, senior technology advisor to the American Academy of Family Physicians quoted in the article, "Claims data is notoriously inaccurate and notoriously incomplete with respect to an expression of the problems a person has."

The Globe article - a great piece for anyone interested in the subject - says that Google's stance on this highly complex issue is that for patients, some information is better than none, and that inaccuracies over time will be resolved. While that may be true, that's one caveat that needs to be spelled out much more clearly in these early days of creating visibility and mobility for this most personal of information.


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