The research question
Which symptoms and supportive-care needs are missed by infrequent study assessments?
Proposed design
Clinically supported prospective symptom reporting aligned with treatment cycles, with a predefined escalation and safety-reporting process.
Illustrative design: 8- to 12-week observation aligned to treatment cycles; setup and recruitment are scoped separately.
Data to collect
- Patient-reported symptom severity and interference
- Treatment-cycle context
- Daily function and supportive-care use
- Care contacts and reporting completion
Planned outputs
- Treatment-aligned symptom trajectories
- Supportive-care needs and burden summaries
- Assessment feasibility and missing-data report
What we confirm with you
We agree the population, sample size, country, collection tools, analysis plan and budget. Collection starts after the required consent, ethics or other permissions and a signed scope are in place.
- Confirm cancer type, treatment and cohort definitions
- Establish clinical escalation and adverse-event handling
- Choose permitted measures; diaries alone do not establish tumor response or survival
Clinical records, laboratory results, photographs and device integrations are included only when access, collection quality and permitted use have been verified. Self-reported findings are identified as such.
Research context
These published sources explain the research need or method. They are not RIDLY customers, endorsements or purchase commitments.
- PRO-TECT electronic cancer symptom study, 2025
The trial evaluated electronic symptom monitoring during cancer treatment, supporting study of symptoms between visits.
- NCI patient-reported symptomatic adverse-event measures
NCI provides a measurement system for patient-reported symptomatic adverse events in cancer clinical trials.
Related dataset profiles
For an existing-data inquiry, start with a coverage review.