On this page
What should the clinical efficacy summary in CTD 2.7.3 establish?
The efficacy summary should give an indication-specific account of the relevant studies and their combined interpretation, including unsuccessful or discordant findings. Preserve the population, comparator, endpoint, timepoint and uncertainty behind important claims. Explain the basis for dose and durability conclusions without treating incompatible results as one homogeneous dataset.
Before you begin
M4E(R2) efficacy summary. Closely related indications may be considered together with a reasoned scope; this page does not establish that a Module 2 summary satisfies every FDA integrated-summary requirement.
What you will prepare: A complete, source-linked efficacy narrative whose interpretation can be checked against study and integrated-analysis reports.
Set the indication and evidence denominator
Start with the proposed indication and the complete set of relevant efficacy studies, not only positive pivotal trials. M4E recommends an indication-specific presentation while allowing closely related indications to be considered together. Record the rationale if evidence is combined.
Collect final study reports, protocols and analysis plans needed to understand the reported results, integrated-analysis reports, labeling proposals and relevant pharmacology findings. Identify study populations, comparators, endpoints, timepoints and prespecified versus exploratory analyses.
Build an editorial evidence inventory with a disposition for every relevant study. A study that failed to support the main conclusion still informs the program. A missing final report is a preparation gap, not a reason to remove the study from the denominator.
Compare results without erasing design differences
Introduce the program, summarize important individual studies, and then explain the cross-study picture. Include unfavorable or inconsistent findings. Distinguish a comparison of results from an analysis pooling participant data; they answer different questions and may use different evidence.
For a major efficacy statement, preserve population, treatment comparison, endpoint definition, analysis set, timepoint, estimate and uncertainty. Use the approved statistical interpretation, including material issues with missing data or multiplicity, rather than inferring a conclusion from one p-value.
Discuss evidence relevant to dosing and the persistence of efficacy or tolerance. Cross-reference pharmacology evidence where it informs the dose proposal. Extensive integrated analyses belong with their source reports; a concise summary should still let the reviewer find and understand the underlying work.
Worked example: two endpoints share a familiar label
Fictional editorial exercise: two studies both report a “response rate,” but one evaluates response at week 8 and the other uses sustained response through week 24. A draft table presents the percentages in a single undifferentiated column.
Add endpoint definitions, timepoints and analysis populations to the comparison. Ask the statistician whether a direct comparison or pooling is meaningful. Preserve the study-specific results even if a broader synthesis is justified. Do not describe the difference between percentages as treatment superiority without the appropriate comparison.
If a durability claim relies only on a selected continuation population, identify that selection and the resulting limitation. Reconcile the final conclusion with 2.5 and the proposed indication so a qualification does not disappear at the overview level.
Build a comparison grid before writing the integrated conclusion
An efficacy table should reveal why results can or cannot be compared. Use the following working columns before condensing the program into narrative. They are editorial controls, not a substitute for the approved statistical analysis.
| Column | What must remain identifiable | Failure exposed |
|---|---|---|
| Study and role | Identifier, design and role in the program | Excluding a negative study without explanation |
| Population | Eligibility and the analysis set behind the result | Presenting a selected subgroup as the whole intended population |
| Comparison | Treatment, control and relevant regimen | Implying a head-to-head comparison where none was performed |
| Outcome | Exact endpoint, timepoint and how it was analyzed | Pooling results that merely share a familiar label |
| Result | Estimate, uncertainty and material analysis qualifications | Reducing the result to a favorable p-value |
| Interpretation | Supported conclusion and limitation | Promoting an exploratory finding into a confirmatory claim |
Write the individual-study account first enough to establish these facts, then explain the cross-study pattern. A study-level comparison and an integrated analysis of participant data are different activities. Name which one supports the conclusion and link its source report.
Review exercise: a durability sentence relies on an extension entered only by participants who completed the initial trial. Keep the continuation criteria and population in the statement's evidence record. Ask the clinical and statistical owners what the extension can establish; do not generalize its duration result to everyone initially randomized merely because both periods used the same study drug.
Use the clinical overview to explain the implications of this evidence for the proposed use. The qualification should survive that handoff. If the overview removes the endpoint or population condition that made a statement true, the issue is substantive even when every copied number is correct.
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
Should unsuccessful trials be included in the efficacy summary?
Relevant unsuccessful and discordant studies belong in the evidence account. Explain their results and how they affect the overall interpretation. Building the summary only from positive pivotal studies can distort the program and hide questions about population, design or consistency that a reviewer needs to assess.
Can closely related indications share an efficacy summary?
M4E allows closely related indications to be considered together when the presentation is appropriate. Make the scope and rationale clear, and preserve indication-specific evidence and limitations. Combining the document must not imply that evidence from one indication automatically supports another.
Is a cross-study comparison the same as a pooled efficacy analysis?
No. Comparing study-level results describes the pattern across studies. A pooled participant-level analysis combines data under specified methods and population rules. Identify which approach produced the conclusion and preserve the underlying definitions; a table of percentages is not automatically a valid integrated analysis.
Does CTD 2.7.3 automatically satisfy every FDA integrated-summary obligation?
No. The CTD summary structure alone does not establish that all application-specific FDA integrated-summary requirements have been met. Confirm the applicable obligations and submission plan separately. Use 2.7.3 to provide a traceable summary of the relevant efficacy evidence and identify the supporting integrated analyses.
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.3. A heading identifies placement, not mandatory applicability.