Tutorials › Optimal Design and Model-Informed Dosing › Response-Guided Titration With Delayed Measurements

Dose Regimens and Titration Algorithms · Tutorial 263 of 497

Response-Guided Titration With Delayed Measurements

Build a titration rule that accounts for measurement and response delays by linking every observation to the regimen history that produced it.

Advanced 12 min read

What You'll Learn

  • Distinguish the time a response is measured from the time its result becomes available.
  • Track the dose version and relevant regimen history for every observation.
  • Formulate a delayed-response update rule with explicit timing and action conditions.
  • Use a conditional mean-zero assumption when interpreting response-model residuals.
  • Identify stale results, overlapping effects, and other threats to valid titration decisions.
  • Compare immediate, wait-for-result, and history-aware approaches to delayed measurements.

Why the Measurement Time Matters

A titration rule can be mathematically clear and still make the wrong decision if it treats a newly received result as a measurement of the current dose. A laboratory value, symptom score, or other clinical response may be collected days before it is reported. In addition, the response itself may take time to reflect a dose change. These are distinct delays: reporting delay is the time from collection to availability, while response delay is the time required for the measured outcome to reflect a changed regimen.

The central design task is therefore not just to specify how a response changes the dose. It is to specify which regimen history the response represents, when the response is collected, when it becomes available, and whether it is still appropriate to use for a dose decision. This builds on state-update rules and bounded titration: the update must operate on the correct state and must respect the allowed dose range.

Definition: A dose version is a uniquely identified regimen in effect over a defined time interval, such as dose 6 mg once daily from day 0 through day 6. An observation record should identify at least its collection time, result-availability time, response value and units, and the dose version or regimen history in effect during the period relevant to that response. A delayed observation is stale for a direct update when the regimen that generated it is no longer the regimen on which the proposed update rule is based.

Representing Delayed Measurements in the Algorithm

Let \(D_k\) denote the dose chosen at decision occasion \(k\), and let \(Y_j\) denote a response collected at occasion \(j\). Let \(a(j)\) be the occasion at which the result of \(Y_j\) becomes available. In general, \(a(j)>j\). The result must retain its collection label \(j\), even when it arrives at occasion \(a(j)\). The dose in effect when the result arrives is not automatically the dose that generated the response.

A useful record can be written as \((j,a(j),Y_j,v_j,H_j)\), where \(v_j\) identifies the regimen version associated with the observation and \(H_j\) records the relevant dose history. If response depends on cumulative exposure, dose timing, or more than one previous dose, \(H_j\) must describe that history; a single dose label is not enough. A single-version label is appropriate only when the clinical and pharmacologic assumptions make the response attributable to that version—for example, the dose was held long enough for the selected response metric to represent that regimen.

The rule also needs an explicit policy for pending or stale results. A conservative policy is to allow a simple response-threshold update only when the result is available, its source regimen is still the current regimen, and the response has had the required time to reflect that regimen. Stale results can still inform a model or clinical review, but they should not be substituted into a direct current-dose rule without accounting for the intervening regimen history.

$$ D_{k+1} = \begin{cases} \operatorname{clip}\{g(D_k,Y_j),D_{\min},D_{\max}\}, & \text{if }Y_j\text{ is available and eligible at }k,\\ D_k, & \text{otherwise.} \end{cases} $$

Here \(g\) is the chosen update rule, and \(\operatorname{clip}\) restricts a proposed dose to the interval from \(D_{\min}\) to \(D_{\max}\). Eligibility is part of the algorithm, not an informal judgement added after the calculation. It can require a matching dose version, a minimum time on that regimen, and no unresolved change that makes the response history ambiguous. In a clinical application, safety rules and monitoring plans also need to be specified; the equation alone is not a treatment recommendation.

A Model-Based Justification

Consider a simple response model for a setting where the response is measured after the regimen has been held long enough to represent a single dose version:

$$ Y_j=\alpha+\beta D_{v_j}+\varepsilon_j. $$

Here \(\alpha\) is an intercept, \(\beta\) is the response change per unit of dose, and \(\varepsilon_j\) is unexplained variation. To interpret the fitted mean response for a particular dose history, the needed assumption is not merely that the errors average to zero over all observations. The relevant condition is conditional mean zero given the information that determined the dose and describes the response history.

