Tutorials › Model-Informed Drug Development (MIDD) › Building an Auditable Integrated Evidence Argument

Evidence Integration Across Models · Tutorial 72 of 596

Building an Auditable Integrated Evidence Argument

You will learn to make an integrated model prediction traceable from its source data and assumptions to its validation, uncertainty, and development claim.

Advanced 13 min read

What You'll Learn

  • Specify a development claim so its population, regimen, endpoint, and time horizon are explicit.
  • Trace source data and model outputs across evidence-chain handoffs.
  • Record assumptions and checks that affect transfer between models or scenarios.
  • Distinguish validation findings from evidence that a model is true.
  • Report uncertainty alongside a final prediction and identify what it excludes.
  • Recognize gaps and overstatements that make an integrated argument unauditable.

From a Model Chain to a Development Claim

An integrated prediction is useful only if a reviewer can see how it supports a particular development claim. A sequence of plausible model outputs is not, by itself, an argument: the data may not represent the target population, a transferred quantity may change meaning at a model handoff, or validation may concern a different endpoint. The central task is to make each link, assumption, and limitation inspectable.

For example, a claim might concern the probability of a specified clinical response under a proposed regimen in a defined population by a stated time. The evidence chain could use pharmacokinetic data to predict exposure, then an exposure-response model to predict response. The final estimate cannot be interpreted properly unless the source data, model conditions, transfer between models, and uncertainty are all visible.

Definition: An auditable integrated evidence argument is a traceable account that connects a precisely stated development claim to its source data, model assumptions, transferred quantities, validation findings, uncertainty, and final prediction. A reader should be able to identify what supports each link, what could invalidate it, and what the prediction does not establish.

An argument should begin with the claim, not with the available models. State the target population, intervention or regimen, endpoint, and time horizon. Then specify the quantity being predicted and, where relevant, the decision threshold. A claim such as “the regimen is effective” is too broad to audit: it does not say which population, outcome, or level of response is meant.

For each model in the chain, distinguish the data used to estimate or inform it from outputs passed to the next model. At a handoff, record the transferred quantity, its definition and units, the scenario to which it applies, and any transformation or assumption needed to use it downstream. A numerical value without those details is not a traceable transfer.

1
Write the claim.
Specify the target population, regimen, endpoint, time horizon, and predicted quantity.
2
Inventory the evidence.
Identify each source dataset, its relevant population and measurements, and the model informed by it.
3
Document each handoff.
Name the transferred quantity, units, scenario, transformation, and assumptions needed for the receiving model.
4
Report checks and uncertainty.
State what validation evaluated, what uncertainty is included, and what remains untested or omitted.
5
Return to the claim.
Give the final prediction in context and explain how its uncertainty and limitations affect the intended interpretation.

Make Every Handoff Explicit

A useful audit trail can be represented as a table with one row per link in the argument. The table is not a substitute for scientific reasoning; it is a way to expose where that reasoning occurs. “Model output” should not be used as a stand-in for an explanation of what a number represents.

Argument elementWhat to recordAudit question
ClaimPopulation, regimen, endpoint, time, predicted quantityCould two readers interpret the target differently?
Source dataMeasurements, population, study conditions, data roleDo these data inform the link being claimed?
Model and assumptionsModel purpose, key structural and transfer assumptionsWhat must be true for this output to be relevant?
HandoffTransferred quantity, units, scenario, transformationDoes the downstream input mean the same thing?
ValidationValidation data, comparison, findings, scopeWas the relevant prediction tested under comparable conditions?
Uncertainty and predictionIncluded uncertainty, omissions, final estimate or rangeDoes the reported uncertainty cover the important sources?

Validation findings should be attached to the link they evaluate. Agreement with external data can increase confidence in a prediction for conditions represented by those data, but does not establish that every model assumption is correct or that performance transfers to a new population, regimen, or endpoint. Earlier material on cross-model posterior predictive checks and external calibration provides tools for particular checks; the integrated argument must still state what was checked and how its result bears on the claim.

Worked Example: Defining a Traceable Claim

Hypothetical case. A development team wants to predict response by week 12 for adults with a specified disease receiving a proposed oral regimen. It has a pharmacokinetic model informed by concentration measurements and an exposure-response model informed by trial data. The proposed claim is that at least 45% of this target population will meet a prespecified response definition by week 12.

