Thursday, June 2, 2016

Why do we put up with it?

I've so often heard "Why do people put up with bad EHR systems".  Before you go there, for those of you who read this blog, answer me this:

Why do you put up with a system for storing meeting invitations that doesn't have a place to put in a teleconference number and passcode, and a web URL in a way that makes it easy for you to dial into the teleconference, and connect to the screen sharing service?

When you get to that answer, you'll have the answer to your first question.



  1. The RFC 5545 (iCalendar) ATTACH property can be used to communicate teleconference access data. However, there is no current active IETF working group to define standard ATTACH data objects. As with other cross-industry standards, some major vendors have not fully implemented RFC 5545, thus limiting interoperability. I suspect that there are no compelling market justifications for interoperable calendars beyond the base standard and current implementations.

    In healthcare IT, we seem to have too many active groups -- and vendors -- working on the same problems but not with each other. The result is the same as having no active group and no compelling market case.

  2. My Android phone handles this nicely. So why do you Apple fanboys put up with it?