Related: <a href="http://www.wbur.org/commonhealth/2017/05/12/boston-electronic-medical-records" rel="nofollow">http://www.wbur.org/commonhealth/2017/05/12/boston-electroni...</a><p>I always see people ragging on EMRs. They're inefficient, have poor UX, require way too much documentation, etc. These are all fair criticisms, but I don't think people spend enough time asking why. Why are all the major EMR systems shitty in exactly the same way?<p>I think there's 2 main parts to the answer. The first is the sales process. The people selling EMRs to hospitals aren't selling their product to clinicians, they're selling their brand to the hospital administration. It's like the saying "nobody ever got fired for choosing Oracle", but far worse. The end result is years-long implementation processes, broken promises, and terrible tools that are optimized to allow the hospital to fire a few members of the low-level administrative staff (billing, coding, etc) instead of providing better care to the community they serve.<p>The second part of this problem is overregulation. The justification is that EMRs should be able to meet a certain level of functionality. Based on personal experience working with these regulations, I'm convinced that the real reason these certifications exist is to prevent new players from entering the market. They are very much in the spirit of "well all these legacy systems do [something], so _obviously_ everybody else should too" without ever leaving room to come up with a better solution. They shackle you to terrible design choices and assume that all hospitals, from a 10-bed critical access hospital to a 500-bed academic medical center, should all be run the same way. And worst of all, they make it impossible to design a system based on what the HOSPITAL needs, because half of the system is devoted to what the GOVERNMENT needs. Kind of like how people complain about interoperability between electronic medical systems. So the government introduces legislation to mandate interoperability, by requiring implementation of poorly-defined "standards" (designed by committees comprised mostly of, you guessed it, representatives from legacy vendors). From personal experience, I can say that every. single. one. of the interfaces required for federal certification is completely unable to be reused by actual hospitals. But that's the entire purpose, that's exactly why lobbyists paid so much money to get the regulations passed in the first place! If potential new competition has to sink thousands of man-hours every year into building useless functionality, that's thousands of man-hours that didn't go into making their product competitive and disrupting the marketshare of legacy systems. Meanwhile, legacy systems are maintaining their market share, not by improving their product and helping healthcare providers do a better job. Instead they're actively creating situations where smaller hospitals are forced to choose between buying onto the licenses of larger hospitals or shutting their doors.<p>Obviously this is all just my personal opinion.