Short answer
An adverse event is a medical problem observed during drug use; the term does not establish that the drug caused it. The FDA AEMS FAQ uses side effect for an adverse drug reaction supported by evidence of a drug connection. That is a useful distinction, but side-effect usage is not uniform. 1 2
On this page
At a glance
Scroll to compare all columns →
| Question | Adverse event | Side effect |
|---|---|---|
| What does it identify? | An unfavorable medical occurrence during product use | A drug-related reaction in the AEMS FAQ |
| Must causation be established? | No | The FAQ calls for specific evidence of a connection |
| Is the terminology consistent? | E2A supplies a formal research definition | E2A notes variation in usage |
These meanings come from FDA’s March 1995 E2A guidance and its supplied AEMS FAQ. 1 2
What each thing is
In clinical research, an adverse event can be a symptom, disease, unfavorable sign, or abnormal laboratory result. It is broader than a complaint someone feels. Side effect, under the AEMS FAQ’s definition, identifies the drug-related subset rather than every problem occurring during treatment. 1 2
Key differences
The central difference is observation versus causal attribution. Recording an adverse event leaves the cause open. Calling it an adverse drug reaction adds a causal assessment, but not necessarily certainty: the March 1995 E2A guidance uses at least a reasonable possibility of causation for preapproval reactions. The AEMS FAQ instead describes specific evidence of a connection. 1 2
How to tell them apart
Ask whether the wording merely records a problem during drug use or also attributes it to the drug. Then check the document’s definition of side effect or reaction. Limit: a dashboard heading or reaction label alone cannot settle causation; FDA explicitly warns that the existence of an AEMS report does not establish it. 2
Where they overlap
Under the AEMS FAQ’s terminology, every adverse drug reaction—and therefore every side effect—is also an adverse event. The reverse does not follow. The categories can describe the same occurrence at different levels: first as an observed problem, then as a problem with evidence of a drug connection. 2
Edge cases
A headache can be a known side effect of a drug without that drug having caused a particular patient’s headache. FDA uses headaches to explain this difficulty. Existing disease, environment, diet, or sleep habits can offer alternative explanations, so general knowledge about a drug does not automatically resolve an individual event’s cause. 2
Why the distinction exists
Keeping observation separate from attribution allows safety information to include problems whose causes remain uncertain. The March 1995 E2A guidance seeks consistent collection and handling of clinical-development safety information. The AEMS FAQ likewise distinguishes reported events from causal conclusions in FDA’s US postmarketing surveillance database. 1 2
Common misconceptions
Neither term means that a report count measures how often a problem occurs. FDA says AEMS counts cannot estimate incidence because reporting is incomplete and influenced by multiple factors. Nor should side effect be treated as having one fixed meaning everywhere: E2A acknowledges varied usage, while the FAQ supplies its own definition. 1 2
Examples
Hypothetical research case: an abnormal laboratory finding appears during treatment, with no causal assessment yet. It can be an adverse event without being an established drug reaction. 1
Hypothetical attribution case: a symptom occurs during drug use and specific evidence connects it to the drug. Under the AEMS FAQ, it qualifies as both an adverse event and a side effect. 2