Tutorials › Pharmacokinetic-Pharmacodynamic (PK/PD) Modeling › Simulation Checks For Population PD Model Stability

Population PK/PD Model Building · Tutorial 447 of 598

Simulation Checks For Population PD Model Stability

Use repeated simulated datasets to test whether a candidate population PD model and planned sampling design can reliably recover parameters and covariate effects.

Advanced 12 min read

What You'll Learn

  • Specify a simulation that reflects the candidate population PD model and planned study design
  • Calculate empirical bias, relative bias, precision, and root mean squared error
  • Report convergence and parameter-boundary problems separately from recovery summaries
  • Assess whether covariate-effect estimates are stable under the planned covariate distribution
  • Distinguish parameter-recovery simulations from bootstrap and predictive-check approaches
  • Recognize what simulation checks can and cannot establish about a model

Why Simulate Before Relying on a Population PD Model?

A candidate population PD model can fit observed data and still be difficult to estimate reliably under the intended study design. For example, sparse observations near the concentration range where a response changes may leave an \(EC_{50}\) weakly identified. A covariate effect may also be hard to distinguish from between-subject variability when the covariate has little variation or is unevenly represented. Simulation checks make these vulnerabilities visible by asking a direct question: if this model and design generated the data, would the planned estimation procedure recover the parameters?

A parameter-recovery simulation generates many hypothetical datasets from a specified population model, using the planned sampling design, and refits the candidate model to each dataset. The results describe the behavior of the full estimation process under those assumptions. They do not prove that the model is true, nor do they establish that its assumptions match the actual population.

Definition: In a parameter-recovery simulation, the generating model and its parameter values are specified first. Each simulated dataset is generated under those values and the planned design, then analyzed using the candidate estimation procedure. Comparing fitted estimates with the known generating values assesses recovery, including bias, precision, convergence, and—in covariate models—the stability of covariate-effect estimates.

Specify the Simulation Before Interpreting It

The simulation needs to represent the features of the planned study that affect estimation: numbers of subjects and observations, dose or concentration profiles, observation times, covariate distributions, missing data assumptions, between-subject variability, residual variability, and the response model. When concentration is treated as an input to the PD model, its simulated or supplied values should still reflect the planned concentration range and observation schedule. The analysis step should use the same model structure, parameter constraints, and estimation procedure intended for the study.

For illustration, suppose response \(Y_{ij}\) for subject \(i\) at observation \(j\) follows an Emax model with a covariate on the population Emax:

$$ E_{\max,i}=E_{\max}\exp(\beta z_i+\eta_i), \qquad Y_{ij}=E_0+\frac{E_{\max,i}C_{ij}}{EC_{50}+C_{ij}}+\epsilon_{ij}. $$

Here \(C_{ij}\) is concentration, \(z_i\) is a covariate centered and scaled so that one unit is one standard deviation, and \(\eta_i\) represents subject-level variation in Emax. A typical simulation might specify \(\eta_i\sim N(0,\omega^2)\) and \(\epsilon_{ij}\sim N(0,\sigma^2)\), with independent subject effects and residual errors. Those distributional and independence assumptions are part of the simulation, not facts established by the fitted model. Other error structures or random-effects assumptions require corresponding changes to the generator.

A useful design specification preserves the planned distribution of \(z_i\), including relevant subgroup sizes and correlations with other covariates. It also uses realistic concentration and time profiles. Simulating an evenly balanced covariate when the planned study has a small subgroup, for example, can make the covariate effect look more precisely estimable than it will be in practice.

Summarize Parameter Recovery

Let \(R\) be the number of simulated datasets for which the estimation procedure produced an estimate of a parameter \(\theta\), and write the estimate from replicate \(r\) as \(\hat{\theta}_r\). If all \(R\) estimates are available, empirical bias and relative bias are:

$$ \operatorname{Bias}(\hat{\theta})= \frac{1}{R}\sum_{r=1}^{R}(\hat{\theta}_r-\theta), \qquad \operatorname{Relative\ Bias}(\%)= 100\frac{\operatorname{Bias}(\hat{\theta})}{\theta}. $$

Relative bias is useful for nonzero parameters, but can be misleading or undefined when the true value is near zero. In that setting, report bias in the parameter’s units and consider a scale suited to the parameter. Empirical precision is commonly summarized by the sample standard deviation of the estimates across replicates:

$$ s_{\hat{\theta}}= \sqrt{\frac{1}{R-1}\sum_{r=1}^{R}(\hat{\theta}_r-\bar{\hat{\theta}})^2}. $$

This is the variation of estimates across simulated datasets, not the standard error reported by a single fit. Root mean squared error (RMSE) combines variability and bias. For the sample-variance convention above, it can be written:

