Tutorials › Biostatistics › Model-Assisted vs. Model-Based Dose-Finding Designs

Phase I & Adaptive Dose-Finding

Model-Assisted vs. Model-Based Dose-Finding Designs

A computational guide to Fleming's two-stage design for single-arm Phase II clinical trials, including early stopping for both futility and efficacy, binomial operating characteristics, probability of early termination, expected sample size, and a complete worked example.

Advanced 20 min read

What You'll Learn

  • What distinguishes model-assisted from model-based dose-finding
  • How BOIN, mTPI, Keyboard, and CRM fit into the taxonomy
  • How interval-based and model-based dose decisions differ
  • How CRM estimates the dose-toxicity relationship
  • How overdose control and pending DLTs affect dose selection
  • How to compare candidate designs using simulation

Introduction

Early-phase oncology trials must answer a difficult question: which dose provides an acceptable balance between toxicity and the need to treat patients at sufficiently high exposure?

Traditional dose-escalation approaches often use simple rules such as the 3+3 design. More modern approaches fall into two broad statistical families: model-assisted and model-based dose-finding designs.

The distinction is important because both families use statistical thinking, but they use it in fundamentally different ways. A model-assisted design typically converts statistical calculations into a prespecified decision algorithm or dose-toxicity table. A model-based design explicitly fits a dose-toxicity model to the accumulating data and uses the fitted model to guide dose selection.

Key idea: Model-assisted designs generally use model-derived decision rules without requiring investigators to fit a statistical model after every cohort. Model-based designs explicitly estimate the dose-toxicity relationship during the trial and use that fitted model to select the next dose.

The Dose-Finding Problem

Suppose a Phase I oncology trial evaluates several dose levels:

  • \(d_1\): lowest dose
  • \(d_2\): second dose
  • \(d_3\): third dose
  • \(\ldots\)
  • \(d_K\): highest prespecified dose

Let \(p_j\) denote the true probability of a dose-limiting toxicity (DLT) at dose \(d_j\).

$$ p_j=P(\mathrm{DLT}\mid d_j) $$

The objective is usually to identify a dose whose toxicity probability is close to a prespecified target \(p_T\). For example, an oncology study might define:

$$ p_T=0.30 $$

The target is not necessarily the dose with the lowest observed DLT rate. Rather, the trial seeks a dose whose underlying toxicity probability is acceptably close to the target while maintaining appropriate safety constraints.

Important: The maximum tolerated dose (MTD) is a model- and design-dependent concept. The dose with the largest observed number of DLTs is not automatically the MTD, and the dose with zero observed DLTs is not automatically safe. Observed DLT counts are noisy estimates of the underlying dose-toxicity relationship.

What Is a Model-Assisted Design?

A model-assisted design uses statistical modeling to construct a set of prespecified dose-escalation and de-escalation rules, but the operational decision can often be made from a simple table or algorithm based on the number of patients treated and the number of DLTs observed.

Examples include:

  • Bayesian Optimal Interval (BOIN)
  • modified Toxicity Probability Interval (mTPI and related interval designs)
  • Keyboard designs
  • other interval-based or model-assisted dose-finding procedures

The design is statistically derived, but investigators do not necessarily have to refit a dose-toxicity curve after every cohort.

Think of model-assisted designs as: model-derived rules that have been translated into an operational decision table. The statistical model is important for constructing the rules, but the trial team can often execute the design by looking up the observed DLT rate and following the prespecified action.

What Is a Model-Based Design?

A model-based design explicitly specifies a mathematical relationship between dose and toxicity and estimates that relationship as patient data accumulate.

A generic dose-toxicity model can be written as:

$$ p(d;\theta)=P(\mathrm{DLT}\mid d,\theta) $$

where \(\theta\) represents unknown model parameters.

At each decision point, the accumulating DLT data are used to update information about \(\theta\). The fitted model is then used to estimate the toxicity probability at each candidate dose.

$$ \widehat{p}(d_j)=P(\mathrm{DLT}\mid d_j,\widehat{\theta}) $$

The next dose is selected according to a prespecified rule based on those model-based estimates, often choosing the dose whose estimated toxicity probability is closest to \(p_T\), subject to safety restrictions.

The classic example is the Continual Reassessment Method (CRM). Other model-based approaches include time-to-event extensions such as TITE-CRM and Bayesian escalation methods such as EWOC.

Model-Assisted vs. Model-Based: The Core Difference

The easiest way to understand the distinction is to ask: what is used directly to make the next dose decision?

