Tutorials › Physiologically-Based Pharmacokinetics (PBPK) › Context-of-Use Statements for PBPK Decision Claims

Model Qualification and Credibility Assessment · Tutorial 772 of 799

Context-of-Use Statements for PBPK Decision Claims

Build a clear, decision-linked PBPK context-of-use statement and identify the conditions that limit what it claims.

Intermediate 11 min read

What You'll Learn

  • Distinguish a context-of-use statement from a model description or a claim that the model is credible.
  • Specify the drug, population, regimen, prediction target, decision, and conditions of use.
  • Link a prediction to an explicit decision without claiming the model proves the decision is correct.
  • Narrow an overbroad statement by making its population and operating conditions explicit.
  • Check whether a statement leaves out inputs that could change the prediction or its intended interpretation.
  • Recognize when a proposed use extends beyond the stated context.

Why a PBPK Decision Claim Needs a Defined Context

A PBPK model can be used to answer different questions about the same drug. It might predict exposure after a dose change, compare exposure across populations, or estimate the effect of a food condition. A statement such as “the model predicts exposure” does not tell a reviewer which use is intended, what prediction is being made, or what decision the prediction is meant to inform. Without those details, the claim is difficult to interpret and easy to apply beyond its intended scope.

A context of use (COU) describes the specific purpose and boundaries of a model application. It is not a general description of the model’s structure, and it is not evidence that the model performs adequately for that application. The introductory material on predictive intervals explains ways to summarize uncertainty in predictions; here the central task is to specify which prediction and decision the analysis is intended to address.

Definition: A PBPK context-of-use statement specifies the drug, population, regimen, prediction target, decision to be informed, and conditions under which the model is intended to be used. Its scope is the particular application described; it does not, by itself, establish model credibility or support use outside that scope.

A useful statement is specific enough that another analyst can tell what is included and what is not. The six elements are connected: the regimen and population define the scenario; the prediction target identifies the model output; the decision explains why that output matters; and the conditions state which assumptions, co-medications, formulations, and other circumstances bound the use.

Six Elements to Make Explicit

  • Drug: Name the drug and, when relevant to the application, its formulation, route, or salt form. If a decision concerns a particular formulation, a statement about the active ingredient alone may be too broad.
  • Population: Describe the population relevant to the question, such as adults with normal renal function or children in a specified age and weight range. Avoid terms such as “patients” when the group can be defined more precisely.
  • Regimen: State the dose, route, frequency, duration or treatment state, and any comparator regimen needed to interpret the prediction. Distinguish a single dose from steady-state dosing.
  • Prediction target: Name the quantity and its relevant time window or comparison. Examples include AUC over a dosing interval, maximum concentration after a dose, or an exposure ratio between two conditions.
  • Decision: State the action or decision the prediction is intended to inform. “Support dose selection” is more informative than “support development,” but a specific choice among doses or a dosing instruction is clearer still.
  • Conditions: State important operating conditions and exclusions, such as fed or fasted state, organ-function range, concomitant medications, formulation, or whether the decision is limited to a specified interaction scenario.

The statement need not list every parameter or implementation detail in the model. Those belong in the model description and analysis documentation. It should, however, identify conditions that could change the meaning of the prediction or cause the intended decision to differ.

From an Output to a Bounded Decision Claim

The need for these elements follows from the structure of a decision. A decision rule uses a prediction of some target under a defined scenario. If the target or scenario changes, the same numerical output may no longer answer the same question. Likewise, a prediction without an intended decision says what the model calculates but not what the calculation is meant to support.

$$ \text{scenario} \longrightarrow \text{prediction target} \longrightarrow \text{decision} $$

For example, suppose a decision is based on whether an exposure ratio exceeds a prespecified threshold. The scenario must identify which two conditions are compared; the target must identify which exposure measure is used; and the decision statement must name the threshold-based action. If any of those are absent, the claim is underdefined. This is a logical reason to state the full COU, not a demonstration that a particular model prediction is reliable.

