How to read an IND Safety Report

An IND safety report exists to answer one question fast: does this adverse event change what an investigator, an IRB, or FDA needs to know right now about a drug still in trials. Reading one means checking whether it actually earned that urgency, or whether it’s a case report dressed up as a signal.

What “unexpected” actually means

Under § 312.32(a), an adverse event is unexpected when its nature, severity, or frequency isn’t consistent with the current investigator’s brochure, or with the labeling if one exists. That reference point is deliberate and narrow: a rare but documented reaction stays expected even in a case where it happens to be unusually severe, because severity in a single case doesn’t change what the IB already discloses. What flips an event to unexpected is either its absence from the IB entirely, or a frequency or specificity that the IB understates — a listed “elevated liver enzymes” entry doesn’t cover a case of acute liver failure if the IB never characterized that degree of severity as a possibility. Reading a safety report well means checking the current IB version cited, not assuming the sponsor’s judgment call was made against the right document.

Why the causality judgment carries the report

“Reasonable possibility” is a deliberately lower bar than proof, and it’s the judgment that actually determines whether an event gets reported at all. A report has to show evidence suggesting a causal relationship — timing consistent with drug exposure, a plausible mechanism, resolution on withdrawal, recurrence on rechallenge if that happened — rather than simply noting the event occurred while the subject was on drug. This is also where aggregate data matters alongside the individual case: an event that looks unremarkable on its own can still trigger a report if it’s occurring at a rate that exceeds what the underlying population would produce without the drug, the same background-rate reasoning that shapes how FDA evaluates a proposed REMS once a drug reaches approval. Skipping that comparison is how a real signal gets read as an isolated, unconnected case.

None of this reasoning is unique to IND safety reporting — it’s the same signal-versus-noise discipline that shapes a drug’s Complete Response Letter review years later, when the agency is weighing an accumulated safety record instead of a single case. What makes an IND safety report distinct is how early it happens: before approval, before a REMS, sometimes before anyone has enough cases to know yet whether a signal is real.