COA Instruments

COA Measurement Properties: Evidence a Trial Still Needs

After a named COA is chosen, which reliability, construct-validity, and ability-to-detect-change results still support using that score as a trial endpoint.

· · 20 min read

Editorial still life of an analog balance scale, unmarked assessment booklets, a wooden ruler, and a fountain pen on warm parchment and oxblood linen.

The decision is which measurement-property results this trial still needs after the COA is chosen

When a clinical development team, biostatistical group, and outcome-assessment working group agree on a therapeutic concept of interest—such as morning joint stiffness in arthritis, ambulatory fatigue in multiple sclerosis, or caregiver-observed irritability in neurodevelopmental disorders—and select an existing or modified instrument to measure it, the selection stage is finished. The operational question is the measurement-property package: which reliability, construct-validity, and ability-to-detect-change results this trial still needs before that named score is used as a confirmatory endpoint in this population and protocol context.

This single operational problem defines the boundary of the post-selection measurement-property package. It is anchored by two FDA documents. First, FDA's December 2009 guidance Patient-Reported Outcome Measures: Use in Medical Product Development to Support Labeling Claims remains a listed current guidance (landing page content current as of 17 October 2019; docket FDA-2006-D-0362). Draft April 2023 PFDD Guidance 4 states that when the Patient-Focused Drug Development (PFDD) series is final it will replace the 2009 document. As of 16 September 2026, Guidance 4 remains draft and not for implementation. The 2009 PRO guidance is therefore a predecessor that is still listed current, not a withdrawn rule, and it remains FDA's detailed public review structure for reliability, construct validity, and ability to detect change after content validity.

Second, FDA's final October 2025 PFDD Guidance 3 (Selecting, Developing, or Modifying Fit-for-Purpose Clinical Outcome Assessments; docket FDA-2022-D-1385) broadens those fundamental psychometric principles beyond patient-reported outcomes to encompass all four clinical outcome assessment modalities: clinician-reported outcomes (ClinRO), observer-reported outcomes (ObsRO), performance outcomes (PerfO), and patient-reported outcomes (PRO). Guidance 3 organizes these requirements under Component G (scores are not overly influenced by measurement error) and Component H (scores correspond to the meaningful aspect of health related to the concept of interest). Under 21 CFR 10.115, these guidances represent FDA's nonbinding current thinking. They do not establish legally enforceable rights or responsibilities, and completing the property package is not labeling, qualification, or Agency acceptance of the endpoint.

Keep this quantitative property package separate from adjacent trial-design jobs already published on Trial Endpoints. Eliciting what matters directly from patients belongs to PFDD Guidance 2 concept elicitation. Selecting between PRO, ClinRO, ObsRO, and PerfO belongs to COA modality selection. Choosing an existing instrument or justifying minor modifications belongs to PFDD Guidance 3 fit-for-purpose selection. Managing clinician raters and preventing rater drift belongs to ClinRO rater operational controls. Evaluating migration from paper to electronic screens belongs to eCOA mode comparability, and sensor validation belongs to digital health technology endpoint verification. Finally, defining meaningful score differences (MSD) or within-patient responder thresholds belongs to draft PFDD Guidance 4 endpoint construction.

Crucially, assembling this trial-specific measurement-property package does not constitute formal drug development tool qualification under Section 507 of the Federal Food, Drug, and Cosmetic Act, does not guarantee marketing approval or labeling claims, and does not render the instrument permanently 'validated' for future indications. It is the trial-specific argument that remaining score variation can still be interpreted as variation in the targeted concept in this context of use.

Do not start property testing until the concept is already the right one, and do not copy coefficients from another population

The most consequential error in clinical trial psychometrics is treating mathematical reliability or statistical correlation as a substitute for clinical relevance. FDA's 2009 guidance states that testing other measurement properties will not replace or rectify problems with content validity. Content validity is qualitative evidence that items and domains are appropriate and comprehensive for the intended concept, population, and use. If an instrument measures symptoms patients do not experience, omits disabling manifestations, or uses phrasing patients misunderstand, a high Cronbach's alpha or test-retest coefficient cannot rescue the score. Consistency in measuring the wrong construct produces an uninterpretable endpoint.

Modern measurement theory has formalized this principle. As noted in Guidance 3 footnote 33, what was historically categorized as distinct subtypes of validity is recognized under the 2014 AERA/APA/NCME Standards for Educational and Psychological Testing and contemporary psychometric literature (such as Edwards et al., 2017, and Zigler & Coles, 2024) as a unitary evidentiary argument. Validity is not an inherent stamp or certificate belonging to an instrument; it is the degree to which accumulated empirical evidence and theoretical rationales support specific interpretations of test scores for a proposed clinical use. Quantitative property testing represents the structural and empirical phases of that argument, which completely collapse if the qualitative foundation is absent.

