Why FOCUS4 Results Need to Be Read Module by Module
FOCUS4 used a shared screening and randomization platform, but its treatment modules did not answer one interchangeable question. Patients entered modules according to molecular findings and were assigned to different interventions against different comparators. A result from one module therefore describes a particular treatment contrast in a particular population—not automatically an effect that applies to every patient enrolled in FOCUS4.
This matters when comparing reported results. A treatment may improve progression-free survival (PFS) in a molecularly selected group, while a different treatment shows little evidence of benefit in another group. Those findings are not contradictory: they concern different interventions and populations. Nor can they be combined just because the modules share a platform or use the same endpoint name.
Three Modules, Three Treatment Questions
FOCUS4 enrolled patients with advanced colorectal cancer whose disease had not progressed after initial chemotherapy, then used molecular screening to guide assignment to treatment modules. The important comparison is not simply “FOCUS4 treatment versus control.” The module determines who is compared, what is given, and what the result can support.
| Module | Population defining the comparison | Intervention and comparator | Reading the result |
|---|---|---|---|
| FOCUS4-N | The non-stratified group not assigned to the molecularly selected treatment modules | Maintenance capecitabine versus active monitoring | A maintenance strategy compared with no maintenance chemotherapy in this group |
| FOCUS4-C | Patients selected for a PIK3CA mutation | Aspirin versus placebo | A test of aspirin in this molecularly selected population |
| FOCUS4-D | Patients selected for RAS- and TP53-mutant disease | Adavosertib versus active monitoring | A test of adavosertib in a distinct molecularly selected population |
The N group is best understood as the non-stratified module population, not as a claim that every participant had identical molecular biology. C and D selected patients by different molecular features. Their interventions also differed: aspirin is not capecitabine or adavosertib, and placebo is not the same treatment condition as active monitoring. These details are part of the estimand—the precise treatment effect the comparison is intended to estimate.
Worked Example: Naming the Question Before Comparing Results
Suppose a report says that capecitabine improved PFS in FOCUS4-N, while aspirin did not show evidence of PFS benefit in FOCUS4-C. What can be concluded from these statements?
The first comparison concerns maintenance capecitabine versus active monitoring among patients in the non-stratified module. The second concerns aspirin versus placebo among patients selected for PIK3CA mutation. Each statement is conditional on its own population and comparator.
It is reasonable to say that the two module reports describe different evidence. It is not justified to conclude from this contrast alone that capecitabine is more effective than aspirin: the modules did not randomize patients between capecitabine and aspirin, and their eligible populations differed. The relevant direct treatment comparison was not made.
What Makes an Effect Comparable?
For a time-to-event endpoint such as PFS, a common summary is a hazard ratio (HR). In a proportional-hazards model, the HR compares the instantaneous event rates between assigned groups over follow-up, conditional on the model. An HR below 1 favors the intervention when the event is progression or death. This interpretation depends on how the endpoint and analysis are defined; an HR is not a ratio of median PFS times.
A shared endpoint label is helpful but insufficient for pooling. The modules must also have sufficiently comparable definitions of progression and death, assessment schedules, follow-up, censoring rules, and analysis populations. Moreover, an overall summary needs a clinical target. For example, it might target an average treatment effect across a specified distribution of module populations. Without defining that target, “the FOCUS4 effect” has no single clear meaning.
One way to see the assumptions behind a simple summary is to consider independent module estimates \(\hat\theta_j=\log(\widehat{HR}_j)\) with estimated variances \(v_j\). Under a fixed-effect model, each module is assumed to estimate one common log-HR \(\theta\), with sampling error but no real between-module difference. The inverse-variance estimate follows by minimizing the weighted squared deviations:
Differentiating and setting the result to zero gives \(\sum_j(\hat\theta_j-\theta)/v_j=0\). Rearranging yields the weighted estimate and its model-based standard error:
Exponentiating \(\hat\theta_{\mathrm{FE}}\) gives a pooled HR. But the calculation does not prove the common-effect assumption. In FOCUS4, different molecular populations, drugs, and control conditions make that assumption a substantive scientific claim, not a routine consequence of using the same platform.
Worked Example: A Pooled Number Can Hide Incompatible Questions
Consider two hypothetical independent module estimates, not FOCUS4 results. Module A has HR \(0.50\) with a 95% confidence interval from \(0.30\) to \(0.83\). Module B has HR \(1.10\) with a 95% confidence interval from \(0.70\) to \(1.73\). Suppose, only to illustrate the arithmetic, that both are treated as estimates of one common log-HR.
For a confidence interval on the log scale, estimate the standard error as the interval width divided by \(2(1.96)=3.92\). Thus:
The inverse-variance weights are \(w_A=1/0.2596^2=14.84\) and \(w_B=1/0.2308^2=18.77\). Therefore:
The pooled HR is \(\exp(-0.2528)=0.777\). A 95% interval on the log scale is \(-0.2528\pm1.96(0.1725)\), or \((-0.5909,\,0.0853)\); exponentiating gives an interval of approximately \((0.554,\,1.089)\). Under the assumed model this interval includes 1, so it does not rule out a common HR of 1 at the 5% level.
The arithmetic is internally consistent; the scientific interpretation may not be. If A and B used different interventions or populations, the pooled HR is not automatically an effect of either intervention, nor an effect for all patients. The fixed-effect calculation answers a common-effect question only if that common effect is a defensible target.
Population, Comparator, and Endpoint Must Travel Together
A treatment effect can vary across populations. Molecular selection may identify patients with a different prognosis, a different response to a drug, or both. The control condition also matters: active monitoring estimates the effect of offering treatment instead of monitoring, while placebo control estimates the effect of the active drug relative to its placebo condition. Background care and treatment burden are part of that contrast.
Endpoints require equally careful reading. PFS is commonly used in these maintenance comparisons, but identical wording does not ensure identical measurement or analysis. PFS depends on the time origin, the rules for defining progression, the timing of assessments, and how incomplete follow-up is handled. Overall survival (OS), response, and adverse events answer different questions and cannot be substituted for PFS. A result on one endpoint does not establish benefit on all others.
Worked Example: A Shared Time Point Does Not Make Populations Exchangeable
Suppose two hypothetical modules both report progression by six months. In module C, 36 of 60 intervention patients and 40 of 60 control patients progress. In module D, 18 of 40 intervention patients and 30 of 40 control patients progress. Assume complete outcome ascertainment for this illustration.
In C, the six-month risks are \(36/60=0.600\) and \(40/60=0.667\), so the risk difference (intervention minus control) is \(0.600-0.667=-0.067\), or 6.7 percentage points fewer progressions in the intervention group. In D, the risks are \(18/40=0.450\) and \(30/40=0.750\), giving a risk difference of \(0.450-0.750=-0.300\), or 30.0 percentage points fewer.
Both modules used a six-month outcome, but the risk differences differ substantially. The calculation alone cannot tell whether the difference reflects treatment-effect variation, different patient prognosis, chance, or other design and measurement differences. Nor does it establish that the interventions are directly comparable. A pooled absolute effect would require an explicit target population and a defensible method for transporting each module’s contrast to it.
Diagnostics, Alternatives, and Limits
Before making a cross-module claim, check whether it is going wrong in any of these ways:
- Population drift: The eligibility criteria or molecular profiles differ, but the conclusion is worded as if it applied to one common patient group.
- Comparator substitution: Active monitoring and placebo are treated as equivalent without considering what participants received and what contrast randomization identifies.
- Endpoint shorthand: A shared label such as PFS is taken to guarantee the same time origin, assessments, event definition, or censoring.
- Significance-by-comparison: One module has a statistically significant result and another does not, so a difference in treatment effects is asserted. A difference between significance labels is not itself a statistical test of the difference.
- Over-reading pooled estimates: A narrow interval from a calculation is taken as evidence that the populations and treatment effects are genuinely interchangeable.
The strongest alternative to indirect comparison is a randomized head-to-head comparison in the population and setting of interest. If a direct comparison is unavailable, a carefully specified synthesis may still be useful, but it needs a target population, harmonized outcome definitions, and assumptions about comparability and effect variation. Depending on the question, investigators may report module-specific effects separately, use a model allowing between-module variation, or standardize effects to a defined patient mix. These approaches do not repair missing comparability by themselves; their assumptions must be stated and examined.
FOCUS4’s modular structure was useful for evaluating different strategies in biologically defined groups. Its limitation for cross-module interpretation is the same feature: different modules were designed to answer different questions. The reported evidence should therefore remain attached to its population, intervention, comparator, and endpoint unless a separate analysis justifies broader transport or synthesis.
Check Your Understanding
Answer the questions, then compare your reasoning with the brief solutions.
- Why is FOCUS4-N not simply another name for the PIK3CA-selected FOCUS4-C population?
- What treatment contrast does FOCUS4-D estimate, and what molecular features define its selected group?
- Two modules report PFS. Name two additional features that must be checked before treating their estimates as directly comparable.
- Why does a significant effect in one module and a non-significant effect in another not establish different treatment effects?
- What is the key scientific assumption behind the fixed-effect pooled HR in the worked example?
Solutions. (1) N is the non-stratified group not assigned to a molecularly selected treatment module; C selects patients with PIK3CA mutation. (2) D compares adavosertib with active monitoring in patients with RAS- and TP53-mutant disease. (3) Examples include the time origin, event definition, assessment schedule, follow-up, and censoring rules. (4) The significance labels reflect separate tests against no effect, not a test of the difference between module effects. (5) It assumes both estimates represent one common underlying log-HR, with observed differences attributable to sampling error.