Tutorials › Response-Adaptive Randomization › Sensitivity to Treatment-Effect Magnitude

Operating Characteristics and Controversies · Tutorial 343 of 501

Sensitivity to Treatment-Effect Magnitude

Build and interpret a treatment-effect sensitivity analysis that shows how adaptive allocation, expected patient benefit, and power change across plausible scenarios.

Advanced 10 min read

What You'll Learn

  • Define a treatment-effect scenario grid using clinically meaningful values.
  • Hold design choices fixed so changes in operating characteristics can be attributed to effect magnitude.
  • Calculate expected patient benefit from the average treatment allocation in each scenario.
  • Interpret simulation estimates with Monte Carlo uncertainty.
  • Compare adaptive-design results with a fixed-allocation benchmark.
  • Diagnose unstable, non-monotone, or overly assumption-dependent sensitivity results.

Why Vary Treatment-Effect Magnitude?

A response-adaptive design changes assignments as outcomes accumulate. Its allocation and operating characteristics can therefore depend on how large the true treatment effect is. If an analysis reports results only at one assumed effect, it may miss important differences between a barely worthwhile effect and a substantial one. Sensitivity analysis makes those differences visible by repeating the same design evaluation over a set of clinically plausible effects.

The point is not to select the effect that makes the design look best. Instead, the scenarios should represent a defensible range, chosen from clinical judgment, prior evidence, or a prespecified decision threshold. The null case is useful as a calibration check, but nonzero effects are needed to see how adaptation responds when treatment truly helps.

Definition: For two treatments, let \(\mu_1\) and \(\mu_0\) denote their mean outcomes, with larger outcomes defined as better. The treatment-effect magnitude is \(\delta=\mu_1-\mu_0\), measured in the outcome's units. A sensitivity analysis over treatment-effect magnitude evaluates the same design under several specified values of \(\delta\), while keeping other design and model choices fixed.

Specify the Model and the Comparison

Consider a hypothetical two-arm trial with a continuous outcome. For this tutorial, assume that patient \(i\)'s outcome under treatment \(a\) follows a normal distribution with mean \(\mu_a\) and variance \(\sigma^2=1\), for \(a\in\{0,1\}\). Outcomes are independent across patients conditional on their assigned treatments, the treatment effect is constant across patients, and outcomes are available before the next assignment. There are no time trends, missing outcomes, or treatment-by-subgroup effects in this illustrative model. These assumptions make the example transparent; an applied analysis should use a model and data-generating scenarios suitable for its endpoint and trial.

Suppose the response-adaptive rule begins with 10 patients assigned to each arm. After that, it assigns the next patient to treatment 1 with probability \(q_t=P(\mu_1>\mu_0\mid\text{data available at time }t)\), and to treatment 0 otherwise. For a concrete Bayesian implementation, take independent priors \(\mu_0,\mu_1\sim N(0,4)\), with known outcome variance 1. After observing \(n_a\) outcomes with sum \(S_a\) on arm \(a\), the posterior variance and mean are

$$ v_a=\frac{1}{1/4+n_a},\qquad m_a=\frac{S_a}{1/4+n_a},\qquad q_t=\Phi\!\left(\frac{m_1-m_0}{\sqrt{v_1+v_0}}\right). $$

Here \(\Phi\) is the standard normal cumulative distribution function. This rule is specified to make the sensitivity exercise reproducible; the goal is not to compare allocation algorithms. In every scenario, the trial size, prior, initial assignments, update rule, outcome variance, and final testing procedure must remain the same. Only the generating effect \(\delta\) changes.

For a finite trial, useful operating characteristics include the expected fraction assigned to treatment 1, the expected patient benefit relative to assigning everyone to control, and power. If \(N_1\) is the number assigned to treatment 1 among \(N\) patients, then under a constant additive effect the expected treatment benefit per randomized patient is

$$ B(\delta)=\delta\,E\!\left(\frac{N_1}{N}\right). $$

This is an average outcome difference per patient, in outcome units. It is not a claim that every patient benefits by that amount. Power at a scenario value \(\delta\) is the probability that the prespecified final test rejects \(H_0\) at significance level \(\alpha\), when that value is the true effect. Because assignments depend on observed outcomes, the final test must have its type I error evaluated under the actual adaptive design; an ordinary fixed-allocation reference distribution should not be assumed valid without justification.

Construct a Scenario Grid

A practical grid includes the null, an effect near the smallest clinically important difference, and one or more larger effects that remain credible. For example, if a difference of 0.3 outcome units is considered clinically important, a grid might include \(\delta=0,\ 0.2,\ 0.3,\ 0.5,\ 0.8\). The precise values depend on context. Include values on both sides of the decision threshold when that helps distinguish a design that performs adequately only under optimistic assumptions from one that performs adequately across a broader range.

The analysis should define the scenarios before looking at the simulated results. If the effect is reported in standardized units, state the standard deviation used; if reported in natural units, retain those units in the table and interpretation. A scenario grid is not a probability distribution over effects. It describes separate conditional operating characteristics, unless a probability model over scenarios is explicitly added.

