Crafting Effective Summary Results Tables for Clinical Trial Registries

Importance of Summary Tables in Results Disclosure

Summary results tables are the foundation of data transparency on public clinical trial registries. These tables condense the trial’s key findings into structured, readable, and regulatory-compliant formats. Agencies like the FDA, EMA, and WHO require accurate tabular summaries for participant flow, baseline characteristics, outcomes, and adverse events.

Whether you are posting on ClinicalTrials.gov, EudraCT, or CTIS, proper table design ensures reviewers, patients, and regulators can interpret the study outcomes clearly. Poorly formatted or incomplete tables are a leading cause of Quality Control (QC) errors and result rejections.

Essential Table Types and What They Should Include

The four primary table categories common to most registries include:

• Participant Flow: Number of participants assigned, completed, or withdrawn at each phase.
• Baseline Characteristics: Demographic and clinical profile of the randomized population.
• Outcome Measures: Primary and secondary endpoint data with effect sizes and confidence intervals.
• Adverse Events: Summary of all reported adverse events, serious and non-serious, by arm.

Each table must be populated based on the analysis population defined in the statistical analysis plan (e.g., ITT or PP). The granularity required depends on the registry. CTIS and EudraCT support broader formats, while ClinicalTrials.gov enforces stricter structural and numerical rules through its PRS (Protocol Registration and Results System).

How to Structure a Baseline Characteristics Table

The baseline table helps readers determine whether the treatment groups were balanced before intervention. It must include:

• Age (mean ± SD or median + range)
• Sex (M/F counts and %)
• Disease duration or severity scale, if relevant
• Any other trial-specific covariates

Sample format:

Ensure that the totals match the number randomized in the participant flow table, as mismatches often trigger registry errors or flags.

Creating Effective Outcome Measure Tables

Outcome tables must show both statistical and clinical relevance. They typically include:

• Outcome label (e.g., “Change in Systolic Blood Pressure at Week 12”)
• Time point (Day, Week, Month)
• Value per group (Mean ± SD or Median + IQR)
• Between-group difference (if applicable)
• 95% Confidence Interval (CI)
• p-value (only if required by registry or protocol)

Tip: If results are unavailable at the time of posting, use “NA” but explain the reason in the free-text comment field of the registry.

Adverse Event Summary Table Formatting

Registries often require both all-cause and serious adverse event summaries. Adverse Event (AE) tables should follow standard MedDRA hierarchy or investigator terms. Include:

• Total number of participants experiencing ≥1 AE
• System organ class / Preferred term
• Severity (Mild, Moderate, Severe)
• Serious vs Non-serious status

Example Table:

Ensure AE totals reflect the safety population and align with source documents submitted to health authorities or used in the CSR.

Tools and Templates for Creating Tables

Several sponsors use predefined Excel templates to collate registry-compliant summary data. Tools such as:

• ClinicalTrials.gov PRS XML validator
• CTIS Module 5 format guidelines
• EudraCT Results QC checklist

can reduce formatting errors. Templates should include field-level instructions (e.g., decimal places, mandatory fields, allowable ranges) and be shared with all relevant stakeholders (Biostats, MW, QA).

For reusable templates, visit PharmaSOP.in.

Common Quality Control Failures and Fixes

Registry submissions often get flagged due to:

• Inconsistent participant numbers across tables
• Invalid statistical formats (e.g., CI without limits)
• Missing timepoints in outcome tables
• AE percentages exceeding 100%
• Unexplained “NA” entries

Before submission, perform a peer QC or use internal registry compliance tools. Annotated table maps that link to SAP and source data files are highly recommended.

Conclusion

Well-crafted summary tables not only fulfill a regulatory mandate but also build public and scientific trust. Consistency, traceability, and format accuracy are key to successful results posting. Training medical writers and data managers in these practices helps reduce delays and regulatory queries.

Explore more guidance on registry data formatting and transparency expectations at ICH.org.

Meeting U.S. Regulatory Requirements for Clinical Trial Results Disclosure

Introduction: The Importance of Posting Results

Results disclosure is a fundamental component of clinical trial transparency in the United States. While trial registration alerts the public to a study’s existence, posting trial results ensures that the findings—positive or negative—are available for patients, researchers, regulators, and healthcare professionals.

Under FDAAA 801 and the Final Rule (42 CFR Part 11), sponsors and responsible parties must post summary results for applicable clinical trials (ACTs) on ClinicalTrials.gov. Failure to comply can result in legal penalties, public notices of noncompliance, and loss of funding from government agencies like the NIH.

