About a year ago we posted a piece that basically summed up Google Health as on its death bed. Google, of course was quick to defend itself saying that Google Health was very much alive and well. We even had a long conversation with the senior leadership of Google Health who told us they were taking Google Health in a new direction, had been doing a significant rebuild of the underlying architecture which culminated in a “new” Google Health which had far greater focus on health and wellness. They even went so far, in very uncharacteristic fashion to give adoption numbers. Granted, those adoption numbers were only those from users of the Android App CardioNet, but hey, it was something.
Beginning in late March 2011, we started hearing the rumors of the impending demise of Google Health once again (is this becoming some sort of annual thing with Google Health?). We waited a few weeks to see if the rumors would die down, they did not. We put a call into Google Health to set up a briefing, get an update. Response back was slow (one yellow flag). When they did get back to us, they said it will be at least a couple of weeks (two yellow flags). Next, our Google contact told us by email that they were going to hand Chilmark’s inquiry off to Google’s PR department (screaming dark orange flag). And now today, we received an email from one of Google Health’s most visible spokespersons, Missy Krasner that she is leaving Google.
There is now no doubt in our mind that the Google Health development team has been dis-banded and Google Health has been placed in a cryogenic state until the moribund consumer adoption of such tools comes to life. It would be far to big a PR nightmare for Google to completely pull the plug on Google Health as they have done in the past with other less then stellar launches. No, they’ll put an engineer or two on Google Health to keep it up and running but don’t expect anything new out of Google Health for at least the next 5 years. This baby is frozen.
John Moore is an IT Analyst at Chilmark Research, where this post was first published.