World Library  
Flag as Inappropriate
Email this Article

Nanotoxicology

Article Id: WHEBN0009497908
Reproduction Date:

Title: Nanotoxicology  
Author: World Heritage Encyclopedia
Language: English
Subject: Nanotechnology, Nanoreactor, Outline of nanotechnology, Nanofoundry, Nanomedicine
Collection: Nanomedicine, Toxicology
Publisher: World Heritage Encyclopedia
Publication
Date:
 

Nanotoxicology


Nanotoxicology is the study of the toxicity of nanomaterials. Because of quantum size effects and large surface area to volume ratio, nanomaterials have unique properties compared with their larger counterparts.

Nanotoxicology is a branch of bionanoscience which deals with the study and application of toxicity of nanomaterials.[1] Nanomaterials, even when made of inert elements like gold, become highly active at nanometer dimensions. Nanotoxicological studies are intended to determine whether and to what extent these properties may pose a threat to the environment and to human beings.[2] For instance, Diesel nanoparticles have been found to damage the cardiovascular system in a mouse model.[3]

Contents

Human health and safety

Calls for tighter regulation of nanotechnology have arisen alongside a growing debate related to the human health and safety risks associated with nanotechnology. [4] The Royal Society identifies the potential for nanoparticles to penetrate the skin, and recommends that the use of nanoparticles in cosmetics be conditional upon a favorable assessment by the relevant European Commission safety advisory committee. Andrew Maynard[5] also reports that ‘certain nanoparticles may move easily into sensitive lung tissues after inhalation, and cause damage that can lead to chronic breathing problems’. [6]

Carbon nanotubes – characterized by their microscopic size and incredible tensile strength – are frequently likened to asbestos, due to their needle-like fiber shape. In a recent study that introduced carbon nanotubes into the abdominal cavity of mice, results demonstrated that long thin carbon nanotubes showed the same effects as long thin asbestos fibers, raising concerns that exposure to carbon nanotubes may lead to pleural abnormalities such as mesothelioma (cancer of the lining of the lungs caused by exposure to asbestos).[7] Given these risks, effective and rigorous regulation has been called for to determine if, and under what circumstances, carbon nanotubes are manufactured, as well as ensuring their safe handling and disposal.[8]

The Woodrow Wilson Centre’s Project on Emerging Technologies conclude that there is insufficient funding for human health and safety research, and as a result there is currently limited understanding of the human health and safety risks associated with nanotechnology. While the US National Nanotechnology Initiative reports that around four percent (about $40 million) is dedicated to risk related research and development, the Woodrow Wilson Centre estimate that only around $11 million is actually directed towards risk related research. They argued in 2007 that it would be necessary to increase funding to a minimum of $50 million in the following two years so as to fill the gaps in knowledge in these areas.[9]

The potential for workplace exposure was highlighted by the 2004 Royal Society report[10] which recommended a review of existing regulations to assess and control workplace exposure to nanoparticles and nanotubes. The report expressed particular concern for the inhalation of large quantities of nanoparticles by workers involved in the manufacturing process.