1
Choose clinically plausible effects.
Include the null and effects that span the clinically meaningful range, expressed in outcome units.
2
Hold the design fixed.
Keep the sample size, adaptive rule, prior, outcome variance, and final test unchanged across scenarios.
3
Repeat the complete trial simulation.
For each \(\delta\), generate outcomes, update assignments, and apply the prespecified final test in every simulated trial.
4
Summarize and check uncertainty.
Report allocation, patient benefit, and power, together with Monte Carlo uncertainty and relevant diagnostics.

Worked Sensitivity Analysis

Worked Example: Comparing Allocation, Benefit, and Power

Suppose the hypothetical design above has \(N=100\) patients. An analyst runs \(R=5{,}000\) simulated trials at each of four prespecified effects. The final test is calibrated by simulation under the adaptive design so that its null rejection rate is approximately 0.05. The following are hypothetical simulation summaries, not results from a real trial.

True effect \(\delta\) (units)Mean fraction assigned to treatment 1Expected benefit per patient (units)Estimated power
0.00.500.0000.050
0.20.580.1160.160
0.50.720.3600.580
0.80.820.6560.910

The benefit column is calculated from the allocation fraction, not estimated as a separate outcome average. At \(\delta=0.5\), for example,

$$ B(0.5)=0.5\times 0.72=0.360\text{ outcome units per patient}. $$

At \(\delta=0.8\), the corresponding calculation is \(0.8\times0.82=0.656\) units per patient. At the null, the treatment offers no mean benefit, so the expected benefit is zero even though half the patients are assigned to it on average. The simulated allocation fraction rises as the effect grows, which is consistent with this rule, but these particular values are illustrative rather than mathematical guarantees.

At \(\delta=0.5\), estimated power is \(2{,}900/5{,}000=0.580\) if 2,900 simulated trials reject. Its Monte Carlo standard error is approximately

$$ SE_{\mathrm{MC}}(\hat{\pi})= \sqrt{\frac{\hat{\pi}(1-\hat{\pi})}{R}} =\sqrt{\frac{0.580(1-0.580)}{5{,}000}} =0.00698. $$

Thus the simulation uncertainty alone is about 0.007, not the uncertainty from sampling patients in a real trial. The estimate suggests that power at an effect of 0.5 units is about 58% under this simulated design and analysis. It does not establish that the true clinical effect is 0.5 units.

Why the Design Can Change Across Scenarios

The effect magnitude influences two linked processes. First, it changes the distribution of outcomes observed on the two arms. Second, those outcomes change the posterior probability used to choose later assignments. With a positive effect, stronger separation in observed outcomes will generally make the rule favor treatment 1 more often. That can increase the proportion of patients receiving the better treatment, and therefore increase expected benefit.

But assigning more patients to one arm also reduces the number available on the other arm. Unequal allocation can make a treatment comparison less precise than a balanced allocation with the same total sample size. Consequently, the direction of change in power is not determined by the direction of change in patient benefit. Power may rise with effect magnitude while remaining below a fixed-allocation benchmark; power can also change irregularly because each simulated allocation path is random. The quantities answer different questions and should be reported side by side rather than collapsed into one score.

Worked Example: A Fixed-Allocation Benchmark

To interpret the adaptive results, consider a separate, hypothetical fixed-allocation benchmark with 50 patients per arm, normally distributed outcomes, known \(\sigma=1\), and a two-sided z test at \(\alpha=0.05\). Under this fixed design, the standard error of the difference in sample means is

$$ SE=\sqrt{\frac{1}{50}+\frac{1}{50}}=0.200. $$

At \(\delta=0.5\), the standardized mean difference is \(0.5/0.2=2.5\). The two-sided power is

$$ P(Z>1.96-2.5)+P(Z<-1.96-2.5) =1-\Phi(-0.54)+\Phi(-4.46) \approx 0.705. $$

At \(\delta=0.2\), the standardized difference is 1. The corresponding power is \(1-\Phi(0.96)+\Phi(-2.96)\approx0.170\). These fixed-design values are benchmarks under the stated normal model and test, not substitutes for power estimates under the adaptive design. In particular, the adaptive table's final test was calibrated for its own assignment process. A fair comparison must use tests with appropriate error control for each design.

Justifying the Benefit Calculation

The expression for average benefit follows directly from the constant-effect model. If patient \(i\) receives treatment 1, the expected outcome improvement relative to control is \(\delta\); if the patient receives control, that improvement is zero. Write \(A_i=1\) for assignment to treatment 1 and \(A_i=0\) otherwise. Then the expected total improvement relative to assigning all \(N\) patients to control is

$$ E\!\left(\sum_{i=1}^{N} A_i\delta\right) =\delta\sum_{i=1}^{N}E(A_i) =\delta E(N_1). $$

