Assessing the Plain Language Planner for Communication About Common Palliative Care Medications
Elaine Wittenberg,(1) PhD, Betty Ferrell,(2) RN, PhD, MA, FAAN, FPCN, CHPN, and Joy Goldsmith,(3) PhD
(1)Communication Studies, California State University, Los Angeles, California; (2)City of Hope National Medical Center, Division of Nursing Research and Education, Duarte, California; (3)Department of Communication, University of Memphis, Memphis, Tennessee
Authors’ disclosures of potential conflicts of interest are found at the end of this article.
Joy Goldsmith, PhD, Department of Communication, 235 Art and Communication Building, University of Memphis, Memphis, TN 38152. E-mail: firstname.lastname@example.org
J Adv Pract Oncol 2017;8:575–580 |
© 2017 Harborside Press®
Using plain language to communicate about oncology and palliative care medications and symptoms is recommended as a communication strategy to address patient/family health literacy demands. This study tested the Plain Language Planner©, a provider tool for communicating about medication and symptoms using plain language. Prior to and immediately following an oncology and palliative care nurse educational session, participants (n = 87) role-played about a symptom and medication. Common symptoms (nausea, constipation, and anxiety) and medications were selected. Self-evaluation and peer evaluation addressing the extent of plain language used during the role-play were rated. Plain language characteristics improved post educational role-play sessions for nurses. The largest improvement in plain language was the inclusion of the brand and generic names of medication in relating the drug to the symptom. The pocket guide provided during the educational session was consulted by 86% of nurses during the postsession role-play. Brief training with the Plain Language Planner may improve provider communication and meet patient/family health literacy needs. This resource may be a valuable asset to other health-care disciplines working in oncology and palliative care contexts.
For access to the full length article, please sign in