Stakeholders concerned by the lack of a regulatory framework to assess and control risks associated with the release of nanoparticles and nanotubes have drawn parallels with bovine spongiform encephalopathy (‘mad cow’s disease'), thalidomide, genetically modified food,[11] nuclear energy, reproductive technologies, biotechnology, and asbestosis. In light of such concerns, the Canadian based ETC Group have called for a moratorium on nano-related research until comprehensive regulatory frameworks are developed that will ensure workplace safety.

California

In October 2008, the Department of Toxic Substances Control (DTSC), within the California Environmental Protection Agency, announced its intent to request information regarding analytical test methods, fate and transport in the environment, and other relevant information from manufacturers of carbon nanotubes.[12] The term "manufacturers” includes persons and businesses that produce nanotubes in California, or import carbon nanotubes into California for sale. This information request is meant to identify information gaps and to develop further knowledge about the health and safety of carbon nanotubes.

DTSC exercises its authority under California Health and Safety Code, Chapter 699, sections 57018-57020.[13] These sections were added as a result of the adoption of Assembly Bill AB 289 (2006). They are intended to make information on the fate and transport, detection and analysis, and other information on chemicals more available. The law places the responsibility to provide this information to the Department on those who manufacture or import the chemicals. On January 22, 2009, a formal information request letter was sent to manufacturers who produce or import carbon nanotubes in California, or who may export carbon nanotubes into the State. This letter constitutes the first formal implementation of the authorities placed into statute by AB 289 (2006) and is directed to manufacturers of carbon nanotubes, both industry and academia within the State, and to manufacturers outside California who export carbon nanotubes to California. This request for information must be met by the manufacturers within one year.

On January 22, 2010, California manufacturers and importers of carbon nanotubes were required to submit their responses. On January 25, 2010, DTSC posted the responses received to date along with a list of companies that had failed to respond to the information request. On February 16, 2010, DTSC issued a follow-up letter to the companies that failed to submit a response.

DTSC is indicating interest in expanding the Specific Chemical Information Call-in to members of the brominated flame retardants, members of the methyl siloxanes, and other nanometals and nanometal oxides such as vanadium oxide, aluminum oxide, silicon dioxide, titanium dioxide, zinc oxide, cerium oxide, nano platinum, nano silver, and nano zerovalent iron. DTSC is also planning to include quantum dots, ocean plastics, and nanoclay into the list of chemicals of interest.

Toxicology of nanoparticles

Background

Pathways of exposure to nanoparticles and associated diseases as suggested by epidemiological, in vivo and in vitro studies.

Nanotoxicology is a sub-specialty of particle toxicology. It addresses the toxicology of nanoparticles (particles <100 nm diameter) which appear to have toxicity effects that are unusual and not seen with larger particles. Nanoparticles can be divided into combustion-derived nanoparticles (like diesel soot), manufactured nanoparticles like carbon nanotubes and naturally occurring nanoparticles from volcanic eruptions, atmospheric chemistry etc. Typical nanoparticles that have been studied are titanium dioxide, alumina, zinc oxide, carbon black, and carbon nanotubes, and "nano-C60". Nanoparticles have much larger surface area to unit mass ratios which in some cases may lead to greater pro-inflammatory effects (in, for example, lung tissue). In addition, some nanoparticles seem to be able to translocate from their site of deposition to distant sites such as the blood and the brain. This has resulted in a sea-change in how particle toxicology is viewed- instead of being confined to the lungs, nanoparticle toxicologists study the brain, blood, liver, skin and gut. Nanotoxicology has revolutionised particle toxicology and rejuvenated it.

Reactive oxygen species

For some types of particles, the smaller they are, the greater their surface area to volume ratio and the higher their chemical reactivity and biological activity. The greater chemical reactivity of nanomaterials can result in increased production of reactive oxygen species (ROS), including free radicals.[14] ROS production has been found in a diverse range of nanomaterials including carbon fullerenes, carbon nanotubes and nanoparticle metal oxides. ROS and free radical production is one of the primary mechanisms of nanoparticle toxicity; it may result in oxidative stress, inflammation, and consequent damage to proteins, membranes and DNA.[14]

Biodistribution

The extremely small size of nanomaterials also means that they much more readily gain entry into the adsorb onto their surface some of the macromolecules they encounter. This may, for instance, affect the regulatory mechanisms of enzymes and other proteins.

Nanomaterials are able to cross biological membranes and access

  • www.nanoobjects.info Acquisition, evaluation and public orientated presentation of societal relevant data and findings for nanomaterials (DaNa)
  • The ICON Virtual Journal of Nanotechnology Environment, Health and Safety
  • The International Council on Nanotechnology (ICON)
  • The Center for Biological and Environmental Nanotechnology (CBEN), Rice University
  • Nanotoxicity at Institute of Science in Society in London, UK
  • Opportunities and Risks of Nanotechnology
  • TITNT The International Team in NanoToxicology (TITNT) is an initiative of international research scientists interested in different aspects of the risk of toxicity associated to nanoparticles exposure. TITNT is composed of researchers from 5 different countries (Canada, USA, Japan, France and Germany) working together on 5 different specific thematic, and organized as 7 different platforms.
  • Ulrich Hottelet: Tiny particles, huge potential, German Times, December 2009

External links

Further reading

  1. ^ Cristina Buzea, Ivan Pacheco, and Kevin Robbie "Nanomaterials and Nanoparticles: Sources and Toxicity" Biointerphases 2 (1007) MR17-MR71.
  2. ^
  3. ^ http://www.bloomberg.com/apps/news?pid=washingtonstory&sid=aBt.yLf.YfOo study Pollution Particles Lead to Higher Heart Attack Risk (Update1)
  4. ^ The Healthy Facilities Institute archive a document exploring the last 63 years of aerosol nanoparticle evaluation at their web site HERE - http://www.healthyfacilitiesinstitute.com/a_253-Commentary_What_You_Cant_See_Can_Still_Hurt_You
  5. ^
  6. ^ Since 2005 a peer reviewed paper, cited by 1058, has remarked that silver nanoparticles are a bactericide and that this property is "only" size dependent, EPA reference - http://hero.epa.gov/index.cfm?action=reference.details&reference_id=196271
  7. ^
  8. ^ Woodrow Wilson Centre for International Scholars Project on Emerging Nanotechnologies
  9. ^
  10. ^
  11. ^
  12. ^
  13. ^
  14. ^ a b c
  15. ^
  16. ^ a b c
  17. ^ a b
  18. ^
  19. ^
  20. ^ a b c
  21. ^ a b
  22. ^
  23. ^ a b
  24. ^
  25. ^
  26. ^
  27. ^
  28. ^
  29. ^
  30. ^
  31. ^
  32. ^
  33. ^
  34. ^ http://www.nanosafe.org/scripts/home/publigen/content/templates/show.asp?P=63&L=EN&ITEMID=13
  35. ^
  36. ^ Mol. Cell. Neurosci. 31 (2006) 642 – 648
return p

end

', table.concat(classes, ' '), s )
%s
function p._hatnote(s, options) checkType('_hatnote', 1, s, 'string') checkType('_hatnote', 2, options, 'table', true) local classes = {'hatnote'} local extraclasses = options.extraclasses local selfref = options.selfref if type(extraclasses) == 'string' then classes[#classes + 1] = extraclasses end if selfref then classes[#classes + 1] = 'selfref' end return string.format( '

function p.hatnote(frame) local args = getArgs(frame) local s = args[1] local options = {} if not s then return p.makeWikitextError( 'no text specified', 'Template:Hatnote#Errors', args.category ) end options.extraclasses = args.extraclasses options.selfref = args.selfref return p._hatnote(s, options) end


-- Hatnote -- -- Produces standard hatnote text. Implements the template.


function p._formatLink(link, display) -- Find whether we need to use the colon trick or not. We need to use the -- colon trick for categories and files, as otherwise category links -- categorise the page and file links display the file. checkType('_formatLink', 1, link, 'string') checkType('_formatLink', 2, display, 'string', true) link = removeInitialColon(link) local namespace = p.findNamespaceId(link, false) local colon if namespace == 6 or namespace == 14 then colon = ':' else colon = end -- Find whether a faux display value has been added with the | magic -- word. if not display then local prePipe, postPipe = link:match('^(.-)|(.*)$') link = prePipe or link display = postPipe end -- Find the display value. if not display then local page, section = link:match('^(.-)#(.*)$') if page then display = page .. ' § ' .. section end end -- Assemble the link. if display then return string.format('%s', colon, link, display) else return string.format('%s%s', colon, link) end end

function p.formatLink(frame) local args = getArgs(frame) local link = args[1] local display = args[2] if not link then return p.makeWikitextError( 'no link specified', 'Template:Format hatnote link#Errors', args.category ) end return p._formatLink(link, display) end


-- Format link -- -- Makes a wikilink from the given link and display values. Links are escaped -- with colons if necessary, and links to sections are detected and displayed -- with " § " as a separator rather than the standard MediaWiki "#". Used in -- the template.


function p.makeWikitextError(msg, helpLink, addTrackingCategory) -- Formats an error message to be returned to wikitext. If -- addTrackingCategory is not false after being returned from -- Module:Yesno, and if we are not on a talk page, a tracking category -- is added. checkType('makeWikitextError', 1, msg, 'string') checkType('makeWikitextError', 2, helpLink, 'string', true) yesno = require('Module:Yesno') local title = mw.title.getCurrentTitle() -- Make the help link text. local helpText if helpLink then helpText = ' (help)' else helpText = end -- Make the category text. local category if not title.isTalkPage and yesno(addTrackingCategory) ~= false then category = 'Hatnote templates with errors' category = string.format( '%s:%s', mw.site.namespaces[14].name, category ) else category = end return string.format( '%s', msg, helpText, category ) end

function p.formatPageTables(...) -- Takes a list of page/display tables and returns it as a list of -- formatted links. Nil values are not allowed. local pages = {...} local links = {} for i, t in ipairs(pages) do checkType('formatPageTables', i, t, 'table') local link = t[1] local display = t[2] links[i] = p._formatLink(link, display) end return links end

function p.formatPages(...) -- Formats a list of pages using formatLink and returns it as an array. Nil -- values are not allowed. local pages = {...} local ret = {} for i, page in ipairs(pages) do ret[i] = p._formatLink(page) end return ret end

function p.findNamespaceId(link, removeColon) -- Finds the namespace id (namespace number) of a link or a pagename. This -- function will not work if the link is enclosed in double brackets. Colons -- are trimmed from the start of the link by default. To skip colon -- trimming, set the removeColon parameter to true. checkType('findNamespaceId', 1, link, 'string') checkType('findNamespaceId', 2, removeColon, 'boolean', true) if removeColon ~= false then link = removeInitialColon(link) end local namespace = link:match('^(.-):') if namespace then local nsTable = mw.site.namespaces[namespace] if nsTable then return nsTable.id end end return 0 end

local function removeInitialColon(s) -- Removes the initial colon from a string, if present. return s:match('^:?(.*)') end

local function getArgs(frame) -- Fetches the arguments from the parent frame. Whitespace is trimmed and -- blanks are removed. mArguments = require('Module:Arguments') return mArguments.getArgs(frame, {parentOnly = true}) end


-- Helper functions


local p = {}

local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local mArguments -- lazily initialise Module:Arguments local yesno -- lazily initialise Module:Yesno


return p-------------------------------------------------------------------------------- -- Module:Hatnote -- -- -- -- This module produces hatnote links and links to related articles. It -- -- implements the and meta-templates and includes -- -- helper functions for other Lua hatnote modules. --

end

', table.concat(classes, ' '), s )
%s
function p._hatnote(s, options) checkType('_hatnote', 1, s, 'string') checkType('_hatnote', 2, options, 'table', true) local classes = {'hatnote'} local extraclasses = options.extraclasses local selfref = options.selfref if type(extraclasses) == 'string' then classes[#classes + 1] = extraclasses end if selfref then classes[#classes + 1] = 'selfref' end return string.format( '

function p.hatnote(frame) local args = getArgs(frame) local s = args[1] local options = {} if not s then return p.makeWikitextError( 'no text specified', 'Template:Hatnote#Errors', args.category ) end options.extraclasses = args.extraclasses options.selfref = args.selfref return p._hatnote(s, options) end


-- Hatnote -- -- Produces standard hatnote text. Implements the template.


function p._formatLink(link, display) -- Find whether we need to use the colon trick or not. We need to use the -- colon trick for categories and files, as otherwise category links -- categorise the page and file links display the file. checkType('_formatLink', 1, link, 'string') checkType('_formatLink', 2, display, 'string', true) link = removeInitialColon(link) local namespace = p.findNamespaceId(link, false) local colon if namespace == 6 or namespace == 14 then colon = ':' else colon = end -- Find whether a faux display value has been added with the | magic -- word. if not display then local prePipe, postPipe = link:match('^(.-)|(.*)$') link = prePipe or link display = postPipe end -- Find the display value. if not display then local page, section = link:match('^(.-)#(.*)$') if page then display = page .. ' § ' .. section end end -- Assemble the link. if display then return string.format('%s', colon, link, display) else return string.format('%s%s', colon, link) end end

function p.formatLink(frame) local args = getArgs(frame) local link = args[1] local display = args[2] if not link then return p.makeWikitextError( 'no link specified', 'Template:Format hatnote link#Errors', args.category ) end return p._formatLink(link, display) end


-- Format link -- -- Makes a wikilink from the given link and display values. Links are escaped -- with colons if necessary, and links to sections are detected and displayed -- with " § " as a separator rather than the standard MediaWiki "#". Used in -- the template.


function p.makeWikitextError(msg, helpLink, addTrackingCategory) -- Formats an error message to be returned to wikitext. If -- addTrackingCategory is not false after being returned from -- Module:Yesno, and if we are not on a talk page, a tracking category -- is added. checkType('makeWikitextError', 1, msg, 'string') checkType('makeWikitextError', 2, helpLink, 'string', true) yesno = require('Module:Yesno') local title = mw.title.getCurrentTitle() -- Make the help link text. local helpText if helpLink then helpText = ' (help)' else helpText = end -- Make the category text. local category if not title.isTalkPage and yesno(addTrackingCategory) ~= false then category = 'Hatnote templates with errors' category = string.format( '%s:%s', mw.site.namespaces[14].name, category ) else category = end return string.format( '%s', msg, helpText, category ) end

function p.formatPageTables(...) -- Takes a list of page/display tables and returns it as a list of -- formatted links. Nil values are not allowed. local pages = {...} local links = {} for i, t in ipairs(pages) do checkType('formatPageTables', i, t, 'table') local link = t[1] local display = t[2] links[i] = p._formatLink(link, display) end return links end

function p.formatPages(...) -- Formats a list of pages using formatLink and returns it as an array. Nil -- values are not allowed. local pages = {...} local ret = {} for i, page in ipairs(pages) do ret[i] = p._formatLink(page) end return ret end

function p.findNamespaceId(link, removeColon) -- Finds the namespace id (namespace number) of a link or a pagename. This -- function will not work if the link is enclosed in double brackets. Colons -- are trimmed from the start of the link by default. To skip colon -- trimming, set the removeColon parameter to true. checkType('findNamespaceId', 1, link, 'string') checkType('findNamespaceId', 2, removeColon, 'boolean', true) if removeColon ~= false then link = removeInitialColon(link) end local namespace = link:match('^(.-):') if namespace then local nsTable = mw.site.namespaces[namespace] if nsTable then return nsTable.id end end return 0 end

local function removeInitialColon(s) -- Removes the initial colon from a string, if present. return s:match('^:?(.*)') end

local function getArgs(frame) -- Fetches the arguments from the parent frame. Whitespace is trimmed and -- blanks are removed. mArguments = require('Module:Arguments') return mArguments.getArgs(frame, {parentOnly = true}) end


-- Helper functions


local p = {}

local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local mArguments -- lazily initialise Module:Arguments local yesno -- lazily initialise Module:Yesno


-- Module:Hatnote -- -- -- -- This module produces hatnote links and links to related articles. It -- -- implements the and meta-templates and includes -- -- helper functions for other Lua hatnote modules. --


References

See also

AEM - Analytical Electron Microscopy was used over 40 years ago to investigate amphibole asbestos bodies in Lake Superior from the Reserve Mining operations. This could non-destructively characterise sub micron particles. Today AEM can fully characterise to atom dimensions. Perhaps AEM should be employed to attempt to achieve those goals discussed above?

It is not easy to determine to what extent a given nanoparticle has a dramatic effect when compared to comparable nanoparticles already present in our environment either through natural/biological origin or through human activity.[36]

There is a need for new methodologies to quickly assess the presence and reactivity of nanoparticles in commercial, environmental, and biological samples since current detection techniques require expensive and complex analytical instrumentation. There have been recent attempts to address these issues by developing and investigating sensitive, simple and portable colorimetric detection assays that asses for the surface reactivity of NPs, which can be used to detect the presence of NPs, in environmental and biological relevant samples.[35] Surface redox reactivity is a key emerging property related to potential toxicity of NPs with living cells, and can be used as a key surrogate for determine for the presence of NPs and a first tier analytical strategy toward assessing NP exposures.

With comparison to more conventional toxicology studies, the nanotoxicology field is however suffering from a lack of easy characterisation of the potential contaminants, the "nano" scale being a scale difficult to comprehend. The biological systems are themselves still not completely known at this scale. Ultimate Atomic visualisation methods such as Electron microscopy (SEM and TEM) and Atomic force microscopy (AFM) analysis allow visualisation of the nano world. Further nanotoxicology studies will require precise characterisation of the specificities of a given nano-element : size, chemical composition, detailed shape, level of aggregation, combination with other vectors, etc. Above all, these properties would have to be determined not only on the nanocomponent before its introduction in the living environment but also in the (mostly aqueous) biological environment.[34]

Challenges of the nano-visualisation and related unknowns in nanotoxicology

A method was published that can be used to produce different mean sizes of stable agglomerates of several metal, metal oxide, and polymer nanoparticles in cell culture media for cell toxicity studies.[33] Different mean sizes of agglomerates are produced by allowing the nanoparticles to agglomerate to a particular size in cell culture media without protein, and then adding protein to coat the agglomerates and "freeze" them at that size. By waiting different amounts of time before adding protein, different mean sizes of agglomerates of a single type of nanoparticle can be produced in an otherwise identical solution, allowing one to study how agglomerate size affects toxicity. In addition, it was found that vortexing while adding a high concentration of nanoparticles to the cell culture media produces much less agglomerated nanoparticles than if the dispersed solution is only mixed after adding the nanoparticles.

Many nanoparticles agglomerate or aggregate when they are placed in environmental or biological fluids.[32] The terms agglomeration and aggregation have distinct definitions according to the standards organizations ISO and ASTM, where agglomeration signifies more loosely bound particles and aggregation signifies very tightly bound or fused particles (typically occurring during synthesis or drying). Nanoparticles frequently agglomerate due to the high ionic strength of environmental and biological fluids, which shields the repulsion due to charges on the nanoparticles. Unfortunately, agglomeration has frequently been ignored in nanotoxicity studies, even though agglomeration would be expected to affect nanotoxicity since it changes the size, surface area, and sedimentation properties of the nanoparticles. In addition, many nanoparticles will agglomerate to some extent in the environment or in the body before they reach their target, so it is desirable to study how toxicity is affected by agglomeration.

Effect of aggregation or agglomeration of nanoparticles

In addition, standarization of toxicology tests between laboratories are needed. Díaz, B. et al. from the University of Vigo (Spain) has shown (Small, 2008) that many different cell lines should be studied in order to know if a nanostructure induces toxicity, and human cells can internalize aggregated nanoparticles. Moreover, it is important to take into account that many nanostructures aggregate in biological fluids, but groups manufacturing nanostructures do not care much about this matter. Many efforts of interdisciplinary groups are strongly needed in order to progress in this field.

Size is therefore a key factor in determining the potential toxicity of a particle. However it is not the only important factor. Other properties of nanomaterials that influence toxicity include: chemical composition, shape, surface structure, surface charge, aggregation and solubility,[14] and the presence or absence of functional groups of other chemicals.[31] The large number of variables influencing toxicity means that it is difficult to generalise about health risks associated with exposure to nanomaterials – each new nanomaterial must be assessed individually and all material properties must be taken into account.

Complications with nanotoxicity studies

Very little attention has been directed towards the potential immunogenicity of nanostructures. Nanostructures can activate the immune system, inducing inflammation, immune responses, allergy, or even affect to the immune cells in a deleterious or beneficial way (immunosuppression in autoimmune diseases, improving immune responses in vaccines). More studies are needed in order to know the potential deleterious or beneficial effects of nanostructures in the immune system. In comparison to conventional pharmaceutical agents, nanostructures have very large sizes, and immune cells, especially phagocytic cells, recognize and try to destroy them.

Immunogenicity of nanoparticles

A comprehensive and recent review of work on fullerene toxicity is available in "Toxicity Studies of Fullerenes and Derivatives," a chapter from the book "Bio-applications of Nanoparticles".[30] In this work, the authors review the work on fullerene toxicity beginning in the early 1990s to present, and conclude that the evidence gathered since the discovery of fullerenes overwhelmingly points to C60 being non-toxic. As is the case for toxicity profile with any chemical modification of a structural moiety, the authors suggest that individual molecules be assessed individually.

Nanoparticles can also be made of C60, as is the case with almost any room temperature solid, and several groups have done this and studied toxicity of such particles. The results in the work of Oberdörster at Southern Methodist University, published in "Environmental Health Perspectives" in July 2004, in which questions were raised of potential cytotoxicity, has now been shown by several sources to be likely caused by the tetrahydrofuran used in preparing the 30 nm–100 nm particles of C60 used in the research. Isakovic, et al., 2006, who review this phenomenon, gives results showing that removal of THF from the C60 particles resulted in a loss of toxicity.[28] Sayes, et al., 2007, also show that particles prepared as in Oberdorster caused no detectable inflammatory response when instilled intratracheally in rats after observation for 3 months,[29] suggesting that even the particles prepared by Oberdorster do not exhibit markers of toxicity in mammalian models. This work used as a benchmark quartz particles, which did give an inflammatory response.

No fullerene toxicity reported

As the use of nanomaterials increases worldwide, concerns for worker and user safety are mounting. To address such concerns, the Swedish Karolinska Institute conducted a study in which various nanoparticles were introduced to human lung epithelial cells. The results, released in 2008, showed that iron oxide nanoparticles caused little DNA damage and were non-toxic. Zinc oxide nanoparticles were slightly worse. Titanium dioxide caused only DNA damage. Carbon nanotubes caused DNA damage at low levels. Copper oxide was found to be the worst offender, and was the only nanomaterial identified by the researchers as a clear health risk.[26] The latest toxicology studies on mice involving exposure to carbon nanotubes (CNT) showed a limited pulmonary inflammatory potential of MWCNT at levels corresponding to the average inhalable elemental carbon concentrations observed in U.S.-based CNT facilities. The study estimated that considerable years of exposure are necessary for significant pathology to occur. [27]

Researcher Shosaku Kashiwada of the brain, testis, liver, and bloodstream. One major result from this study was the fact that salinity may have a large influence on the bioavailibility and toxicity of nanoparticles to penetrate membranes and eventually kill the specimen.[25]

Since there is no authority to regulate nanotech-based products, there are many products that could possibly be dangerous to humans. Scientific research has indicated the potential for some nanomaterials to be toxic to humans or the environment.[16][17] In March 2004 tests conducted by environmental toxicologist Eva Oberdörster, Ph.D. working with Southern Methodist University in Texas, found extensive brain damage to fish exposed to fullerenes for a period of just 48 hours at a relatively moderate dose of 0.5 parts per million (commensurate with levels of other kinds of pollution found in bays). The fish also exhibited changed gene markers in their livers, indicating their entire physiology was affected. In a concurrent test, the fullerenes killed water fleas, an important link in the marine food chain.[20] The extremely small size of fabricated nanomaterials also means that they are much more readily taken up by living tissue than presently known toxins. Nanoparticles can be inhaled, swallowed, absorbed through skin and deliberately or accidentally injected during medical procedures. They might be accidentally or inadvertently released from materials implanted into living tissue.

Nanotoxicity studies

[24][21] and induce major structural damage to mitochondria, even resulting in cell death.[23]mutation DNA Studies demonstrate the potential for nanomaterials to cause [23][22].cell nucleus and the [21]mitochondria Unlike larger particles, nanomaterials may be taken up by cell [16].cell death production and cytokine, inflammatory oxidative stress Nanomaterials have proved toxic to human tissue and cell cultures, resulting in increased [20]

This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 


Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.