Can DSUR appendices be submitted electronically?

Yes. Electronic submissions are standard for IND and safety reporting; ensure file formats meet agency requirements and retain an auditable trail of who prepared and signed each file.

Are electronic signatures legally valid for these documents?

Electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted; ensure intent, consent, attribution, and retention capabilities are met.

Do I need a BAA for eSignature platforms?

If appendices contain protected health information, a HIPAA Business Associate Agreement (BAA) is required with vendors that access PHI; confirm BAA availability and relevant controls.

What file format should I use for long-term storage?

Use PDF/A for archival preservation and include original export metadata; for agency schemas, provide XML when required by the receiving authority.

How long must I keep source records and appendices?

Retain safety and source records per regulatory minima (see 21 CFR Part 312 guidance), HIPAA (45 CFR §164.530(j) for PHI) and financial rules (IRC §6501(a)), and longer where state law requires it.

Who signs and certifies the appendices?

Authorized sponsor representatives, pharmacovigilance leads, or designated regulatory officers typically sign submissions; document signatory authority in internal SOPs and maintain signature attestations.

Electronic Signature
Templates
Healthcare
Healthcare DSUR Appendices

Healthcare DSUR Appendices

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

HEALTHCARE DSUR APPENDICES

Sponsor Name: Clinical Study Title:

Protocol/Reference Number: DSUR Report Reference Number:

Reporting Period Start: End:

Index of Appendices Included

Indicate which appendices are included with this DSUR submission by checking the applicable items and attaching the referenced documents.

Appendices (check all that apply): Investigator / Site Listing Ethics Committee Listings Patient Case Narratives Line Listings of Adverse Events Summary of Serious Adverse Events Safety Signal Evaluation Regulatory Correspondence Data Monitoring Committee Reports Other

If Other, describe:

Investigator and Site Listings

Provide a comprehensive listing of principal investigators and investigational sites included in this reporting period. Include name, institution, site identifier, and contact information for each.

Ethics Committees and Approval Details

Provide names of reviewing ethics committees, approval reference numbers, and dates of approval or termination relevant to this reporting period.

Patient / Participant Information (for included case narratives)

If full identifiers are included, obtain explicit consent. If data are de‑identified, indicate the coded identifier and provide limited demographics below.

Participant Full Name (if applicable): Participant ID / Code:

Date of Birth:

Gender: Male Female Other/Prefer not to say

Address:

Phone:

Emergency Contact (Name, Phone, Relationship):

Insurance / Coverage Information

Insurance Provider:

Policy Number:

Group Number / Subscriber:

Medical History and Current Medications

Current Medications (include dose and frequency): Known Allergies (drug, food, other): Prior Surgeries / Hospitalizations: Chronic Conditions / Relevant Medical History:

Summary of Serious Adverse Events (SAEs)

Provide a concise summary of SAEs reported during the reporting period. Include event description, onset date, outcome, causality assessment, and seriousness criteria applicable.

SAE #1 — Brief Description:

Onset Date:

Outcome:

Causality Assessment: Related Not Related Unknown

SAE #1 — Applicable Seriousness Criteria (check all that apply):

Death Life‑threatening Hospitalization/prolonged hospitalization Persistent/significant disability Congenital anomaly/birth defect Other

SAE #1 — Narrative (concise clinical course and actions taken): SAE #2 — Brief Description:

Onset Date:

Outcome:

Causality Assessment: Related Not Related Unknown

SAE #2 — Applicable Seriousness Criteria (check all that apply):

Death Life‑threatening Hospitalization/prolonged hospitalization Persistent/significant disability Congenital anomaly/birth defect Other

SAE #2 — Narrative (concise clinical course and actions taken):

Expedited Reports and Regulatory Correspondence

Summarize expedited safety reports submitted during the reporting period and record key regulatory interactions and outcomes.

Regulatory Correspondence Summary:

Data Monitoring Committee / Signal Evaluation Findings

DMC Conclusions / Signal Assessment:

Data Privacy, Consent and Authorization