$$ E(\varepsilon_j\mid H_j,D_{v_j})=0 \quad\Longrightarrow\quad E(Y_j\mid H_j,D_{v_j})=\alpha+\beta D_{v_j}. $$

The implication follows by taking conditional expectations of both sides of the response model. The dose and intercept are known conditional on the stated information, so \(E(Y_j\mid H_j,D_{v_j})=\alpha+\beta D_{v_j}+E(\varepsilon_j\mid H_j,D_{v_j})\), which reduces to the displayed mean under the conditional assumption. An unconditional statement \(E(\varepsilon_j)=0\) is insufficient: errors could have mean zero overall yet have systematically different means for different dose histories. In adaptive titration, this distinction matters because past responses may determine later doses.

This linear model is a simplifying example, not a universal response model. If the response depends on prior doses, time since dose change, or other covariates, those predictors belong in the model or in \(H_j\). The dose label then identifies a regimen history rather than claiming that one isolated dose caused the entire observed response. Even with a correctly specified model, delayed results do not automatically establish a causal dose effect; interpretation also depends on the design, covariates, and assumptions about unmeasured influences.

Building a Delayed-Response Rule

1
Define the response and timing.
Specify the response metric, its units, when it is collected, and the expected response delay after a regimen change.
2
Version each regimen.
Assign a new version whenever the dose or schedule changes. Store the start and end times and the relevant history for each version.
3
Record and queue observations.
For every result, preserve collection time and source regimen history separately from the date it is reported. A result arriving later must not be relabelled as current.
4
Apply eligibility before updating.
Check availability, source regimen, sufficient response time, and any safety or data-quality requirements. State what happens to ineligible results.
5
Update and log the decision.
Apply the specified rule to an eligible result, enforce dose bounds, and record the result used, source version, old dose, new dose, and decision time.

Worked Examples

Worked Example: One-Occasion Reporting Delay

Suppose a hypothetical response is measured in response units, with a desired range of 8 to 10 units. The rule increases the dose by 2 mg if an eligible response is below 8, decreases it by 2 mg if the response is above 10, and otherwise holds it. Doses are bounded between 4 and 12 mg. The reporting delay is one weekly occasion, and the dose is held until a result is available.

At week 0 the dose is 6 mg (version V1). A response of 7.2 units is collected at the week 1 visit while V1 is still in effect. It is not reported until week 2. The record is therefore collection week 1, availability week 2, value 7.2 units, source V1—not “response on 6 mg at week 2” by virtue of the report date.

At week 2 the result is available, V1 remains current, and the hypothetical rule regards the response timing as adequate. Since \(7.2<8\), the proposed dose is \(6+2=8\) mg. Clipping gives \(\min(12,\max(4,8))=8\) mg, so the next regimen is 8 mg (V2). The arithmetic is valid because the result is linked to V1 and no intervening dose change occurred. If V1 had been replaced before the result arrived, this simple direct update would fail its eligibility check.

Worked Example: A Stale Result in the Queue

Use the same hypothetical bounds, 4–12 mg, and target range, 8–10 response units. A response is collected weekly but takes two weeks to be reported. At week 0, V1 is 6 mg. At week 1, a response of 7.0 units is collected under V1. At week 2, before that result is available, a different eligible result leads to a change to 8 mg (V2). The week 1 result arrives at week 3.

At week 3 the current dose is 8 mg, but the arriving 7.0-unit result was collected under V1, 6 mg. If the simple threshold rule is applied mechanically, it proposes \(8+2=10\) mg because 7.0 is below 8. That is an update from the current dose using a response from a different regimen; the rule has no justification for treating that old response as the response to 8 mg.

Under the conservative eligibility policy, the version check fails: source V1 is not current V2. The result is logged as stale for direct threshold adjustment, and the dose remains 8 mg pending an eligible assessment or an explicitly history-aware analysis. The proposed 10 mg is not applied. The arithmetic itself is simple; the decisive issue is that the response and dose used in the update do not correspond.

Worked Example: Using the Source Dose in a Response Model

For illustration, suppose a hypothetical steady-regimen model is \(E(Y\mid D)=2+0.8D\), where \(Y\) is measured in response units and \(D\) in mg. Assume the regimen was held long enough for this model to apply, and a result of 8.4 units is collected under 8 mg. It arrives after the current regimen has already changed to 10 mg.

