Tutorials › Nonlinear Mixed-Effects Models (NLME) › Predictive Checks Across Multiple Endpoints

Visual and Numerical Predictive Checks · Tutorial 599 of 797

Predictive Checks Across Multiple Endpoints

Construct endpoint-specific predictive summaries, account for dependence among outcomes measured on the same subjects, and interpret apparent discrepancies in light of scale and multiplicity.

Intermediate 10 min read

What You'll Learn

  • Define observed and simulated summaries separately for each endpoint.
  • Match simulation design and data handling to the observed study.
  • Explain why outcomes from shared subjects cannot be treated as independent.
  • Compare predictive deviations on endpoint-specific scales.
  • Recognize how inspecting many endpoints can produce apparent anomalies.
  • Distinguish a useful multi-endpoint display from an unjustified pooled statistic.

Why Check Endpoints Separately?

A pharmacometric model may describe several outcomes measured on the same subjects, such as drug concentration and a continuous biomarker. A model can reproduce one outcome well and miss another; even when both are adequately reproduced, their numerical scales may be very different. A predictive check across endpoints must therefore do two things at once: assess each endpoint in a meaningful way and preserve the fact that outcomes from the same subject may be related.

The basic strategy is to make endpoint-specific predictive summaries. For each outcome, compare the observed data with replicate data generated under the fitted model, using summaries appropriate to that outcome and its sampling schedule. Interpret the resulting checks together, but do not combine raw values from different endpoints as if they had a common scale.

Definition: Let \(Y_{ikj}\) denote the observation for subject \(i\), endpoint \(k\), and observation occasion \(j\). A predictive check for endpoint \(k\) compares a chosen summary of its observed data with the same summary calculated from replicate data simulated under the model. The summaries may be stratified by time, dose, or another design feature, but the observed and simulated summaries must use the same definition and data-handling rules.

Constructing Endpoint-Specific Checks

For each endpoint, first decide what feature of the data the check is meant to assess. A continuous concentration endpoint might be summarized by medians and percentiles within time bins; a continuous biomarker might be summarized by its mean or by percentiles within clinically meaningful time windows. The statistic should reflect the question and the outcome’s distribution. The observed and simulated data must then be summarized in exactly the same way.

Suppose there are \(R\) simulated replicate data sets. For endpoint \(k\), let \(T_k^{obs}\) be the observed summary and \(T_{kr}\) the summary from replicate \(r\). The empirical predictive distribution of \(T_{kr}\) describes the range of summaries produced by the fitted model under the chosen simulation scheme. Comparing \(T_k^{obs}\) with this distribution makes the check interpretable in that endpoint’s own units.

The simulation scheme matters. Simulations should reproduce the study design relevant to the check, including doses, observation times, and the records included in each summary. If an endpoint has missing observations, the simulated data should be handled consistently with the observed data and the intended estimand. A comparison can be misleading if, for example, observed summaries use only available records while simulated summaries use a different pattern of records.

When several endpoints are measured on the same subjects, joint simulation is preferable: each replicate should generate all endpoints for the same simulated subjects, using the model’s shared subject effects and any modeled dependence between outcomes. Simulating each endpoint independently can preserve its marginal distribution while failing to reproduce cross-endpoint association. That failure matters when the question concerns the pattern of outcomes within subjects or a joint summary.

Worked Example: Comparing a Biomarker Summary With Its Predictive Distribution

Consider a hypothetical study with a continuous biomarker measured at a prespecified visit. The observed median is 9.1 units. Across 100 simulations, the median biomarker value has a mean of 8.4 units and a standard deviation of 0.35 units. Use a standardized predictive deviation to describe the observed median’s position.

For a simulated summary \(T\), define the standardized deviation as \(Z=(T^{obs}-\bar{T}^{sim})/s_T^{sim}\), where \(\bar{T}^{sim}\) and \(s_T^{sim}\) are the mean and standard deviation of the simulated summaries. Substituting the values gives

$$ Z=\frac{9.1-8.4}{0.35}=\frac{0.7}{0.35}=2.00. $$

Thus, the observed median is 2.00 simulated-summary standard deviations above the simulated mean. This is a diagnostic description, not by itself a formal hypothesis test or a probability that the model is wrong. The distribution of simulated medians should also be inspected: if it is strongly skewed, a standardized distance from the mean may be less informative than the observed median’s empirical rank or its position relative to predictive quantiles.

Shared Subjects and Cross-Endpoint Dependence