Make the claim specific. The population is adults with the specified disease; the intervention is the proposed oral regimen; the endpoint is the prespecified response definition; the time horizon is week 12; and the quantity is the response probability. The decision threshold is 0.45. This is more auditable than saying only that the regimen is expected to work.

Trace the proposed chain. The concentration data inform a pharmacokinetic model. That model predicts an exposure summary for the proposed regimen. The exposure-response model maps that summary to response probability. The transfer record must name the exposure summary and its units, confirm that it refers to the proposed regimen and target scenario, and state the assumption that the exposure-response relationship is applicable to the target population.

Identify what is not yet established. The description alone does not show that the models were validated for this population or that the prediction exceeds the decision threshold with adequate certainty. Those are evidence questions, not consequences of the chain’s structure. The argument must report the relevant validation results and uncertainty before concluding how strongly the claim is supported.

This example illustrates why specifying the claim first matters: it reveals exactly which transfers and validation conditions need to be justified. It does not turn a model-based prediction into a causal conclusion or a guarantee of a future trial result.

Quantify Uncertainty Without Hiding Its Scope

An integrated prediction can be uncertain because of the source data, estimated model parameters, model structure, the transfer between scenarios, or discrepancies between model predictions and observed outcomes. These sources need not be combined in one number in every analysis, but the report should say what the stated uncertainty includes and what it omits. The earlier material on uncertainty attribution addresses ways to investigate contributions from model components; here the emphasis is on making the final claim interpretable.

A simple calculation shows why uncertainty in an upstream transferred quantity can matter downstream. Suppose an exposure-response model has logit response probability \(\eta=\alpha+\beta A\), where \(A\) is exposure. If estimates of \(\alpha\), \(\beta\), and \(A\) are uncertain, a first-order approximation can propagate their variances to \(\eta\). Let \(g(\alpha,\beta,A)=\alpha+\beta A\). Its gradient is \((1,A,\beta)\). If the three quantities are independent, the first-order variance approximation is the sum of each input variance multiplied by the square of its corresponding gradient component. This follows by approximating small changes in \(g\) with its linear Taylor expansion.

$$ \operatorname{Var}(\eta)\approx \operatorname{Var}(\alpha)+A^2\operatorname{Var}(\beta)+\beta^2\operatorname{Var}(A) $$

Independence is a substantive assumption here, not a default truth. If inputs are correlated, covariance terms are also required. Further, this approximation reflects uncertainty in the stated quantities under the stated model; it does not automatically include structural model error, population-transfer error, or all forms of predictive variability.

Worked Example: Propagating Uncertainty Through an Exposure-Response Link

Hypothetical values. Suppose the model is \(\eta=\alpha+\beta A\), with \(\alpha=-2.00\), \(\beta=0.0250\) per \(\text{mg}\cdot\text{h}/\text{L}\), and predicted exposure \(A=80.0\ \text{mg}\cdot\text{h}/\text{L}\). Assume standard errors of 0.200 for \(\alpha\), 0.00300 for \(\beta\), and \(8.00\ \text{mg}\cdot\text{h}/\text{L}\) for \(A\). For this illustrative calculation, treat these inputs as independent.

The central logit is \(\eta=-2.00+(0.0250)(80.0)=0\). The corresponding response probability is \(p=1/(1+\exp(-\eta))=0.500\).

The approximate variance of the logit is \(\operatorname{Var}(\eta)\approx(0.200)^2+(80.0)^2(0.00300)^2+(0.0250)^2(8.00)^2\). The three contributions are \(0.0400\), \(0.0576\), and \(0.0400\), so the total is \(0.1376\), and \(SE(\eta)\approx\sqrt{0.1376}=0.371\).

The derivative of \(p=1/(1+\exp(-\eta))\) with respect to \(\eta\) is \(p(1-p)\). At \(p=0.500\), this derivative is \(0.250\), giving the approximate \(SE(p)=0.250(0.371)=0.0928\). A rough normal-approximation interval is \(0.500\pm1.96(0.0928)\), or approximately \(0.318\) to \(0.682\).

This interval is an illustration of first-order propagation, not a definitive predictive interval. It uses an independence assumption and does not include model discrepancy or other omitted variability. Although the central estimate is above the hypothetical 0.45 threshold, this calculation alone does not establish that the response probability is at least 0.45 with high confidence.

Validation, Failure Modes, and Alternatives

