Adverse Event Classification After a Device-Related Serious Event
During a multicenter trial of a vascular closure device, a participant develops a pseudoaneurysm requiring surgical repair three days after the index procedure. The site coordinator logs it as an adverse event, non-serious, 'unrelated to device, related to procedure.' The sponsor's medical monitor reviews it and believes it is serious (it required intervention to prevent impairment) and possibly device-related (deployment difficulty was noted in the case report form). The investigator disagrees on both points and refuses to change the assessment. The protocol states the investigator's causality assessment is recorded but the sponsor may provide its own. The event occurred at a site with a recent monitor change and a backlog of unreported events. The IRB reporting deadline for unanticipated problems is 10 working days. Five working days have elapsed since the site became aware.
1. How should seriousness and causality be resolved, given the disagreement, and what governs each determination?
Read the worked answer
Seriousness is an outcome-based determination, not a matter of opinion. The regulatory definition turns on whether the event resulted in death, life-threatening condition, inpatient hospitalization or prolongation, persistent or significant disability, congenital anomaly, or required intervention to prevent permanent impairment or damage. A pseudoaneurysm requiring surgical repair fits the 'intervention to prevent permanent impairment' prong. The coordinator's 'non-serious' entry is a documentation error that should be corrected regardless of the causality dispute.
Causality is a judgment, and the framework permits two recorded views. The investigator's assessment is required and is recorded; the sponsor is entitled to its own assessment, and the protocol here says so explicitly. The resolution is not to force the investigator to change the entry but to:
- Record both assessments in the safety database with rationale.
- Have the medical monitor document the basis for 'possibly related' (deployment difficulty in the CRF, temporal relationship, known device failure modes).
- Escalate the divergence for a documented discussion; if unresolved, both stand.
Practical point: 'related to procedure' vs. 'related to device' is often a false dichotomy in device trials - deployment difficulty is a device performance issue that manifests as a procedural complication. The monitor should probe whether the deployment difficulty is itself a device deficiency, which carries separate reporting obligations.
2. What are the reporting obligations and deadlines, and what should the monitor do about the unreported-event backlog?
Read the worked answer
Reporting clock. The 10-working-day IRB deadline runs from the site's awareness date, not from when the sponsor agrees with the classification. Five working days have elapsed, leaving five. The monitor should not let the causality dispute consume the reporting window. A defensible approach: submit the report on the seriousness grounds (which are not genuinely in dispute once the intervention criterion is applied), noting the divergent causality assessments, and supplement if the assessment changes.
Layers of obligation:
- IRB: unanticipated problem reporting, per the 10-day rule and the IRB's own policy.
- Sponsor: internal safety review and, where applicable, reporting to the regulatory authority under the trial's safety reporting plan and applicable device regulations.
- Site: documentation in source and the safety log.
Backlog. The monitor should treat the backlog as a systemic finding, not a series of isolated ones: request a full reconciliation of source documents against the safety log for the period since the monitor change, prioritize events with seriousness or device-relationship potential, document the reconciliation, and open a CAPA addressing monitor turnover handoff and site safety reporting training. Verify at the next visit that the backlog is cleared and that new events are logged within the site's stated timeframe.