$$ \operatorname{RMSE}= \sqrt{\frac{1}{R}\sum_{r=1}^{R}(\hat{\theta}_r-\theta)^2} = \sqrt{\frac{R-1}{R}s_{\hat{\theta}}^2+\operatorname{Bias}(\hat{\theta})^2}. $$

The identity follows by writing \(\hat{\theta}_r-\theta=(\hat{\theta}_r-\bar{\hat{\theta}})+(\bar{\hat{\theta}}-\theta)\), squaring and summing across replicates. The cross-product sums to zero because \(\sum_r(\hat{\theta}_r-\bar{\hat{\theta}})=0\). Thus the average squared error is the centered sum of squares divided by \(R\), plus the squared bias. RMSE is therefore small only when both bias and variability are limited.

Worked Example: Bias and Precision for a PD Parameter

Suppose five hypothetical datasets are generated with true \(E_{\max}=8.00\) response units. Refitting the candidate model gives estimates of 7.60, 8.40, 8.10, 7.90, and 8.00 response units. This small number of replicates is for demonstrating the arithmetic; a practical simulation would ordinarily use many more.

The mean estimate is \(\bar{\hat{\theta}}=(7.60+8.40+8.10+7.90+8.00)/5=8.00\) response units. Therefore the empirical bias is \(8.00-8.00=0.00\) response units, and the relative bias is \(100(0.00/8.00)=0.00\%\).

The deviations from the mean are \(-0.40,\ 0.40,\ 0.10,\ -0.10,\) and \(0.00\) response units. The empirical standard deviation is \(s_{\hat{\theta}}=\sqrt{(0.16+0.16+0.01+0.01+0.00)/4}=\sqrt{0.085}=0.292\) response units.

The RMSE is \(\sqrt{[(7.60-8.00)^2+(8.40-8.00)^2+(8.10-8.00)^2+(7.90-8.00)^2+(8.00-8.00)^2]/5} =\sqrt{0.068}=0.261\) response units. The RMSE is slightly below the sample standard deviation because it uses a divisor of \(R\) for the squared errors, whereas the sample variance uses \(R-1\). These five estimates show no bias in their mean, but five replicates are far too few to establish stable performance.

Convergence Is Part of the Result

A fitted estimate is informative only if the estimation procedure has reached a defensible solution. Define convergence criteria before running the simulation. They might include a successful optimizer termination, acceptable gradient or objective-function checks, finite estimates and standard errors, and estimates away from inappropriate parameter boundaries. A software convergence flag alone is not a guarantee that the fitted solution is reliable; inspect whether different starting values or optimizers lead to materially different results.

Report the convergence rate as the number of fits meeting the prespecified criteria divided by the total number of simulated datasets. Also tabulate failure types, boundary estimates, and other concerning outcomes. Bias and precision calculated only from converged fits describe the distribution conditional on convergence. If difficult datasets fail disproportionately, those summaries can give an overly reassuring picture of performance. Do not silently discard failures or treat them as zero-valued estimates.

Worked Example: Reporting Failures Alongside Recovery

In 100 hypothetical simulations, 96 fits meet prespecified convergence criteria. The 96 successful estimates of a positive parameter \(\theta\), whose generating value is 1.00, sum to 99.84. Of those estimates, 91 lie within the prespecified plausible interval from 0.50 to 1.50.

The convergence rate is \(96/100=0.960\), or 96.0%; four fits did not meet the criteria and must be reported as failures. Among the converged fits, the mean estimate is \(99.84/96=1.04\), so the conditional empirical bias is \(1.04-1.00=0.040\), and relative bias is \(100(0.040/1.00)=4.00\%\).

The proportion of converged estimates within the prespecified interval is \(91/96=0.9479\), or 94.8%. This is a descriptive check against that interval, not a formal measure of interval coverage. The five estimates outside the interval warrant inspection even though their fits converged. Recovery summaries here apply only to the 96 converged fits; they do not erase the four failures or show what their estimates would have been.

Check Covariate-Effect Stability Under the Planned Design

For a covariate parameter such as \(\beta\), assess recovery on its model scale and in an interpretable clinical scale where appropriate. In the Emax example, increasing \(z_i\) by one standard deviation multiplies the typical Emax by \(\exp(\beta)\). Thus \(\beta=0.30\) corresponds to a multiplier of \(\exp(0.30)=1.35\), approximately a 35.0% increase. This interpretation depends on the stated log-linear covariate model.

Stability is not just whether the average estimate is close to the generating value. Also examine spread, sign changes, boundary estimates, convergence, and sensitivity to the covariate distribution and observation schedule. If covariates are correlated, simulate their planned joint distribution rather than varying each one in isolation. A targeted set of scenarios can reveal whether the effect remains estimable when subgroup sizes, missingness, or concentration coverage are less favorable.

