Posts Tagged ‘Dossia’

Since its initial launch to much fanfare, Google Health has struggled to be relevant.  Since its formal launch in May 2008, Google Health has not dedicated the resources to build out this platform into a truly engaging ecosystem of applications to assist the consumer in managing their health or the health of a loved one.  Rather than build out new features, support a broadening array of standards, focus on the necessary business development that is required to establish partnerships, Google has taken a laissez-faire attitude to this product/service never dedicating more than a handful of engineers to the effort and most often flexing in outside vendors, such as IBM who built the module to bring in biometric from Continua compliant devices.

Rumors are now floating about that this lack of relevancy, this lack of a true commitment to Google Health has led to that oh so fateful executive decision – pulling the plug on Google Health and either letting the team go or reassigning them to other divisions within the organization.  With maybe 25 employees max at any one time working on Google Health, this will not have major implications internally, but it may have some broad repercussions in the industry that include:

Without a viable competitor, will HealthVault languish in its efforts to provide a truly clean, easy to engage and use platform?
Google Health’s interface and ease of interaction has always been one of its key features. Unlike Microsoft’s HealthVault, which initially was a beast to try and use, Google Health from the start was simple, intuitive and dare one say it, almost fun to use.  Though HealthVault has come a long way in improving the user experience, it remains a more trying experience. With Google Health put on the proverbial shelf, will HealthVault no longer be pushed as hard to continuously improve the user experience.

Perception that Personal Health Platform (PHP) market is dead.
Markets do not exist if there are no competitors. If the rumors are true, what we have left are Dossia, the private, employer-based platform and HealthVault.  These two alone do not constitute a market, therefore, can we now boldly state that there is no market for consumer-based PHPs?  Market would seem to say yes, though Chilmark has a hard-time admitting as much as we have been strong proponents of the PHP concept.  It may simply be that this market is still extremely immature as the consumer is not well-educated in the value in managing their own personal health information (PHI), nor is such information in easy to access and use digital form factors.  History is littered with great inventions by great inventors who ended up in the poor-house simply because the timing was off, This may indeed be the case for PHP.

Lack of options for small, consumer-focused independent software vendors (ISVs).
Dossia takes a very cautious approach to adding ISVs to its ecosystem, basically choosing those that their employer members wish to have available for their employees.  Microsoft has been quite aggressive in adding an increasingly wide array of ISV partners to create a fairly rich ecosystem.  Problem is, some ISVs are reluctant to work with Microsoft for whatever reason.  Without Google as an option, they are left with few options.

Could stall innovation.
Similar to the first point wherein Google Health’s attractive and easy to engage interface was a welcome relief to our experiences with HealthVault which subsequently put the pressure on Microsoft to improve the user experience, without Google pushing the innovation envelop in directions that Microsoft or to a lesser extent Dossia may not have pushed, we are now left with the very real possibility of not seeing truly new, innovative models for how consumers can gain access to, use and leverage their PHI to improve their health as well as their interactions with the healthcare system.  This may ultimately prove to be the biggest repercussion in this nascent market of consumer health IT.

It is critical to state that though, if rumors prove true – Google has disbanded its Google Health team, that does not mean Google Health is dead.  What it does mean is that Google Health has been put into stasis, that we will not see any new innovations, we will not see an expansion of its support of standards beyond the bastardized version of CCR that Google Health currently uses and the number of new partners, be it those providing data (payers, providers, etc.) or using it (ISVs), joining the Google Health ecosystem will trend to zero.  Sure, one can still store their PHI on Google Health and one will be able to able to use one of the existing ISVs, just don’t expect much more than what we have today going forward.

So without Google Health to keep the boys and girls in Redmond on their toes, might we continue to use the metaphor in Microsoft’s efforts to package the iPod as the metaphor for the user experience at HealthVault.  We sure hope not and many of the most senior executives at Microsoft have assured us that this will not be the case. In fact, to their credit, it was one of these executives that first guided us to the Microsoft exercise in repackaging the iPod video, so we remain optimistically hopeful.

Read Full Post »

Round Two: A Dossia Update

dossialogoLast Friday had the chance to meet up with the folks at Dossia, the personal health platform (PHP) formed by a consortium of employers. Purpose of the meeting was to get a deep dive update on Dossia and learn more about what they have done in the last year or so since they went live with Wal-Mart in fall 2008.

Since that go-live, Dossia has been fairly quiet, though they did announce two new “founding members” and released the open API this past summer. But frankly, not much to write home about.

