Apple now enters into the Health Platform API fray with something called HealthKit, after Google has left the field, and Microsoft simply carries on with its Health Vault platform. This isn't really really new news, so much as confirmation of what we've been hearing for a little while about Apple's entry into the Health and Quantified Self space. As someone who has more than 5 QS/Health apps on his phone and iPad which DO NOT work together at all, I appreciate that the iOS platform will soon have these capabilities built in. And I can also see that vendors developing these applications will have to rather quickly start working with the new APIs.
Looking at the basic descriptions of what Apple has in store for us at the moment, it seems as if Apple's definition of a Health API isn't all that much more than what HL7 FHIR already has with regard to definition for various Health related resources. I expect some enterprising FHIR developers will be building bridges between the new Apple Health APIs and FHIR. We've already seen some development of FHIR in Objective-C, and I expect that the Apple announcement of HealthKit will encourage others to explore bridging between it and HL7's FHIR specification. But don't expect Apple to start showing up at HL7 FHIR Connectathons, or participating in FHIR development.
Just as I expect Microsoft will be doing similar things with Health Vault at some point in the future. But they won't be doing it right away according to at least one Microsoft employee. Even so, at least Microsoft shows up.
We'll just have to see how this all plays out. I'm not really too worried about Apple's entry into the Health API space. After all, the world doesn't live on iOS alone, there will be always be a need for a consensus standard Health API like FHIR that can work on any platform.