In response to David Burda's "Reporter's notebook: EHRs put some docs on edge":
The next to last paragraph really struck a chord with me. "Some practicing physicians are getting so frustrated trying to figure out how to use EHRs that they're lashing out at their peers" and "They just don't see why they have to change."
In the training that I have been exposed to, it was put forth that it is the IT professional's responsibility to bridge any gaps between the software package (EHR) and the customer.
Clearly from the first quote there has been significant failure to properly train the customer (physician) to a comfort level of proficiency with the EHR. That the issue has risen to the point where some physicians need to seek professional mental health assistance is testament enough to this failure.
The second quote points out another failure on the part of the IT professional.
If it can not be demonstrated that the EHR being presented will make the physician's life better, faster, more proficientall in all easierthen the EHR package in question needs to go back for a rewrite until such time as it can be so demonstrated to the physician.
My training was years ago and I never made the leap from clinical engineering to IT. Perhaps the concept that the program writer is responsible to produce software that is logical and easy-to-use for the non-IT professional is no longer taught or was unique to the college I attended.
Having some training and having seen some poorly written software, I have nothing but understanding
and sympathy for those physicians.
Craig HunterPittsburghTo submit a letter to YOUR VIEWS,
href="mailto:[email protected]"> click here. Please include your name, title and