Worked Example: A Covariate Effect Under Two Sampling Designs

Suppose the generating covariate coefficient is \(\beta=0.30\) per one-standard-deviation increase in \(z_i\). In four hypothetical replicates with a well-balanced covariate distribution, the fitted coefficients are 0.26, 0.31, 0.34, and 0.29. Their mean is \((0.26+0.31+0.34+0.29)/4=0.30\), so the empirical bias is \(0.00\) per standard deviation.

Their sample standard deviation is \(\sqrt{[(−0.04)^2+0.01^2+0.04^2+(−0.01)^2]/3} =\sqrt{0.0034/3}=0.0337\) per standard deviation. For contrast, suppose four simulations using a sparse-subgroup design give 0.10, 0.18, 0.35, and 0.57. Their mean is also \(0.30\), but their sample standard deviation is \(\sqrt{[(-0.20)^2+(-0.12)^2+0.05^2+0.27^2]/3} =\sqrt{0.1298/3}=0.208\) per standard deviation.

Both sets have zero mean bias in these few replicates, but the sparse-subgroup estimates vary much more. On the Emax scale, the true one-standard-deviation multiplier is \(\exp(0.30)=1.35\). The wide spread in the second set signals that individual fitted covariate effects may be unstable even when the average across replicates equals the generating value. Four replicates are illustrative only; a real assessment needs enough simulations to characterize performance reliably.

Diagnostics, Alternatives, and Limitations

Review simulation output as a set of diagnostics, not a single pass-or-fail statistic. Plot estimates against replicate number and compare their distributions with the generating values. Look for skewness, multimodality, long tails, repeated boundary estimates, or patterns linked to particular covariate or concentration scenarios. Compare the intended estimator with its reported standard errors: consistently small empirical spread alongside much larger reported standard errors, or the reverse, deserves investigation. Examine convergence failures by scenario, since aggregate rates can hide a design feature that makes a particular subgroup or parameter difficult to estimate.

Simulation-based parameter recovery answers a different question from common alternatives. A nonparametric bootstrap resamples observed data units to assess variation relative to the observed sample; it does not automatically test recovery under a fully specified generating model and planned future design. A visual predictive check compares simulated and observed data summaries for model adequacy, but a good predictive comparison does not by itself show that individual parameters are precisely recoverable. Standard errors from a single fitted model are local, model-based uncertainty measures; simulation can assess their behavior across repeated datasets under chosen assumptions.

The principal limitation is that the conclusions depend on the generator. If it reproduces the candidate model exactly, reassuring recovery shows that the design and estimation procedure can recover parameters under that model; it does not rule out misspecification. Add plausible alternative scenarios when important assumptions are uncertain, and state which assumption each scenario changes. Simulation results also have Monte Carlo uncertainty: a small number of replicates can make estimated bias, precision, or convergence rates themselves unstable.

Common pitfall: “The mean estimate matched the generating value, so the parameter is reliably estimated.” A mean can match while individual estimates are highly variable, boundary-prone, or often nonconvergent. Report the convergence rate and failure patterns alongside bias, empirical precision, and RMSE, and assess covariate stability under the actual planned design.
1
Define the generating scenarios.
Specify the population PD model, parameter values, covariate distribution, sampling schedule, and variability assumptions. Include additional plausible scenarios where design or model assumptions are uncertain.
2
Generate and refit datasets.
Use the planned design and the intended estimation procedure. Prespecify convergence and boundary criteria before examining results.
3
Summarize recovery and diagnose failures.
Report convergence, bias, precision, and RMSE with their denominators. Inspect parameter distributions and covariate-effect stability across relevant scenarios.

Check Your Understanding

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

  1. What does a parameter-recovery simulation establish, and what does it not establish?
  2. In 200 simulations, 190 fits converge. What is the convergence rate, and what denominator should be stated for bias calculated only from converged estimates?
  3. Why can a covariate coefficient have little average bias yet be unstable for a planned study?
  4. When the true parameter is zero, why is relative bias an unsuitable summary?

Solutions. (1) It assesses recovery by the estimation procedure under the specified generating model and design; it does not establish that those assumptions are true or that the model is adequate for observed data. (2) The rate is \(190/200=95.0\%\). Conditional bias uses 190 converged estimates, and the 10 failures must also be reported. (3) The estimates can be widely dispersed, change sign, hit boundaries, or fail to converge in some replicates while averaging near the generating value. (4) Relative bias divides by the true parameter, so division by zero is undefined; report absolute bias in the parameter’s units and suitable measures of spread instead.

Clinical Biostats