3 Tech Things That Irk Me
Destructive APIs, a lack of interoperability standards—and their glacial pace—and Twitter are a few of the tech irritants on Scott Mace's mind this week.
This week, I've worked up a mini-rant about some of the most maddening things about information technology, in a healthcare context, of course.
1. APIs work great, until they break
Epic recently announced an application program interface (API) for its EHR software. Details remain sketchy, but I can guarantee one thing: Somewhere down the road, for some good reason, Epic will change its API and break a whole bunch of things built on top of the first API.
Don't blame Epic. It's the nature of APIs to change, particularly if the business model of the company publishing them depends on not allowing too much openness with competitors or potential competitors.
That's why we hunger for standards from groups such as HL7 to set the APIs in concrete. But standards are usually the product of vendors jockeying to deny each other any kind of competitive advantage, so they always end up being some kind of least common denominator.
- CMS Offers Some ACOs $114M for 'Upfront' Costs
- WellPoint Dominates Nearly Half of Markets, AMA Says
- Ebola: Second TX Nurse Diagnosed After Improper Protective Gear Application
- 16 Medicare Advantage Plans Earn 5-Star Ratings
- Ebola: A Call for Designated Hospitals
- Providers Ask HHS to Address EHR Interoperability Barriers
- CDC admits to mistakes in Ebola protocol
- 76% of Nurses Say No Ebola Policy Communicated by Hospitals
- CMS' new investment model will help ACOs with health IT
- Obama Names 'Ebola Czar'