Despite being the first “out the door” PHP, several months ahead of Microsoft’s formal announcement of HealthVault in early October 2007, Dossia has floundered.  First was the break-up with their first development partner, Omnimedix which led to Dossia forming a relationship with Children’s Hospital, Boston to use the open source Indivo PHP.  After nearly a year of work with the Indivo team, Dossia finally had WebMD linked into Dossia.  This integration between WebMD and the core Indivo-based Dossia platform was done under some pretty tight deadlines to meet Wal-Mart’s aggressive roll-out schedule – as part of their annual fall health fairs for employees across the country.  The push led to a less than ideal integration with the WebMD, an integration that could not be readily duplicated with any other third party independent software vendors (ISVs).  Thus, Dossia’s desire to build an ecosystem of apps on top of their PHP was put into stasis as the Dossia team focused on the Wal-Mart roll-out.

A year later much has been learned.

Dossia discovered that Indivo V3.2 was not fully scalable to meet large enterprise needs.

The Indivo platform was developed by Harvard Med School academics to test the concepts and policies associated with a patient-controlled health record system.  Prior to Dossia’s adoption of Indivo, the platform had seen small scale implementations at Children’s Hospital, MIT’s on-campus hospital and at Hewlett-Packard in association with a flu vaccination study. In each of these implementations, no ecosystem of apps was deployed via a common and open application programming interface (API).  This is understandable as Indivo was structured to test concepts, not necessarily structured for large scale commercial roll-out.

Since last fall, the Dossia team hired a completely new team of developers (size of Dossia team on par with Google Health ~15-18 FTEs), completely re-architected their platform to meet scalability requirements, addressed user interface (UI) issues (Indivo lacked a modern, intuitive interface), and developed a stable API that ISVs could use.  On October 15th, the new platform/UI went live.

The new API was released at the end of June and there are now 20 ISVs modifying their apps to sit on the Dossia platform.  As of today, in addition to WebMD, Dossia has eClinicalWorks (eCW is used in Wal-Mart’s retail & corporate clinics – don’t forget that eCW is also being sold through Sam’s Club), Healthtrio, Medikeeper and Metavante, who had acquired CapMed, live on the platform.

Indivo platform did not adequately address the myriad of state laws relating to record consent and sharing for teenagers.

Last year’s Wal-Mart roll-out was targeted at just employees. No incentives were provided, it was completely left up to the employee as to whether or not they wished to participate.  While Wal-Mart obtained “favorable” adoption, a key desire of employees was to have a Dossia account not only for themselves but also for their dependents. This desire led to some fairly significant challenges for Dossia in providing the appropriate consent structure for teenage dependents where State laws vary significantly.  These new consent requirements were built into the new platform as well.

Employers wanted support for dental records.

Another request from employer consortium members was the ability to support dental record data.  As part of the platform rebuild, Dossia has also embedded a dental data schema.  To the best of our knowledge, Dossia is the only PHP who has this capability today.

User interface needed to be simpler, more intuitive to provide easy access to personal health information (PHI).

During the meeting, Dossia provided a demo of its new interface, which was very simple to navigate, ranking on par with Google’s and a more intuitive experience than that of HealthVault.  Dossia has a slight advantage here in that employers define which apps employees have access to and upon sign-up populate an employee’s account with their claims and pharmacy benefits management (PBM) data.  For either Google Health or HealthVault, most consumers must go through the actions of loading their own data, choosing their own apps, etc., to establish a viable and personally value producing account.  This is similar to the adage “with freedom comes responsibility.”

Challenges Remain:

Dossia has made impressive progress since its initial launch last fall.  They have addressed the scalability issue, they have finally released an open API for ISVs to create an ecosystem of future apps and several other consortium members will be going live on the platform in the near future.  Despite these gains, challenges remain.

Where’s the lab data?

While Dossia has the ability to support clinical data in either CCR or CCD formats, today they are only importing claims and medication data from PBM firms.  Dossia, like Google Health and HealthVault does not support images today.  In somewhat of a surprise, Dossia also does not currently support lab data imports from either Quest or LabCorp.  This is a surprise for two reasons: First, viewing labs online has been found to be one of the most desired attributes of a a personal health account and secondly, both Google and Microsoft can import lab data from either of these national testing labs that represent some 80%+ of all labs done in the US.  If Google and Microsoft can do it, why not Dossia?

What’s the value proposition for employers?

