Start With the Prediction Task
An external dataset is useful only in relation to a defined task. A collection of concentration measurements does not, by itself, establish what population or treatment setting the data represent, what predictions the data can evaluate, or whether the recorded information is sufficient to interpret those predictions. Dataset design therefore starts by specifying the intended use and the population to which the evaluation is meant to apply.
For a population PK model, a prediction task should state the drug and formulation, the population of interest, the treatment conditions, and the concentration outcomes to be evaluated. It should also say what information about a patient and their treatment will be available for making the prediction. For example, a task might concern concentrations after a specified regimen in adults with a particular disease, using baseline covariates and dose history available at the time of prediction. The intended prediction time or times should be explicit.
The task specification determines the dataset requirements. If the intended use is prediction in a new hospital, a dataset from that hospital is relevant only if its patients and treatment practices also match the target population. If the intended use concerns concentrations near the end of a dosing interval, measurements only around the expected peak may not be informative. A design should make these connections explicit before recruitment or data extraction.
Specify Patients, Sites, and Treatment Conditions
Eligibility criteria should describe the patients to whom the evaluation is intended to apply, not merely those easiest to recruit. Specify age range, disease or indication, relevant organ-function range, treatment history, and any other defining characteristics. Record clinically relevant covariates even when they are not eligibility criteria: they help characterize who was actually observed and whether the data cover the intended population. Include patients across the range of covariate values expected in use, rather than concentrating only near the average.
Sites and treatment settings matter because clinical practice can shape the data. State the number and type of sites, whether care is inpatient or outpatient, and whether dosing follows a common protocol or routine practice. Record the dose, formulation, route, dosing interval, treatment duration, and relevant dose changes. The design should include the settings to which the conclusions are intended to apply. A large patient count from one unusually specialized site may describe that site well but provide limited information about variation across ordinary practice.
Define the sampling unit and the observation unit separately. Patients are usually the independent sampling units; concentration records are repeated observations within patients. More records per patient can clarify an individual concentration-time profile, but do not create the same breadth of population information as enrolling more patients. The planned balance depends on the task: a design should have enough patients to represent between-patient variation and enough appropriately timed samples to observe the concentration patterns of interest.
Worked Example: Turning a Clinical Question Into Eligibility Criteria
A team wants to evaluate a model for predicting concentrations of a hypothetical oral medicine in adults with a specified chronic condition receiving a stable once-daily regimen. The intended setting is routine outpatient care. A vague plan to “collect adult concentrations” is not enough to make the task testable.
Population. Define adults as age 18 years or older, state the diagnostic criteria for the condition, and specify the range of renal function and body size relevant to intended use. Record age, body weight, sex, renal function, and other prespecified clinical covariates. Do not exclude a patient merely for having an unusual but relevant covariate value if the model is intended for that value range.
Treatment. Specify oral formulation, dose, once-daily interval, and the minimum duration on the regimen required before sampling. Record actual dose times, missed doses, dose changes, and concomitant medicines that may alter exposure.
Setting. Recruit from several outpatient clinics that provide the type of care where the model is intended to be used. Record site and setting for each patient. The resulting data can address the stated adult outpatient task; they do not automatically support use in children, inpatient care, or a different formulation.
The criteria now connect the patients, treatment, and setting to a defined task. The design still needs a sampling schedule and complete concentration outcomes, addressed below.
Plan Sampling Times Around the Concentration-Time Question
Sampling times should be chosen in relation to dose times and the pharmacokinetic behavior the task needs to evaluate. A schedule intended to characterize early absorption should include appropriately timed early samples; one intended to assess late-interval concentrations needs observations near the end of the dosing interval. When the target concerns the full profile, measurements should cover relevant portions of the interval rather than clustering at one convenient time.
The schedule must be feasible in the clinical setting. A scientifically attractive sequence that patients cannot follow will yield missed or mistimed samples. State whether sampling is at prespecified times, within allowed windows, or opportunistic. For every sample, record the actual collection date and time, not only the nominal time. Record the exact times and amounts of doses around the sample, including deviations from the planned regimen. A concentration without a usable time relative to dosing may be difficult to interpret.
Repeated measurements within a patient are correlated. A simple calculation shows why counting records alone can overstate how much independent information a dataset contains. Suppose, for illustration, that each patient has \(m\) measurements with a common variance \(\sigma^2\), and every pair has correlation \(\rho\). For the mean of those \(m\) measurements,
The factor \(1+(m-1)\rho\) is the design effect relative to \(m\) independent measurements. Under this simplified exchangeable-correlation illustration, the equivalent number of independent observations is \(m/[1+(m-1)\rho]\). It is not a universal sample-size formula for PK profiles: correlations can vary with time, and patient effects and residual variation have different roles. Its purpose is to demonstrate why more samples from the same patient cannot substitute without limit for additional patients.
Worked Example: Choosing a Feasible Sampling Schedule
For a hypothetical once-daily medicine, the task is to evaluate predictions at early, middle, and late portions of the dosing interval. The planned interval is 24 hours. A proposed schedule collects one sample near each of 2, 8, and 23 hours after an observed dose. These times are illustrative and would need clinical and assay justification for the actual medicine.
If 36 patients complete the schedule, the planned number of concentration records is \(36 \times 3=108\). That is 36 patients, not 108 independent patients. For a simplified illustration with \(m=3\) measurements per patient and within-patient correlation \(\rho=0.5\), the design effect is \(1+(3-1)(0.5)=2\). The equivalent independent-observation count for estimating a common mean under the exchangeable model is \(108/2=54\), not 108.
This calculation does not establish that 36 patients are sufficient for every prediction task. It shows why the design must report both patient count and records per patient. The actual schedule should also capture collection times, actual dose times, missed doses, and sample timing deviations; otherwise, the nominal three-point schedule may not describe the observed profiles.
Define the Outcome and the Minimum Data Record
The principal outcome for a concentration prediction task is a measured drug concentration linked to a particular patient, dose history, and actual sample time. Specify the analyte, biological matrix, units, assay method, and any relevant handling or storage information. Use a consistent laboratory procedure where practical, and preserve the information needed to identify assay or protocol differences. These details help distinguish a genuine model-prediction discrepancy from a measurement or recording problem.
At minimum, each concentration record should be linkable to a patient identifier, sample date and time, actual dose history, and treatment regimen. The patient-level record should include eligibility information, relevant covariates, site, treatment setting, and dates of treatment and sampling. Preserve the original recorded values and units, along with any derived or transformed values used for analysis. Record whether a sample was collected, missed, unusable, or not scheduled; otherwise, the observed dataset may conceal systematic gaps.
The dataset specification should state what information is available when a prediction is made. Do not rely on a covariate or clinical measurement collected only after the prediction time if that information would not be available in intended use. This distinction prevents an evaluation from quietly using information unavailable to the real task. It also makes clear which measurements are predictors or context and which are outcomes used to evaluate the predictions.
Worked Example: Auditing a Planned External Dataset
A hypothetical retrospective dataset contains 80 adults from four outpatient clinics, with two concentration records per patient. The intended task is prediction during stable once-daily dosing. The records include concentration values, patient age and weight, and nominal sample time. The extraction team proposes to proceed directly to evaluation.
Patient and site coverage. There are 80 patients across four clinics, or 20 patients per clinic if evenly distributed. Verify the actual site counts and describe eligibility, disease status, and treatment regimen. The number of clinics alone does not establish that the sites represent the intended care setting.
Timing and dosing. Nominal sample time is not enough. Check whether actual collection times and actual dose times are available. If not, the elapsed time since dose cannot be verified, and the data may not support the stated task. Determine whether dose changes or missed doses occurred during the relevant period.
Outcomes and covariates. Confirm concentration units, analyte, assay information, and patient-to-sample linkage. Compare the observed age and weight ranges with the intended population. If renal function is important to the target population but was not recorded, the dataset cannot adequately describe that aspect of coverage.
The dataset has 160 concentration records, but still only 80 patients. It may be usable if the required timing, dosing, assay, and population details are recoverable. If these are missing, a larger record count does not remedy the central design deficiencies.
Design Checks, Alternatives, and Limitations
Before data collection or extraction is finalized, check whether the specification supports the task. A useful review asks whether the eligibility criteria match intended use; the recruited sites and treatment settings are relevant; the covariates cover clinically important ranges; the sampling schedule addresses the requested times; and each outcome can be linked to reliable dose and time information. Confirm that the expected number of patients, not merely the total number of samples, is adequate for the planned evaluation. Any adequacy claim should be tied to a prespecified precision or decision objective rather than to a generic record-count threshold.
Failure modes include enrolling only highly adherent patients when routine-use prediction is the goal, sampling at convenient times that miss the concentration region of interest, omitting actual dose times, and recording outcomes without assay or unit information. Missingness can also be informative: for example, patients who feel unwell may miss visits or have treatment changed. Report the extent and reasons for missing samples where known. A schedule with poor completion or a narrow covariate range may leave the dataset unable to address its stated task, even when the collected measurements are accurate.
A prospective external study can specify eligibility, sampling windows, and data capture before observations occur. A retrospective external dataset may be less costly and reflect routine practice, but the available records can limit timing precision, covariate coverage, and control over measurement procedures. A dense sampling design describes within-patient profiles more fully but may burden participants and produce many correlated records. A sparse design can be more feasible and may represent routine practice, but its value depends on appropriate timing across patients and sufficient patient-level coverage. Neither design is inherently superior; the choice follows from the prediction task and practical constraints.
External data also have limits. A dataset from a different population or setting may assess performance in that setting without establishing relevance to every intended population. A single site may not reveal between-site variation. A well-documented concentration dataset can support a defined evaluation, but cannot compensate for a task that was never specified or for essential information that was never recorded.
Check Your Understanding
Answer each question, then compare with the solutions.
- A dataset has 50 patients and four concentration records per patient. How many patients and how many concentration records does it contain, and why should these counts not be treated as interchangeable?
- A task concerns late-interval concentrations, but the proposed schedule collects only samples near the expected peak. Identify the design problem.
- Name four pieces of information, in addition to the concentration value, that should be recorded or linked to a sample.
- A retrospective dataset comes from one specialist center, while intended use is routine care across several general hospitals. What limitation should be stated?
Solutions. (1) It contains 50 patients and \(50 \times 4=200\) concentration records. Records within a patient are repeated and correlated, so 200 measurements do not represent 200 independent patients. (2) The schedule does not cover the concentration-time region relevant to the stated task; it should include appropriately timed late-interval samples, with actual collection and dose times recorded. (3) Examples include patient identifier, actual sample date and time, actual dose times and amounts, analyte and units, assay information, site, and relevant covariates. (4) The dataset may describe the specialist center but may not represent routine general-hospital care; its setting limits how broadly the evaluation can be interpreted.