The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

Time-to-Event Continual Reassessment Method

Kristian Brock

2023-03-11

This vignette concerns the Time to Event Continual Reassessment Method (TITE-CRM) dose-finding clinical trial design.

Cheung and Chappell (2000) introduced TITE-CRM as a variant of the regular CRM [OQuigley1990] that handles late-onset toxicities. Dose-finding trials tend to use a short toxicity window after the commencement of therapy, during which each patient is evaluated for the presence or absence of dose-limiting toxicity (DLT). This approach works well in treatments like chemotherapy where toxic reactions are expected to manifest relatively quickly. In contrast, one of the hallmarks of radiotherapy, for instance, is that related adverse reactions can manifest many months after the start of treatment. A similar phenomenon may arise with immunotherapies.

In adaptive dose-finding clinical trials, where doses are selected mid-trial in response to the outcomes experienced by patients evaluated hitherto, late-onset toxic events present a distinct methodological challenge. Naturally, the toxicity window will need to be long enough to give the trial a good chance of observing events of interest. If, however, we wait until each patient completes the evaluation window before using their outcome to forecast the best dose, the trial may take an infeasibly long time and ignore pertinent interim data.

TITE-CRM presents a solution by introducing the notion of a partial tolerance event. If a patient is half way through the evaluation window and has not yet experienced toxicity, we may say that they have experienced half a tolerance. This simple novelty allows partial information to be used in dose-recommendation decisions. If the patient goes on to complete the window with no toxic reaction, they will be regarded as having completely tolerated treatment, as is normally the case with CRM and other dose-finding algorithms. This notion of partial events is only applied to tolerances, however. If a patient experiences toxicity at any point during the evaluation window, they are immediately regarded as having experienced 100% of a DLT event.

To illustrate TITE-CRM mathematically, we start with the likelihood from the plain vanilla CRM. Let \(Y_i\) be a random variable taking values \(\{0, 1\}\) reflecting the absence and presence of DLT respectively in patient \(i\). A patient administered dose \(x_i\) has estimated probability of toxicity \(F(x_i, \theta)\), where \(\theta\) represents the set of model parameters. The likelihood component arising from patient \(i\) is

\[ F(x_i, \theta)^{Y_i} (1 - F(x_i, \theta))^{1-Y_i} \]

and the aggregate likelihood after the evaluation of \(J\) patients is

\[ L_J(\theta) = \prod_{i=1}^J \left\{ F(x_i, \theta) \right\}^{Y_i} \left\{ 1 - F(x_i, \theta) \right\}^{1-Y_i} \]

Cheung and Chappell (2000) observed that each patient may provide a weight, \(w_i\), reflecting the extend to which their outcome has been evaluated. The weighted likelihood is

\[ L_J(\theta) = \prod_{i=1}^J \left\{ w_i F(x_i, \theta) \right\}^{Y_i} \left\{ 1 - w_i F(x_i, \theta) \right\}^{1-Y_i} \]

TITE-CRM weights the outcomes according to the extend to which patients have completed the evaluation period. To illustrate the design, we reproduce the example given on p.124 of Cheung (2011). Four patients have been treated at dose-level 3 and all are part-way through the 126-day toxicity evaluation window.

The authors use the empiric model so that there is one parameter, \(\theta = \beta\), the dose-toxicity relation is \(F(x_i, \beta) = x_i^{exp(\beta)}\), and a \(N(0, \sigma_{\beta}^2)\) prior is specified on \(\beta\).

library(trialr)

fit <- stan_crm(skeleton = c(0.05, 0.12, 0.25, 0.40, 0.55), target = 0.25,
                doses_given = c(3, 3, 3, 3),
                tox = c(0, 0, 0, 0),
                weights = c(73, 66, 35, 28) / 126,
                model = 'empiric', beta_sd = sqrt(1.34), seed = 123)

fit
#>   Patient Dose Toxicity    Weight
#> 1       1    3        0 0.5793651
#> 2       2    3        0 0.5238095
#> 3       3    3        0 0.2777778
#> 4       4    3        0 0.2222222
#> 
#>   Dose Skeleton N Tox ProbTox MedianProbTox ProbMTD
#> 1    1     0.05 0   0  0.0749       0.00703  0.1315
#> 2    2     0.12 0   0  0.1171       0.02993  0.0993
#> 3    3     0.25 4   0  0.1886       0.10083  0.1507
#> 4    4     0.40 0   0  0.2779       0.21949  0.1752
#> 5    5     0.55 0   0  0.3845       0.37180  0.4432
#> 
#> The model targets a toxicity level of 0.25.
#> The dose with estimated toxicity probability closest to target is 4.
#> The dose most likely to be the MTD is 5.
#> Model entropy: 1.45

The first table gives a summary of the patient information. We see that each patient has received dose-level 3, none have yet experienced toxicity although all are only partly through the evaluation window. The second table summarises dose-level information. We see that dose-level 4 has estimated mean probability of toxicity closest to the target 25%, although dose-level 5 is the dose most frequently advocated by the dose-toxicity curves generated by MCMC. This exuberance should be tempered by the fact that we have not yet treated any patients at dose-level 4, although it is currently recommended for the next patient.

A TITE-CRM option is provided for each of the CRM variants implemented in trialr. It is enabled simply by specifying the weights parameter. The necessity to provide weights under TITE-CRM rather obscures the attraction of using the outcome string approach of describing patients’ doses and DLT outcomes demonstrated in the CRM vignette. Thus, we provide stan_crm the three vectors doses_given, tox and weights to convey the patient-level information.

The object returned by stan_crm is the same, regardless of whether weights are provided or not. Thus, all of the visualistion methods presented in the CRM visualistion vignette apply.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.