Yes, but they act like MTs were raking in 6-figure - incomes! Posted: Jun 7th, 2021 - 2:44 am In Reply to: It's not entirely the doctors fault. They had to do what the - bean counters decided as best. SM
If anything, many of us never got the chance to enjoy a decent paycheck for very long before the cutbacks started happening.
So they all collectively blew it - the docs, the hospitals, and the bean counters. And look who's crying now...
It has been reported in EHR Intelligence (September 27, 2019) - "EHRs are largely to blame for the physician burnout and stress epidemic that runs rampant in the medical industry, according to a group of researchers from the University of New Mexico)."
According to Philip Kroth, MD, who has researched the subject at UNM, “We are losing the equivalent of seven graduating classes of physicians yearly to burnout and, as they leave the profession, they point their finger at the time now required for them to document their work and how it has led to the loss of quality time spent with patients and families.” Kroth goes on to say, “In many ways, physicians are finding that the goals of a traditional medical record have been hijacked.”
But when the Health Information Technology for Economic and Clinical Health (HITECH) Act was signed in 2009, EHRs were supposed to make paperwork easier, lead to more cost-effective healthcare, and reduce paper waste.
Ten years later, the survey shows that the time set aside to medical record-keeping has doubled. Physicians now spend two minutes at the computer for every one minute spent with patients, and the workdays have extended into the physicians’ home life.
Kroth continues, “We went to school to see patients, but now, for every minute we have with a patient, we are spending two additional minutes on the computer." It often takes a 60-hour week just to keep up with documentation, and that is tough on personal relationships and families.”
It's real hard to feel sorry for them...
Post A Reply Reply By Email Options
Complete Discussion Below: (  marks the location of current message within thread)
|