Measurement properties are strictly conditional upon the exact instrument version, conceptual framework, item phrasing, response options, recall period, scoring algorithm, administration format (e.g., self-report vs interviewer-administered), patient population, clinical setting, and statistical analysis plan. The 2009 guidance glossary explicitly warns that psychometric attributes cannot be assumed to be relevant to all measurement situations, clinical purposes, patient demographics, or disease severities in which an instrument is deployed.

Equally vital is rejecting fabricated regulatory benchmarks. Neither the 2009 PRO guidance nor final Guidance 3 publishes a numeric Cronbach's alpha, ICC, or correlation cutoff as an FDA acceptance criterion. Guidance 3 Component G asks whether scores are overly influenced by measurement error so that remaining variation can still be interpreted as variation in the concept of interest; whether a COA-based endpoint is reliable enough to detect treatment effects of interest is pointed to PFDD Guidance 4. COSMIN guideline version 2.0 (2024) rates reliability as 'good' in a systematic review when ICC, (weighted) kappa, or a Pearson/Spearman correlation is at least 0.70. Those conventions grade published PROM studies; they are not labeling-claim acceptance rules and should not be copied into a protocol as FDA thresholds.

Match reliability evidence to the sources of variation that can scramble this COA type

In clinical trials, endpoints are evaluated longitudinally to detect treatment-induced differences between study arms. Consequently, the 2009 PRO guidance reviews reliability because trials measure change over time, so the instrument should yield consistent, reproducible estimates. Final Guidance 3 restates the same issue under Component G: scores should not be overly influenced by measurement error, so remaining variation can still be interpreted as variation in the concept of interest.

Because different COA types are vulnerable to different sources of error, Guidance 3 Table 3 maps possible sources of variation—and the corresponding evidence types—to PRO, ObsRO, ClinRO, and PerfO. The table is a map of likely error sources in the context of use, not a mandatory all-cells checklist. A PRO is vulnerable to recall and short-term fluctuation; a ClinRO to rater differences and drift; an ObsRO to differences between caregivers; and a PerfO to evaluator coaching, protocol adherence, and practice or learning effects. Appendix C of Guidance 3 recommends evaluating intra- and inter-rater reliability before using a proposed ClinRO in a registration trial; rater qualification, training, and drift monitoring belong to the published ClinRO operations article rather than this property package.

COA typeLikely sources of score variationGuidance 3 Table 3 evidence typesEstimation notes (not FDA cutoffs)
Patient-reported outcome (PRO)Time in patients who can remain stable; differences across related items in a multi-item score.Test-retest reliability when health status can remain stable; evaluation of score differences between related items or item sets. Internal consistency is additional information, not a substitute for stability over time.Guidance 3 recommends an ICC for test-retest in most cases, and the sponsor should justify the selected method. Cronbach's alpha or an IRT information-function estimate may add information; Guidance 3 states that those estimates alone may not be sufficient for Component G.
Clinician-reported outcome (ClinRO)Rater differences, within-rater variation, and time (which may mix the two); related items. Appendix C points to intra- and inter-rater work before a registration trial.Test-retest in stable patients (which may mix raters); inter-rater reliability; intra-rater reliability; related-item score differences. Point rater training and drift control to the published ClinRO article.Justify the ICC (or other) formula against which sources of variation were repeated versus held stable. Do not treat a training certificate as the reliability coefficient.
Observer-reported outcome (ObsRO)Time in stable patients (which may mix raters); different caregivers rating the same patient; within-caregiver variation; related items.Test-retest with the same observer when the patient is stable; inter-rater reliability when two different caregivers (for example, parent and preschool teacher) rate the same patient; intra-rater reliability; related-item score differences.Same ICC-justification rule as for ClinRO. Inter-rater evidence is relevant when more than one observer will generate the trial score.
Performance outcome (PerfO)Time; evaluator differences if a trained rater scores the task; practice or learning effects; related tasks. Guidance 3 sends strategies for practice effects to Appendix D and Guidance 4.Test-retest across repeated sessions; inter-rater and intra-rater reliability only if the PerfO requires a trained rater; evaluation of score differences between related tasks or task sets.Justify the ICC method. Mokkink et al. (2023), which Guidance 3 cites for collecting reliability data, treat reliability and measurement error as related but distinct and require ICC and SEM formulas to match the design. That methods paper is not an FDA cutoff document.

