Slashdot Mirror
Major Health Organization Stops Forcing Doctors To Adopt New Technology (internalmedicinenews.com)
nbauman writes: The administrator of the Centers for Medicare & Medicaid Services, told an investors' conference that they will be backing off the unpopular requirement that doctors show "meaningful use" of their new computer systems. Andy Slavitt, acting administrator, admitted that "physician burden and frustration levels are real. Programs that are designed to improve often distract. Done poorly, measures are divorced from how physicians practice and add to the cynicism that the people who build these programs just don't get it."
Dr. James L. Madara, CEO of the American Medical Association, agreed that EHRs were having a negative impact on physicians' practices. Many physicians are spending at least two hours each workday using their EHR and may click up to 4,000 times per 8-hour shift, he said. Instead, CMS will reward health care providers for patient outcomes through the merit-based incentive pay systems created by last year's Medicare Access and CHIP Reauthorization Act (MACRA) legislation.CMS is calling on the private sector to create apps and analytic tools that will keep data secure while fostering true and widespread interoperability.
Dr. James L. Madara, CEO of the American Medical Association, agreed that EHRs were having a negative impact on physicians' practices. Many physicians are spending at least two hours each workday using their EHR and may click up to 4,000 times per 8-hour shift, he said. Instead, CMS will reward health care providers for patient outcomes through the merit-based incentive pay systems created by last year's Medicare Access and CHIP Reauthorization Act (MACRA) legislation.CMS is calling on the private sector to create apps and analytic tools that will keep data secure while fostering true and widespread interoperability.
Exactly, trying to force the tasks required for a specialized task to fit into a GUI designed by someone who has no idea of what that task actually entails is madness.
Would you do complex engineering with a checklist which looks like it was written as a first year project and which imposes the process on you, but can't me made to actually match the real world?
Hell, on numerous occasions I've been on the receiving end of some bloody accountant trying to apply his idiotic metrics to something which can't be quantified readily ... why, no, I can't quantify the way in which I will find and fix bugs in a way which is meaningful to an accountant ... and, no, your standard template document has nothing to do with be solving a tricky problem of semantics.
One size really doesn't fit all. Some sizes don't fit anybody.
Lost at C:>. Found at C.