Dividing by \(N\) gives \(B(\delta)=\delta E(N_1/N)\). This argument needs the stated constant additive effect and a meaningful control comparison. If treatment effects vary across patients, the benefit depends on which patients are assigned to treatment, and the simple product may not apply. It also describes mean outcome benefit under the model, not a complete accounting of harms, costs, or downstream consequences.

Worked Example: Checking a Sensitivity Contrast

Using the hypothetical table, compare the \(\delta=0.2\) and \(\delta=0.8\) scenarios. The expected treatment allocation rises from 0.58 to 0.82, a difference of \(0.82-0.58=0.24\), or 24 percentage points. Expected benefit rises from 0.116 to 0.656 units per patient, a difference of \(0.656-0.116=0.540\) units. Estimated power rises from 0.160 to 0.910, a difference of 0.750, or 75 percentage points.

These contrasts describe the simulated design under two different assumed truths. They do not mean that increasing the effect in an actual trial would itself cause better allocation or higher power; the true effect is not a design setting that investigators can change. Nor does the larger patient benefit alone show that the design is preferable: the power, error control, and uncertainty in the operating-characteristic estimates also matter.

Diagnostics, Alternatives, and Limitations

A sensitivity analysis is only informative if the simulation represents the stated design and the comparisons are stable enough to interpret. Check that the null scenario has a rejection rate near the target \(\alpha\), especially when the final test is calibrated by simulation. Report the number of replicates and Monte Carlo standard errors. For a simulated rejection proportion \(\hat{\pi}\), a standard estimate is \(\sqrt{\hat{\pi}(1-\hat{\pi})/R}\). For an average allocation fraction, report its replicate-to-replicate standard deviation divided by \(\sqrt{R}\), or provide an appropriate interval.

Also inspect the distribution of allocation fractions across simulated trials, not only its mean. A mean near 0.7 could arise from most trials assigning roughly 70% to treatment 1, or from a mixture of trials assigning nearly everyone to one arm or the other. Those patterns have different implications for precision and reproducibility. Review the simulated allocation histories and final arm sizes for coding errors, unexpected early lock-in, or large run-to-run variability.

Three approaches are often contrasted:

ApproachWhat it answersMain limitation
One assumed effectHow the design performs at a single chosen scenarioCan hide sensitivity to the effect assumption
Scenario gridHow allocation, benefit, and power vary across specified effectsDoes not assign probabilities to the scenarios
Fixed allocation benchmarkHow a non-adaptive design performs under matched outcome assumptionsDoes not reproduce the adaptive assignment process

A grid is usually more transparent than presenting only a favorable single scenario. A fixed-allocation benchmark helps show what is specific to adaptation, but comparisons should hold trial size, endpoint model, significance level, and inferential goal as similar as possible. Averaging results over a distribution of effects is a different analysis: it requires choosing and justifying that distribution, rather than treating a list of scenarios as if they were equally likely.

Do not require every estimated operating characteristic to change monotonically with \(\delta\). In expectation, the specified rule may allocate more often to treatment 1 as evidence of benefit strengthens, but finite simulations are noisy and adaptive paths can be irregular. If a pattern looks implausible, increase the number of replicates, check the update and randomization code, examine the scenario-specific allocation distributions, and verify that only the intended parameter changed. A non-monotone result can be real under a complex rule, but it should not be dismissed as simulation noise without checking.

Finally, the analysis is conditional on its model. A constant effect, known variance, prompt outcomes, and a particular prior are simplifying assumptions here. If plausible variance, response, or outcome-delay assumptions also matter, assess those separately or in a clearly labelled joint sensitivity analysis. A scenario grid cannot guarantee performance for effects outside its range, and expected benefit does not capture all clinical trade-offs.

Key takeaway: Vary the treatment-effect magnitude while holding the design fixed, and report allocation, expected patient benefit, and power together. A sensitivity analysis shows which conclusions persist across plausible effects; it does not identify the true effect or replace checks of model fit, test calibration, and simulation error.

Check Your Understanding

Answer each question, then compare with the brief solutions below.

  1. In the constant-effect model, what is the expected benefit per patient if \(\delta=0.4\) outcome units and the expected treatment allocation fraction is 0.65?
  2. Why should the null scenario be included in a treatment-effect sensitivity analysis?
  3. With 4,000 simulated trials and estimated power \(\hat{\pi}=0.25\), calculate the Monte Carlo standard error.
  4. If mean allocation to treatment 1 increases across scenarios, must power also increase? Explain.
  5. What must be held fixed to attribute changes in operating characteristics to treatment-effect magnitude?

Solutions. (1) \(B=0.4(0.65)=0.260\) outcome units per patient. (2) It checks behavior when there is no treatment effect and helps assess whether the final test's null rejection rate is near \(\alpha\). (3) \(SE_{\mathrm{MC}}=\sqrt{0.25(0.75)/4{,}000}=0.00685\). (4) No. Greater imbalance can reduce precision, and power also depends on the effect size and the validity and behavior of the final test. (5) Keep the sample size, allocation algorithm, prior, outcome model and variance, initial assignments, and final testing procedure unchanged.

Clinical Biostats