The undersigned certifies that all patient information included in these appendices is provided in accordance with applicable data protection and human subjects regulations. Identifiable information will not be disclosed without explicit informed consent. When case narratives include identifiers, explicit written consent has been obtained and is retained by the sponsor or investigator.

Authorization Expiration Date (if consent provided):

Patient has provided written consent for inclusion of identifiable information Patient has withdrawn consent during reporting period

By signing below, the signatory attests that the information contained in the attached appendices is complete and accurate to the best of their knowledge, that all necessary consents and approvals have been obtained, and that any disclosed personal data is being processed in accordance with applicable legal and ethical obligations. The signatory acknowledges the right to withdraw consent and the obligation to notify the sponsor and regulator of any material change affecting safety information.

If signing on behalf of the participant, indicate relationship (e.g., parent, legal guardian):

Patient / Signatory Printed Name:

By:

Date:

What the Healthcare DSUR Appendices Are

The Healthcare DSUR Appendices are the supplemental materials submitted alongside a Development Safety Update Report (DSUR) to document detailed safety data, line listings, aggregate summaries, and regulatory correspondence for an investigational medicinal product. Appendices typically include patient-level case narratives, tabulated adverse event listings, safety signal analyses, periodic aggregate safety tables, and copies of relevant safety communications. In U.S. contexts DSUR content often supports IND annual reports or safety submissions to FDA under 21 CFR; appendices provide the supporting evidence reviewers use to evaluate a sponsor’s safety conclusions and proposed risk-mitigation actions.

Why Complete Healthcare DSUR Appendices Carefully

Accurate, well-structured appendices ensure regulators can verify safety assessments, reduce follow-up questions, and support timely review of ongoing clinical development. Clear appendices also document sponsor compliance with reporting obligations and create an auditable safety record for inspections or safety signal follow-up.

Who Prepares and Reviews DSUR Appendices

Sponsors, safety physicians, pharmacovigilance teams, clinical data managers, and regulatory affairs professionals collaborate to prepare DSUR appendices.

Sponsor pharmacovigilance team: Prepares aggregate analyses and interprets safety signals for regulatory submission and internal risk management.
Clinical data management: Produces line listings, case report extracts, and reconciled datasets for submission.
Regulatory affairs specialists: Ensure format, required content, and routing align with IND or global regulatory expectations.

External reviewers and regulators use the appendices to validate conclusions in the DSUR and to decide whether additional action or information is needed.

Core Components to Include in a Professional Appendix Set

Appendices should be organized, indexed, and cross-referenced to the main DSUR sections to facilitate rapid review and traceability.

Case Line Listings

Comprehensive patient-level listings with unique subject ID, event description, onset date, outcome, seriousness, relationship assessment, and concurrent medications to allow case-by-case review.

Narratives

Concise clinical narratives for serious or sentinel events that summarize chronology, interventions, relevant labs, and investigator/sponsor causality assessments.

Aggregate Tables

Tabulations by MedDRA preferred term, system organ class, severity, and seriousness providing numerator/denominator context and exposure-adjusted incidence rates where appropriate.

Safety Signal Analysis

Documentation of detected signals, methods used (e.g., disproportionality or trend analysis), supporting data, and conclusions or proposed follow-up actions.

Regulatory Correspondence

Copies of communications with health authorities, IND amendments, and prior safety committee recommendations relevant to the reporting period.

Data Listings Index

A clear index mapping each appendix file name to the DSUR section and describing file format and generation method to support reproducibility.

Essential Data Elements to Capture

Subject Identifier: Unique code

Event Date: MM/DD/YYYY

Event Term: MedDRA term

Seriousness: Yes/No

Outcome: Resolved/Not resolved

Causality: Investigator assessment

Stepwise Process to Prepare and Assemble Appendices

Follow a reproducible sequence to gather data, validate content, and produce final PDF or XML files for submission.

01

Extract Data: Pull reconciled safety datasets from the clinical data warehouse.
02

Generate Listings: Produce line listings and aggregate tables using validated scripts.
03

Draft Narratives: Write concise narratives for qualifying serious events.
04

Assemble Index: Create an index linking each appendix to the DSUR section.

Typical Digital Workflow Settings for eSubmissions

