Establishing secure connection…Loading editor…Preparing document…

Healthcare SUSAR Submission

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

HEALTHCARE SUSAR SUBMISSION

This Suspected Unexpected Serious Adverse Reaction (SUSAR) Submission documents a serious or unexpected adverse reaction observed in a clinical investigation. Submitter must provide accurate clinical, investigational, and identification data to enable timely safety assessment and reporting. All information provided below will be used solely for safety evaluation and regulatory reporting in accordance with applicable laws and confidentiality obligations.

Study and Report Identification

Sponsor Name:

Study Title:

Protocol Identifier:    Study Site/Institution:

Investigator Name:    Investigator Contact Phone:

Report Reference Number:    Initial Report Date:

Patient Information

Date of Birth:

Gender:

Patient ID/Subject Number:

Phone:

Emergency Contact:

Emergency Phone:

Event Description

Medical History and Concomitant Treatments

Investigations and Supporting Data

Seriousness Criteria (select all that apply)

Death    Life-threatening    Hospitalization or Prolonged Hospitalization    Persistent or Significant Disability    Congenital Anomaly/Birth Defect    Other (specify):

Causality and Expectedness

Causality Assessment: Unrelated    Possible    Probable    Definite

Expectedness: Expected for investigational product    Unexpected for investigational product    If unexpected, provide rationale:

Reporter and Submission Details

Attachments and Additional Documentation

Authorization and Certification

By signing below, I certify that I am the patient named above or the patient's legally authorized representative and that the information supplied in this SUSAR Submission is true, accurate, and complete to the best of my knowledge. I authorize the collection, use, and disclosure of my health information as necessary for safety evaluation, pharmacovigilance, and regulatory reporting in connection with this clinical study. I understand that information will be handled in accordance with applicable privacy and confidentiality requirements and that I may withdraw this authorization in writing except to the extent that processing has already occurred.

Authorization Expiration Date:

Patient / Representative Consent: I consent to the use and disclosure described above and certify accuracy of this report.

Acknowledgment of Time‑Critical Reporting Obligations: I acknowledge that SUSARs may require expedited reporting to regulatory authorities and ethics committees and that timely communication is necessary for participant safety.

Patient Name:

Signature:

Date:

Relationship to patient (if signing as legally authorized representative):

Enter text✕

What a Healthcare SUSAR Submission Is

A Healthcare SUSAR Submission is the formal report sent by sponsors or investigators to regulatory authorities and ethics committees when a Suspected Unexpected Serious Adverse Reaction (SUSAR) occurs during a clinical trial. It documents unexpected serious harms that may be related to the investigational product, summarizes patient information, event description, timing, outcome and causal assessment, and includes relevant lab or diagnostic data. The submission supports pharmacovigilance, patient safety monitoring, and regulatory oversight, and must follow timelines, format and confidentiality controls required by regulatory agencies and applicable privacy laws.

Why Timely and Complete SUSAR Reporting Matters

Submitting SUSARs promptly is critical to protect trial participants, maintain regulatory compliance, and enable timely benefit-risk assessment. Accurate, complete submissions reduce follow-up requests from agencies, support safety signal detection, and help meet reporting obligations under FDA and international guidance.

Why Timely and Complete SUSAR Reporting Matters

Who Prepares and Submits SUSARs

Typical submitters include clinical trial sponsors, contract research organizations, principal investigators, and pharmacovigilance teams responsible for safety reporting.

  • Clinical sponsors: prepare SUSAR narratives, assess causality, and file reports to regulators and ethics committees.
  • CRO safety teams: collect source data, perform expedited review, and manage submission logistics across sites.
  • Investigators/site staff: report serious events locally, supply case details, consent documentation, and follow-up information.

Organizations should assign a single pharmacovigilance point of contact to coordinate SUSAR timelines, quality checks, and regulatory correspondence.

Core Elements of a Professional Healthcare SUSAR Submission

Core components of a professional Healthcare SUSAR Submission ensure clarity, regulatory completeness, patient privacy protection, and traceable decision-making for safety evaluation.

Case Summary

Provide concise narrative of the adverse event, onset, progression, severity, outcome, and relationship to the investigational product, including relevant concomitant medications and laboratory findings.

Patient Data

Include age, sex, weight, relevant medical history, trial ID, site identifier, and de-identified patient code to protect privacy while enabling follow-up.

Investigations

Attach laboratory reports, imaging summaries, ECGs, biopsy results and other diagnostics that support the case assessment and temporal association with the investigational product where available.

Causality

Document investigator and sponsor causality assessments, rationale for judgments, alternative explanations considered, and whether the event meets seriousness and unexpectedness criteria with reference to protocol-defined stopping rules.

Regulatory Info

Record submission recipient(s), regulatory form/version used, reporting timeline (e.g., 7-day or 15-day window), and previous related reports or safety signals, including accelerated reporting where applicable.

Audit Trail

Maintain timestamps, submitter identity, version history, and attachments in an auditable record with exportable logs and retention per regulation to support inspections and queries.

Required Fields and Sensitive Data Controls

Patient Identifier: Use assigned de-identified patient code
Event Date: Exact onset date MM/DD/YYYY
Seriousness Criteria: Specify criteria met such as hospitalization
Causality Assessment: Investigator and sponsor opinion
Concomitant Meds: List active medications and doses
Attachments: Lab reports, ECGs, imaging, and notes

