Abstract

Community stakeholders often participate in community research training curricula development. There is limited information describing how their input informs curricula. This paper describes input solicitation methods, input received, and examples of its integration. From June 2014 to June 2016, community members (CMs) and community-based organizations (CBOs) guided curricula development tailored for CMs and CBOs, respectively. Engagement methods included a strategic planning retreat, surveys, a listening session, workgroup meetings, and community engagement studios. Descriptive statistics were used to summarize survey input. For other methods, input was extracted and compiled from facilitator notes. CMs (n = 37) and CBOs (n = 83) providing input included patients and caregivers and advocacy, community service, and faith-based organizations, respectively. The major feedback categories were training topic priorities, format (e.g., face-to-face vs. online), logistics (e.g., training frequency), and compensation (e.g., appro-priateness). Input directly guided design of CBO and CM curricula (e.g., additional time devoted to specific topics based on feedback) or helped to finalize logistics. Multiple quantitative and qualitative methods can be used to elicit input from community stakeholders to inform the development of community research training curricula. This input is essential for the development of training curricula that are culturally relevant and acceptable.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.