To expand on that EMRs, much like SAP and other enterprise offerings aren't so much fixed pieces of software as ridiculously flexible frameworks for making software. And the people deciding how to configure Epic, and deciding how the doctors and nurses need to use it aren't practitioners, they are administrators who are making decisions for bureaucrats reasons, CYA being high on the list. Anytime an accident occurs, rather than understanding why it occurs, the solution is always to add more administrative controls, to record more details in the chart, more busy work to do that makes each step of the process take longer.
As a result, the number of things that practitioners need to enter into EMRs keeps growing, and every year they spend more and more time charting. This in turn decreases the signal-to-noise ratio of the information in the charts, resulting in the practitioners getting less information out of them despite the fact that more information keeps getting put in. Which results in more accidents rather than less.
Most people don't know that always writing tickets, even if they get refused and ignored, will have an impact. Your goal is not to convince level1 support to be your friend, but to turn the statistics into a way that forces administration to consider your concern. So always write tickets and encourage your colleagues to do the same. And if they get ignored make a screenshot and send it with the headline "lol, got refused again" to the watercooler mailing list and laugh about it together.
As a result, the number of things that practitioners need to enter into EMRs keeps growing, and every year they spend more and more time charting. This in turn decreases the signal-to-noise ratio of the information in the charts, resulting in the practitioners getting less information out of them despite the fact that more information keeps getting put in. Which results in more accidents rather than less.