Feature Model-Assisted Model-Based
Statistical model used in design development Yes Yes
Model explicitly fit during dose escalation Usually not required Yes
Operational decision Prespecified decision table/algorithm Fitted dose-toxicity model
Typical examples BOIN, mTPI, Keyboard CRM, TITE-CRM, EWOC
Implementation complexity Usually lower Usually higher
Model dependence during the trial Lower Higher
Transparency of bedside decision rule High Moderate
Adaptation to observed dose-toxicity relationship Rule-based Directly model-based
The distinction is not “statistical versus non-statistical.” Model-assisted designs are statistically principled. The distinction is whether a fitted dose-toxicity model is used directly and repeatedly to make dose decisions during the trial.

Why the Distinction Matters

The choice affects how investigators design, execute, monitor, simulate, and communicate a Phase I study.

A model-assisted design may be attractive when the sponsor wants a statistically efficient design that is relatively simple to implement and explain. A model-based design may be attractive when the sponsor wants the dose-toxicity model itself to drive dose selection and is willing to accept greater statistical and operational complexity.

1
Model-assisted: estimate or calibrate decision boundaries before the trial.
2
Model-assisted: observe DLTs and apply the prespecified decision rule.
3
Model-based: specify a dose-toxicity model before the trial.
4
Model-based: update the model as DLT data accumulate.
5
Use the resulting toxicity estimates to select the next dose, subject to prespecified safety constraints.

Defining the Target Toxicity Probability

Both design families require a clinically meaningful target. Let:

$$ p_T=\text{target DLT probability} $$

For illustration, suppose:

$$ p_T=0.25 $$

The trial is then attempting to identify the dose whose true DLT probability is near 25%.

The target should be established from clinical and pharmacologic considerations, not selected simply because it makes the statistical design convenient. Different therapeutic settings may justify different target toxicity probabilities.

The Three Fundamental Dose Decisions

Most dose-finding designs can be understood in terms of three possible actions:

Observed / Estimated Toxicity Typical Action
Too low relative to target Escalate
Acceptably close to target Stay at the dose
Too high relative to target De-escalate

The major difference is how the design determines whether the toxicity is “too low,” “close,” or “too high.”

  • Model-assisted: use a prespecified interval or decision algorithm.
  • Model-based: estimate the toxicity probability from the fitted dose-toxicity model.

Model-Assisted Designs: The Interval Concept

Many model-assisted designs define an interval around the target toxicity probability. For illustration, suppose the target is:

$$ p_T=0.25 $$

A design might use a statistically calibrated interval such as:

$$ (p_L,p_U)=(0.20,0.30) $$

The operating rule is conceptually:

Observed DLT Rate Decision
\(\widehat p Escalate
\(p_L\le\widehat p\le p_U\) Stay
\(\widehat p>p_U\) De-escalate

The actual boundaries used by a particular design should be calculated from the design methodology and target, rather than arbitrarily selected.

Why call this model-assisted? The interval and decision boundaries are statistically calibrated before the trial. During the trial, however, the investigator can frequently determine the action directly from the observed toxicity data and the prespecified table.

BOIN as a Model-Assisted Example

The Bayesian Optimal Interval design, commonly abbreviated BOIN, is a widely used model-assisted design.

Conceptually, BOIN creates escalation and de-escalation boundaries around the target toxicity probability. Let the target be \(p_T\), and let \(\lambda_e\) and \(\lambda_d\) denote the calibrated escalation and de-escalation boundaries.

$$ \widehat p_j\le\lambda_e \quad\Rightarrow\quad \text{escalate} $$
$$ \lambda_e<\widehat p_j<\lambda_d \quad\Rightarrow\quad \text{stay} $$
$$ \widehat p_j\ge\lambda_d \quad\Rightarrow\quad \text{de-escalate} $$

The boundaries are not chosen merely as arbitrary percentages. They are derived from the target toxicity probability and the statistical decision criterion of the design.

Keyboard Designs

Keyboard designs use a similar interval-based concept, but organize the decision process into a sequence of probability intervals represented as “keys.”

The observed number of DLTs and treated patients determines which toxicity interval is most compatible with the data. The design then recommends escalation, staying, or de-escalation according to the prespecified decision rule.

The important conceptual point is that the operational procedure is table- or interval-driven, rather than requiring the trial team to fit and interpret a nonlinear dose-toxicity curve at each decision.

mTPI and Related Interval Designs

The modified Toxicity Probability Interval framework, or mTPI, also divides the toxicity probability space into regions around a target.

The statistical calculations determine which interval has the greatest posterior support, after which the design maps that result to an escalation, stay, or de-escalation action.

mTPI and its descendants are therefore often grouped with model-assisted rather than model-based designs in the practical taxonomy used for Phase I dose finding.

Model-Based Designs: The Dose-Toxicity Curve

A model-based design instead specifies a functional relationship between dose and DLT probability.

A generic logistic formulation is:

$$ \operatorname{logit}\{p(d)\} = \alpha+\beta x(d) $$

where \(x(d)\) is a transformed dose metric and \(\alpha,\beta\) are unknown parameters.

A Bayesian model-based design assigns prior distributions to the unknown parameters:

$$ \theta\sim\pi(\theta) $$

After observing DLT outcomes, the prior is updated to a posterior distribution:

$$ \pi(\theta\mid D) \propto L(\theta\mid D)\pi(\theta) $$

The posterior distribution is then used to estimate toxicity probabilities at candidate doses.

The Continual Reassessment Method (CRM)

The Continual Reassessment Method is the canonical example of a model-based dose-finding design.

Suppose the candidate doses are represented by standardized scores \(x_1,\ldots,x_K\), and the model is:

$$ p_j=P(\mathrm{DLT}\mid d_j,\theta) $$

The CRM updates the model as patient outcomes become available. The next dose is then selected using the updated estimate of the dose-toxicity relationship, typically with safeguards against overly aggressive escalation.

A simplified selection criterion is:

$$ d_{\mathrm{next}} = \arg\min_{d_j} \left| \widehat p_j-p_T \right| $$

The actual CRM implementation can include overdose control, dose-skipping restrictions, cohort-size rules, and other safeguards. These details are essential parts of the design rather than optional additions.

CRM is not simply “pick the dose with the highest response.” The primary model is usually the dose-toxicity relationship, and the design uses the accumulating toxicity data to estimate which dose is closest to the target while respecting safety constraints.

Worked Example: Same Data, Different Design Logic

Consider five dose levels:

Dose Patients Treated DLTs Observed DLT Rate
10 mg 3 0 0%
20 mg 3 0 0%
30 mg 3 1 33.3%
40 mg 3 1 33.3%
50 mg 3 2 66.7%

Suppose the target DLT probability is:

$$ p_T=0.30 $$

A model-assisted interval design evaluates the observed DLT rate at the currently tested dose against its prespecified escalation, stay, and de-escalation boundaries.

A model-based design instead considers all accumulated information and fits a dose-toxicity model. The estimated toxicity at 20, 30, 40, and 50 mg is therefore influenced by the assumed dose-response structure and by the data from neighboring dose levels.

Key distinction: At 40 mg, both approaches may see an observed DLT rate of 33.3%. But they do not necessarily interpret that observation in the same way. An interval design may apply a local decision rule, while a model-based design can use the entire dose-toxicity trajectory to estimate the underlying probability at 40 mg.

Step 1: Define the Dose Levels

The first step is to specify the candidate doses and the maximum dose that may be administered.

Parameter Example
Number of dose levels 5
Lowest dose 10 mg
Highest planned dose 50 mg
Cohort size 3 patients
Target DLT probability 30%

The dose grid should be justified clinically and pharmacologically. The statistical design should not be used to compensate for a poorly chosen starting dose or implausible dose levels.

Step 2: Define the Target

For this example:

$$ p_T=0.30 $$

The target represents the toxicity probability that the design is attempting to identify.

It is useful to distinguish three quantities:

  • Target toxicity probability: the design target.
  • Observed DLT rate: the sample proportion observed so far.
  • Estimated toxicity probability: a model-based or model-assisted statistical estimate used for decision making.

Step 3: Apply a Model-Assisted Rule

Suppose the selected model-assisted design has already been calibrated to produce an escalation boundary and a de-escalation boundary.

At a dose with \(n\) treated patients and \(y\) DLTs:

$$ \widehat p=\frac{y}{n} $$

The decision is then made from the prespecified rule:

Condition Action
\(\widehat p\) below escalation boundary Escalate
\(\widehat p\) inside target interval Stay
\(\widehat p\) above de-escalation boundary De-escalate

For an actual study, the boundaries must be taken from the chosen design's calibration rather than from an informal approximation.

Step 4: Fit the Model in a Model-Based Design

For a model-based design, the same DLT observations are incorporated into the dose-toxicity model.

Let \(Y_i=1\) if patient \(i\) experiences a DLT and \(Y_i=0\) otherwise. Then:

$$ Y_i\sim\operatorname{Bernoulli}\{p(d_i;\theta)\} $$

The likelihood is:

$$ L(\theta) = \prod_{i=1}^{N} p(d_i;\theta)^{Y_i} \left[1-p(d_i;\theta)\right]^{1-Y_i} $$

In a Bayesian implementation, the likelihood is combined with the prior to obtain the posterior distribution.

$$ \pi(\theta\mid D) \propto L(\theta)\pi(\theta) $$

The fitted model can then produce posterior estimates for each candidate dose.

Step 5: Select the Next Dose

Suppose the fitted model produces:

Dose Estimated DLT Probability
10 mg 0.05
20 mg 0.12
30 mg 0.23
40 mg 0.34
50 mg 0.55

With \(p_T=0.30\), the closest model-estimated toxicity probability is at 40 mg:

$$ |0.34-0.30|=0.04 $$

whereas at 30 mg:

$$ |0.23-0.30|=0.07 $$

A model-based design could therefore consider 40 mg the dose closest to the target, subject to its prespecified overdose-control and escalation rules.

Do not confuse “closest to target” with “automatically administer.” Real model-based designs generally include safety constraints, such as a maximum allowable probability of excessive toxicity, restrictions on dose skipping, and rules for whether escalation is permitted before all pending DLT information is available.

Local Information vs. Borrowing Across Doses

One of the most important conceptual differences is how information from neighboring doses influences a decision.

A simple interval rule is strongly tied to the observed outcomes at the current dose. A model-based approach explicitly links doses through the dose-toxicity model.

For example, if a patient experiences a DLT at 30 mg, a fitted monotonic dose-toxicity model may update the estimated toxicity probabilities at 20, 30, 40, and 50 mg simultaneously.

$$ \text{Data at one dose} \quad\longrightarrow\quad \text{updated toxicity estimates across the dose range} $$

This borrowing of information is one reason model-based designs can be statistically efficient when the dose-toxicity model is appropriate.

Why Model Misspecification Matters

The major tradeoff is that a model-based design depends on the assumed dose-toxicity model.

If the model is poorly specified, the fitted curve can provide misleading toxicity estimates. For example, a model that imposes a particular shape or monotonic relationship may not adequately describe the actual biological relationship.

Model-based does not mean model-correct. A sophisticated model can still be wrong. Model selection, prior specification, dose transformation, sensitivity analyses, and simulation are therefore important parts of model-based design development.

Why Model-Assisted Designs Can Be Attractive

Model-assisted designs attempt to capture much of the statistical efficiency of principled dose-finding while simplifying implementation.

  • Decision rules can be transparent.
  • Operational implementation can be straightforward.
  • The design can be simulated before the study.
  • Statistical calibration can control escalation and de-escalation behavior.
  • The design does not necessarily require real-time nonlinear model fitting.
  • Investigators can often explain the decision process using a table.

This can be particularly useful when the clinical team wants a sophisticated design without making every dose decision dependent on a model-fitting workflow.

Why Model-Based Designs Can Be Attractive

Model-based designs can use the accumulating data more directly and can borrow information across dose levels through the assumed dose-toxicity relationship.

  • They directly estimate the dose-toxicity curve.
  • They can use information across multiple dose levels.
  • They can accommodate flexible Bayesian or likelihood-based frameworks.
  • They can be extended to time-to-event outcomes.
  • They can incorporate formal overdose-control criteria.
  • They can be highly efficient when the model is well specified.

CRM vs. BOIN: A Useful Comparison

Feature BOIN CRM
Design family Model-assisted Model-based
Primary operational mechanism Interval decision rule Fitted dose-toxicity model
Target toxicity Explicit Explicit
Model fitted during trial Not required for the operational rule Yes
Information borrowing across doses Limited / rule-based Explicit through the model
Implementation Relatively simple More complex
Need for simulation Important Important
Potential sensitivity to model specification Lower Higher
Bottom line: BOIN and CRM are not simply two different names for the same method. BOIN uses a calibrated interval-based decision rule, whereas CRM explicitly estimates a dose-toxicity model during the trial.

3+3 Is Not the Same as Model-Assisted

A frequent source of confusion is the statement that the 3+3 design is “model-assisted” because it uses a dose-escalation rule.

That terminology should be used carefully.

The traditional 3+3 design is generally considered a rule-based algorithmic design, not a model-assisted design in the modern statistical taxonomy.

Design Common Classification
3+3 Rule-based / algorithmic
BOIN Model-assisted
mTPI / related interval designs Model-assisted
Keyboard Model-assisted
CRM Model-based
TITE-CRM Model-based
EWOC Model-based Bayesian

The important point is that a design can be algorithmic without being statistically classified as model-assisted.

Safety Constraints Apply to Both Families

Neither model-assisted nor model-based classification eliminates the need for explicit safety controls.

A dose-finding protocol may include rules concerning:

  • Maximum tolerated dose or maximum administered dose
  • Maximum allowable overdose probability
  • Restrictions on skipping dose levels
  • Maximum dose-escalation magnitude
  • Stopping for excessive toxicity
  • Stopping for insufficient information
  • Requirements for evaluable patients
  • Handling of pending DLT observations
Safety constraints are part of the design. A model that estimates a candidate dose near the target does not mean that dose should automatically be administered if the probability of excessive toxicity violates the prespecified safety rule.

Handling Pending Toxicity Data

Conventional cohort-based designs often wait for the required DLT assessment window before making the next decision. That can be operationally slow when the DLT window is long.

Model-based approaches can be extended to incorporate partial follow-up. The best-known example is TITE-CRM, which incorporates time-to-event information into dose-finding.

Conceptually:

$$ \text{complete DLT information} \neq \text{only information that can be used} $$

The exact weighting or likelihood contribution depends on the selected time-to-event model and must be prespecified.

Model-Assisted vs. Model-Based: Operational Complexity

Operational Issue Model-Assisted Model-Based
Decision lookup Often straightforward Requires model update
Statistical programming Moderate Higher
Real-time model fitting Usually unnecessary Usually required
Training burden Lower Higher
Model diagnostics Less central during escalation Important
Simulation Essential for design evaluation Essential and often extensive
Transparency to clinical team Generally high Requires more explanation

Statistical Operating Characteristics

Both design families should be evaluated through simulation before being used in a clinical trial.

Important operating characteristics include:

  • Probability of selecting the true target dose
  • Probability of selecting an overdose
  • Probability of selecting an underdose
  • Probability of excessive toxicity
  • Average number of patients treated
  • Probability of early stopping
  • Number of dose escalations
  • Number of dose de-escalations
  • Trial duration
  • Patient exposure at each dose

Let \(D^*\) denote the true target dose. Then one important metric is:

$$ P(\widehat D=D^*) $$

where \(\widehat D\) is the dose ultimately selected by the design.

Probability of Selecting the Target Dose

Suppose there are five dose levels and dose 3 is the true target dose. A useful simulation metric is the proportion of simulated trials that select dose 3 at the end of the study.

Selected Dose Probability in Simulation
Dose 1 5%
Dose 2 15%
Dose 3 62%
Dose 4 15%
Dose 5 3%

The target-selection probability is therefore:

$$ P(\widehat D=D_3)=0.62 $$

The exact values are design-specific and should be obtained from simulation rather than assumed.

Overdose Control

Target-dose selection alone is not enough. A design may have a high probability of selecting the target dose but still expose too many patients to doses whose toxicity is unacceptably high.

Let \(p_{\mathrm{OD}}\) represent an overdose threshold. For example:

$$ p_{\mathrm{OD}}=0.40 $$

An overdose-control rule can be expressed conceptually as:

$$ P\{p(d_j)>p_{\mathrm{OD}}\mid D\} \le q $$

where \(q\) is a prespecified maximum acceptable probability of overdose.

The exact formulation depends on the selected design. Bayesian model-based designs can naturally express such posterior overdose probabilities, while model-assisted designs can incorporate safety boundaries into their decision rules.

Why Simulation Is Essential

A dose-finding design is a sequential decision process. Its behavior depends on the entire path of DLT outcomes, not merely on the final DLT rate.

For a candidate design, investigators should simulate many possible trials under a range of true dose-toxicity scenarios.

1
Specify a plausible true dose-toxicity scenario.
2
Generate patient DLT outcomes according to the scenario.
3
Apply the complete dose-finding algorithm.
4
Record the doses administered and the final selected dose.
5
Repeat thousands of times and summarize the operating characteristics.

Example Simulation Scenarios

Suppose the target DLT probability is 30%. Three possible underlying dose-toxicity scenarios might be:

Dose Scenario A Scenario B Scenario C
Dose 1 0.05 0.05 0.05
Dose 2 0.10 0.15 0.10
Dose 3 0.20 0.30 0.20
Dose 4 0.30 0.45 0.35
Dose 5 0.45 0.60 0.70

Scenario B has dose 3 as the target dose. Scenario A has dose 4 as the target dose. Scenario C creates a more difficult separation between doses 3 and 4.

A useful design comparison asks whether BOIN, CRM, or another candidate design behaves appropriately under all three scenarios rather than only under the scenario that is most favorable to one method.

Common Misconception: “Model-Based Is Always Better”

A more sophisticated statistical model is not automatically a better clinical trial design.

Model-based methods can be highly efficient when their assumptions are reasonable, but they can also be more sensitive to model specification and implementation details.

Model-assisted designs can offer an attractive compromise: statistically calibrated decision rules with less dependence on real-time model fitting.

Design selection should be comparative, not ideological. The appropriate question is not “Which method is most sophisticated?” It is “Which method provides acceptable safety, target-dose selection, operational feasibility, and statistical performance for this specific trial?”

Common Misconception: “Model-Assisted Means No Model”

This is also incorrect.

A model-assisted design may rely heavily on statistical modeling during its development. The distinction is that the final operational decision is expressed as a prespecified rule rather than requiring the trial team to fit the underlying model continuously.

Thus:

$$ \text{Model-assisted} \neq \text{model-free} $$

Instead:

$$ \text{Model-assisted} = \text{model-derived decision procedure} $$

Common Misconception: “Observed DLT Rate Is the Toxicity Probability”

If 1 of 3 patients experiences a DLT, the observed DLT rate is:

$$ \widehat p=\frac{1}{3}=0.333 $$

But the true toxicity probability is unknown.

The observed proportion is an estimate with substantial uncertainty. Model-assisted and model-based designs differ partly in how they translate that limited information into a dose decision.

Model-Assisted vs. Model-Based: Strengths and Limitations

Dimension Model-Assisted Model-Based
Ease of implementation Strong advantage More demanding
Decision transparency Strong advantage Moderate
Explicit dose-toxicity estimation Limited Strong advantage
Borrowing across doses Less direct Strong
Dependence on model assumptions Generally lower Higher
Flexibility High within rule framework Very high
Programming complexity Lower Higher
Need for simulation High Very high

When a Model-Assisted Design May Be Preferable

A model-assisted approach may be attractive when:

  • The sponsor wants a modern statistical design with straightforward operational rules.
  • The clinical team values transparent escalation and de-escalation decisions.
  • Real-time model fitting would create unnecessary operational complexity.
  • The trial has relatively standard discrete dose levels.
  • The sponsor wants a design that can be implemented with a clear decision table.
  • Strong safeguards against unsafe escalation are important.

When a Model-Based Design May Be Preferable

A model-based approach may be particularly attractive when:

  • The dose-toxicity relationship is expected to contain useful information across neighboring dose levels.
  • The sponsor has strong statistical programming and Bayesian modeling capabilities.
  • Time-to-event information should be incorporated during escalation.
  • Complex overdose-control rules are required.
  • The trial requires substantial adaptation to accumulating evidence.
  • Extensive simulation and model diagnostics are feasible.

Protocol Considerations

Regardless of the design family, the protocol should define the dose-finding procedure before enrollment begins.

At minimum, specify:

  • Starting dose
  • Candidate dose levels
  • Cohort size
  • Target toxicity probability
  • DLT definition
  • DLT observation window
  • Escalation rule
  • De-escalation rule
  • Rules for staying at a dose
  • Dose-skipping restrictions
  • Overdose-control criteria
  • Maximum administered dose
  • Stopping rules
  • Rules for pending DLT assessments
  • Rules for unevaluable patients
  • Final dose-selection rule
Do not improvise the dose-escalation algorithm. Changing escalation, de-escalation, or stopping rules after seeing the data can materially change the operating characteristics that were evaluated during design development.

Statistical Analysis Plan Considerations

The statistical documentation should make the dose-finding procedure reproducible.

For a model-assisted design, document:

  • Target toxicity probability
  • Exact decision boundaries
  • Decision table or algorithm
  • Cohort rules
  • Safety restrictions
  • Final dose-selection procedure

For a model-based design, additionally document:

  • Model form
  • Dose transformation
  • Prior distributions, if Bayesian
  • Parameter constraints
  • Posterior updating method
  • Dose-selection criterion
  • Overdose-control criterion
  • Restrictions on escalation and dose skipping
  • Handling of pending outcomes
  • Final posterior or model-based dose-selection rule

Practical Workflow for Choosing Between the Two

1
Define the clinical target toxicity probability.
2
Define the dose levels and starting dose using clinical and pharmacologic evidence.
3
Specify DLT definitions and the assessment window.
4
Decide whether an interval-based model-assisted procedure or an explicitly fitted model-based procedure better matches the trial objectives.
5
Specify escalation, de-escalation, stay, overdose-control, and stopping rules.
6
Simulate the complete design across clinically plausible dose-toxicity scenarios.
7
Evaluate target-dose selection, overdose exposure, underdose selection, sample size, and trial duration.
8
Perform sensitivity analyses for alternative toxicity scenarios and, for model-based designs, alternative model assumptions and priors.
9
Freeze the design and document the operational algorithm before enrollment.

R Implementation: A Simple Model-Assisted Decision Rule

The following example illustrates the logic of an interval-style model-assisted rule. It is intentionally generic; actual BOIN, Keyboard, or mTPI boundaries should be generated using the corresponding design methodology.

target <- 0.30
lower  <- 0.20
upper  <- 0.40

decision <- function(dlt, n) {
  p_hat <- dlt / n

  if (p_hat < lower) {
    "Escalate"
  } else if (p_hat > upper) {
    "De-escalate"
  } else {
    "Stay"
  }
}

decision(dlt = 0, n = 3)
decision(dlt = 1, n = 3)
decision(dlt = 2, n = 3)

The output illustrates the structure of an interval rule:

# 0/3  -> Escalate
# 1/3  -> Stay
# 2/3  -> De-escalate
Teaching example only: The numerical boundaries above are illustrative and are not presented as the calibrated boundaries for a specific published design.

R Implementation: A Generic Model-Based Framework

A simple Bayesian model-based workflow can be represented conceptually as:

# Candidate doses
dose <- c(10, 20, 30, 40, 50)

# Observed DLT data
n_dose   <- c(3, 3, 3, 3, 3)
dlt_dose <- c(0, 0, 1, 1, 2)

# Fit a prespecified dose-toxicity model
# and obtain estimated toxicity probabilities
#
# p_hat <- fitted_model(dose, n_dose, dlt_dose)

# Select the admissible dose closest to target
target <- 0.30
#
# next_dose <- dose[
#   which.min(abs(p_hat - target))
# ]

In an actual CRM implementation, the model-fitting and dose-selection functions would be defined explicitly, along with prior distributions, safety constraints, and rules for pending data.

Comparing Designs Through Simulation

A simple simulation framework repeatedly generates DLT outcomes under a specified true toxicity vector and applies the entire dose-finding algorithm.

true_p <- c(0.05, 0.10, 0.20, 0.30, 0.50)

simulate_trial <- function(true_p, nsim = 10000) {
  # Initialize counters
  selected <- integer(length(true_p))

  # Apply the complete prespecified
  # dose-finding algorithm in each simulation.
  #
  # The actual implementation depends
  # on the selected design.

  selected
}

The purpose of the simulation is not to prove that one design is universally better. It is to determine how each candidate design behaves under the specific scenarios relevant to the clinical program.

What a Good Simulation Report Should Show

Metric Question Answered
Target selection probability How often is the correct dose selected?
Overdose selection probability How often is an excessively toxic dose selected?
Underdose selection probability How often is a dose below the target selected?
Average patients per dose Where are patients being exposed?
Average total sample size How large is the typical trial?
Maximum sample size What is the enrollment ceiling?
Stopping probability How often does the trial terminate early?
Trial duration How long is the dose-finding process expected to take?

Final Dose Selection Is Different From Next-Dose Selection

A subtle but important point is that the dose given to the next cohort is not necessarily the dose ultimately recommended for later development.

During escalation, the design repeatedly asks:

$$ \text{Which dose should be administered next?} $$

At the end, the study asks:

$$ \text{Which dose should be selected as the recommended dose?} $$

The final selection may incorporate all accumulated information and may use a different rule from the operational next-dose decision.

Do not conflate dose escalation with final dose selection. A design can use one rule to protect patients during escalation and another statistical rule to identify the dose recommended for subsequent development.

Relationship to the MTD Concept

Historically, Phase I oncology studies often focused on the maximum tolerated dose, or MTD.

Modern dose-finding programs increasingly recognize that the biologically and clinically appropriate dose may not be the highest tolerable dose. Exposure-response, pharmacodynamics, efficacy, safety, and the overall benefit-risk profile may all contribute to dose selection.

Consequently, a design may target a toxicity probability while the final clinical dose recommendation incorporates additional information.

$$ \text{Dose selection} \neq \text{toxicity probability alone} $$

This distinction becomes particularly important for targeted therapies, immunotherapies, molecularly driven treatments, and drugs with delayed or cumulative toxicity.

Common Mistakes

  1. Calling every rule-based design model-assisted. The traditional 3+3 design is generally classified as rule-based rather than model-assisted.
  2. Assuming model-assisted means model-free. Model-assisted designs are statistically derived; they simply operationalize the statistical information through prespecified rules.
  3. Assuming model-based designs are automatically superior. Model-based efficiency depends on appropriate model specification and careful implementation.
  4. Ignoring overdose control. Selecting the dose closest to the target without a safety constraint can expose patients to unacceptable toxicity.
  5. Ignoring pending DLT information. A design must prespecify how incomplete follow-up affects dose decisions.
  6. Failing to simulate the design. Small-cohort dose finding is highly variable, so analytical intuition alone is not sufficient.
  7. Changing the algorithm after observing data. Unplanned changes can invalidate the original operating-characteristic evaluation.
  8. Assuming the observed DLT rate equals the true toxicity probability. Small cohorts produce highly uncertain observed rates.
  9. Using the same design for every program. The appropriate method depends on the drug, dose range, toxicity timing, clinical objective, and operational environment.
  10. Assuming the MTD is necessarily the recommended Phase II dose. The final dose recommendation may require pharmacokinetic, pharmacodynamic, efficacy, and broader safety information.

Model-Assisted vs. Model-Based: Decision Framework

Question If Yes, Consider
Do we want a transparent decision table? Model-assisted
Do we want direct real-time estimation of the dose-toxicity curve? Model-based
Do we need time-to-event modeling? Model-based approaches such as TITE-CRM
Do we want a relatively simple operational workflow? Model-assisted
Do we have strong Bayesian modeling and simulation infrastructure? Model-based may be attractive
Is model misspecification a major concern? Consider robust model-assisted alternatives and extensive sensitivity analysis
Is explicit borrowing across dose levels important? Model-based

The Most Important Concept

The most important distinction is not whether a design uses mathematics. Both model-assisted and model-based designs are statistical methods.

The key question is: does the trial directly fit and update a dose-toxicity model to make the dose decision, or does it use a prespecified statistically calibrated decision rule?

$$ \boxed{ \begin{array}{c} \text{Model-assisted}\\ \text{statistical model} \rightarrow \text{prespecified decision rule} \end{array} } $$
$$ \boxed{ \begin{array}{c} \text{Model-based}\\ \text{patient data} \rightarrow \text{fit/update dose-toxicity model} \rightarrow \text{dose decision} \end{array} } $$

Model-assisted designs such as BOIN, Keyboard, and mTPI-type methods provide a statistically principled middle ground between simple algorithmic escalation and fully model-based dose finding. Model-based methods such as CRM explicitly estimate the dose-toxicity relationship and can use information across dose levels more directly.

Bottom line: Model-assisted designs use statistically calibrated rules to make dose decisions without necessarily fitting a dose-toxicity model in real time. Model-based designs explicitly fit and update a dose-toxicity model as data accumulate. Model-assisted methods generally offer greater operational simplicity and transparency, whereas model-based methods can provide more direct use of the dose-toxicity relationship and greater modeling flexibility. Neither class is universally superior: the appropriate choice should be determined by the clinical objective, toxicity timing, safety requirements, operational capabilities, and simulated operating characteristics of the specific trial.

References

O'Quigley, J., Pepe, M. & Fisher, L. (1990). Continual reassessment method: a practical design for phase 1 clinical trials in cancer. Biometrics, 46, 33–48.
Ji, Y. & Wang, S.J. (2013). Modified toxicity probability interval design: a safer and more reliable method than the 3+3 design for dose-finding studies. Clinical Trials, 10, 567–576.
Liu, S. & Yuan, Y. (2015). Bayesian optimal interval designs for phase I clinical trials. Journal of the Royal Statistical Society: Series C, 64, 507–523.
Neuenschwander, B., Branson, M. & Gsponer, T. (2008). Critical aspects of the Bayesian approach to phase I cancer trials. Statistics in Medicine, 27, 2420–2439.
Cheung, Y.K. (2011). Dose Finding by the Continual Reassessment Method. Chapman & Hall/CRC.
Rogatko, A., Schoenfeld, D., Tighiouart, M., et al. (2007). Translation of innovative designs into phase I trials. Journal of Clinical Oncology, 25, 4982–4986.
Jiménez, J.L., Tighiouart, M. & Cook-Walden, R. (2018). Keyboard design for phase I clinical trials. Clinical Cancer Research, 24, 5588–5596.
Ji, Y., Liu, P., Li, Y. & Bekele, B.N. (2010). A modified toxicity probability interval method for dose-finding trials. Clinical Trials, 7, 653–663.