Chilmark still struggles to understand what the value proposition is an employer to adopt the Dossia platform for their employees. Yes, Dossia may be a non-profit looking to provide a common platform that will provide employers more flexibility in the health-related tools (PHRs, HRAs, wellness apps, etc.) they can offer their employees to better manage employee health and wellness, but is that enough? Today, few employers see the strategic advantage of providing even the simplest of such tools (e.g. a WebMD account, an online wellness program, a disease management program that actually works, etc.) to their employees. If it is difficult for them to see value here, how can they realistically make the leap to considering a health platform with an ecosystem of apps?

And the value prop for employees is…?

Yes, the interface is much improved and yes, PHI data is automatically imported into an account and an employee’s Dossia account is fully their own, but beyond that, why would an employee sign-up to have an account? What other attributes and services does Dossia provide that are attractive to a consumer? According to Kaiser-Permanente and others, those who adopt and use such system use them to look at their lab data and conduct simple transactions such as Rx refills and appointment scheduling, all features that Dossia does not support.  So again, the value for a consumer in using Dossia is?

A couple of suggestions:

Rev up the marketing engine

If Dossia’s claims are indeed true, that the platform is stable, scalable and open to third party ISVs to build-out the ecosystem, then it is time for Dossia to become more aggressive on the marketing front.  Who better to market Dossia than its consortium members?

To date, Dossia’s consortium members have been extremely quiet and they are arguably, Dossia’s strongest marketing partner.  But if Dossia’s founding members are not out there promoting the platform, clearly stating the value proposition they see in being a member and even, as in the case of Wal-Mart, begin talking about the successes they have seen since launching Dossia, then how is any other employer suppose to buy-in to the concept?

And a concept it is for there are few in the industry today, including health benefits management firms and consultants, that fully understand what the ecosystem/PHP model represents and the value it may deliver to employers over the long-term.  The best advocates, the best marketing Dossia can receive at this critical juncture, is the vocal support of its members. So where are they?

Get the labs

Ability to access, view and share lab data is one of the top features that early adopters of PHRs and PHPs appreciate.  Dossia needs to get this issue addressed immediately. End of story.

Delivery a value proposition that employees will appreciate and use

Critical to the success of the most popular personal health systems in the market today are their ability to support transactional processes.  While it would be extremely difficult, if not impossible for Dossia to support such functions as appointment scheduling, Rx refills, eVisits with one’s primary care doctor, there is one transaction area where they could excel: providing health-related financial decision support tools.  Such tools would provide support for health savings accounts, plan deductables and balances, pricing transparency for common procedures, medications, etc., special employee health discounts, and the list goes on.   There are a number of interesting apps now entering the market that provide such capabilities and Dossia would be wise to focus on these ISVs providing an added level of assistance to get them on-board quickly.


Walking into the briefing, expectations were quite low for what we might hear from Dossia. Their quiet, reclusive nature, lack of partners, and seemingly little progress being demonstrated to the market left one thinking that Dossia will fade over the next couple of years.  The briefing put many fears to rest.  Dossia is proceeding ahead at a careful measured pace and has accomplished much over the last year.  It is far too early to count them out.

But will Dossia ultimately succeed, will they be a force to be reckoned with will they become a key market influencer?

Still too early to tell.  The platform is stable, the API is there for third party ISVs and with Dossia representing over 8 million potential users (employees) this is a market nearly 3x the size of the most popular PHR today, that of Kaiser-Permanente – a very sizable and attractive market for most any ISV.  But without strong vocal support (marketing) by executives of its consortium members, Dossia will struggle to make its presence known, struggle to clearly articulate its value proposition and struggle to influence the market and subsequently drive market adoption among employers on behalf of their employees.

Read Full Post »

Gave the Keynote presentation this morning at the Lab InfoTech Summit here in Las Vegas.  The organizer, Bruce Friedman, Professor Emeritus in Pathology at University of Michigan, asked me to update the audience on what is happening in the PHR market and more broadly, what are the implications, either implied or explicit are trends in PHRs to pathology labs.

Took me some time to think this one through, but finally a light-bulb went off in my head!  What are KP members most enthralled with in using the KP PHR – its getting their lab results quickly, online and with background information on what those results mean to take appropriate action(s).  Then, if one were to look at RHIOs & HIEs, what types of data are the first to move within these Exchanges, lab data and meds.  Stepping into ER, what does an ER doc most want to see when a patient presents in ER; labs, meds, and allergies.  The need to make lab data “liquid” was everywhere.