1
Write the decision first.
State what choice the model application is intended to inform, not merely that it will “predict PK.”
2
Name the required prediction.
Specify the exposure measure, time window, and comparison needed for that decision.
3
Define the scenario.
Add drug and formulation, population, regimen, and the conditions under which the prediction is intended to apply.
4
Check the boundary.
Ask whether a reader could mistake the statement for a claim about another dose, population, formulation, or decision. If so, make the limitation explicit.

A practical template is: “For [drug and formulation] in [population], under [regimen and conditions], the PBPK model is intended to predict [target] to inform [decision]. This use is limited to [important boundaries or exclusions].” A concise sentence can be sufficient if it includes the information needed to identify the application.

Worked Example: Exposure Change With a Concomitant Drug

Hypothetical scenario. A model application concerns oral Drug A, given as 100 mg once daily at steady state to adults with normal hepatic and renal function. The decision is whether to consider a dose-adjustment strategy when Drug A is used with a specified strong enzyme inhibitor. The prediction target is the ratio of AUC over 24 hours with the inhibitor to AUC over 24 hours without it. A hypothetical simulation gives an AUC of 1,200 ng·h/mL with the inhibitor and 600 ng·h/mL without it.

The ratio is calculated as:

$$ \text{AUC ratio} = \frac{1{,}200\ \text{ng}\cdot\text{h/mL}} {600\ \text{ng}\cdot\text{h/mL}} = 2.00 $$

The units cancel, so the result is a dimensionless ratio. For this hypothetical decision framework, suppose a ratio greater than 2.00 triggers consideration of a dose-adjustment strategy. Since 2.00 is not greater than 2.00, this particular point prediction does not cross the stated trigger. That arithmetic alone is not evidence that the model is adequate, nor does it establish that no adjustment is clinically appropriate.

COU statement: “For oral Drug A at 100 mg once daily at steady state in adults with normal hepatic and renal function, the PBPK model is intended to predict the ratio of AUC over 24 hours with versus without the specified strong enzyme inhibitor to inform whether a dose-adjustment strategy should be considered when the ratio exceeds 2.00. This use is limited to the stated formulation, regimen, population, and inhibitor scenario.”

The statement names the comparator conditions, target, decision, and threshold as well as the population and regimen. It does not claim the model can evaluate every inhibitor, dose, or patient group. The threshold is part of this hypothetical decision framework, not a universal rule.

Making Boundaries Concrete

Boundaries are most useful when they rule in or rule out specific conditions. “In adults” may still be too broad if the intended use excludes organ impairment or interacting medications. “At the proposed dose” is ambiguous if the dose, route, and dosing interval are not given. A list of limitations should not replace the COU itself: the reader first needs to know the intended application, then the important restrictions on that application.

Worked Example: Defining a Pediatric Dose-Selection Use

Hypothetical scenario. A model is intended to compare two oral regimens of Drug B in adolescents aged 12 to 17 years who weigh 40 to 70 kg and have normal renal function. The regimens are 10 mg/kg every 24 hours and 15 mg/kg every 24 hours. The prediction target is AUC over the 24-hour dosing interval at steady state, and the decision is which regimen to take forward for evaluation in this defined group.

For a 50 kg adolescent, the daily doses implied by the two regimens are:

$$ 10\ \text{mg/kg}\times 50\ \text{kg}=500\ \text{mg per 24 hours} $$
$$ 15\ \text{mg/kg}\times 50\ \text{kg}=750\ \text{mg per 24 hours} $$

For the stated weight range, the first regimen corresponds to 400 to 700 mg every 24 hours, and the second to 600 to 1,050 mg every 24 hours. For example, \(10\ \text{mg/kg}\times40\ \text{kg}=400\ \text{mg}\), while \(15\ \text{mg/kg}\times70\ \text{kg}=1{,}050\ \text{mg}\). These arithmetic checks make the regimen concrete; they do not supply a clinical recommendation.

COU statement: “For oral Drug B in adolescents aged 12 to 17 years weighing 40 to 70 kg with normal renal function, the PBPK model is intended to compare steady-state AUC over 24 hours for 10 mg/kg and 15 mg/kg given every 24 hours to inform which regimen should be taken forward for evaluation in this population. This use does not cover children under 12 years, patients outside the stated weight range, renal impairment, or other routes or dosing intervals.”