Step-by-Step: Preparing and Submitting a SUSAR

Follow these sequential steps to prepare and submit a Healthcare SUSAR Submission accurately and on time.

  • 01
    Collect Data: Gather source documents, narratives, and diagnostics promptly.
  • 02
    Assess Causality: Complete investigator causal assessment and sponsor review.
  • 03
    Prepare Report: Assemble narrative, case details, attachments, and regulatory fields.
  • 04
    Submit: File to regulators and ethics committees within required timeframe.

Configuring an Electronic SUSAR Submission Workflow

Configure your eSubmission workflow to match protocol templates, required fields, and regulatory timelines for efficient electronic submission management.

Field Configuration
Authentication Email link or SMS code
Mandatory Fields Set required checkboxes for key safety elements
Conditional Fields Show follow-up questions based on initial answers
Document Retention Enable A/V recording and exportable audit logs

Where to File and Who Receives a SUSAR

Understand the routing options for a Healthcare SUSAR Submission: national regulators, local IRBs/ethics committees, and sponsor safety databases.

  • Regulatory Agency: Submit to FDA MedWatch or regional competent authority electronic portal
  • Ethics Committee: Provide report to institutional IRB within site-specific timelines
  • Sponsor Database: Upload case to sponsor pharmacovigilance system with cross-reference ID
  • Global Reporting: Notify international authorities per ICH E2A timelines when applicable

Digital Signing and Platform Requirements

Select eSignature and submission platforms that support audit trails, strong authentication, HIPAA BAA options, and exportable records for inspection.

  • eSignature: Support ESIGN/UETA and audit trail
  • Authentication: SMS, SSO, or KBA options
  • Integrations: Connect to EDC, safety DB, and storage

Key Reporting Deadlines and Expectations

Reporting deadlines for SUSARs depend on seriousness and causality; follow applicable regulatory timelines for initial and follow-up reports.

7-Day Reporting Window:

Initial report required within 7 calendar days

15-Day Reporting Window:

Reportable within 15 calendar days per regulation

Follow-Up Reporting:

Submit follow-up data as available within statutory timeframes

Local IRB Notification:

Notify institutional review board per site policy

International Timelines:

Observe ICH E2A and local authority differences

Common Preparation Mistakes to Avoid

  • Incomplete timelines: omitting exact onset or failing to indicate whether the report is initial or follow-up, causing regulatory queries and potential noncompliance.
  • Insufficient causality rationale: providing a checklist response without documented reasoning from investigator and sponsor reduces credibility and may trigger requests for clarification.
  • Missing source documents: failing to attach key lab reports, imaging, or consent documentation slows assessment and can invalidate the report.
  • Privacy lapses: including direct identifiers or unrestricted PHI can breach HIPAA privacy rules and require remedial actions or redaction.

Risks and Consequences of Incorrect Reporting

Regulatory Action: Warning letters, clinical hold
Inspection Findings: FDA 483 observations possible
Trial Impact: Protocol suspension or enrollment pause
Legal Liability: Increased sponsor exposure to litigation
Data Integrity: Compromised dataset validity for safety analyses
Patient Harm: Delayed risk mitigation actions

Practical Examples of SUSAR Reporting Workflows

Practical examples show how sponsors and sites manage SUSAR submissions, including rapid reporting, follow-up data collection, and regulator correspondence.

Multicenter Trial Sponsor

A multicenter oncology sponsor detected a SUSAR across two sites and initiated expedited internal review.

  • Consolidated case data in 48 hours.
  • They submitted an initial 7-day report to the competent authority and site IRBs, provided timely follow-up with diagnostic reports, and documented decisions in an auditable safety database to satisfy inspection queries.

Academic Site Investigator

An investigator at an academic hospital reported a serious unexpected reaction observed during a Phase II study and sought sponsor guidance.

  • Site supplied source documentation and consent forms.
  • The combined documentation enabled the sponsor to assess causality, issue a single SUSAR submission, and coordinate IRB follow-up; thorough source-to-report linkage prevented additional agency inquiries and updated safety management plans accordingly.

Frequently Asked Questions about Healthcare SUSAR Submissions

Answers to common questions about preparing, submitting, and correcting Healthcare SUSAR Submissions, and how electronic workflows affect compliance.


Need help? Contact support

eSignature Pricing and Feature Comparison for SUSAR Workflows

Compare common eSignature plan features and costs relevant when choosing a platform for Healthcare SUSAR Submission workflows and PHI handling.

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, no credit card required Check vendor trial terms and availability Check vendor trial terms and availability Check vendor trial terms and availability Check vendor trial terms and availability
Bulk Send Yes (available on Business Premium) Yes (available on select plans) Yes (bulk send available on business tiers) Yes (document merge and bulk capabilities) Limited, depends on plan and tier
Audit Trail Yes, full audit trail included Yes, audit logs and timestamps Yes, audit logs and timestamps Yes, audit logs and timestamps Yes, audit logs and timestamps
HIPAA Compliant Yes — BAA available upon request Yes — HIPAA support with BAA Yes — enterprise HIPAA options No — HIPAA compliance not standard No — limited HIPAA support
Envelope Cap No envelope cap or per-user limit Limited to 100 envelopes per user per year Varies by plan; verify limits Varies by tier; consult vendor Varies by plan and usage limits apply
be ready to get more
Join over 28 million airSlate SignNow users