Abstract

ObjectivesIt is unclear if provider recommendations regarding colorectal cancer (CRC) screening modalities affect patient compliance. We evaluated provider–patient communications about CRC screening with and without a specific screening modality recommendation on patient compliance with screening guidelines. MethodsWe used the 2007 Health Information National Trends Survey (HINTS) and identified 4283 respondents who were at least 50years of age and answered questions about their communication with their care providers and CRC screening uptake. We defined being compliant with CRC screening as the use of fecal occult blood testing (FOBT) within 1year, sigmoidoscopy within 5years, or colonoscopy within 10years. We used survey weights in all analyses. ResultsCRC screening discussions occurred with 3320 (76.2%) respondents. Approximately 95% of these discussions were with physicians. Overall, 2793 (62.6%) respondents were current with CRC screening regardless of the screening modality. Discussion about screening (odds ratio (OR)=8.83; 95% confidence interval (CI): 7.20–10.84) and providers making a specific recommendation about screening modality rather than leaving it to the patient to decide (OR=2.04; 95% CI: 1.54–2.68) were associated with patient compliance with CRC screening guidelines. ConclusionCompliance with CRC screening guidelines is improved when providers discuss options and make specific screening test recommendations.

Full Text
Paper version not known

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.