Skip to content

Integrated Summary of Efficacy (ISE) vs Integrated Summary of Safety (ISS): Key Differences and FDA Requirements

Learn what the Integrated Summary of Efficacy and Integrated Summary of Safety are, what they contain, and where they belong in an FDA submission.

An Integrated Summary of Efficacy (ISE) and an Integrated Summary of Safety (ISS) are detailed, integrated analyses of clinical evidence compiled across all relevant studies supporting a marketing application. The ISE evaluates the evidence of drug effectiveness across those studies, while the ISS assesses the overall safety profile. 

Both go beyond summarizing individual Clinical Study Reports by incorporating cross-study analyses that pool data, examine consistency, and present findings across the full clinical program.

Together, they give regulators what no single CSR can: a complete view of how a product performs across the evidence base.

What Are the Key Differences Between ISE and ISS?

Both documents draw on the same clinical program but serve distinct regulatory functions:


ISE

ISS


Primary purpose

Establish effectiveness across relevant clinical studies

Evaluate overall safety across relevant clinical studies


Principal evidence

Efficacy endpoints, study outcomes, subgroup findings

Adverse events, exposure, laboratory findings, safety signals


Analytical focus

Consistency of effects, dose-response, and subgroup differences

Adverse event frequencies, exposure patterns, and safety differences


Regulatory role

Supports evidence for proposed indications and dosing

Supports assessment of risks and the overall safety profile


Regulators need both analyses to reach a benefit-risk conclusion on a marketing application. The ISE establishes whether the clinical evidence supports the proposed indication. The ISS establishes whether the product's safety profile is acceptable for that use. Neither document can substitute for the other.

What Information Should Be Included in an ISE and ISS?

Researcher in a lab coat and face mask typing at a desktop computer in a laboratory

The content of an ISS and an ISE document follows the structure of the clinical evidence they synthesize.

What Evidence Should an Integrated Summary of Efficacy Contain?

An ISE covers these areas of clinical evidence:

  • Clinical Study Overview: List the relevant studies, their designs, and principal efficacy findings, including the justification for which studies were included in the integrated analysis.

  • Integrated Efficacy Analysis: Compare individual and pooled results across studies to evaluate the consistency of effectiveness, including study-to-study comparisons and justification where reliance on a single study is proposed.

  • Subgroup and Dose-Response Analyses: Examine effectiveness data by sex, age, and racial subgroups, and evaluate dose-response relationships, onset and duration of effect, and any relevant differences across subpopulations.

  • Supporting Evidence: Include comparisons with alternative drugs, long-term effects, tolerance, withdrawal findings, and exploratory results where applicable.

What Information Should an Integrated Summary of Safety Contain?

An ISS addresses safety across four categories of clinical data:

  • Clinical Safety Overview: Identify the relevant studies included in the analysis and summarize their safety findings, with phase I data from healthy volunteers presented separately where applicable.

  • Exposure and Demographics: Examine the overall extent and duration of drug exposure across patient numbers, demographic subgroups, and dose levels.

  • Adverse Event Analysis: Cover common and serious adverse events, deaths, discontinuations due to adverse events, and adverse events of special interest, including occurrence rates across all studies.

  • Additional Safety Assessments: Include laboratory findings, vital signs, ECG results, potential drug interactions, dose-response analysis of adverse effects, and long-term safety findings of six months or more, as applicable.

Both documents incorporate relevant tables, figures, statistical methods, and supporting appendices. 

What Are the FDA Regulatory Requirements for ISE and ISS?

FDA guidance for an Integrated Summary of Efficacy and an Integrated Summary of Safety varies by application type and submission format.

When Are Integrated Summaries Required for FDA Submissions?

The FDA requires ISE and ISS analyses for New Drug Applications (NDAs) under 21 CFR 314.50(d)(5)(v) and (d)(5)(vi). There are no corresponding regulations requiring their inclusion in Biologics License Applications (BLAs), though the FDA encourages applicants to provide them.

This requirement is specific to the United States. In Europe and Japan, the content of an ISE and ISS is captured within the CTD format as clinical summaries and Clinical Study Reports, without a separately named integrated summary document being mandated.

