If one more person describes Epic’s new API as being “open”, I’m going to turn purple. Don’t let the URL fool you: http://open.epic.com/
Last week EHR vendor Epic unveiled it’s new API (application programming interface) targeted at developers — more specifically at remote patient monitoring companies and health/wellness apps or portals. Epic seems to have had second thoughts about the site since only remnants of the landing page are still there as of today.
Not to worry. As a public service, I kept a copy and have reproduced the text below — with personal annotations/translations added.
What’s Wrong With Epic’s API?
What’s wrong with Epic’s API from a developers POV? Data goes in. It doesn’t come out. If you are a developer, this is a great way to disintermediate yourself — you create all the value, Epic captures all the value.
Would you bank at an institution that allows you to make deposits, but not withdrawals?
Despite the chatty language that was on Epic’s website, their API is a continuing extension of Epic’s ethos of control rather than collaboration. It’s downright condescending.
What part of health information exchange do they not get over at Epic?
Enough banter. Let’s get to the meat of it.