Adverse event reporting: AE, SAE, and what the sponsor actually sends

Adverse event reporting is two different jobs that teams collapse into one phrase. The first job is recognizing an adverse event and keeping it. The second is deciding whether a regulator, an investigator, or an ethics committee must hear about it on a clock. An AE is not automatically an SAE. An SAE is not automatically a report that leaves the building today.

What an adverse event is

An adverse event is any untoward medical occurrence in a patient or clinical-trial subject given a pharmaceutical product. It does not have to have a causal relationship with the treatment. A headache, a lab shift, a fall, a rash: if it happened after the product was given and someone reported it, it is an AE until a reviewer says otherwise. Lack of effect is usually handled as a separate concept. Your protocol should say so rather than leaving it to inbox custom.

Severity is how bad the event felt or how it was graded. Seriousness is whether it met a regulatory criterion. A severe headache can be non-serious. A short hospitalization for a mild event can be serious. Intake forms that use one checkbox for both create bad cases. The PV case intake form should store the verbatim and leave seriousness as a reviewed field.

What makes an event an SAE

ICH E2A seriousness criteria are the ones drug-safety teams actually use. An event is serious when it results in any of the following:

• Death.
• A life-threatening event. Life-threatening means the patient was at immediate risk of death, not that a worse outcome was theoretically possible.
• Inpatient hospitalization or prolongation of existing hospitalization.
• Persistent or significant disability or incapacity.
• A congenital anomaly or birth defect.
• A medically important event that may jeopardize the patient or require intervention to prevent one of the outcomes above.

Hospitalization for a planned procedure, or an emergency-room visit that does not become an admission, is a frequent argument. The criterion is the one in your SOP, aligned to ICH and to the region of the trial. The intake record should quote what the reporter said about admission, not a paraphrase that already assumes the answer.

What actually gets reported, and when

Collection is broader than expedited reporting. On an IND, the sponsor's expedited duty under 21 CFR 312.32 is aimed at suspected adverse reactions that are both serious and unexpected. Unexpected fatal or life-threatening suspected adverse reactions are reported as soon as possible and no later than 7 calendar days after the sponsor's initial receipt of the information. Other serious and unexpected suspected adverse reactions are reported as soon as possible and no later than 15 calendar days after the sponsor determines the information qualifies for reporting. Those are US IND clocks. Marketed-product clocks and EU clinical-trial clocks are related and not identical.

"Suspected" means there is a reasonable possibility the product caused the event. "Unexpected" means it is not listed in the investigator's brochure, or for a marketed product in the reference safety information, at the specificity the event actually has. A listed headache does not make an unexpected liver failure expected. The document and its version belong in the case. AE Connect does not author the company core data sheet or the brochure.

When the event is serious, unexpected, and suspected in a clinical trial, teams often call it a SUSAR. The US rule uses the longer name. The intake work is the same: do not lose the receipt date while you decide.

What the workspace drafts, and what it refuses to do

In the AE Connect workspace, a reviewer pastes or uploads the source. The draft proposes seriousness against those ICH criteria, a MedDRA preferred term and system organ class to confirm, WHO-UMC causality, expectedness as a check against the brochure or core data sheet, and a timeline such as 7-day, 15-day, or not required. Each field has a short rationale. You accept or override it.

That draft is decision support inside drug-safety case processing. It is not the IND safety report, not an E2B(R3) message, and not a letter to investigators. Transmission is covered in E2B(R3) ICSR submissions. Events that are not expedited still have to be findable later for aggregate reports.

If the narrative is really a quality defect, or a defect plus an event, read it against product quality complaint reporting before you force it into an SAE template.