If two endpoints are measured on the same subject, their observations are generally not independent. They may share subject-specific effects, such as an individual’s underlying disease severity, or have correlated residual variation. A model may represent these links explicitly, or it may leave some dependence unmodeled. In either case, interpretation must distinguish a marginal check of each endpoint from a joint check of their relationship.

A separate endpoint-specific VPC or predictive summary can assess whether each endpoint’s marginal behavior is plausible. It does not, by itself, show that the model reproduces the association between endpoints. To examine that association, define a joint statistic—such as the within-subject covariance of appropriately scaled residuals—and calculate it for both the observed and jointly simulated data. The statistic and its interpretation must account for the pairing of outcomes by subject.

Worked Example: Why Paired Outcomes Cannot Be Counted as Independent

Suppose four hypothetical subjects have centered predictive residuals for endpoint A of \(1,-1,1,-1\) units and for endpoint B of \(2,-2,2,-2\) units. The residuals are paired by subject. Calculate their sample covariance and explain what the pairing shows.

Both residual means are zero. The sample covariance is the sum of paired products divided by \(n-1\):

$$ s_{AB}=\frac{1(2)+(-1)(-2)+1(2)+(-1)(-2)}{4-1} =\frac{8}{3}=2.667. $$

The sample standard deviations are \(s_A=\sqrt{4/3}=1.155\) units and \(s_B=\sqrt{16/3}=2.309\) units. Therefore the paired sample correlation is

$$ r_{AB}=\frac{s_{AB}}{s_As_B} =\frac{2.667}{(1.155)(2.309)}=1.00. $$

In this small hypothetical data set, the residuals move together perfectly: subjects above the predictive center on endpoint A are also above it on endpoint B. The eight residual values are not eight independent subject-level observations; there are four paired subjects. Treating all eight values as independent would discard the pairing and misrepresent the information available about cross-endpoint dependence. Four subjects are far too few for a stable correlation estimate, so this calculation illustrates the principle rather than establishing a reliable dependence pattern.

Different Scales and Meaningful Comparisons

Endpoints may have different units, ranges, and variability. A concentration in mg/L and a biomarker in units cannot sensibly be compared by subtracting their raw values or pooling them into one mean error. First compare each observed summary with its own endpoint’s predictive distribution. If a common display is useful, scale deviations relative to endpoint-specific predictive variation or show endpoint-specific predictive quantiles; explain clearly what the scale represents.

Standardization can help compare the relative extremeness of summaries, but it does not make unlike scientific outcomes interchangeable. A deviation of two predictive standard deviations for one endpoint does not necessarily have the same clinical importance as the same standardized deviation for another. Clinical relevance depends on the endpoint, its units, and the consequences of the discrepancy, not only on its position in a predictive distribution.

The reason standardization removes units is direct. If a summary \(T\) is transformed to \(T^*=a+bT\), with \(b>0\), then its predictive mean and standard deviation become \(a+b\bar T\) and \(bs_T\). Consequently,

$$ \frac{T^{*obs}-\bar T^{*sim}}{s_{T^*}^{sim}} = \frac{a+bT^{obs}-(a+b\bar T^{sim})}{bs_T^{sim}} = \frac{T^{obs}-\bar T^{sim}}{s_T^{sim}}. $$

The standardized deviation is unchanged by a positive change of units, such as converting a concentration from one unit to another. It remains a summary of relative predictive discrepancy, not a universal measure of clinical importance.

Worked Example: Keeping Endpoint Scales Distinct

In a hypothetical analysis, the observed median concentration is 2.4 mg/L, while the simulated medians have mean 2.0 mg/L and standard deviation 0.20 mg/L. For a continuous biomarker, the observed median is 50 units, while the simulated medians have mean 47 units and standard deviation 1.5 units. Calculate and compare standardized deviations.

For concentration, \(Z_C=(2.4-2.0)/0.20=2.00\). For the biomarker, \(Z_B=(50-47)/1.5=2.00\). Both observed medians are two simulated-summary standard deviations above their respective simulated means.

The raw differences are 0.4 mg/L and 3 biomarker units; they should not be pooled or compared as quantities of the same kind. The equal standardized deviations indicate equal relative distances under these two simulated-summary scales, but do not establish equal clinical importance or prove that either discrepancy is statistically significant. The empirical predictive distributions and the endpoints’ scientific meaning still need consideration.

Multiplicity: Many Checks, More Opportunities for an Anomaly

