Outbreak reportcited by the Tayebat archivefull text checked★ key study A-LEG-03 in-depth review

Raw kidney bean poisoning in the UK

Red kidney bean poisoning in the UK: an analysis of 50 suspected incidents between 1976 and 1989.

Overview

Rodhouse JC et al.. Epidemiol Infect 1990 · PMID 2249712 · DOI 10.1017/s095026880004810x

50 poisoning incidents from raw or undercooked kidney beans; thorough cooking inactivates the toxin.

Does the study support the specific claim? Partly · Methodological quality: moderate

Original publication

Plain-language summary

Study explained simply
What did the researchers want to find out?

Describe kidney bean poisonings

How was the study done?

Outbreak analysis

How many people, animals or samples were studied?

50 incidents

What was actually found?

Vomiting/diarrhoea 1-7 h after raw/undercooked beans

How large was the observed effect?

Not applicable

What do the results mean in everyday life?

Always soak and boil kidney beans.

What are the study's limitations?

Passive reporting

What does it say about Elawady's specific claim?

Supports raw-bean toxicity only

Do the results apply to Germany and Europe?

High

What can explicitly not be concluded from this study?

Cannot show harm from cooked beans.

Scientific in-depth review

1. Full reference

Authors
Rodhouse JC, Haugh CA, Roberts D, Gilbert RJ
Journal
Epidemiol Infect
Year
1990
Identifier
PMID 2249712 DOI 10.1017/s095026880004810x · PMC2271815
Verification
verified – PubMed E-utilities efetch, 2026-10-25
Retracted
no
Corrections
none
Extent checked
full text
Conflicts of interest and funding

Not stated in full text (authors from the government Public Health Laboratory Service, London)

2. Research question

Characterise suspected red kidney bean poisoning incidents.

3. Study design and population

Study design
Outbreak report – Descriptive analysis of surveillance-reported suspected food-poisoning incidents with laboratory haemagglutinin assay of implicated beans
Population

Incidents reported to the PHLS Food Hygiene Laboratory or the Communicable Disease Surveillance Centre (Colindale), involving more than 200 cases

Country

United Kingdom

Period

July 1976 - February 1989

Sample size

50 suspected incidents (>200 cases); beans tested in 31; 32 judged compatible (9 confirmed by haemagglutinin >3200 HAU/g, 23 on symptoms/incubation/preparation history); 18 not confirmed

Inclusion and exclusion criteria

All food-poisoning incidents allegedly associated with red kidney beans reported to FHL or CDSC July 1976 - Feb 1989 (incl. 7 previously published)

4. Methods and endpoints

Exposure / intervention

Raw or inadequately heated red kidney beans

Comparator

None

Endpoints

Symptoms, incubation time, bean preparation, haemagglutinin activity (HAU/g dry weight; rabbit erythrocyte assay)

Statistical methods

Descriptive

5. Actual results

Results

32/50 incidents compatible with red kidney bean poisoning. Nine laboratory-confirmed incidents had 3200-102400 HAU/g (raw beans 80000-100000 HAU/g; well-cooked baseline 400 HAU/g); incubation mostly 1-7 h; vomiting with or without diarrhoea and abdominal pain; recovery usually rapid. In all compatible incidents soaking and/or boiling were inadequate (raw, soaked but uncooked, slow cooker, low-temperature casserole/baking, boiled 4 min). None of the confirmed incidents involved canned beans; 10 unconfirmed incidents involved canned products. A 1988 test showed haemagglutinin in pre-soaked beans destroyed within the recommended 10 minutes of boiling.

Absolute risks

not reported (no denominator of bean consumers); cases per incident ranged from 1 to 11 in confirmed incidents; a 1981 BBC appeal identified 355 letters covering 870 people, suggesting about tenfold under-reporting

Authors' conclusion