Who Must Report and What Is an Applicable Clinical Trial?

The obligation to disclose results falls on the “responsible party,” usually the trial sponsor or designated principal investigator. This includes:

• Drug, biologic, or device manufacturers sponsoring the study
• Academic institutions leading investigator-initiated trials
• Collaborative groups or consortia listed as sponsors or responsible parties

An Applicable Clinical Trial (ACT) is defined as a controlled clinical study (excluding most Phase I drug trials and small feasibility device studies) involving FDA-regulated products that are not exempt from IND or IDE requirements.

When Must Results Be Submitted?

Results for ACTs must be submitted within 12 months after the “Primary Completion Date”, which is the date when the final subject was examined or received an intervention for the purpose of final collection of data for the primary outcome measure.

In rare cases, responsible parties may request a delay or certification extension—for example, when FDA approval is pending—but these requests are time-bound and must be justified with supporting documentation.

What Must Be Included in Results Submissions?

ClinicalTrials.gov requires a structured and standardized results summary. The following modules must be completed:

• Participant Flow: Number of participants at each trial stage and reasons for dropout
• Baseline Characteristics: Demographics and baseline measures by arm/group
• Outcome Measures: Results for each pre-specified primary and secondary endpoint, including units and statistical analyses
• Adverse Events: Serious and other adverse events categorized by frequency and severity

All information must be entered into structured tables using ClinicalTrials.gov’s web-based submission system or through XML uploads via the Protocol Registration and Results System (PRS).

Adverse Events: Reporting Expectations

Reporting of adverse events is mandatory and includes two main tables:

1. Serious Adverse Events: Events that resulted in death, were life-threatening, required hospitalization, caused disability, or led to birth defects
2. Other (Non-Serious) Adverse Events: Events occurring at or above 5% frequency in any arm/group

Events must be categorized using MedDRA system organ class and preferred terms. If no events occurred, the table must still be submitted with a “0” entry to comply with formatting rules.

Quality Control and Posting Timeline

After submission, ClinicalTrials.gov conducts a Quality Control (QC) review, which typically takes 30–45 days. Sponsors will receive feedback and may need to revise and resubmit data if inconsistencies or missing fields are identified.

Once passed, the data is posted publicly and becomes searchable by the public. As of 2024, ClinicalTrials.gov lists the date results are submitted, posted, and revised, maintaining transparency of sponsor responsiveness.

Case Example: NIH-Funded Trial on Asthma

A multicenter trial funded by the NIH on asthma drug efficacy completed data collection in July 2023. The sponsor submitted results by July 2024 but failed initial QC due to incomplete outcome measure details.

After revision, results were posted in October 2024. Despite the delay, the sponsor avoided penalties by initiating submission on time and responding to QC comments promptly—highlighting the importance of early and complete submission.

Penalties for Late or Incomplete Reporting

The FDA has legal authority to enforce compliance with FDAAA 801. Penalties may include:

• Monetary fines up to $13,237 per day of noncompliance
• Public notices of violation listed on the FDA’s enforcement page
• Loss of eligibility for federal research grants
• Institutional damage to reputation and future partnerships

In 2021, the FDA issued over a dozen noncompliance notices, including to major universities and large CROs. Public enforcement has increased visibility into result posting performance.

Formatting and Common Pitfalls

Common issues that delay posting include:

• Inconsistent unit definitions across arms
• Failure to provide statistical analysis plans or p-values
• Missing denominators in AE tables
• Inadequate explanation of outcome time points

To avoid rejection, sponsors should prepare a results submission plan that mirrors the original protocol endpoints and statistical analysis methods, aligning submitted data with registered outcomes.

Best Practices for Results Disclosure Compliance

• Create a disclosure calendar aligned with your trial milestones
• Start results preparation before trial closeout using draft tables
• Assign roles to trained medical writers or disclosure leads
• Use validation tools provided by PRS to check format before submission
• Maintain internal QC reviews to catch issues prior to external QC

Larger organizations often implement SOPs and templates to streamline submissions and avoid inconsistencies across trial teams.

Conclusion: Transparency Begins with Results

Posting results on ClinicalTrials.gov is not a bureaucratic formality—it’s a legal, ethical, and scientific obligation. With increasing scrutiny from regulators, funders, and the public, trial sponsors must prioritize accuracy, timeliness, and completeness of their results submissions.

By understanding the FDAAA 801 requirements and building internal compliance structures, sponsors can not only avoid penalties but also contribute meaningfully to scientific progress and public trust in medical research.