Free scoping read. A written assessment of your manuscript in two business days, at no cost.

Start one
Contents

Academy · Research Data, Analytics & AI · Adverse Drug Effects

Adverse Drug Effects: Definition and Classification

Describing every adverse outcome after a dose as an “adverse drug effect” obscures the distinction that determines subsequent action: whether the drug caused it.

Pubrica AcademyWritten by a pharmacovigilance reviewer Reviewed bya clinical data manager Published10 October 2026 Last checked10 October 2026 Reading time8 minutes Sources1 peer-reviewed

An adverse drug reaction is a response to a drug that is noxious and unintended, occurring at doses normally used for prophylaxis, diagnosis or therapy — distinct from an adverse event, which is simply an untoward occurrence during drug treatment, with no claim yet made about whether the drug caused it.

Learning objectives

  • The precise distinction between an adverse event and an adverse drug reaction.
  • The standard classification of adverse drug reactions by mechanism (Type A through Type F).
  • Why this classification affects how a reaction is detected, reported and managed.
  • Why causality has to be assessed, not assumed, before a reaction is attributed to a drug.

Common misconceptions

  • “Adverse event and adverse drug reaction mean the same thing.” An adverse event is any untoward occurrence during treatment, observed with no causal claim; an adverse drug reaction specifically implies the drug caused it — the distinction determines what reporting and causality-assessment obligations apply.
  • “All adverse drug reactions are dose-related and predictable.” The standard mechanistic classification separates dose-related, predictable reactions (Type A) from reactions that are not dose-related, often immunological, and harder to predict (Type B), among other types with different detection and management implications.

Adverse event versus adverse drug reaction

Edwards and Aronson, in their widely cited Lancet review on adverse drug reaction definitions, diagnosis and management, set out the terminology precisely: an adverse event is any untoward medical occurrence in a patient given a drug, without any implication of a causal relationship, while an adverse drug reaction specifically describes a response judged to be caused by the drug1. The distinction is substantive rather than stylistic: it determines whether a case requires causality assessment at all, and what a regulator expects once that assessment has been made.

Mechanistic classification from Type A to Type F

Edwards and Aronson describe the standard mechanistic classification used to group adverse drug reactions: Type A reactions are dose-related and predictable from the drug's known pharmacology (for example, an exaggerated therapeutic effect); Type B reactions are not dose-related, often idiosyncratic or immunologically mediated, and harder to predict from pharmacology alone; further types in the scheme cover dose-related and time-related effects, withdrawal reactions, and unexpected failure of therapy1. The type into which a suspected reaction falls shapes the practical response: a Type A reaction is often managed by dose adjustment, whereas a Type B reaction more often requires withdrawal of the drug and its designation as contraindicated for that patient thereafter.

Importance of causality assessment

Because an adverse event only becomes an adverse drug reaction once causality is established, Edwards and Aronson's review discusses the structured approaches used to make that judgement — considering the time course, whether the reaction resolves on stopping the drug (dechallenge) or recurs on restarting it (rechallenge), and whether an alternative explanation (the underlying condition, another medicine) better accounts for the event1. Omitting this step and attributing every adverse event to the drug by default risks both overstating the drug’s risk profile and overlooking the true explanation for the event.

Key points

Key points

An adverse event is a neutral observation; an adverse drug reaction is a causal claim that requires structured assessment to support, and knowing which mechanistic type a reaction falls into (dose-related and predictable versus idiosyncratic and unpredictable) determines how it should be detected, reported and managed.

Practical application

Practical application

  1. Use “adverse event” until causality has been assessed. The term “adverse drug reaction” should be reserved for cases in which a structured causality assessment has been performed, rather than used as a default label for any adverse outcome during treatment.
  2. Classify by mechanism where possible. Whether a suspected reaction appears dose-related and predictable (Type A) or idiosyncratic (Type B) should be noted, since this affects both the clinical response and the manner of reporting.
  3. Document the causality-assessment basis explicitly. Time course, dechallenge and rechallenge information where available, and alternative explanations considered, should be recorded, rather than causation being asserted without that basis.

Frequently asked questions

A side effect is usually a known, often non-serious and predictable pharmacological effect; it may overlap with Type A adverse drug reactions, but “adverse drug reaction” is the broader, causally defined term.

A structured causality assessment, considering time course, dechallenge/rechallenge evidence, and alternative explanations, rather than an informal judgement based on timing alone.

Reporting obligations vary by jurisdiction and by whether the event is serious or unexpected; this article covers the definitional distinction, not jurisdiction-specific reporting rules.

References

  1. Edwards IR, Aronson JK. Adverse drug reactions: definitions, diagnosis, and management. Lancet. 2000;356(9237):1255-1259. read 10 October 2026. View on PubMed

Every source above is a peer-reviewed article, a publisher’s record of one, or a standard issued by the body that owns it. Each carries the date it was last read. Where a standard moves, this article is revised rather than left up with a note.

How to cite this article

Pick your referencing style and copy it. Your university or target journal may vary the punctuation — check its guide if it has one.

Pubrica Academy. (2026, October 10). Adverse Drug Effects: Definition and Classification. Pubrica. https://pubrica.com/academy/concepts-definitions/adverse-drug-effects/

This article is written to be learned from. Cite it if you are referring to what it says; if you are using the evidence behind it, cite the sources listed above instead.

Adverse event / ADR triage stub

Use when logging a suspected drug-related occurrence.

Event description: ____
Time course relative to dosing: ____
Dechallenge outcome (if applicable): ____
Rechallenge outcome (if applicable): ____
Alternative explanations considered: ____
Mechanistic type (if ADR confirmed): [ ] A  [ ] B  [ ] Other
Causality assessment conclusion: ____

Pubrica AcademyWritten and maintained by Pubrica’s subject matter experts. Articles are revised when the underlying standards change, and each article states the date on which it was last reviewed.

How Pubrica can help

Pubrica’s pharmacovigilance team supports structured causality assessment and mechanistic classification of suspected adverse drug reactions, and prepares the documentation that regulators and ethics committees expect.

Find something else

Search the Pubrica Academy

Access is free and requires no account. Enter a topic, or open the full library to filter by category, sub-topic or resource type.

Documentation of suspected adverse drug reactions to a defensible standard

A scoping assessment is free and takes two business days. It provides a written assessment of what the work requires and which specialist would undertake it.

Get a free quote

Regulations

Check your project against this rule

  1. 1Your work
  2. 2Your details
  3. 3Send
What do you need?

Material you send is held under signed confidentiality, with access limited to the assigned team and encrypted transfer. It is not used to train anything and is not passed to third-party tools. Ask for the agreement before you send anything you would rather cover first.