>If a system stores data, the vendor will provide an API and/or SDK, with accompanying documentation, such that authenticated requests may create, read, update

>If a system stores data, the vendor will provide an API and/or SDK, with accompanying documentation, such that authenticated requests may create, read, update or delete that data programmatically as appropriate. I almost feel like you're overstating the current state of the market here. Yes, things are very bad as they stand today. Interop is nowhere near where it should be. There are definitely vendors that do their best to wring out as much lock-in as possible (e.g., Epic), but most systems can be integrated through HL7 messaging and --increasingly-- CCD exchange. I'd say that the biggest issue with it right now is that most vendors treat integration as a (very expensive) value-add rather than core functionality. The situation could be better, but the problem today has as much to do with legacy systems that are going to take a long time to integrate or replace as anything, IMO. I do find it interesting that you talk about healthcare taking a page from social media because that's essentially the direction the market is already headed with HIEs. I'm most familiar with McKesson's RelayHealth because it's what I've worked on, but HIEs can be thought of as Facebook for healthcare. Patients can connect to their providers, messages can be sent between provider and patient, and clinical data can be shared to the patient or to other providers that are appropriately linked (like with a referral). From what I've seen, industry reaction to HealthKit has been pretty lukewarm. I'm not optimistic about Apple establishing themselves as a particularly strong presence in the larger healthcare space. And, FWIW, the HITECH has lit a fire for both facilities and vendors both to get their act together on this front by tying Medicare reimbursement rates to use of both EHRs and interop with HIEs.