This “aha moment” led to the creation of a presentation, see below, that folds in our previous research on PHRs, more recent research on Cloud Computing in healthcare, some even more recent work on RHIOs and HIEs with what all this means to the lab market.

Read Full Post »

wii-fitThe extremely popular Wii gaming system will begin connecting directly to health professionals in April.  It appears that this will be first offered in Japan combining the existing Wii Fit and Wii Balance devices with bi-directional online communication capabilities.  Moving beyond just providing the gaming devices and platform, Nintendo is partnering with NEC, Hitatci and Panasonic to provide a service whereby users of Wii Fit or Balance will be able to send their work-outs to “health professionals” and receive feedback, via email, regarding these workouts with suggestions (e.g. only 10 push-ups? do 20 next time).

Interesting concept but half-baked.  Sure, it may be nice to get some feedback on a given workout but is it really all that useful if you do not have any biometric data to go with it?  And what is a “health professional” anyway, a recent graduate of We Are Physical Therapy University?

We’ll have to wait and see what ultimately arises from this initial trial balloon.

In a broader sense, it really is a brilliant idea that may quickly move beyond the shores of Japan to North America.  We can readily foresee employers and payers adopting a Wii Health-type of service combining the Wii, with the bi-directional communication capabilities to health coaches and maybe even to a consumer’s PHR.  HealthString is one such PHR that has a heavy focus on health coaching and sells their product/services almost exclusively to employers. One can easily imagine an employer who offers HealthString to its employees combining their health coaching service and PHR with an incentive/rebate on the purchase of Wii Fit to foster healthy behaviors among its employees to improve overall population health.

Or maybe, again via a rebate program, an employer can set-up an internal team challenge using something like Limeade (another health solution targeting employers), combining their solutions with the bi-directional communication and logging of work-outs capabilities of Wii Fit to promote peer-based fitness.  Clearly, there are all sorts of permutations and scenarios of services that one can build upon with the Wii Fit and this future bi-directional communication capability.

Makes us wonder if Nintendo has had any discussions with the folks at HealthVault and their Connection Center.

Oops, HealthVault is owned by Microsoft with its competing Xbox.  Nintendo, better look to Google Health and Dossia, both would be receptive to their overtures.

Read Full Post »

gh1Chilmark Research is furiously working on its next report that will take an in-depth look at the three major platform plays, Dossia, Google Health and Microsoft’s HealthVault.  Shaping up to be an excellent report (in our humble opinion) with a target release date of mid-December.

One of the challenges in writing this report is taking what is a fairly new concept in IT, “Cloud Computing” and even newer, “Platform as a Service” (PaaS) and convey its implications to the healthcare sector.   Hard to do in a space that is changing so fast.

We foresee that this trend holds a lot of promise for the healthcare sector greatly accelerating the use of HIT, across the continuum (consumers, physicians, caregivers, etc.) for the simple reason that it removes the burden of infrastructure (hardware & much software) support and will likely be a hell of a lot easier to use then many of the client-server systems of today.

But we digress.

In looking at the three platform plays, we have a section in the report that addresses their operating models.  While doing research on the subject we stumbled across an excellent analysis of Google’s strategy by Nick Carr.  This is the clearest, most cogent analysis we have seen and is spot-on.

If you are even remotely interested in Google, we highly recommend reading Carr’s piece.

After reading one will quickly realize exactly why Google may be able to offer Google Health free forgoing the need for sponsored ads or selling data (even if it’s anonymized) to third parties, both fears that are frequently bantered about in the healthcare sector.  These fears appear to be ill-informed and many times are simply fear mongering by those either wanting to make a name for themselves or simply do not want to give up the data.

Read Full Post »

hvdevicelabelIn an interesting twist, Cleveland Clinic and Microsoft’s HealthVault Grp announced a partnership this morning to address chronic disease management. The interesting twist is that Cleveland Clinic was the showcase beta customer for Google Health, which was announced by Google’s CEO Eric Schmidt earlier this year at HIMSS. Like their counterpart in Boston, Beth Israel Deaconess Medical Center, who was part of the initial Google Health public roll-out in May and who has since also established a link to HealthVault for their PatientSite users, Cleveland Clinic is taking an agnostic approach to the major platform plays with this agreement.

The Cleveland Clinic-HealthVault announcement is distinctive in that it focuses on chronic disease management, via telehealth, through use of HealthVault’s unique Connection Center. With some 50 devices from 9 vendors, the Connection Center allows the consumer to upload device data (e.g., glucose readings, heart rate, blood pressure, weight, peak flow, etc.) directly to their HealthVault account. In the Cleveland Clinic project, which began last week (Nov. 3rd), uploaded biometric data from HealthVault compliant devices will automatically be pushed to Cleveland Clinic’s EMR and subsequently exposed to the physician for patient tracking and follow-up.

