25.12.2012 Views

revised final - Agency for Toxic Substances and Disease Registry ...

revised final - Agency for Toxic Substances and Disease Registry ...

revised final - Agency for Toxic Substances and Disease Registry ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

MERCURY 345<br />

2. HEALTH EFFECTS<br />

Additional chronic-duration oral exposure in<strong>for</strong>mation in animals concerning renal effects following<br />

inorganic mercury exposure is needed to evaluate the threshold of this effect in humans following chronic<br />

exposure. The data would be useful if populations living near hazardous waste sites were to be exposed<br />

chronically to inorganic mercury that leached into near-by wells or water supplies.<br />

Forestomach squamous cell papillomas <strong>and</strong> thyroid follicular cell carcinomas have been observed in rats<br />

<strong>and</strong> renal tubule tumors have been observed in mice following oral exposure to mercuric chloride (NTP<br />

1993). Renal tumors have also been observed in rats <strong>and</strong> mice after oral exposure to organic mercury<br />

(Hirano et al. 1986; Mitsumori et al. 1981, 1990; Solecki et al. 1991). These results suggest the potential<br />

carcinogenicity of mercury to humans. There<strong>for</strong>e, additional chronic-duration animal studies on metallic,<br />

inorganic, <strong>and</strong> organic mercury are needed to confirm the findings of the NTP study. Additional longterm<br />

follow-up studies examining carcinogenicity in highly exposed populations (i.e., those involved in<br />

mercury mining, or the exposed Iraqi or Japanese populations) are needed to evaluate the likelihood of<br />

tumors appearing in humans.<br />

Genotoxicity. Although there are data from several in vivo studies on rats (oral exposure) <strong>and</strong> mice<br />

(intraperitoneal) indicating that inorganic <strong>and</strong> organic mercury compounds can cause clastogenic effects<br />

in mammalian germinal cells, the differences in species sensitivity, <strong>and</strong> in some cases strain sensitivity,<br />

do not permit the use of these findings <strong>for</strong> predicting a potential hazard to human genetic material (Suter<br />

1975; Zasukhina et al. 1983). Epidemiological studies of humans occupationally or accidentally exposed<br />

to mercurials were inconclusive, but the combined results from these studies did not suggest that metallic<br />

mercury <strong>and</strong> organic mercury are clastogens <strong>for</strong> human somatic cells (Anwar <strong>and</strong> Gabal 1991; Barregard<br />

et al. 1991; Mabille et al. 1984; Popescu et al. 1979; Verschaeve et al. 1976, 1979; Wulf et al. 1986).<br />

There is, however, convincing evidence that inorganic <strong>and</strong> organic mercury compounds can interact with<br />

<strong>and</strong> damage DNA in vitro (Williams et al. 1987). The outcome of this damage has not been<br />

characterized, but there is some indication that mercury compounds are weak mutagens <strong>for</strong> cultured<br />

mammalian cells. In addition, in vitro results with human cells (Betti et al. 1992) <strong>and</strong> animal cells<br />

(Howard et al. 1991) <strong>and</strong> in vivo data in mice (Ghosh et al. 1991) suggest that mercury compounds can<br />

cause clastogenic effects in somatic cells. Considering the problems stated above in using the whole<br />

animal data, <strong>and</strong> the apparent species- <strong>and</strong> strain-specific responses noted in the DNA damage tests with<br />

cultured mammalian cells, the in vitro data, while of interest, are probably not reliable indicators of<br />

potential adverse effects in humans exposed to mercury. Well controlled human epidemiological studies<br />

are needed to determine the genetic hazard of mercury compounds to humans.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!