An adequate test-retest study needs three design choices that match Guidance 3. First, sponsors should specify one or more criteria to define stable patients. Evaluating agreement while patients are progressing or being titrated confounds true change with measurement error. Stability criteria should be independent of the COA under test.

Second, the interval between test and retest should be long enough that respondents are unlikely to recall their initial responses, but short enough that health status is still stable. Guidance 3 uses 1 to 2 weeks as an example of a period during which some conditions can remain stable, not as a universal interval. The 2009 guidance acknowledges that for remitting, relapsing, or episodic diseases, test-retest may be difficult or impossible to establish. In those populations, Guidance 3 tells sponsors to consider alternative ways to demonstrate reliability of the scores rather than forcing a two-week retest that cannot isolate measurement error.

Third, the estimator should match the design. Citing McGraw and Wong (1996) and Qin et al. (2019), Guidance 3 recommends an ICC to estimate test-retest reliability in most cases, and the sponsor should justify the selected method. Mokkink et al. (2023)—the reliability-data citation in Guidance 3—treat reliability and measurement error as related but distinct properties: the ICC is a ratio of patient variance to total variance, so a heterogeneous sample can produce a high ICC even when absolute error is large, and a restricted trial cohort can produce a modest ICC even when absolute error is small. There is no single ICC or SEM formula; the formula has to reflect which sources of variation were repeated versus held stable. Do not treat the common approximation SEM = SD * sqrt(1 - ICC)) as an FDA-required calculation. Report the ICC formulation actually used and, where measurement error is the scientific question, the matching SEM from the same variance components.

Internal consistency should stay in its lane. Cronbach's alpha assesses agreement among items that contribute to a score at one administration. The 2009 PRO guidance states that internal consistency, in the absence of test-retest reliability, may not constitute sufficient evidence of reliability for clinical trial purposes. Guidance 3 agrees that alpha can provide additional information but that IRT-based and internal-consistency estimates alone may not be sufficient for Component G. Alpha does not describe stability over time or rater agreement, and it is not applicable in the same way to a single-item score or to a composite-indicator model that does not assume items reflect one underlying construct. A published alpha from another population is not evidence that this trial's total score is reliable.

The 2009 guidance notes that flaws in reliability tend to increase Type II error and that instruments with poor reliability are unlikely to produce a false-positive result. That is not permission to skip reliability work: an unreliable score wastes sample size and can fail to detect a real effect.

flowchart TD
  subgraph Stage1["Qualitative Foundation (Prior Work)"]
    A["Concept Elicitation & Selection"] --> B["Establish Content Validity"]
    B -.->|"Qualitative Priority: Cannot be rescued by statistics"| C{"Content Valid?"}
  end

  subgraph Stage2["Exploratory Psychometrics (Phase 2)"]
    C -->|"Yes"| D["Specify A Priori Hypotheses"]
    D --> E["Reliability Testing (Component G)"]
    D --> F["Construct Validity Testing (Component H)"]
    E --> E1["Test-Retest ICC (Stable Cohort)"]
    E --> E2["Inter/Intra-Rater ICC (ClinRO/ObsRO)"]
    E --> E3["Absolute Error (SEM Estimation)"]
    F --> F1["Convergent & Discriminant Correlations"]
    F --> F2["Known-Groups Separation (Clinical Strata)"]
  end

  subgraph Stage3["Longitudinal Responsiveness (Pre-Phase 3 SAP Lock)"]
    E1 & E2 & F1 & F2 --> G["Ability to Detect Change"]
    G --> G1["Bidirectional Sensitivity (Gains & Losses)"]
    G --> G2["External Anchor Tracking (Clinical Markers)"]
    G1 & G2 --> H["Protocol & SAP Endpoint Specification"]
  end

  subgraph Stage4["Confirmatory Trial & Interpretation (Phase 3)"]
    H --> I["Phase 3 Confirmatory Trial Execution"]
    I --> J["Meaningful Change Thresholds (MSD / CDF)"]
    J -.->|"Governed by Draft Guidance 4 (Interpretability)"| K["Pivotal Labeling & Efficacy Review"]
  end

  style Stage1 fill:#fdf8f5,stroke:#8b2635,stroke-width:2px
  style Stage2 fill:#f4f7f9,stroke:#1d3557,stroke-width:2px
  style Stage3 fill:#fdfbf7,stroke:#4a4e69,stroke-width:2px
  style Stage4 fill:#f7f9f6,stroke:#2a9d8f,stroke-width:2px
