7 research outputs found
Effects of patient-reported outcome assessment order
Background: In clinical trials and clinical practice, patient-reported outcomes are almost always assessed using multiple patient-reported outcome measures at the same time. This raises concerns about whether patient responses are affected by the order in which the patient-reported outcome measures are administered. Methods: This questionnaire-based study of order effects included adult cancer patients from five cancer centers. Patients were randomly assigned to complete questionnaires via paper booklets, interactive voice response system, or tablet web survey. Linear Analogue Self-Assessment, Patient-Reported Outcomes Version of the Common Terminology Criteria for Adverse Events, and Patient-Reported Outcomes Measurement Information System assessment tools were each used to measure general health, physical function, social function, emotional distress/anxiety, emotional distress/depression, fatigue, sleep, and pain. The order in which the three tools, and domains within tools, were presented to patients was randomized. Rates of missing data, scale scores, and Cronbach’s alpha coefficients were compared by the order in which they were assessed. Analyses included Cochran–Armitage trend tests and mixed models adjusted for performance score, age, sex, cancer type, and curative intent. Results: A total of 1830 patients provided baseline patient-reported outcome assessments. There were no significant trends in rates of missing values by whether a scale was assessed earlier or later. The largest order effect for scale scores was due to a large mean score at one assessment time point. The largest difference in Cronbach’s alpha between the versions for the Patient-Reported Outcomes Measurement Information System scales was 0.106. Conclusion: The well-being of a cancer patient has many different aspects such as pain, fatigue, depression, and anxiety. These are assessed using a variety of surveys often collected at the same time. This study shows that the order in which the different aspects are collected from the patient is not important
Ensuring comprehensive assessment of urinary problems in prostate cancer through patient-physician concordance
Ensuring comprehensive assessment of urinary problems in prostate cancer through patient-physician concordance
Objectives: To examine the concordance between clinicians and men diagnosed with prostate cancer on a clinician-derived pathophysiological classification of the following self-reported urinary complications: storage (irritative), voiding (obstructive), and leakage/incontinence. Materials and methods: Fourteen urology experts classified 37 urinary function questionnaire items into 3 primary conceptual dimensions (e.g., storage [irritative], voiding [obstructive] and urinary leakage/incontinence) that would best reflect each item's content. In addition, 218 patient participants provided responses to the 37 items. Using classifications by experts to develop the conceptual framework, the structure was tested using confirmatory factor analyses with patient data. Results: Expert consensus was achieved in the classification of 31 out of 37 items. Using the 3-factor conceptual framework and patient data, the fit indices for the overall correlated factor model suggested an acceptable overall model fit. The analyses of the separate domains showed acceptable fit for the storage/irritative domain and the leaking/incontinence domain. The dimensionality of the voiding/obstructive domain was too difficult to estimate. Conclusions: Our analysis found items that conceptually and psychometrically support 2 constructs (leaking/incontinence and storage/irritative). The consistency of this support between the groups suggests a clinical relevance that is useful in treating patients. We have conceptual support for a third hypothesis (voiding/obstructive), although there were too few items to assess this psychometrically. Relative motivating factors of bother and urinary complaints were not addressed and remain an unmet need in this field