"Sometimes, the hardest thing for a physician to do is nothing," observed my colleague Jay Siwek, MD in a recent editorial in American Family Physician. "And although patients are sometimes a source of excess utilization, physicians, responding to conventional practices, current fads, and the rituals of medicine, often order tests or treatments that don’t stand up to clinical scrutiny. How do we do better? How do we know not only what to do, but also what not to do?"
The editorial compiles family medicine-relevant items from the multi-specialty Choosing Wisely campaign that aims to reduce the provision of "unnecessary" care, defined as medical tests and treatments that offer no health benefits and may result in harm to patients. Based on trusted sources of evidence-based medicine such as the U.S. Preventive Services Task Force, the Cochrane Database of Systematic Reviews, and Essential Evidence Plus, these "don't do" recommendations have the potential to save both lives and money, if they can be effectively put into practice. To inform patients about the campaign, Consumer Reports has created fact sheets about many of the included items.
Reactions to the Choosing Wisely campaign in the blogosphere have been varied. Calling it "the health reform we need," cardiologist John Mandrola writes, "I hope it sticks like super glue." On the other side, emergency physician William Sullivan argues that the campaign "has good intentions, but isn't a good idea," noting that "there isn’t a Suing Wisely campaign for attorneys and there isn’t a Legislating Wisely campaign for Congress." Similarly, family physician Mike Sevilla contends that while Choosing Wisely may "score political points" for sponsoring physician organizations, it is unlikely to change their members' behavior, which is also driven by patient demands and fears of lawsuits over interventions not taken. Where do you stand on this spectrum of opinions? Is the Choosing Wisely campaign good or bad for patients, or perhaps some of both?
A slightly different version of this post first appeared on the AFP Community Blog.