Chronological evidence progression from qualitative content validation through exploratory psychometric testing, responsiveness verification, and confirmatory endpoint interpretation.

Prespecify construct-validity hypotheses instead of mining tertiles after the fact

Under the 2009 PRO guidance, construct validity represents evidence that empirical relationships among items, domains, and external clinical measures conform to logical, prespecified scientific hypotheses. Final Guidance 3 re-articulates this under Component H: scores correspond to the meaningful aspect of health related to the concept of interest. Meeting Component H depends on testing a priori hypotheses about those relationships rather than mining correlations after seeing the data.

For convergent and discriminant evidence, the analysis plan should predefine the direction—and, where a magnitude is hypothesized, the expected magnitude—of relationships with reference measures. Convergent evidence tests that the COA relates as predicted to other measures of related concepts. Discriminant evidence tests that it relates weakly, or not as predicted, to measures of distinct domains. An adequate study of any specific property should test a prespecified hypothesis; a hypothesized correlation when comparing a new score with an existing related measure is the 2009 example.

Expected correlation strength depends on whether the COA measures the concept directly or as an indirect stand-in. Guidance 3 notes that when a measure directly reflects lived experience—for example, patient-reported pain intensity—there may be little uncertainty that scores correspond to that experience. When the concept is an indirect stand-in—for example, a standardized walking-capacity or walking-speed task used for daily lower-limb function—sponsors should collect convergent evidence against variables closer to lived experience.

Guidance 3 reminds sponsors that if they prespecify correlation cutoffs in a psychometric SAP, those cutoffs are trial-specific hypotheses. They should take attenuation from restriction of range and unreliability into account; a moderate rather than large correlation can be the expected result when methods or environments differ. That reminder is not an FDA numeric acceptance range.

Known-groups evidence asks whether scores differentiate groups hypothesized in advance to differ on the meaningful aspect of health. Groups should represent distinct severity or impairment levels, with the model and hypothesis tests stated.

Guidance 3 does not recommend dividing COA scores into groups based on the distribution of a reference measure—tertiles, quartiles, medians, or quintiles—because those percentile cutoffs are arbitrary, may vary across samples, and may not represent clinically distinct groups. Sponsors should propose reference measures and justify cutoffs that represent distinct severity or impairment levels, and should provide the model and hypothesis tests.

Criterion validity is reviewed only if a gold-standard criterion is justified. The 2009 guidance notes that in rare cases FDA will review criterion validity when a criterion measure is purported for the concept (its example is a new sleep scale compared with polysomnography). For most PROs, and for any symptom known only to the patient, a criterion measure often cannot exist. Do not force a criterion analysis against an irrelevant biomarker.

Show that scores move when the concept moves, without turning that into a meaningful-change threshold

Ability to detect change—classified as 'responsiveness' within the COSMIN taxonomy (Mokkink et al., 2010)—is defined under the 2009 PRO guidance as the empirical demonstration that an instrument's score changes over time when a patient's true clinical state with respect to the concept of interest changes. Because registration clinical trials are designed specifically to quantify therapeutic change, an instrument that remains insensitive to real clinical evolution is useless as a primary or secondary endpoint.

Establishing ability to detect change requires analyzing prospective longitudinal data (typically gathered during Phase 2 trials, open-label extension cohorts, or dedicated natural history studies) that track COA scores alongside independent, external indicators of clinical change. External anchors may include clinician global ratings of change or other measures indicating that the patient's state has changed with respect to the concept of interest. A review of ability to detect change includes evidence that the instrument is equally sensitive to gains and losses and to change across the range expected for the trial population. If important subgroup differences in ability to detect change (for example, by sex, race, or age) are known, the 2009 guidance says those documented differences should be taken into account.

Psychometric evaluation of longitudinal data is designed to uncover two fatal failure modes:

  1. The Concept Changes, but the Score Does Not: Patients experience documented, clinically verifiable improvement or disease progression (confirmed by external anchors), but the COA score remains static. This failure mode indicates severe insensitivity, coarse response categories, or destructive ceiling/floor effects. Using such an instrument severely compromises trial power and dramatically increases required sample sizes.

  2. The Score Changes for the Wrong Reason: The COA score fluctuates significantly over time, but these movements do not correlate with shifts in the target concept of interest, or occur in response to extraneous clinical confounders (e.g., general systemic inflammation altering a disease-specific joint score). This failure mode indicates a severe lack of specificity, fundamentally threatening construct validity.

