Establishing secure connection…Loading editor…Preparing document…

Healthcare SUSAR Log

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

HEALTHCARE SUSAR LOG

Administrative and Study Identification

Case Identification

Report ID:    Subject Initials:    Subject ID:

Age (at event):    Gender:

Event Summary and Classification

Seriousness Criteria (check all that apply):

Was the event unexpected relative to the Investigator Brochure / product information?      

Was the event assessed as SUSAR (Suspected Unexpected Serious Adverse Reaction)?      

Causality, Outcome & Treatment

Outcome (check all that apply):

Regulatory / Reporting Details

Expedited report required per sponsor policy or applicable regulation?      

Follow-up and Attachments

Additional follow-up required?      

Reporter / Responsible Person

Certification and Confidentiality

I certify that the information recorded on this SUSAR Log is complete and accurate to the best of my knowledge. This record will be handled and disclosed in accordance with applicable confidentiality and safety reporting requirements. I acknowledge the obligation to provide prompt written follow-up should additional clinically relevant information become available.

The reporter and signatory accept responsibility for prompt internal notification and for forwarding this case to the sponsor and other oversight bodies as required by study procedures and applicable law. Any known conflicts of interest or deviations from the protocol related to this event have been noted in the attachments.

Printed Name:

Signature:

Date:

Position / Role:

Relationship to subject (if applicable):

Enter text✕
Prepare your document for signing right on this page
  • 01 Edit the text and complete the fields
  • 02 Click Sign Now and on the next screen add recipients and signature fields in SignNow
  • 03 Start your free trial to sign and send your doc
Sign Now

What the Healthcare SUSAR Log Is and when it matters

A Healthcare SUSAR Log is a structured record used in clinical trials and pharmacovigilance to track Suspected Unexpected Serious Adverse Reactions (SUSARs). It summarizes the event, patient identifiers (de-identified where required), onset and resolution dates, seriousness and expectedness assessments, causality conclusions, and regulatory reporting status. The log supports expedited reporting to regulatory agencies, safety committees, and sponsors and is maintained so reviewers can reconstruct decision timelines, submission dates, and follow-up actions associated with each SUSAR.

Why maintaining a clear SUSAR Log improves regulatory compliance

A properly kept SUSAR Log centralizes safety signals, supports timely regulatory notifications under FDA and ICH guidance, and documents decisions for audits and inspections. Accurate logs reduce reporting delays, demonstrate chain-of-custody for safety data, and help teams meet statutory timelines.

Why maintaining a clear SUSAR Log improves regulatory compliance

Who typically prepares and uses a SUSAR Log

Clinical trial sponsors, pharmacovigilance teams, safety officers, and clinical research organizations are the primary users responsible for creating and maintaining SUSAR Logs.

  • Clinical Trial Sponsors — Maintain the Master SUSAR Log to fulfill IND/NDA reporting obligations and coordinate submissions to FDA and ethics committees.
  • Pharmacovigilance Teams — Collect, triage, and assess individual case safety reports prior to entry in the SUSAR Log and onward reporting.
  • Site Safety Coordinators — Provide source documentation and follow-up data from investigators to populate the log accurately.

Accurate assignment of roles ensures timely data flow from investigator reports to regulatory submissions and audit-ready records.

Authorized signers and maintainers

Safety Officer

A qualified safety officer or designated pharmacovigilance lead is typically authorized to certify SUSAR entries and attest to causality assessments. Their signature documents internal review and readiness for regulatory submission, and should be recorded alongside role and date.

Sponsor Representative

A sponsor-designated signatory (medical monitor or regulatory lead) may approve final reporting status and confirm that expedited reports were submitted to FDA, ethics committees, and international regulators as required.

Core elements to include in a professional SUSAR Log

A complete SUSAR Log combines case identifiers, event details, assessment results, and regulatory actions in a single index to support auditability and timely reporting.

Case Identifier

Unique trial-specific code linking to the full individual case safety report and source documents for traceability.

Event Dates

Onset, report receipt, and resolution dates recorded in MM/DD/YYYY format to support timeline reconstruction.

Seriousness & Expectedness

Document whether the event meets seriousness criteria and whether it was expected per the investigator brochure or protocol.

Causality Assessment

Investigator and sponsor causality determinations with supporting rationale and reviewer initials/date.

Regulatory Filings

Status of expedited reports (submitted, pending, waived), submission dates, and agency receipt confirmations where available.

Follow-up Actions

Required follow-up, corrective actions, and link to updated safety reports or protocol amendments.

Step-by-step: create and maintain each SUSAR entry