Where Do ISE and ISS Belong in the Common Technical Document (CTD)?

The FDA's guidance places the full ISE and ISS in Module 5, section 5.3.5.3 of the CTD, titled “Reports of Analyses of Data from More than One Study.”

CTD Section

Documentation

Module 2.7.3

Summary of Clinical Efficacy (SCE): Shorter summary derived from the ISE

Module 2.7.4

Summary of Clinical Safety (SCS): Shorter summary derived from the ISS

Module 5.3.5.3

Full ISE and ISS: Detailed integrated analyses with appendices

The Module 2 clinical summaries contain summarized information derived from the full ISE and ISS. They are not substitutes for the full analyses. Placing the full documents only in Module 2 can make an application incomplete and lead to a refusal-to-file action. A limited exception applies where narratives may be placed in Module 2 and appendices in Module 5, with cross-references in both locations.

Which CDISC Data Standards Apply to Integrated Summaries?

CDISC standards govern the structure and submission of clinical data supporting integrated analyses. 

  • SDTM (Study Data Tabulation Model) standardizes how individual study data is structured for submission.

  • ADaM (Analysis Data Model) defines how analysis datasets and statistical outputs are derived and documented. 

  • Define-XML provides dataset metadata, variable definitions, and reviewer guides that allow FDA staff to navigate submitted datasets.

For integrated summaries, teams must document data transformations and maintain traceability between integrated outputs and their source datasets. Any legacy-to-CDISC conversion approach should be documented in the clinical study data reviewer's guide. 

The integration method chosen, whether from integrated SDTM, study ADaM, or legacy analysis data, can vary depending on the studies included and whether the data was designed for integration from the outset.

What Challenges Arise When Preparing Integrated Summaries of Safety and Efficacy?

ISE and ISS preparation is among the most resource-intensive deliverables in a regulatory submission program. The complexity compounds when studies were not designed with integration in mind:

  • Data Harmonisation: Differences in study design, endpoints, analysis populations, and coding dictionaries complicate data integration. 

  • Inconsistent Data Standards: Legacy datasets and differing CDISC implementation versions may require additional mapping. Teams must decide whether legacy studies need single-study CDISC conversion or can stand alongside standardized datasets.

  • Statistical Planning: Integrated Statistical Analysis Plans must define pooling methods, treatment groupings, and analysis approaches across studies, with mock shells developed before programming begins.

  • Data Traceability: Integrated counts must be checked against individual study outputs, and any data transformation approach must be documented in the reviewer's guide to support FDA inspection.

  • Cross-Functional Reviews: Medical writers, statisticians, programmers, and regulatory teams must coordinate document development, data verification, and QC across the full integrated package.

Plan study integration, integrated SAPs, TFL production, and quality control early. Waiting until final document preparation to address data gaps, pooling decisions, or legacy dataset gaps can increase submission-timeline risk.

How Can AI Support Integrated Clinical Summary Documentation?

Preparing ISE and ISS documentation involves coordinating clinical source data, statistical outputs, and narrative sections across a large and interconnected document set. AuroraPrime, AlphaLife Sciences' AI platform for clinical documentation and regulatory authoring, addresses the most demanding stages of that process:

  • Automated Content Drafting: AuroraPrime ingests clinical source documents, including protocols and SAPs, to support automated regulatory documentation across data-independent sections, reducing the manual drafting effort required at the start of document production.

  • Data Synchronization: TFL data connects directly to generated document content. When source data changes, AuroraPrime detects the upstream update and automatically revises linked sections, maintaining consistency across the integrated document package.

  • GenAI Quality Assurance: Automated QC checks evaluate generated content for inconsistencies, omissions, and unsupported statements before human review begins. Quality criteria are configurable to align with document-specific requirements.

  • Clinical Documentation Support: AuroraPrime supports Summary of Clinical Efficacy (SCE) and Summary of Clinical Safety (SCS) document production, covering Module 2 deliverables derived from and required to remain consistent with the full ISE and ISS.

Explore AuroraPrime's AI-powered regulatory document authoring solutions.

Close