Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Marianne Kolbasuk McGee

Marianne Kolbasuk McGee

Senior Writer, InformationWeek

5 Reasons Why Google Health Failed

What doomed Google's online personal health record system? For starters, consumers haven't bought into the basic idea.

Last week, Google confirmed what had been rumored for quite some time: The company is pulling the plug on Google Health, the online personal health record system that they launched in 2008. The service never really took off, and here are five reasons why:

1. Consumers, for the most part, just weren't interested or didn't even know what a personal e-health record is.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Despite all the attention e-health records have been getting from healthcare providers since the HITECH Act was passed in 2009, consumers are still pretty oblivious to offerings that allow them to electronically compile and manage their health data. In fact, an IDC Health Insights online survey of 1,199 consumers earlier this year found that only about 7% of respondents reported ever having used a PHR. The leading reason for consumers not using a PHR? About half said they haven't been exposed to the idea of using a PHR. In a similar survey done by IDC five years ago, 52% gave the same reason for not using a PHR. Not exactly progress.

2. Consumers who are aware of PHRs tend to use physician, hospital, and even health-plan portals to keep track of their records.

That's because, unlike Google Health and many other consumer-oriented PHRs, the bulk of the patient's key data--like test results--is already available in the record, supplied by the provider or health plan. Also, unless patients have a chronic or serious health issue, they only use personal health records very sporadically. By the time many healthy patients have another occasion to use a PHR after it's been set up, they probably have forgotten they even started a record and can't be bothered.

In fact, of consumers that have tried PHRs and stopped using them, 15.9% said they didn't want to spend time entering their data and 22% didn't see value in doing so, according to the recent IDC survey.

3. Lack of provider relationships and other data sources.

There weren't enough third-party sources allowing patient data to be imported to Google Health, with the exception of a handful of big name providers, including Cleveland Clinic and Beth Israel Deaconess Medical Center in Boston, and some more recent partners, like University of Pittsburgh Medical Center and Sharp Healthcare, as well as a few large national pharmacy chains like CVS and related partners like SureScripts. Google Health also lacked relationships with big labs so consumers weren't able to access their test results, which is one of the key attractions that often get patients using PHRs.

"One of the key insights we've developed over time is that in PHRs, connections to providers, and having an open platform" to support the import of data from multiple sources and applications, including medical devices, is "vitally important," Nate McLemore, general manager of business development and policy in Microsoft's Health Solutions Group, said in an interview with InformationWeek Healthcare. Microsoft's PHR platform HealthVault currently has about 300 third-party applications, including about 10% of which "also supported Google Health," he said.

4. Google lacked other communication and convenience features that patients look for when dealing with their health information electronically.

That includes secure messaging with healthcare providers and being able to schedule appointments. Both those capabilities are typically found in provider portals offering PHRs.

In recent months, Google Health had shifted gears a bit with its services and third-party relationships, hoping to make the site easier to use and more appealing to fitness buffs. That included new tools to let consumers monitor and record their daily physical activity, as well as help patients with chronic conditions like high blood pressure track their health-related goals. That required Google Health to forge relationships with makers of wearable health device makers. Apparently those new capabilities didn't exactly attract the masses, either.

5. Privacy and security concerns by consumers, whether warranted or not.

While Google officials said they didn't hear many concerns about privacy from consumers, fears about security and suspicion by some patients about whether Google Health had ulterior motives for collecting their health data was undoubtedly a factor that stopped some from using Google Health--or any online service for that matter--to store their personal health information.

"We all have our irrational fears," said Lynne Dunbrack, IDC Health Insights program director in an interview with InformationWeek Healthcare. "And some consumers undoubtedly had fears that their health information would show up in a Google search."

If Google had had more patience with patients (and doctors) getting comfortable with online e-health records, and had addressed some of its major weaknesses, the service might've become much healthier (pun intended).

By the way, Google just introduced a social networking service to compete with Facebook. Does that mean Facebook is working on a PHR? Probably not. However, Microsoft recently added capabilities to allow users to log into their HealthVault accounts using their Facebook credentials. I suppose that's one way to entice consumers into using a PHR.

The Healthcare IT Leadership Forum is a day-long venue where senior IT leaders in healthcare come together to discuss how they're using technology to improve clinical care. It happens in New York City on July 12. Find out more.



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.