Skip to main content

First, do no iHarm

In this post, I will be commenting on the New Yorker article “Why Doctors Hate Their Computers” by Atul Gawande, from November 12, 2018. It focused on doctor’s frustrations with the transition to Electronic Medical Records, or EMRs.

Learning about this it has been surprising how painful the transition process has been. I have heard similar complaints from friends in the field, but I did not know how widespread it was.

By the sound of it, it is hundreds of little reasons that make the doctors’ lives harder. For one, it is much harder to add a simple note to a patients’ file. There is a lot of unnecessary information  that needs to be filled out, and many of these fields are mandatory. Another reason is that the computer gives the doctor arbitrary limits, like they cannot view lab results from a week before because their window for viewing it has expired.

Yet another reason is that the user interface is not very user friendly. It takes several more clicks than it should to do any one thing. The list of complaints seem to be endless, and unfortunately the issues brought up in the article are likely just the tip of the iceberg.

The real customer for the system is certainly not the two groups that would ideally benefit the most — the doctors (and nurses and the like) or the patients. It has made the doctor’s jobs much more difficult without much to show for it. The strain that it puts on the doctors are felt by the customers as well. There might be a few advantages, but most are marginal at best.

No, the real customer is the creator of the EMR systems. They stand to profit from it quite a bit. The fact that they were ridged to any outside influence to make the system better shows their true motives.

The lessons from the implementation from this system most certainly do not only apply to the Electronic Medical Record systems. The article touched on one of the patient’s experience in his own life working in construction. He echoed one of the complaints of his doctor, which was that the automated alerts created a signal fatigue, and the solution is to do the old school way of going back to picking up the phone over using the computer.

When I read about the doctor not being able to submit a form unless all the fields were complete, I thought about when I worked at the YMCA when I was sixteen. There was an extensive incident report that took forever to fill out, so consequently, we never used it save for major events. Of course, these were still done on paper, but if a paper could get in the way of doing our job properly, I have no doubt a much more complicated system would as well.

This reading has not changed my opinion because I was already aware on the topic. I have read up on it in the Boston Globe, and I have talked about it with friends who are in the field. The New Yorker article just confirms everything I have already thought about it.

I was hoping the article might forecast what might come. As they are now, EMRs are awful, but they are here to stay. They have only been around for a little over a decade most places. This is just the natural growing pains we have to get through in order to get to something that benefits us all.

Comments

Popular posts from this blog

Sprint 5 Retrospective (Capstone)

It is a shame that we are so close to the end of the semester. We were gaining so much momentum. It took us a while for us to get off the ground, but once we did, we never stopped gaining speed. I feel we will be able to keep this up through this last sprint. My hopes at the beginning of the semester for what we could accomplish were unrealistically high, but I am not disappointed with what we accomplished. We have not completed a full working component quite yet, but we are very close. I think our efforts are best spent finishing the one we are currently working on and doing it right. If we divided our efforts into starting something new, we run the risk of not fully completing anything. In the sage words of Ron Swanson, “Never half-ass two things. Whole-ass one thing.” If we are able to get the tabs working beautifully, I will be happy with our effort. I have felt that our group has done a phenomenal job this sprint and every sprint before with our communication. We have a few ...

Testing: Like Destroying Sandcastles

https://joecolantonio.com/testtalks/223-testing-dream-journaling-smashing-sand-castles-with-noemi-ferrera/ In this blog for software quality assurance and testing, I decided to return to the “Test Talks” podcast, presented by Joe Colantonio, for another episode (#223). In it, he sat down with Noemi Ferrera, a software tester for a Chinese mobile gaming company to get her take on the subject. Noemi gave a few interesting metaphors that I appreciated for how to look at testing. In one, she gave the example of going to a movie where you had already read the book. It was different than how you imagined it while reading it, and testing is a way of making the “movie version” fit the way you envisioned it playing out.  The other metaphor for testing that she gave was, if you were children at the beach, the developers would be the ones building the sandcastles, whereas the testers would be the ones destroying them. I don’t know if that would be the most accurate way of lookin...

Apprenticeship Pattern “Practice, Practice, Practice”

The apprenticeship pattern framed the problem is that if you do not have room to make mistakes in your day to day programming, you will not have room to grow. The next line hit close to home, “It’s as if you’re always on stage.” I learn quite a bit from my school assignments, but I don’t always think I have mastered each area before moving on to the next topic. The problem arises when I know my code could be improved upon, but it’s currently working. I don’t want to restructure my code too much, because I’m afraid of making it worse. The term comes to mind, “If it ain’t broke don’t fix it.” I have problems with this way of thinking, but when you’re pressed to make something work before the impending deadline, “good enough” is sometimes feels like the only option I have left. This pattern champions a different approach to this kind of mentality. I like the idealized version that they have laid out based on the research of K. Anders Ericsson. This describes where a mentor would ass...