Skip to content
Assyro AI
Assyro AI
Module 5
5.4
Guide

Prepare Module 5 clinical literature references

Deliver identifiable, accessible source documents and connect each one to the clinical claim it supports.

By Assyro
Published
Article updated FDA · eCTD v4.0 placement
On this page

What should the Module 5 clinical reference package include?

Provide the identifiable documents supporting the relevant clinical citations, including important publications and applicable official advice or meeting records. Check their actual versions, content and context. Distinguish a reference used for background from published evidence serving a more specific efficacy or safety report role.

Before you begin

Clinical reference material in 5.4. Publications serving as primary clinical evidence may require report-family placement as well as precise cross-references.

What you will prepare: A deduplicated reference package with verified identity, accurate citations and visible evidence limitations.

Collect the documents behind the citations

Export references from the Clinical Overview, Clinical Summary and relevant technical reports, then obtain the actual cited versions. M4E's reference section includes important publications and relevant official advice or meeting records; it is not limited to journal articles. Record title, authors or issuing body, date, identifier and the dossier locations that cite it.

Distinguish a bibliographic record from an available document. A DOI, abstract or working hyperlink does not prove the complete source is in the package. If only an abstract is available, label that limitation and ask the scientific owner whether it supports the intended claim. Do not expand an abstract into a fabricated full study report.

Check what the source actually supports

Read the relevant passage together with the population, product, endpoint and study limitations. Record corrections or retractions where identified, and determine whether the cited version remains the appropriate evidence. For agency advice, preserve the actual application context and status; a meeting discussion is not automatically an approval or a universal rule.

If a publication provides important evidence for the claimed efficacy rather than background context, assess the appropriate 5.3.5 report-family treatment with the regulatory owner. Avoid a blanket rule that every published paper belongs only in 5.4. Use one authoritative copy where appropriate and precise cross-references rather than independently maintained duplicates.

Verify the citation-to-file path

Fictional exercise: the clinical summary cites a final article, but the supplied file is an earlier conference abstract with a shorter follow-up period. Compare identity and results, obtain the intended article or qualify the claim to the available source. Renaming the abstract with the article's title does not resolve the evidence gap.

Use consistent document titles and inspect legibility, page completeness and reference links in the assembled package. Resolve duplicate records that have different spellings or identifiers. The final handoff should let a reviewer move from a material clinical assertion to the exact supporting document without guessing which version was intended.

Assign each reference a role before checking its filename

Use the following record to make source identity and clinical relevance separate review questions.

Assign each reference a role before checking its filename
RoleRecordQualification to preserve
BackgroundCited statement and exact source passageContext is not direct evidence for this product
Clinical evidencePopulation, product, outcome and follow-upApplicability and reporting limitations
Regulatory adviceIssuer, date, application context and statusAdvice is not automatically approval or a universal rule
Updated publicationEarlier version, correction and affected claimsWhich evidence changed and which remains valid

Review exercise: an official meeting record is cited as if it approved the final study design, but the discussion concerned an earlier proposal. Retain the actual record and ask the regulatory owner to resolve the extent of the advice. Do not improve the apparent support by paraphrasing away the qualification.

Check the final citation-to-file path from the clinical overview and the clinical summary reference inventory. One authoritative source copy can support several precise references without becoming several independent pieces of evidence.

Your preparation checklist

0/4 checked

Use this to track your review in this visit. Checks are not saved and do not establish regulatory compliance.

Frequently asked questions

Is section 5.4 limited to journal articles?

No. M4E includes referenced documents such as important publications, official meeting minutes and other relevant regulatory guidance or advice. Identify the actual document and its context so reviewers can assess what the citation supports.

Can an abstract be supplied under the title of the final article?

No. An abstract and final article can differ in methods, follow-up and results. Identify the document actually available and obtain the intended source or qualify the claim. Renaming the file cannot resolve an evidence-version mismatch.

Does all published clinical evidence belong only in the literature section?

No. A publication important to the efficacy demonstration may need treatment in the appropriate clinical report family under M4E. Assess its role and use precise cross-references rather than assuming publication format alone determines its only location.

Sources and revisions

Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.

Guidance

FDA M4E(R2): The CTD: Efficacy ↗

July 2017, Revision 1, final. Module 5, printed pp.56–64. Organization guidance, not a list of studies required for every application. Reopened September 22, 2026.

Technical specification · placement only

FDA eCTD v4.0 comprehensive hierarchy ↗

Version 2.2, February 2025. Section 5.4. A heading identifies placement, not mandatory applicability.

Talk with Assyro about your next document