On this page
How should the CTD clinical summary, references and study synopses be assembled?
Coordinate the four scientific summaries against a common study and report-version register, make the cited literature retrievable in 2.7.5, and align the 2.7.6 study listing and synopses with Module 5. Use the synopsis from the controlling study report rather than creating a separately edited account for Module 2.
Before you begin
M4E(R2) clinical-summary organization and sections 2.7.5–2.7.6. The 2.7 family is not an instruction to duplicate all four summaries in another file.
What you will prepare: A reconciled clinical-summary package with current references, a study listing and matching synopsis versions.
Sections covered in this guide (3)
Give each scientific question one accountable home
The clinical-summary family brings together biopharmaceutics, clinical pharmacology, efficacy and safety. Before final assembly, agree the controlling study register, data cutoffs and source-report versions with those authors. Use cross-references when a study contributes to more than one question, while preserving the different interpretations needed by each discipline.
Maintain an editorial handoff table: study identifier, report version, summary locations, synopsis version, relevant analysis cutoff and unresolved issue. The purpose is to identify disagreement, not force different analysis populations to have identical numbers.
For example, efficacy and safety populations may legitimately differ. Require an explanation tied to the analysis definitions rather than “correcting” one count to match the other. Resolve unexplained differences before the overview relies on the combined package.
2.7.5: make each reference retrievable
Create the list from literature actually cited in the clinical summary. Reconcile author, title, year and other identifiers with the source rather than a copied citation string. M4E directs important reference copies to Module 5 section 5.4 and asks the list to identify which references are available there; references not supplied should remain available on request.
Use an editorial reference register with citation key, source identity, cited claim, copy location and retrieval status. Check that a reference supports the statement for which it is cited. A related paper is not evidence for an exact numerical result found only in another report.
If a source is inaccessible or an identifier resolves to the wrong article, flag it and obtain the correct record. Do not fabricate a complete-looking citation. Retain the qualifications around indirect or published evidence when assembling the final narrative.
2.7.6: match each synopsis to the controlling study report
M4E describes a clinical-study listing followed by individual synopses in the Module 5 study-report sequence, with the same synopsis used here and in the corresponding report. Gather the synopsis from the controlled report package rather than rewriting it independently for Module 2.
Compare study identifier, report date/version, objectives, populations, primary results and conclusions. A synopsis is a compact account of an individual study; it should not quietly introduce an integrated result or a new statistical interpretation absent from that report.
Fictional editorial exercise: the report was amended to correct an analysis population, but 2.7.6 still contains the earlier synopsis. Identify the controlling report, obtain its approved synopsis and assess affected summary statements with the study owner. Repair both the content and the version relationship; changing only the filename leaves the inconsistency intact.
A release register for the clinical-summary package
Assemble the package from controlled documents rather than from whichever files arrived most recently by email. The following editorial register exposes the relationships that need checking before the summaries and overview are finalized.
| Record | Minimum identity to retain | Final comparison |
|---|---|---|
| Clinical study | Study identifier and controlling report version | Module 5 listing, relevant scientific summaries and synopsis |
| Integrated analysis | Analysis identifier, population definition and cutoff | Summary tables and the interpretation carried into 2.5 |
| Literature citation | Author/title identifiers and the exact work cited | Claim supported, reference-list entry and supplied copy location |
| Synopsis | Source report and amendment status | Same study facts and conclusions as the report package |
| Open issue | Affected documents, owner and decision | No silent omission from the final handoff |
Do not force every population count to match. The efficacy summary and safety summary may use different analysis sets. The register should point to the definitions explaining the difference. An unexplained mismatch is a finding; a documented difference is information the reviewer may need.
For references, check both identity and support. A citation that resolves successfully can still be the wrong paper for the claim. Open the actual source, verify the result or argument being used, and record the relevant location. Avoid replacing a difficult-to-retrieve reference with a superficially related publication.
For a report amendment, compare the old and controlling synopsis before assembling 2.7.6. Determine whether results, populations or conclusions changed and ask the study owner which downstream summaries are affected. Renaming an old PDF to match a new report date does not establish version agreement. Keep the editorial issue open until the source and its dependent documents actually agree.
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 the synopsis in 2.7.6 be rewritten to fit Module 2?
M4E calls for the same synopsis in 2.7.6 and the corresponding Module 5 study report. Use the controlled report synopsis and confirm its amendment status. Independent rewriting can create different populations, results or conclusions for the same study, even when the intention is simply to shorten it.
Where should the important clinical-summary reference copies be placed?
M4E directs important literature reference copies to Module 5 section 5.4, with the 2.7.5 list identifying which references are supplied there. References not supplied should remain available on request. Verify the identity and retrieval status of the actual cited work before final assembly.
Does the 2.7 heading require another duplicate clinical-summary document?
The heading organizes the clinical-summary family; it is not by itself a reason to duplicate all the scientific summaries in another file. Follow the applicable electronic structure and submission plan. Give each scientific question a clear home and use consistent cross-references between documents.
What should happen when an amended report changes a study synopsis?
Obtain the controlling synopsis, compare the changed facts with 2.7.6 and every scientific summary using them, and ask the study owner whether interpretation changes. Update the dependent documents together. A matching filename or date is insufficient if the old analysis population or result remains in the text.
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. A heading identifies placement, not mandatory applicability.