Configure your submission platform to preserve audit trails, control access, and produce consistent output files for regulatory review.

Field	Configuration
Document Format	PDF/A for long-term preservation; XML where agency schemas are required
Access Control	Role-based access with least-privilege for safety data handlers
Audit Trail	Retain timestamps, actor ID, and change reason for each edit
Versioning	Automated version numbers and checksum verification

Submission Routing and Review Flow

A clear routing diagram reduces processing time and prevents missing attachments or mismatched indexes.

Internal Review: PV and medical review of tables and narratives.
Quality Check: Data validation, format verification, and file integrity checks.
Regulatory Submission: Prepare IND annual or safety report package.
Regulatory Receipt: Agency acknowledgement and follow-up questions, if any.

Technical Considerations for eSigning and eSubmission

Use a platform that preserves a robust audit trail, supports secure file formats, and can meet healthcare compliance requirements.

Formats Supported: PDF, PDF/A, XML
Integrations: Connectors for EDC, safety databases, and cloud storage
Security Controls: Encryption in transit and at rest

Ensure the chosen platform enables secure signer authentication, a clear audit trail, and the ability to export signed packages in preservation-friendly formats for inspection and archival.

Key Timing Rules and Typical Deadlines

DSUR appendices generally align with periodic safety reporting timelines; sponsors must understand overlapping IND and global reporting obligations.

Annual Reporting:

IND annual reports are submitted annually; FDA expects filings within 60 days of the IND anniversary (21 CFR 312.33).

Expedited Safety Reports:

Fatal or life-threatening suspected adverse reactions must be reported immediately, typically within 7 calendar days (21 CFR 312.32).

Non-fatal Serious Events:

Serious, unexpected suspected adverse reactions usually reported within 15 calendar days (21 CFR 312.32).

Data Cutoff:

Define a clear data lock date for the reporting period and state it in the appendix metadata.

Record Retention Start:

Retention periods run from creation or last effective date; see retention guidance below.

Consequences of Incomplete or Incorrect Appendices

Regulatory Queries: Expect written requests for clarification or additional data.

Clinical Hold Risk: Significant safety reporting gaps may trigger partial or full clinical holds.

Inspection Findings: Deficiencies can appear as inspectional observations during FDA inspections.

Data Integrity Concerns: Inconsistent or missing metadata undermines trust in safety conclusions.

Sponsor Reputation: Repeated reporting errors can affect regulator confidence and trial timelines.

Legal Exposure: Poor documentation increases exposure during litigation or enforcement actions.

eSignature Vendor Comparison for Healthcare Appendices

Comparison focuses on starting price, trial availability, bulk-send capability, audit trail presence, HIPAA support, and envelope limits. signNow is listed first per vendor-comparison conventions.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Varies by vendor	Varies by vendor	Varies by vendor	Varies by vendor
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

FAQs and Troubleshooting for DSUR Appendices

Answers to common questions about formatting, signatures, retention, and regulatory expectations for DSUR appendices in U.S. submissions.

Need help? Contact support

Can DSUR appendices be submitted electronically?
Yes. Electronic submissions are standard for IND and safety reporting; ensure file formats meet agency requirements and retain an auditable trail of who prepared and signed each file.
Are electronic signatures legally valid for these documents?
Electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted; ensure intent, consent, attribution, and retention capabilities are met.
Do I need a BAA for eSignature platforms?
If appendices contain protected health information, a HIPAA Business Associate Agreement (BAA) is required with vendors that access PHI; confirm BAA availability and relevant controls.
What file format should I use for long-term storage?
Use PDF/A for archival preservation and include original export metadata; for agency schemas, provide XML when required by the receiving authority.
How long must I keep source records and appendices?
Retain safety and source records per regulatory minima (see 21 CFR Part 312 guidance), HIPAA (45 CFR §164.530(j) for PHI) and financial rules (IRC §6501(a)), and longer where state law requires it.
Who signs and certifies the appendices?
Authorized sponsor representatives, pharmacovigilance leads, or designated regulatory officers typically sign submissions; document signatory authority in internal SOPs and maintain signature attestations.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now