Patient-Reported Outcomes: When the Patient's Own Report Becomes Data

The gap this was built to close

For decades, side effects in cancer trials were graded by staff. A nurse or doctor watched, asked, and wrote down a number. That system is called the Common Terminology Criteria for Adverse Events, or CTCAE.

It works well for things a lab can measure. It works less well for things only the patient can feel. Nausea, fatigue, tingling, and pain live inside a person. A grade written by someone else is a translation.

The National Cancer Institute built a companion system for those symptoms. It is called PRO-CTCAE, short for the Patient-Reported Outcomes version of the CTCAE. The patient answers directly.

What the system actually measures

PRO-CTCAE does not ask people to grade themselves. It asks plain questions about four things:

• How often a symptom happens.
• How severe it is.
• How much it gets in the way of daily life.
• Whether it is there at all.

The item library holds 124 questions covering 78 symptoms drawn from the CTCAE list. The symptoms include pain, fatigue, nausea, rash, and hand-foot syndrome.

There is a version for children. Ped-PRO-CTCAE lets young people ages 7 to 17 answer for themselves. It has 130 items covering 62 symptoms. A caregiver version exists for when a child cannot answer.

Why the language count matters

NCI reports that PRO-CTCAE is available in more than 60 validated languages. Validated is the key word. A rough translation can shift what a question means.

That work has a purpose beyond convenience. If a trial only collects symptoms in English, it hears from a narrower group of people. The reported side effect profile then reflects that narrower group.

Where the data goes

PRO-CTCAE was designed for clinical trials first. NCI says it is meant to make adverse event reporting more precise and more repeatable, and to add to what clinicians report rather than replace it.

Both records are kept. The clinician grade and the patient report are compared, not merged. When they disagree, that disagreement is itself information.

NCI has also worked with the FDA and a data standards group to set common formats. Shared formats let results from different trials be compared.

The part that is easy to skip

Collecting a symptom score does nothing on its own. Someone has to read it. Someone has to act.

A survey that goes into a database and never reaches the treating team changes nothing for the person who filled it out. If a clinic asks you to complete symptom questionnaires, it is fair to ask who reads them and how fast.

What this does not do

• A symptom score is not a test result. It does not show whether the cancer is growing or shrinking.
• A high score does not automatically mean a treatment should stop.
• A low score does not prove a treatment is working.
• Missing answers can bias results. People who feel worst are often the least likely to fill in a form.

Symptom reporting sits alongside scans, labs, and exams. Our overview of treatment side effects covers what to report and when.

What to ask your clinic

• Who on my team sees my symptom answers, and how soon?
• Will anyone contact me if a score is high?
• Are these answers part of my medical record?
• Does my treatment plan change based on what I report?
• Can I answer in the language I am most comfortable in?

How this article was prepared

An AI-assisted editorial system helped prepare this page. No named medical reviewer has reviewed it unless one is listed.

The National Cancer Information Foundation publishes Cancer Explained. This page is for learning. It is not medical advice and does not suggest a test or treatment.

See an error, old source, or unclear wording? Tell us.