A multi-endpoint assessment often includes several endpoints, time windows, bins, and summaries. Even when a fitted model generates data consistent with the simulation assumptions, one of many inspected summaries may look unusually extreme by chance. This is a multiplicity issue: the more checks a reviewer scans, the greater the opportunity to notice at least one apparent anomaly.

For illustration, if four independent checks each had a 5% chance of crossing a prespecified warning threshold under the model, the probability that at least one crosses it would be

$$ 1-(1-0.05)^4=1-0.95^4=0.1855. $$

This calculation assumes independent checks and a threshold with a genuine 5% per-check false-alarm probability. Predictive plots are often dependent, and a visual flag is not automatically a formal test, so 18.55% is an illustration of the multiplicity principle—not a calibrated error rate for a particular set of plots.

A practical response is to specify key endpoints and summaries in advance, distinguish planned checks from exploratory ones, and look for coherent patterns rather than treating every isolated point as decisive. If a single overall assessment is needed, define a joint discrepancy statistic and evaluate that statistic using joint simulations. Do not simply pool raw endpoint values or apply a correction without considering the dependence structure and the purpose of the check.

Worked Example: Interpreting a Flag Among Several Endpoints

Suppose a hypothetical analysis examines four endpoint-specific summaries. One summary lies beyond its prespecified marginal predictive limits, while the other three are central. The endpoints are measured on shared subjects, so their checks may be dependent. What is a defensible interpretation?

The flagged summary is evidence of a possible local discrepancy worth investigating. It does not establish that the model fails overall: four summaries were inspected, the checks may be dependent, and a marginal predictive limit concerns one summary at a time. The 18.55% calculation above applies only to four independent checks with 5% false-alarm probability each, so it cannot be used as the exact probability of a flag here.

Next inspect the flagged endpoint’s data handling, time pattern, and predictive distribution, then assess whether nearby summaries or related endpoints show a coherent pattern. If the concern is a joint pattern across endpoints, calculate a prespecified joint statistic from the observed paired data and from replicate data simulated jointly. Report the marginal flag and its exploratory context rather than presenting it as a definitive test.

Diagnostics, Alternatives, and Limitations

A multi-endpoint check is difficult to interpret when the simulation design or summary definitions differ across endpoints in unacknowledged ways. Check that observed and simulated records are matched by endpoint and relevant design features, that units and transformations are correct, and that all simulated summaries use the same rules as the observed summaries. Sparse data, very few simulations, or highly skewed predictive summaries can also make apparent bounds or standardized deviations unstable.

The main alternative to a multi-endpoint display is a set of endpoint-specific displays. These are often clearer when endpoints have very different scales or sampling schedules, and they make each endpoint’s predictive distribution easier to inspect. A combined panel can make patterns across endpoints easier to see, but should retain separate axes or other explicit scale labels. A joint statistic can summarize a prespecified cross-endpoint feature, but may hide which endpoint drives the result. No single format replaces careful endpoint-specific interpretation.

Predictive checks depend on the model, the simulation conditions, and the summaries selected. Agreement in a chosen set of summaries does not establish that every feature of the joint data distribution is adequate. Conversely, a visually unusual point does not on its own identify the cause of a discrepancy. These checks are diagnostic evidence, to be interpreted alongside the study design and other model-evaluation information.

Common mistake: “The two endpoints have similar raw deviations, so they contribute equally to model misfit.” This reasoning ignores units, predictive variability, and clinical meaning. Compare each endpoint with its own predictive distribution; use standardized summaries only to describe relative predictive distance, and use joint simulation when the target is cross-endpoint dependence.

Check Your Understanding

Try each question, then compare your reasoning with the solutions below.

  1. What must be held consistent when calculating an observed endpoint summary and its simulated counterparts?
  2. Two endpoints are measured on the same subjects. Why can’t their residuals automatically be treated as independent observations?
  3. An observed endpoint summary is 12 units, with simulated mean 10 units and simulated standard deviation 1 unit. What is its standardized predictive deviation, and what does it describe?
  4. What does examining many endpoint-specific predictive summaries imply for interpreting one isolated flag?

Solutions. (1) Use the same summary definition and the same relevant data-handling rules, including which records are included and any stratification. (2) Measurements on one subject may share subject effects or residual dependence; the pairing must be retained when assessing joint behavior. (3) \(Z=(12-10)/1=2.00\). The observed summary is two simulated-summary standard deviations above the simulated mean; this is a relative diagnostic description, not by itself a formal test. (4) Multiple inspection increases the opportunity for an apparently unusual summary, so treat an isolated flag as a reason to investigate, not as decisive evidence, and consider dependence and the broader pattern.