Hey—we've moved. Visit
The Keyword
for all the latest news and stories from Google
Official Blog
Insights from Googlers into our products, technology, and the Google culture
Listening to Google Health users
April 27, 2009
At Google, we believe that consumers should have convenient and secure access to all their health data so that they can be better informed and be more involved in their care. Recently, a data-savvy patient known as e-Patient Dave
blogged
about data that was imported into his Google Health Account from his hospital in Boston,
Beth Israel Deaconess Medical Center
. Once he saw his data in Google Health, he saw diagnoses that were both alarming and wrong. Where did they come from?
It turns out that they came from the billing codes and associated descriptions used by the hospital to bill the patient's insurance company. These descriptions, from the
International Classification of Diseases (ICD-9)
, often do not accurately describe a patient because the right ICD-9 code may not exist. So the doctor or hospital administrator chooses something that is "close enough" for billing purposes. In other cases, the assigned code is precisely what the doctor is trying to rule out, and if the patient turns out not to have that often scary diagnosis, it is still associated with their record. Google Health faithfully displayed the data we received on Dave's behalf. We and Beth Israel knew that this type of administrative data has its limitations but felt that patients would find it a good starting point. Too often, this is wrong.
At Google, we are constantly learning important lessons from our users. Two days after we learned about this issue, I met with Beth Israel
CIO John Halamka
, the patient's physician
Dr. Danny Sands
, and e-Patient Dave himself. We agreed on a reasonable plan: Beth Israel will stop sending ICD-9 billing codes and will instead only send to Google Health the free text descriptions entered by doctors. Beth Israel is also working with the
National Library of Medicine (NLM)
to associate those free text descriptions with a more clinically useful coding system called
SNOMED-CT
, so that we can offer patients useful services like automatic drug interaction checking. The result will be more accurate and useful information in patients' Google Health profiles.
This week, all four of us were also at a conference called
Health 2.0
in Boston. Dave's story, and the lessons we all learned, were the focus of much discussion. We are grateful to Dave for his openness and passion for making things right. We're also glad this happened because we and many others now better understand the limitations of certain types of health data and we are working with partners to improve the quality of the data before it gets to Google Health and our users. We look forward to sharing what we learn with the broader community. We also learned that the patient community is surprisingly interested in understanding these data issues. Dave and his doctor Danny Sands collaborated on an
informative post
about different data vocabularies used in different aspects of healthcare. The patient-controlled "data liquidity" that Google Health supports is clearly an important part of the future of health care. We are more committed than ever to putting consumers in charge of their own health information.
Posted by Roni Zeiger, M.D., Product Manager, Google Health
Labels
accessibility
41
acquisition
26
ads
131
Africa
19
Android
58
apps
419
April 1
4
Asia
39
books + book search
48
commerce
12
computing history
7
crisis response
33
culture
12
developers
120
diversity
35
doodles
68
education and research
144
entrepreneurs at Google
14
Europe
46
faster web
16
free expression
61
google.org
73
googleplus
50
googlers and culture
202
green
102
Latin America
18
maps and earth
194
mobile
124
online safety
19
open source
19
photos
39
policy and issues
139
politics
71
privacy
66
recruiting and hiring
32
scholarships
31
search
505
search quality
24
search trends
118
security
36
small business
31
user experience and usability
41
youtube and video
140
Archive
2016
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2015
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2014
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2013
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2012
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2011
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2010
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2009
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2008
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2007
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2006
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2005
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2004
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Feed
Google
on
Follow @google
Follow
Give us feedback in our
Product Forums
.
Follow