Had a call this morning with Microsoft and one this afternoon with Cleveland Clinic who both shared further details on this announcement:

A target of 460 Cleveland Clinic patients will participate representing three distinct disease categories; hypertension, diabetes and heart failure. The roll-out is across the Cleveland Clinic Integrated Delivery Network (IDN) and not just hospital patients. Clearly, they are focusing on the big chronic disease categories that result in huge costs that many believe better telehealth monitoring can mitigate.

  • Hypertension patients, of which there are 400, will measure blood pressure only.
  • Diabetes patients, of which there will be 30, will use five devices to measure glucose, blood pressure, peakflow, pedometer and weight.
  • Heart Failure patients, the remaining 30, will use four devices to measure blood pressure, peakflow, pedometer and weight.

Pilot will initially be for an extremely short 90 days. Cleveland Clinic expects to have all patients active within 4-6 weeks. Not sure what they can accomplish in 90 days, maybe Cleveland is just hedging their bets to see if patients actually comply with the prescribed measurement and upload regime. Assuming that all goes well, one can guarantee that this pilot will be extended for at least a year, if not longer, as that is the only way they will be able to provide some demonstrable results that are publishable (something that Microsoft emphasized) and ultimately may influence future legislation (e.g., CMS funding), health plan reimbursement (P4P), and broader adoption among other Integrated Delivery Networks (IDNs).

Devices are being provided for free to trial participants. The only requirement, beyond the obvious willingness to diligently take their measurements, is that they have a Windows-based (XP SP2) computer and broadband access. Unfortunately, many heart disease patients are among the elderly and it is questionable as to how many have this capability. Still, the point here is to demonstrate, not solve all the problems and it is a good start.

Cleveland Clinic is training patients on the use of the devices(s), and data upload process to HealthVault, that is subsequently pushed to Cleveland Clinic’s EMR. Part of that training includes clearly notifying the patient when a particular reading should prompt a call to their doctor or even 911. Along with providing the device(s) and training, the physician will prescribe to the patient their measurement protocol (e.g., 2x/day, 3x/week, etc.) unique to that individual and the condition they are managing. Patients trust their doctors so receiving the package directly from their physician during an office visit makes a lot of sense and should encourage use and hopefully compliance. It will be interesting to see how compliant patients are to the prescribed compliance regiment as this is often a critical stumbling block. Will incentives be required?

Cleveland Clinic put in the upfront effort to understand how best to incorporate this new data stream into a physician’s workflow to minimize the burden. Specifically, the physician will receive a weekly notice notifying them that their patient(s) biometric data is ready for review. One click later and the physician is in the EMR reviewing their patient’s data for that past week. Prior to this pilot, Cleveland has experimented with other telehealth systems, but none were able to provide this level of integration with the core EMR system (always a stand-alone, silo’d operation) and thus saw little adoption among physicians. This is absolutely critical! Having spoken to many physicians about the success, and most often failure of telehealth initiatives, it nearly always circles back to lack of true integration to existing practices/workflow. Looks like this pilot tackles that issue head-on.

So what is the Business Case?

Wrapped up my conversation with Cleveland Clinic’s CIO, Dr. Martin Harris, (thanks again Martin for your time) by asking him: So what is the business case for this initiative? He outlined two areas where they see a benefit to Cleveland Clinic:

Service Case: In moving to this model of combining telehealth with traditional in-office visits they intend to completely re-design the office visit resulting in a better, more engaged and customer friendly process. This process will lead to higher customer service ratings, customer recruitment and higher customer retention – all important top-line metrics. They also see a service case for the physician as such a “system” will allow the physician to deliver a higher level of proactive care with their patients. Its all about market differentiation, distinguishing themselves in an increasingly crowded market – one that will only get more competitive.

Outcomes Case: One of the objectives of the pilot is to see if Cleveland Clinic can consistently improve the outcomes/health of its chronic care patients that will result in fewer hospital readmissions and/or complications. If all goes as planned, Cleveland Clinic believes that it will be able to use these positive results to request better reimbursement schedules (more income) from health plans. This certainly makes logical sense, but to date, health plans and CMS have been reluctant to support such programs – more of a wait and see approach. Hopefully, Cleveland Clinic will start showing some impressive results in a year or so and get those health plans on-board.