Diagnostics should be tied to the argument’s weak links. Useful warning signs include incompatible units at a handoff, a transferred quantity defined differently in the two models, target conditions outside the range of source data, systematic residual patterns, poor predictive checks, or a final uncertainty interval that omits a plausible source of variation. A check that succeeds for one endpoint or population is not evidence that an untested endpoint or population is also well represented.

Validation has a scope. Record the validation dataset, the prediction that was compared with it, the comparison method, and the result. If validation data were also used to estimate or tune the model, say so; the resulting comparison does not have the same evidential role as an independent external evaluation. When predictions disagree, do not conceal the disagreement by reporting only a preferred chain. Earlier material on adjudicating discordant predictions and weighting unequally reliable models can inform such an analysis, but the audit trail should still identify the alternatives and the basis for any choice.

An integrated chain is not the only possible way to support a claim. Separate model-specific reports may be easier to inspect but can leave the relationship between outputs and the final claim implicit. Competing evidence chains can make dependence on modeling choices visible, while model averaging can represent uncertainty across specified alternatives. These approaches answer different questions and require their own assumptions. None removes the need to define the claim, trace inputs, report validation scope, and explain uncertainty.

Worked Example: Interpreting an External Validation Result

Hypothetical validation data. A model predicts a 0.60 response probability for a group of 100 comparable participants. In an external validation sample of 100 participants, 54 meet the response definition. For a simple screening comparison, treat the predicted probability as fixed and assume independent Bernoulli outcomes with that probability.

The observed proportion is \(\hat{p}=54/100=0.540\). Under the stated prediction, the binomial standard error is \(SE=\sqrt{0.60(1-0.60)/100}=\sqrt{0.0024}=0.0490\). The standardized difference is \((0.540-0.600)/0.0490=-1.22\).

The observed proportion is 0.060 lower than the prediction, or about 1.22 standard errors below it under this simplified calculation. This result does not, by itself, show a serious predictive failure. Nor does it establish good calibration: the calculation ignores uncertainty in the model prediction and any clustering or other dependence among participants. An auditable report would identify those limitations and inspect performance across the relevant prediction range, rather than using this one comparison as a blanket endorsement.

The validation result is informative only for the prediction and population it evaluates. If the final development claim concerns a different regimen or population, the report must explain why this validation evidence is relevant to that transfer.

Common Pitfall: A Plausible Chain Is Not Yet an Argument

A frequent error is to list several model outputs, observe that each seems reasonable, and state that the final claim is therefore supported. That reasoning skips the handoffs: a downstream model may receive a quantity with different units or meaning, a source dataset may not represent the target scenario, and validation may not address the final prediction. Another error is to report a narrow uncertainty range without saying which model components or transfer assumptions it includes.

Correction: For every link, state the input and its source, the model assumption that makes the input relevant, the transferred quantity and its units, the validation evidence that bears on that link, and the uncertainty included in the final result. Then qualify the development claim according to the evidence actually available, including unresolved gaps.

The argument should also distinguish an estimate from a decision. A central prediction above a threshold does not imply that the threshold is met under all plausible assumptions. Conversely, a wide interval does not make the prediction useless; it can show which handoff, data source, or assumption most deserves further evaluation. The purpose of an audit trail is not to make uncertainty disappear but to make its implications reviewable.

Check Your Understanding

Answer each question, then compare your reasoning with the short solutions.

  1. A model predicts exposure for one regimen, but the response model uses exposure summaries from a different dosing schedule. Name two details that must be checked before transferring the prediction.
  2. A validation sample has 36 responses among 60 participants, while the model predicted 0.50. Calculate the observed proportion and describe the difference from prediction.
  3. In \(\eta=\alpha+\beta A\), explain why uncertainty in \(A\) can affect the response prediction even when \(\alpha\) and \(\beta\) are fixed.
  4. A report gives a final response probability but no target population, endpoint time, or validation scope. What makes the claim unauditable?

Solutions. (1) Check that the exposure summary has the same definition and units and that the regimen and scenario are appropriate for the response relationship; document any transformation and transfer assumption. (2) The observed proportion is \(36/60=0.600\), which is 0.100 above the predicted 0.500; this difference alone does not establish model failure without considering sampling and predictive uncertainty. (3) Since \(\eta\) changes by approximately \(\beta\) times a small change in \(A\), uncertainty in exposure changes the logit and therefore the response probability when \(\beta\ne0\). (4) A reader cannot determine which population and outcome the probability concerns or whether the validation evidence evaluates a relevant prediction, so its support for a development claim cannot be assessed.