It is vital that clinical development teams do not conflate ability to detect change with the determination of meaningful within-patient change. Demonstrating that an instrument moves in response to clinical change is an intrinsic psychometric property of the score. Deciding how large that score change must be to represent a clinically meaningful improvement to patients is an interpretative decision rule governed by draft PFDD Guidance 4. COSMIN formally enshrines this distinction by classifying responsiveness as an intrinsic measurement property, while classifying interpretability (including minimal important differences and responder definitions) as an external characteristic rather than a measurement property.

DimensionAbility to Detect Change (2009 Guidance / Guidance 3)Meaningful Within-Patient Change (Draft Guidance 4)
Core Scientific QuestionDoes the score move longitudinally when the patient's clinical state actually changes?How large must a score change be for the patient to experience it as clinically meaningful?
Regulatory & Methodological RoleAn intrinsic quantitative measurement property of the instrument score.An interpretability decision about how large a move must be to matter to patients, which COSMIN does not classify as a measurement property.
Primary Study TimingExploratory studies (Phase 2, natural history) before confirmatory trial design.Prespecified in protocol/SAP; finalized and applied to Phase 3 confirmatory efficacy data.
Analytical MethodologyLongitudinal comparison of COA change with other measures indicating that the patient's state changed with respect to the concept of interest.Anchor-based interpretation methods for the size of within-patient change, as addressed in the published Guidance 4 article.
Key Output MetricsEvidence that scores move with independent change anchors, in both directions and across the range expected for the trial population.Meaningful score difference (MSD), meaningful score ratio (MSR), or a dichotomized responder definition derived and applied under draft Guidance 4—not as proof of ability to detect change.

Do not treat a minimal clinically important difference (MCID), meaningful score difference, or dichotomized responder definition as proof of ability to detect change. Deriving and applying those interpretation thresholds belongs to draft PFDD Guidance 4. Here, the psychometric obligation is strictly limited to demonstrating that the score functions as a sensitive, responsive measuring tape.

Finish exploratory property work before confirmatory analysis, and do not call the COA validated

FDA staff educational slides on COA review state that, if possible, reliability, construct validity, and ability to detect change should be evaluated in exploratory studies before phase 3 so that performance problems are found before the score is used as a registration endpoint. Those slides are training material, not a guidance document. Guidance 3 notes that cross-sectional reliability evidence obtained during development, with other supporting material, might justify exploratory use in phase 2; that is not the same as locking the registration-trial property package.

A related timing caution appears in the European Medicines Agency July 2005 reflection paper on health-related quality of life measures (EMEA/CHMP/EWP/139391/2004). As a general rule, that paper recommends that validation of an HRQL instrument preferably be completed before therapeutic confirmatory trials, and that in principle the same study should not be used both to validate the HRQL instrument and to test the HRQL change. The paper is HRQL-specific, not a COA-wide psychometric methods guidance and not an FDA requirement. Use it only as a confirmatory-trial timing caution, not as a claim that every COA must complete a separate study branded as a validation study, and not as a substitute for the 2009 and Guidance 3 evidence structure.

Underpinning this entire framework is a crucial conceptual discipline: clinical trialists should stop referring to any COA as 'validated'. In a November 2024 Value in Health analysis, Zigler & Coles demonstrate that clinical outcome assessments are never permanently validated as an inherent property of the questionnaire. Building upon modern validity theory (Edwards et al., 2017), they emphasize that validity is the degree to which empirical evidence and theoretical rationales support specific interpretations of scores for a proposed clinical use. An instrument that has extensive, peer-reviewed psychometric support in ambulatory adult outpatients with mild depression may fail completely when administered to hospitalized adolescents with severe psychiatric comorbidities. Every new trial context, clinical population, and operational environment demands its own context-of-use evidentiary justification.

Trial-level COA evidence is also not the CDER Drug Development Tool qualification pathway. FDA's COA Qualification Program FAQ (content current as of 2 August 2021) states that the measurement principles of content validity, reliability, construct validity, and ability to detect change apply to all COA types, that qualification is not required, and that using a COA in an individual development program does not qualify the instrument. Sponsors are not required to use only qualified COAs.

A qualification conclusion, if one exists, still does not exempt the sponsor from showing that the score performs in this population, administration format, and analysis plan. Before confirmatory analysis, the protocol and statistical analysis plan should lock the instrument version, scoring algorithm, missing-item handling, and the prespecified property analyses, in line with endpoint SAP locking principles. Completing that package supports a review-division discussion. It does not qualify the COA, does not mean the instrument is validated for all uses, and does not constitute FDA acceptance of the endpoint.