The population and exclusions prevent the statement from silently extending to younger children or renal impairment. The decision is “which regimen to take forward for evaluation,” not “which regimen is proven safe or effective.” That distinction keeps the decision claim aligned with what the stated model application is intended to inform.

Comparison, Diagnostics, and Common Pitfalls

A COU is related to, but different from, several other kinds of statements. A model description explains the model’s structure, components, and inputs. An analysis objective says what an analysis will investigate. A COU links a defined model application to a prediction and a decision, while stating its scope. A conclusion reports what the analysis found. Keeping these separate helps prevent a proposed use from being mistaken for a demonstrated result.

Statement typeMain question it answersExample
Model descriptionWhat is represented?“The model represents absorption, distribution, metabolism, and excretion for Drug A.”
Analysis objectiveWhat will be investigated?“The analysis will compare exposure with and without an inhibitor.”
Context of useWhich prediction is intended to inform which decision, for whom and under what conditions?“The model is intended to predict the AUC ratio for the specified regimen and population to inform whether dose adjustment should be considered.”
ConclusionWhat did this analysis find?“The simulated point estimate of the AUC ratio was 2.00.”

Several diagnostic questions expose an incomplete COU:

  • Could two readers choose different populations, doses, routes, or time windows from the wording?
  • Is the prediction target named precisely enough to distinguish AUC, maximum concentration, or another quantity?
  • Does the statement say what decision the prediction will inform, rather than only saying that the model will be used?
  • Are food state, organ function, co-medications, formulation, or other conditions left unstated despite being important to the proposed use?
  • Could a reader mistake a bounded application for a claim that the model works for all drugs, doses, or populations?

Common mistake: “The model predicts exposure in patients and supports dosing.” This wording may sound informative, but it does not specify which drug, patient group, regimen, exposure target, dosing decision, or conditions are meant. It also risks implying that model output alone establishes an appropriate dose.

Correction: State the drug and formulation, define the population and regimen, name the prediction target and decision, and list important conditions or exclusions. Use wording such as “intended to inform” rather than “establishes” when describing the role of the prediction. A clear COU is not a substitute for evaluating the model or the evidence supporting its use.

A COU also has limits. It cannot resolve uncertainty in the prediction, show that the model is fit for the use, or guarantee that the decision will be correct. Those questions require assessment of the model and evidence for the particular application. The statement’s value is narrower but essential: it makes clear what use is being assessed and prevents claims from being silently generalized to scenarios that were not specified.

Key takeaway: Write the COU as a bounded link from a defined drug, population, regimen, and set of conditions to a specific prediction target and decision. A well-written statement clarifies intended use; it does not certify the model or its prediction.

Check Your Understanding

For each question, identify the missing element or revise the wording. Solutions follow each question.

  1. “The model will predict Drug C exposure to support dose selection.” What important COU elements are missing?
  2. A model is intended to compare fed and fasted dosing of a fictional oral drug in adults. Name a suitable prediction target and write a one-sentence COU for a decision about whether a food instruction should be considered.
  3. Why is “the model is intended to predict AUC in adults” not enough to define a decision claim?
  4. A statement specifies a drug, adult population, and dose, but its intended use is to select a regimen for adolescents. What is the problem?

Solutions. (1) It omits the formulation or route where relevant, the population definition, exact regimen, exposure measure and time window, the particular dose-selection decision, and conditions or exclusions. (2) A suitable target is the ratio of AUC over a defined interval under fed versus fasted conditions. For example: “For oral Drug D in adults receiving 50 mg once daily, the PBPK model is intended to predict the fed-to-fasted ratio of AUC over 24 hours to inform whether a food instruction should be considered; this use is limited to the stated formulation, dose, population, and food conditions.” (3) AUC needs a time interval and scenario, and “predict AUC” does not say what decision the prediction is intended to inform. (4) The population in the stated scope does not match the population for the decision. The statement must define adolescents and their relevant characteristics, or the intended decision must be limited to the adult population.