Red kidney bean poisoning is easily prevented: soak beans for at least 5 h, discard the water and boil in fresh water for at least 10 min; low-temperature methods (simmering, low-temperature baking, slow cookers) may be particularly unsuitable.

6. Strengths

  • Laboratory haemagglutinin confirmation in 9 incidents with quantified levels
  • Long national surveillance period
  • Preparation methods documented, allowing cause attribution to inadequate cooking

7. Weaknesses

  • Passive reporting; authors document marked under-reporting
  • 23 of 32 incidents diagnosed on clinical history only; 6 of these had beans with <400 HAU/g
  • No consumer denominator, no dose-response
  • Assay of leftover beans may not reflect the beans eaten (uneven heating)

8. Risk of bias

Orienting tool
none applicable (outbreak/surveillance case series)
Type of assessment
structured assessment based on the full text by a single reviewer (no formal double review)
Full formal assessment
no
Overall risk of bias
some concerns
Rationale

No standard RoB tool fits a surveillance case series; structured single-reviewer judgement from full text, not a formal assessment. Bias concerns do not undermine the main conclusion that poisoning followed raw or inadequately cooked beans.

8. Risk of bias
DomainJudgementRationale
Case ascertainmentsome concernsPassive notification; under-reporting acknowledged; reporting influenced by media attention (1981 BBC programme).
Case definition / outcome attributionsome concernsOnly 9 laboratory-confirmed; 23 on short-incubation symptoms and preparation history; microbiological exclusion done only in the 7 earlier incidents.
Exposure assessmentlowPreparation method documented for most incidents; haemagglutinin quantified against raw and cooked reference levels.
Confounding / alternative causessome concernsS. aureus or B. cereus intoxication not systematically excluded in all incidents.

Full-text review (25 October 2026): Added that only 32/50 incidents were compatible, HAU levels (raw 80000-100000 vs cooked 400 HAU/g), preparation errors in all compatible incidents, no confirmed canned-bean incidents, under-reporting evidence (BBC appeal 870 people), practical prevention advice; structured validity domains; overall unchanged.

9. Assessment of the statistical interpretation

Descriptive counts only; no inferential statistics. Strong qualitative evidence for causation of acute intoxication by raw/undercooked beans (short incubation, high lectin levels, consistent preparation errors).

10. Relevance to the specific claim

Supports C-LEG-06; limits C-LEG-07.

11. Independent contrary findings

None.

12. Transferability to Germany and Europe

High.

13. Overall methodological judgement

Correct use for raw beans.

Multidimensional assessment
Multidimensional assessment
Authenticity of the sourceverified
Methodological qualitymoderate
Risk of biassome concerns
Precision of resultsnot applicable
Directnessdirect
Reproducibilityreplicated
Consistency with the overall evidenceconsistent
Regional transferabilityhigh
Adequacy of the interpretation (by the archive)correctly reported

14. Open questions

Residual lectin after modern slow-cooking or low-temperature methods; lectin content of newer varieties (raised by the authors for 1988).

15. Linked fact checks

Use by the Tayebat archive

Note: according to the archive, the studies were compiled by the archive operators. Whether Dr. Elawady himself cited this study is not established.

What the archive says about the study

50 UK poisoning incidents from raw/undercooked kidney beans due to phytohaemagglutinin.

A. What was actually studied?

UK incidents 1976-1989.

B. What did the authors find?

50 suspected incidents, 32 compatible; all with inadequate soaking/boiling; none due to canned beans; lectin destroyed by soaking and boiling >=10 min.

C. What conclusions do the authors themselves draw?

Thorough cooking of soaked beans prevents poisoning.

D. What does the archive derive from it?

Used as part of the case against legumes.

E. Is this derivation scientifically justified?

Correct for raw or undercooked beans. The same source shows the risk is removed by proper soaking and boiling and that no confirmed incident involved canned beans, which undermines use against normally cooked legumes.

Adequacy of the interpretation (by the archive)
correctly reported