Final Note:

A couple of weeks ago I poked Microsoft about their lack of support for the telehealth consortium, the Continua Alliance. Sean Nolan responded stating a primary reason was Microsoft’s desire to move quickly (consortia always seem to move at a snail’s pace). Looks like that has paid-off as Google Health and Dossia cannot, today, support such capabilities as demonstrated above, though they are on the path having joined the Continua Alliance and Google demonstrated modest capabilities at the recent Connected for Health Symposium.

Looking ahead, we forecast 2009 to be a year of pilots which begin to demonstrate the utility of the platform model (Dossia, Google Health, & HealthVault) in support of telehealth and how telehealth technology and practices are best integrated into existing clinician workflow. Look to 2010 to see actual reimbursement models and P4P programs begin to take shape in support of promotion and adoption of telehealth.

Read Full Post »

One of the treats of this week’s Connected for Health Symposium was the opportunity to moderate a panel entitled: Personal Health Information Platforms and Records: What’s the Nitty-Gritty Situation on the Ground?

Obviously, I could not provide notes on this session while concurrently moderating it, but did find the following article at Healthcare IT News that provides some flavor as to what was discussed.

I began the session with broad questions targeted at all panelists and concluded my questioning with pointed questions to each of the participants. Following are the questions and their answers:

Google Health:

Ques: You currently only support a modified version of the CCR standard and do not allow for unstructured data in Google Health. Will you support other standards and unstructured data?

Ans: Yes, we do intend to support other standards including CCD in the near future. We are also building out the capabilities to support unstructured data.

Assessment: Good to hear that Google intends to support other standards and quite pleased to hear that they will be offering users the capability to store unstructured data (important for journaling, loading up advanced directives, etc.)


Ques: How will you support portability of the record should an employee leave their employer?

Ans: We intend to support portability of the employee’s record. As of today, we have not worked out a pricing model should an employee wish to maintain their data on Dossia.

Assessment: This is the same answer they gave me last year – obviously a back burner issue that Dossia has not spent much time on.


Ques: You are currently working with Dossia and now being rolled-out to Wal-mart employees. Do you intend to become a part of either the Google Health or HealthVault platforms?

Ans: We will become a part of these other platforms when there is a business case for doing so. (In other words: Only when a client asks us to do so and basically pays for it.)

Assessment: Seems logical and why commit to something that to date is still unproven and none of your large enterprise clients have asked for.

Microsoft HealthVault:

Ques: Recently, both Google Health and Dossia became members of the Continua Alliance supporting Continua’s open standard for medical device connectivity. Since biometrics is an important part of HealthVault (and its proprietary Connection Center), why are you not a supporting member of Continua?

Ans: Microsoft wanted to move faster then Continua to deliver a solution to market. We continue to follow what Continua is doing and will reconsider joining Continua at a later date.

Assessment: Yes, Microsoft is correct in that Continua has been moving slowly and understand that they may not have wanted to be hindered, after all, Microsoft now has over 50 devices that can feed data through Connection Center into an individual’s HealthVault account while Continua has yet to bring a single certified product to market.

That being said, Continua standard compliant products will start rolling into the market, en mass, in 2009. Continua gave a very impressive demo (at least for the audience as I was bored having seen similar device connectivity over ten years ago in the manufacturing space, but that is another story), including numerous devices, as well as an upload of device data directly into a Google Health account. Also, Continua is not expensive to join – it is only $5K/yr to become a “contributor” member, chump change for Microsoft.

Just can’t figure out why Microsoft won’t pony up a measly $5K to at least show support for the concept of Continua, unless of course they have every intention to make the Connection Center a lock-in solution. Do not believe this is Microsoft’s intent, but their position on Continua naturally raises suspicion as to their intentions. Hopefully, they will reconsider this stance and join Continua in the near future.

On another note – Microsoft did announce, while up thereon the panel that they have an iPhone app in the works that will be released shortly.  Can’t wait to see what that may be – stay tuned as we plan to dig deeper.

After my questioning I opened up questioning to the audience. The highlight was when someone asked when will we see interoperability between the platforms. This generated some lively discussion between Google and Microsoft with Google’s Jerry Lin finally saying to Microsoft’s Grad Conn that Google was ready when they are. To which Grad responded positively and said let’s talk after the session.

Don’t know what came of those discussions and regret not holding their feet to the fire in front of the audience and asking them when, specifically, will we see such interoperability. Guess that will have to wait for the next such opportunity.

Read Full Post »

Older Posts »