eduKateSG · Why Science?
Turn many clinical studies into one traceable explanation of benefit, risk and appropriate use
Read FDA’s final July 2017 M4E(R2) guidance through the clinical overview, clinical summary, study reports, benefit-risk reasoning, tables, cross-references, global harmonisation and lifecycle updates.
A development programme can contain thousands of pages across pharmacology, efficacy, safety and individual studies. A reviewer needs more than a filing cabinet: the evidence must be organised so the central claim, supporting data and unresolved questions can be followed quickly.
FDA’s final July 2017 ICH M4E(R2) guidance describes the efficacy portion of the Common Technical Document. The revision strengthens the clinical overview and benefit-risk section while retaining detailed summaries and full study reports.
Did you know? CTD harmonisation does not make every regional decision identical. It creates a common technical structure so applicants do not have to rebuild the same scientific dossier from scratch for each authority.
For students, M4E(R2) is a lesson in synthesis. Evidence becomes more useful when summary, interpretation and source reports remain clearly linked.
Chapter index
Chapters 1–9: July 2017 final guidance, CTD modules, clinical overview, summary and study reports
- 1. The CTD gives global dossiers a common architecture
- 2. The July 2017 M4E(R2) guidance is final
- 3. Module 2 contains high-level clinical synthesis
- 4. Module 5 houses clinical study reports
- 5. The clinical overview explains the development programme
- 6. The clinical summary presents detailed evidence
- 7. Efficacy synthesis looks across studies
- 8. Safety synthesis needs exposure and context
- 9. Clinical pharmacology connects dose to use
Chapters 10–17: efficacy, safety, benefit-risk, tables, cross-references, regional context and lifecycle
- 10. Benefit-risk reasoning is an integrated argument
- 11. Therapeutic context changes the balance
- 12. Data quality affects every conclusion
- 13. Tables reveal patterns when definitions are stable
- 14. Cross-references preserve traceability
- 15. Regional material still belongs in the right place
- 16. Lifecycle submissions should preserve the story
- 17. A complete M4E(R2) receipt connects claim to source
CHAPTER 1 OF 17 · See the architecture
1. The CTD gives global dossiers a common architecture
The Common Technical Document organises quality, nonclinical and clinical information into a shared structure for regulatory submissions. M4E addresses efficacy and clinical material, helping authorities and applicants exchange information efficiently.
The practical value of the ctd gives global dossiers a common architecture appears when the scientific claim and its boundary stay together. The Common Technical Document organises quality, nonclinical and clinical information into a shared structure for regulatory submissions. M4E addresses efficacy and clinical material, helping authorities and applicants exchange information efficiently. Keep this boundary visible: A common structure does not replace region-specific law or scientific judgment.
Try this
Build an evidence map for the ctd gives global dossiers a common architecture. Trace a proposed label claim for the ctd gives global dossiers a common architecture from overview to table to study report. Add the owner and decision it supports. Keep this limit: A common structure does not replace region-specific law or scientific judgment.
A strong science note separates observation from interpretation. Trace a proposed label claim for the ctd gives global dossiers a common architecture from overview to table to study report. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Trace a proposed label claim for the ctd gives global dossiers a common architecture from overview to table to study report. Keep this boundary visible: A common structure does not replace region-specific law or scientific judgment.
FDA lists M4E(R2) as final guidance dated July 2017 under docket FDA-2015-D-3235, issued by CBER and CDER. FDA says the common format reduces reformatting and facilitates review and communication.
In the july 2017 m4e(r2) guidance is final, evidence has to match the decision being proposed. FDA lists M4E(R2) as final guidance dated July 2017 under docket FDA-2015-D-3235, issued by CBER and CDER. FDA says the common format reduces reformatting and facilitates review and communication. Preserve this guardrail: The overview must interpret evidence without selectively omitting inconvenient findings.
Try this
Test the reasoning for the july 2017 m4e(r2) guidance is final. Compare efficacy and safety populations for the july 2017 m4e(r2) guidance is final and explain every mismatch. Write the strongest alternative explanation. Respect this boundary: The overview must interpret evidence without selectively omitting inconvenient findings.
A strong science note separates observation from interpretation. Compare efficacy and safety populations for the july 2017 m4e(r2) guidance is final and explain every mismatch. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Compare efficacy and safety populations for the july 2017 m4e(r2) guidance is final and explain every mismatch. Keep this boundary visible: The overview must interpret evidence without selectively omitting inconvenient findings.
CHAPTER 3 OF 17 · See the architecture
3. Module 2 contains high-level clinical synthesis
The clinical overview and clinical summary sit in Module 2. They help a reviewer understand development strategy, findings and reasoning without replacing the detailed evidence in Module 5.
A trustworthy explanation of module 2 contains high-level clinical synthesis shows both what the evidence supports and what remains open. The clinical overview and clinical summary sit in Module 2. They help a reviewer understand development strategy, findings and reasoning without replacing the detailed evidence in Module 5. Remember: A summary cannot repair weaknesses in the underlying studies or data.
Try this
Audit the record for module 2 contains high-level clinical synthesis. Rewrite the benefit-risk section for module 2 contains high-level clinical synthesis with therapeutic context and uncertainty explicit. Mark every assumption and missing link. Preserve this caution: A summary cannot repair weaknesses in the underlying studies or data.
A strong science note separates observation from interpretation. Rewrite the benefit-risk section for module 2 contains high-level clinical synthesis with therapeutic context and uncertainty explicit. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Rewrite the benefit-risk section for module 2 contains high-level clinical synthesis with therapeutic context and uncertainty explicit. Keep this boundary visible: A summary cannot repair weaknesses in the underlying studies or data.
Module 5 contains tabular listings, study reports and related information organised by study type. A clear hierarchy and cross-reference system lets reviewers move from a conclusion to its underlying protocol, analysis and results.
The practical value of module 5 houses clinical study reports appears when the scientific claim and its boundary stay together. Module 5 contains tabular listings, study reports and related information organised by study type. A clear hierarchy and cross-reference system lets reviewers move from a conclusion to its underlying protocol, analysis and results. Keep this boundary visible: Cross-references are useful only when versions and destinations are stable.
Try this
Build an evidence map for module 5 houses clinical study reports. Audit module 5 houses clinical study reports for repeated numbers, inconsistent definitions and broken cross-references. Add the owner and decision it supports. Keep this limit: Cross-references are useful only when versions and destinations are stable.
A strong science note separates observation from interpretation. Audit module 5 houses clinical study reports for repeated numbers, inconsistent definitions and broken cross-references. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Audit module 5 houses clinical study reports for repeated numbers, inconsistent definitions and broken cross-references. Keep this boundary visible: Cross-references are useful only when versions and destinations are stable.
CHAPTER 5 OF 17 · Summarise the evidence
5. The clinical overview explains the development programme
The overview discusses scientific rationale, trial design choices, regulatory guidance, ethical considerations, foreign data and important limitations. It should explain why the programme can answer the proposed indication and use.
In the clinical overview explains the development programme, evidence has to match the decision being proposed. The overview discusses scientific rationale, trial design choices, regulatory guidance, ethical considerations, foreign data and important limitations. It should explain why the programme can answer the proposed indication and use. Preserve this guardrail: A common structure does not replace region-specific law or scientific judgment.
Try this
Test the reasoning for the clinical overview explains the development programme. Trace a proposed label claim for the clinical overview explains the development programme from overview to table to study report. Write the strongest alternative explanation. Respect this boundary: A common structure does not replace region-specific law or scientific judgment.
A strong science note separates observation from interpretation. Trace a proposed label claim for the clinical overview explains the development programme from overview to table to study report. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Trace a proposed label claim for the clinical overview explains the development programme from overview to table to study report. Keep this boundary visible: A common structure does not replace region-specific law or scientific judgment.
CHAPTER 6 OF 17 · Summarise the evidence
6. The clinical summary presents detailed evidence
Summaries cover biopharmaceutics, clinical pharmacology, efficacy and safety, often using tables and figures. They should be factual, balanced and sufficiently detailed for comparison across studies, populations and doses.
A trustworthy explanation of the clinical summary presents detailed evidence shows both what the evidence supports and what remains open. Summaries cover biopharmaceutics, clinical pharmacology, efficacy and safety, often using tables and figures. They should be factual, balanced and sufficiently detailed for comparison across studies, populations and doses. Remember: The overview must interpret evidence without selectively omitting inconvenient findings.
Try this
Audit the record for the clinical summary presents detailed evidence. Compare efficacy and safety populations for the clinical summary presents detailed evidence and explain every mismatch. Mark every assumption and missing link. Preserve this caution: The overview must interpret evidence without selectively omitting inconvenient findings.
A strong science note separates observation from interpretation. Compare efficacy and safety populations for the clinical summary presents detailed evidence and explain every mismatch. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Compare efficacy and safety populations for the clinical summary presents detailed evidence and explain every mismatch. Keep this boundary visible: The overview must interpret evidence without selectively omitting inconvenient findings.
The dossier should explain consistency, effect magnitude, onset, durability, dose response, subgroups, missing data and sensitivity analyses. A list of statistically significant endpoints does not establish a coherent clinical benefit.
The practical value of efficacy synthesis looks across studies appears when the scientific claim and its boundary stay together. The dossier should explain consistency, effect magnitude, onset, durability, dose response, subgroups, missing data and sensitivity analyses. A list of statistically significant endpoints does not establish a coherent clinical benefit. Keep this boundary visible: A summary cannot repair weaknesses in the underlying studies or data.
Try this
Build an evidence map for efficacy synthesis looks across studies. Rewrite the benefit-risk section for efficacy synthesis looks across studies with therapeutic context and uncertainty explicit. Add the owner and decision it supports. Keep this limit: A summary cannot repair weaknesses in the underlying studies or data.
A strong science note separates observation from interpretation. Rewrite the benefit-risk section for efficacy synthesis looks across studies with therapeutic context and uncertainty explicit. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Rewrite the benefit-risk section for efficacy synthesis looks across studies with therapeutic context and uncertainty explicit. Keep this boundary visible: A summary cannot repair weaknesses in the underlying studies or data.
CHAPTER 8 OF 17 · Summarise the evidence
8. Safety synthesis needs exposure and context
Safety evaluation considers the size and duration of exposure, adverse events, serious risks, laboratory findings, discontinuations and relevant subgroups. Event counts need denominators, timing, comparator and ascertainment context.
In safety synthesis needs exposure and context, evidence has to match the decision being proposed. Safety evaluation considers the size and duration of exposure, adverse events, serious risks, laboratory findings, discontinuations and relevant subgroups. Event counts need denominators, timing, comparator and ascertainment context. Preserve this guardrail: Cross-references are useful only when versions and destinations are stable.
Try this
Test the reasoning for safety synthesis needs exposure and context. Audit safety synthesis needs exposure and context for repeated numbers, inconsistent definitions and broken cross-references. Write the strongest alternative explanation. Respect this boundary: Cross-references are useful only when versions and destinations are stable.
A strong science note separates observation from interpretation. Audit safety synthesis needs exposure and context for repeated numbers, inconsistent definitions and broken cross-references. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Audit safety synthesis needs exposure and context for repeated numbers, inconsistent definitions and broken cross-references. Keep this boundary visible: Cross-references are useful only when versions and destinations are stable.
CHAPTER 9 OF 17 · Interpret benefit-risk
9. Clinical pharmacology connects dose to use
Pharmacokinetics, pharmacodynamics, intrinsic and extrinsic factors, interactions and exposure-response analyses support dose selection and instructions. The summary should show how these findings shaped trials and proposed labelling.
A trustworthy explanation of clinical pharmacology connects dose to use shows both what the evidence supports and what remains open. Pharmacokinetics, pharmacodynamics, intrinsic and extrinsic factors, interactions and exposure-response analyses support dose selection and instructions. The summary should show how these findings shaped trials and proposed labelling. Remember: A common structure does not replace region-specific law or scientific judgment.
Try this
Audit the record for clinical pharmacology connects dose to use. Trace a proposed label claim for clinical pharmacology connects dose to use from overview to table to study report. Mark every assumption and missing link. Preserve this caution: A common structure does not replace region-specific law or scientific judgment.
A strong science note separates observation from interpretation. Trace a proposed label claim for clinical pharmacology connects dose to use from overview to table to study report. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Trace a proposed label claim for clinical pharmacology connects dose to use from overview to table to study report. Keep this boundary visible: A common structure does not replace region-specific law or scientific judgment.
CHAPTER 10 OF 17 · Interpret benefit-risk
10. Benefit-risk reasoning is an integrated argument
M4E(R2) emphasises a succinct discussion of therapeutic context, benefits, risks, uncertainty and risk-management implications. It should explain why the proposed use is favourable, including where evidence is less certain.
The practical value of benefit-risk reasoning is an integrated argument appears when the scientific claim and its boundary stay together. M4E(R2) emphasises a succinct discussion of therapeutic context, benefits, risks, uncertainty and risk-management implications. It should explain why the proposed use is favourable, including where evidence is less certain. Keep this boundary visible: The overview must interpret evidence without selectively omitting inconvenient findings.
Try this
Build an evidence map for benefit-risk reasoning is an integrated argument. Compare efficacy and safety populations for benefit-risk reasoning is an integrated argument and explain every mismatch. Add the owner and decision it supports. Keep this limit: The overview must interpret evidence without selectively omitting inconvenient findings.
A strong science note separates observation from interpretation. Compare efficacy and safety populations for benefit-risk reasoning is an integrated argument and explain every mismatch. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Compare efficacy and safety populations for benefit-risk reasoning is an integrated argument and explain every mismatch. Keep this boundary visible: The overview must interpret evidence without selectively omitting inconvenient findings.
CHAPTER 11 OF 17 · Interpret benefit-risk
11. Therapeutic context changes the balance
Disease severity, unmet need, available therapy, population, treatment duration and patient perspective affect how benefits and risks are weighed. The same numerical effect may matter differently in another setting.
In therapeutic context changes the balance, evidence has to match the decision being proposed. Disease severity, unmet need, available therapy, population, treatment duration and patient perspective affect how benefits and risks are weighed. The same numerical effect may matter differently in another setting. Preserve this guardrail: A summary cannot repair weaknesses in the underlying studies or data.
Try this
Test the reasoning for therapeutic context changes the balance. Rewrite the benefit-risk section for therapeutic context changes the balance with therapeutic context and uncertainty explicit. Write the strongest alternative explanation. Respect this boundary: A summary cannot repair weaknesses in the underlying studies or data.
A strong science note separates observation from interpretation. Rewrite the benefit-risk section for therapeutic context changes the balance with therapeutic context and uncertainty explicit. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Rewrite the benefit-risk section for therapeutic context changes the balance with therapeutic context and uncertainty explicit. Keep this boundary visible: A summary cannot repair weaknesses in the underlying studies or data.
Protocol deviations, missing outcomes, multiplicity, unblinding, site issues and data-integrity concerns should be carried into the synthesis. Clean tables cannot erase limitations in how evidence was generated.
A trustworthy explanation of data quality affects every conclusion shows both what the evidence supports and what remains open. Protocol deviations, missing outcomes, multiplicity, unblinding, site issues and data-integrity concerns should be carried into the synthesis. Clean tables cannot erase limitations in how evidence was generated. Remember: Cross-references are useful only when versions and destinations are stable.
Try this
Audit the record for data quality affects every conclusion. Audit data quality affects every conclusion for repeated numbers, inconsistent definitions and broken cross-references. Mark every assumption and missing link. Preserve this caution: Cross-references are useful only when versions and destinations are stable.
A strong science note separates observation from interpretation. Audit data quality affects every conclusion for repeated numbers, inconsistent definitions and broken cross-references. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Audit data quality affects every conclusion for repeated numbers, inconsistent definitions and broken cross-references. Keep this boundary visible: Cross-references are useful only when versions and destinations are stable.
CHAPTER 13 OF 17 · Keep it traceable
13. Tables reveal patterns when definitions are stable
Standardised displays make studies, doses, endpoints and adverse events easier to compare. Footnotes should disclose pooling rules, analysis populations, coding versions and important differences rather than hiding them.
The practical value of tables reveal patterns when definitions are stable appears when the scientific claim and its boundary stay together. Standardised displays make studies, doses, endpoints and adverse events easier to compare. Footnotes should disclose pooling rules, analysis populations, coding versions and important differences rather than hiding them. Keep this boundary visible: A common structure does not replace region-specific law or scientific judgment.
Try this
Build an evidence map for tables reveal patterns when definitions are stable. Trace a proposed label claim for tables reveal patterns when definitions are stable from overview to table to study report. Add the owner and decision it supports. Keep this limit: A common structure does not replace region-specific law or scientific judgment.
A strong science note separates observation from interpretation. Trace a proposed label claim for tables reveal patterns when definitions are stable from overview to table to study report. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Trace a proposed label claim for tables reveal patterns when definitions are stable from overview to table to study report. Keep this boundary visible: A common structure does not replace region-specific law or scientific judgment.
A concise overview can point to summaries and full reports instead of repeating them. Links, document identifiers and consistent naming let reviewers verify claims and reduce the risk of contradictory versions.
In cross-references preserve traceability, evidence has to match the decision being proposed. A concise overview can point to summaries and full reports instead of repeating them. Links, document identifiers and consistent naming let reviewers verify claims and reduce the risk of contradictory versions. Preserve this guardrail: The overview must interpret evidence without selectively omitting inconvenient findings.
Try this
Test the reasoning for cross-references preserve traceability. Compare efficacy and safety populations for cross-references preserve traceability and explain every mismatch. Write the strongest alternative explanation. Respect this boundary: The overview must interpret evidence without selectively omitting inconvenient findings.
A strong science note separates observation from interpretation. Compare efficacy and safety populations for cross-references preserve traceability and explain every mismatch. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Compare efficacy and safety populations for cross-references preserve traceability and explain every mismatch. Keep this boundary visible: The overview must interpret evidence without selectively omitting inconvenient findings.
CHAPTER 15 OF 17 · Keep it traceable
15. Regional material still belongs in the right place
Module 1 contains region-specific administrative content, while Modules 2 through 5 follow the harmonised structure. Applicants must also follow current FDA electronic submission standards and regional requirements.
A trustworthy explanation of regional material still belongs in the right place shows both what the evidence supports and what remains open. Module 1 contains region-specific administrative content, while Modules 2 through 5 follow the harmonised structure. Applicants must also follow current FDA electronic submission standards and regional requirements. Remember: A summary cannot repair weaknesses in the underlying studies or data.
Try this
Audit the record for regional material still belongs in the right place. Rewrite the benefit-risk section for regional material still belongs in the right place with therapeutic context and uncertainty explicit. Mark every assumption and missing link. Preserve this caution: A summary cannot repair weaknesses in the underlying studies or data.
A strong science note separates observation from interpretation. Rewrite the benefit-risk section for regional material still belongs in the right place with therapeutic context and uncertainty explicit. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Rewrite the benefit-risk section for regional material still belongs in the right place with therapeutic context and uncertainty explicit. Keep this boundary visible: A summary cannot repair weaknesses in the underlying studies or data.
CHAPTER 16 OF 17 · Keep it traceable
16. Lifecycle submissions should preserve the story
Supplements, new indications and postapproval evidence add to an existing dossier. Versioning, clear scope and links to prior evidence show what changed and prevent old conclusions from being silently repurposed.
The practical value of lifecycle submissions should preserve the story appears when the scientific claim and its boundary stay together. Supplements, new indications and postapproval evidence add to an existing dossier. Versioning, clear scope and links to prior evidence show what changed and prevent old conclusions from being silently repurposed. Keep this boundary visible: Cross-references are useful only when versions and destinations are stable.
Try this
Build an evidence map for lifecycle submissions should preserve the story. Audit lifecycle submissions should preserve the story for repeated numbers, inconsistent definitions and broken cross-references. Add the owner and decision it supports. Keep this limit: Cross-references are useful only when versions and destinations are stable.
A strong science note separates observation from interpretation. Audit lifecycle submissions should preserve the story for repeated numbers, inconsistent definitions and broken cross-references. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Audit lifecycle submissions should preserve the story for repeated numbers, inconsistent definitions and broken cross-references. Keep this boundary visible: Cross-references are useful only when versions and destinations are stable.
CHAPTER 17 OF 17 · Keep it traceable
17. A complete M4E(R2) receipt connects claim to source
The receipt records indication, population, dose, development rationale, study inventory, endpoints, efficacy and safety synthesis, pharmacology, data-quality issues, benefit-risk reasoning, uncertainty, CTD locations, regional additions and lifecycle changes. It makes review reproducible.
In a complete m4e(r2) receipt connects claim to source, evidence has to match the decision being proposed. The receipt records indication, population, dose, development rationale, study inventory, endpoints, efficacy and safety synthesis, pharmacology, data-quality issues, benefit-risk reasoning, uncertainty, CTD locations, regional additions and lifecycle changes. It makes review reproducible. Preserve this guardrail: A common structure does not replace region-specific law or scientific judgment.
Try this
Test the reasoning for a complete m4e(r2) receipt connects claim to source. Trace a proposed label claim for a complete m4e(r2) receipt connects claim to source from overview to table to study report. Write the strongest alternative explanation. Respect this boundary: A common structure does not replace region-specific law or scientific judgment.
A strong science note separates observation from interpretation. Trace a proposed label claim for a complete m4e(r2) receipt connects claim to source from overview to table to study report. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Trace a proposed label claim for a complete m4e(r2) receipt connects claim to source from overview to table to study report. Keep this boundary visible: A common structure does not replace region-specific law or scientific judgment.
M4E(R2) clinical evidence architecture
| Question | Evidence to capture | Boundary to retain |
|---|---|---|
| Why was it studied? | Clinical overview and development rationale | Explain choices and limits |
| What was found? | Detailed pharmacology, efficacy and safety summaries | Use consistent definitions |
| Where is the proof? | Module 5 study reports and datasets | Keep claims traceable |
| What does it mean? | Therapeutic context and benefit-risk reasoning | Uncertainty belongs in the decision |
Science learning becomes useful when a student can show where a claim came from, why it applies and where it stops. Continue with the eduKate Science Learning Hub, compare choices in the Education Hub, and connect these habits to career pathways built from subject capabilities.
M4E(R2) turns an enormous clinical archive into a navigable scientific argument. Its strength is the path it creates—from the proposed use, through balanced synthesis, down to the exact study evidence—so important decisions can be checked rather than merely accepted.
Primary sources and verification date
Source status checked 26 October 2026. FDA guidance describes the agency’s current thinking and does not replace applicable statutes, regulations or product-specific communication with FDA.
- FDA: ICH M4E(R2) CTD Efficacy — Final guidance, July 2017; docket FDA-2015-D-3235.
- FDA: Full M4E(R2) guidance PDF — Official clinical overview, summary and Module 5 structure.
- FDA: Electronic Common Technical Document — Current FDA eCTD formats and technical submission context, checked 26 October 2026.