SUSAR Reporting Under the Clinical Trials Regulation: Clocks, Roles and Common Gaps

Under the EU Clinical Trials Regulation, sponsors report suspected unexpected serious adverse reactions (SUSARs) straight to EudraVigilance, on fixed clocks that start when the sponsor becomes aware. Most failures are not about the clock itself but about who is aware, and when.

The legal framework

Chapter VII of Regulation (EU) No 536/2014 sets the safety reporting chain. Under Article 41, the investigator records adverse events and reports serious adverse events to the sponsor without undue delay and no later than 24 hours after becoming aware, unless the protocol says certain events need not be reported immediately. The sponsor then assesses causality and expectedness and, under Article 42, reports SUSARs electronically to the EudraVigilance database.

The reporting clocks

  • Fatal or life-threatening SUSARs: as soon as possible and no later than 7 days after the sponsor becomes aware.
  • Other SUSARs: no later than 15 days after the sponsor becomes aware.
  • Reclassification: if a reaction first judged non-fatal proves to be fatal or life-threatening, the 7-day clock applies from the date the sponsor learns this.

The regulation also covers SUSARs from trials conducted only in third countries where the sponsor, a related company or a joint developer sponsors the trial and the active substance is the same, and SUSARs identified after the end of a trial.

Where the process breaks down

  • Awareness: contracts with CROs and vendors that do not define when the sponsor is deemed aware, so the clock is argued rather than managed.
  • Expectedness: assessing against the wrong reference safety information, or against an outdated version of the Investigator’s Brochure or SmPC.
  • Causality disagreements: the investigator and sponsor assessments differ and no rule decides which prevails for reporting purposes.
  • Access: smaller or academic sponsors without registered users in the EudraVigilance clinical trials module until the deadline is already running.

Why it matters beyond the clock

SUSAR data feed the sponsor’s ongoing benefit-risk assessment and the annual safety report. A late or missing SUSAR is therefore a data-quality problem for the whole programme, not just a timeliness metric, and it is the sort of finding that features in clinical trial inspections.

A short readiness checklist

  • Written safety agreements with every party that receives safety information, including time zones and out-of-hours cover.
  • A documented rule for sponsor causality and expectedness assessment, with the reference safety information version controlled.
  • Registered, trained users in the reporting module before the first participant is enrolled.
  • Clock tracking that starts from first receipt, not first review.

How PQRA helps

PQRA can review your safety management plan and CRO safety agreements, define SUSAR workflows and clock rules, and prepare sponsors for the registration and training steps needed to report to EudraVigilance. We can also run a mock reconciliation between the clinical and safety databases.

Contact PQRA to discuss your clinical trial safety processes.

CATEGORIES:

Uncategorized

Tags:

No responses yet

Αφήστε μια απάντηση

Η ηλ. διεύθυνση σας δεν δημοσιεύεται. Τα υποχρεωτικά πεδία σημειώνονται με *