On this page
How do you prepare the clinical pharmacology summary in CTD 2.7.2?
Organize clinical pharmacology evidence around exposure, response, variability and the proposed dosing questions. Explain the important studies and cross-study findings while distinguishing observed human results, model predictions and laboratory evidence. Link each dosing implication to its population, assumptions and supporting analysis rather than presenting extrapolation as direct observation.
Before you begin
M4E(R2) section 2.7.2; content depends on the actual product and program, including vaccine-specific immune-response evidence where relevant.
What you will prepare: A transparent account of clinical pharmacology findings, variability and dosing implications with unresolved extrapolations identified.
Organize around the questions the data can answer
Collect the human PK/PD, human biomaterial, interaction, population-model and relevant special-population reports, with approved analyses and the current dose proposal. Set out the questions about exposure, response, variability and intrinsic or extrinsic factors before drafting study summaries.
Separate observed clinical results from model-based predictions and in vitro findings. Each can be informative, but their evidentiary roles differ. The background should explain the program’s approach, not bury the reader in every individual result.
For a vaccine, assess the relevant immune-response evidence supporting dose, schedule and formulation rather than copying a conventional small-molecule clearance narrative. Unknown modality or intended regimen prevents a reliable template choice.
Connect individual studies with the cross-study account
For key studies, retain the population, regimen, sampling or design features, analytical basis and material results, with the full report linked. Summarize across studies only after confirming compatible parameters and accounting for important sources of variability.
M4E distinguishes clinical pharmacology evidence from studies providing important direct efficacy or safety evidence. Use cross-references where a study is substantively summarized under 2.7.3 or 2.7.4, rather than maintaining competing accounts. Address special studies as appropriate to the product and preserve their assay or design limitations.
Use an editorial dose-evidence table: proposed statement → observed result or model output → relevant population → assumption → limitation → report. This exposes a dose proposal supported in one population but extrapolated to another. Ask the clinical pharmacology owner to resolve any inference that the source analysis does not make.
Worked example: a model prediction becomes a measured result
Fictional editorial exercise: no dedicated severe-impairment cohort was studied. A model predicts increased exposure, but the summary calls that increase “observed in patients with severe impairment.”
Check the population actually studied and the model’s prediction domain. Change the wording to identify the prediction and summarize the assumptions and uncertainty provided by the model report. Obtain expert review of what the result supports for dosing; the writer should not invent an adjustment.
Inspect the overview and proposed dosing discussion for the same measured-versus-predicted confusion. If the model report does not adequately characterize the proposed population, record the gap instead of supplying a universal dose recommendation.
Test each proposed dosing statement against its evidence
Begin with the dosing statements the clinical team proposes to make, then trace each one backward. This reveals gaps that a study-by-study writing plan can miss. The following is an editorial worksheet; it does not recommend any dose or adjustment.
| Proposed statement | Evidence classification | Information needed to assess the statement |
|---|---|---|
| A factor changes exposure | Observed study result, model prediction or in vitro finding | Population, regimen, parameter, comparator and uncertainty |
| No adjustment is proposed | Clinical interpretation supported by identified evidence | How exposure or response differences were evaluated, and the limits of that inference |
| An interaction is relevant | Tested or predicted relationship | Perpetrator/victim roles, conditions and the scope of the conclusion |
| A regimen is supported | Exposure-response or other relevant clinical evidence | Outcomes, population, assumptions and consistency with efficacy and safety summaries |
Do not make the classifications interchangeable. A model can provide valuable evidence, but the narrative should identify it as a model, describe the prediction domain and retain the uncertainty supplied by the analysis. Conversely, a directly observed difference still requires interpretation before becoming a dosing recommendation.
For every consequential sentence, perform a provenance check: can the reader tell whether the result was measured, predicted or inferred? Then perform a scope check: does the proposed population or regimen exceed the evidence being cited? A clean answer to the first question does not guarantee a clean answer to the second.
Coordinate with the efficacy and safety authors where a pharmacology study also supplies important outcome evidence. Give the shared study one stable identifier and cross-reference the substantive analysis, rather than creating incompatible mini-summaries with different population counts.
Your preparation checklist
0/4 checkedUse this to track your review in this visit. Checks are not saved and do not establish regulatory compliance.
Frequently asked questions
Can model-predicted exposure be described as observed exposure?
No. State that the result is predicted and identify the model, population domain and important assumptions. An observed result comes from the actual measurements in the studied population. Both can contribute to interpretation, but their evidentiary roles and uncertainties should remain visible.
Does a change in exposure automatically imply a dose adjustment?
No. A dosing implication requires the responsible experts to consider the exposure-response relationship, efficacy and safety evidence, and the proposed use. The writer should explain the supported interpretation and its limits, rather than convert a percentage exposure difference into an independent dosing recommendation.
Should vaccine clinical pharmacology follow a small-molecule PK template?
Not automatically. Choose the relevant scientific questions for the product, including immune-response evidence where appropriate. A conventional clearance narrative may not answer questions about dose, schedule or formulation for a vaccine. Use the applicable M4E content and product-specific evidence rather than fill irrelevant headings.
Where should a study that also supports efficacy be discussed?
Summarize it according to the scientific questions it answers and cross-reference the substantive efficacy or safety account where appropriate. Keep identifiers and factual results consistent. The goal is a coherent dossier with distinct interpretations, not the same independently maintained study abstract in every section.
Sources and revisions
Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.
Guidance
ICH M4E(R2): Clinical overview and summary ↗Step 4, June 15, 2016; sections 2.5 and 2.7. FDA corresponding M4E(R2) guidance is final, July 2017. Recommendations are distinct from application-specific legal requirements.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 2.7.2. A heading identifies placement, not mandatory applicability.