The model predicts \(2+0.8(8)=8.4\) response units for the source dose, so the observed residual is \(8.4-8.4=0\) units. If the target is 10 units and the model is used to find its corresponding dose, solve \(10=2+0.8D\): \(D=(10-2)/0.8=10\) mg. The result is consistent with a target dose of 10 mg under this hypothetical model.

A tempting but incorrect calculation is to treat the observed 8.4 as the response to the current 10 mg and add the response gap divided by the slope: \(10+(10-8.4)/0.8=12\) mg. That reasoning attaches the old observation to the wrong dose version. The model-based target calculation uses the source-dose relationship, while any decision to alter the current 10 mg still requires an explicit policy about delayed observations, model validity, and eligibility. The example does not authorize an update merely because a delayed result is numerically available.

Diagnostics, Alternatives, and Limitations

The most useful diagnostic is an audit trail that makes the timeline reconstructable: dose-version start and stop times, collection and report times, response value and units, relevant prior doses, decision time, and the result that triggered each update. A table or software log should make it possible to answer, for every change, “Which observation was used, and under which regimen history was it collected?” Missing or contradictory version labels are a design failure, not a minor clerical inconvenience.

Other warning signs include repeated updates from the same result, a dose change made before the expected response delay has elapsed, results arriving out of order, and a long queue of pending observations. Check that a result is used once unless the algorithm explicitly permits repeated use, and define what happens when a result is missing, invalid, or late. If responses reflect overlapping regimens, a single source-dose label is inadequate; retain the full history or wait for an assessment under a sufficiently stable regimen.

There are three broad approaches. A wait-for-result rule holds the regimen until an eligible response arrives; it is straightforward to interpret but can delay adjustment. A history-aware model uses the dose history and response timing to interpret delayed outcomes; it may use information more efficiently but relies on a suitable model and assumptions. An unqualified latest-result rule updates from whatever value most recently arrived; it is simple but can confuse old responses with current effects and should not be used without a justification that makes the result current-relevant.

No single delay policy is appropriate for every response or drug. The result may reflect a gradual transition rather than one dose version, and measurement error, adherence, changes in clinical status, or missing assessments can complicate attribution. A model can also be wrong or poorly identified when dose histories and response delays are highly correlated. The algorithm should therefore state its assumptions and define review or fallback actions for cases in which its provenance checks fail. Selecting sparse sampling schedules and concentration targets are separate design questions; here the emphasis is on correct timing and attribution for response-guided updates.

Common Mistake

Common mistake: “This is the latest result, so it describes the current dose.” That conclusion confuses report time with collection time. The correction is to retrieve the observation’s collection time and source regimen history, then apply the rule only if the result is eligible for that decision. Likewise, an overall mean-zero error assumption does not establish a mean-zero error conditional on dose history; conditional interpretation requires an explicit condition such as \(E(\varepsilon_j\mid H_j,D_{v_j})=0\).
Key takeaway: A delayed response must travel through the titration algorithm with its provenance intact. Define collection and availability times separately, record the regimen history that can explain the response, and make eligibility an explicit part of the update rule.

Check Your Understanding

Answer each question, then compare with the solutions.

  1. A result is collected under 5 mg on day 4 and reported on day 9, after the dose changed to 7 mg on day 7. Which dose version should label the result, and why?
  2. Why does \(E(\varepsilon)=0\) alone not establish \(E(Y\mid D)=\alpha+\beta D\) in the linear response model?
  3. A rule proposes 9 mg from a current dose of 7 mg after a response below target. The response was collected under a different dose version. What should a conservative direct-update policy do?
  4. Give two pieces of information, beyond the response value, that should be retained for every delayed observation.

Solutions. (1) Label it with the version in effect on day 4, the 5 mg version, because the collection time—not report time—determines its source regimen. (2) An unconditional mean-zero error can still have a nonzero conditional mean for a particular dose history; the model’s conditional mean requires \(E(\varepsilon\mid H,D)=0\) or an adequate alternative assumption. (3) Fail the source-version eligibility check and do not apply the simple direct update; retain the result for an appropriate history-aware analysis or review. (4) Examples include collection time, report-availability time, source dose version, and relevant preceding dose history; any two of these answer the question.

Clinical Biostats