Follow a consistent sequence to ensure complete entries and preserve the timeline needed for regulatory review and inspection.

  • 01
    Collect source data: Obtain investigator report, medical records, and lab results before entry.
  • 02
    Assign case ID: Use the study's coding convention and log the ID in the master index.
  • 03
    Assess seriousness: Apply regulatory seriousness criteria and document the determination.
  • 04
    Record regulatory action: Note submission dates, agency acknowledgements, and required follow-up.

How an electronic SUSAR Log fits into your safety workflow

An e-log integrates with case intake, assessment, and regulatory submission so teams can track status and produce audit reports quickly.

  • Intake: Site or vendor submits initial case report to safety desk.
  • Triage: Safety team reviews and prioritizes for expedited assessment.
  • Documentation: Populate SUSAR Log with findings and source links.
  • Submission: Prepare and send expedited regulatory reports with attached case summaries.

Configuring an online SUSAR Log workflow

Standardize routing, authentication, and field logic to ensure consistent entries and controlled access across roles.

Field Configuration
Authentication Two-factor for safety sign-offs
Role Routing Safety → Medical Monitor → Regulatory
Conditional Fields Show follow-up fields when 'Serious' selected
Audit Trail Capture timestamps, IP, and signer identity

Technical considerations for eSubmission and e-signing

Choose a platform that supports secure audit trails, role-based access, and HIPAA-safe configurations for clinical safety data.

  • Document Formats: PDF, DOCX accepted
  • Integrations: EHR/CTMS, regulatory portals
  • Authenticator: 2FA and SSO available

Ensure the vendor supports exportable audit logs and retention formats compatible with inspection requests and agency portals.

Security and compliance basics for health-related SUSAR logs

Encryption: TLS 1.2/1.3; AES-256 at rest
HIPAA: Business Associate Agreement required
Audit Trail: Immutable timestamps and action logs
Access Controls: Role-based permissions
Data Residency: Configurable per contract
Authentication: SSO and multifactor options

Critical reporting deadlines for SUSARs

Expedited reporting windows are statutory or guided by FDA and ICH. Use these timelines to calculate when to file IND or marketing-authority reports.

Fatal or life-threatening:

Report within 7 calendar days (see 21 CFR safety reporting timelines)

Serious but not life-threatening:

Report within 15 calendar days per IND/NDA expedited rules

Follow-up information:

Provide updated reports as additional data becomes available

Aggregate safety reports:

Periodic safety reports follow protocol and regulatory schedules

Sponsor internal deadlines:

Record internal review and submission dates for audit trail

Key milestones from event to regulatory filing

Track these sequential milestones to ensure each SUSAR progresses from detection to submission on a documented timeline.

01

Event Detection

Site identifies and notifies sponsor with source documentation.

02

Initial Assessment

Safety team triages seriousness and expectedness.

03

Log Entry

Create SUSAR Log record and assign case ID.

04

Regulatory Submission

File expedited report and capture agency acknowledgement.

Common pitfalls when preparing a SUSAR Log

  • Incomplete timestamps that obscure reporting windows
  • Using direct identifiers instead of coded subject IDs
  • Failing to link source documents and follow-up data
  • Inconsistent seriousness or expectedness assessments

Risks and regulatory consequences of incorrect reporting

Regulatory fines: Civil penalties and warning letters
Clinical hold: Study suspension for noncompliance
Inspection findings: Form FDA 483 observations
Data integrity risk: Compromised safety signal evaluation
Legal exposure: Civil liability for failure to report
Reputational harm: Loss of sponsor or investigator trust

Practical examples of SUSAR Log use

Two short case scenarios illustrate typical SUSAR Log entries and outcomes to guide format and content decisions.

Case Study 1

A Phase II oncology trial recorded a severe unexpected reaction

  • Sponsor assessed causality as possible
  • The SUSAR Log captured onset, report date, investigator comments, and an IND safety report filed within 7 days; follow-up labs appended to the case.

Case Study 2

A multisite vaccine study observed a non-life-threatening unexpected reaction

  • Team classified it as serious for hospitalization
  • The SUSAR Log logged site reports, blinded identifiers, and a 15-day expedited report with periodic follow-up notes for safety committee review.

Comparing e-signature vendors for Healthcare SUSAR Log workflows

Key vendor differences for SUSAR Log use include starting price, trial availability, bulk-send capability, audit trails, HIPAA support, and envelope or session caps; signNow is listed first for side-by-side comparison.

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 Yes
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

FAQs and troubleshooting for the Healthcare SUSAR Log

Answers to common operational and compliance questions about creating, signing, and submitting SUSAR Log entries in regulated workflows.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users
Sign Now
Company
Forms
Pricing
Resources
Knowledge base
Other Products
© 2026 airSlate Inc. All rights reserved.