In 2014, EFSA has commissioned the compilation of a database specific for the pesticide residues including active substances and their metabolites, which comprises different genotoxicity endpoints, i.e. point mutations, structural and numerical chromosome aberrations, and DNA damage.
Data collection on individual genotoxicity studies has been retrieved from regulatory toxicological reports (Draft or Renewal Assessment Reports, i.e. DARs or RARs, respectively) as provided by the Rapporteur Member State (RMS) during the pesticide peer review process at European Level. The final EFSA conclusion on the overall genotoxic potential of active substance or metabolites taking into account all available information is not included in the database.
The database contains identity and genotoxicity information on more than 290 active substances and some of their metabolites.
The database represents a practical tool to complement in-silico tools i.e. QSAR (Quantitative structure–activity relationship models), grouping and read across for prediction of the genotoxicity hazard of the pesticides residues, and it supposes to enlarge the chemical domains for their application.
DISCLAIMER
Without prejudice to the legal notice applicable to EFSA's website available here, the following legal notice applies to the Pesticide genotoxicity database and any documents, data or information contained therein. Users are advised to read this legal notice carefully before accessing, using or reading any document, data or information made available in this context, or making any other use of the Database. The Pesticide genotoxicity database is a compilation of chemical and genotoxicity information on active substances and some of their metabolites. The database contains the results of individual studies as initially assessed by the Rapporteur member state (RMS) and reported in the respective Draft assessment reports (DARs) or Renewal Assessment Reports (RARs). The final EFSA Conclusions on the respective active substances are available to the public on the EFSA Journal. The database includes the data that was available at the moment of compilation of the database (December 2016) and will be updated on a regular basis by including or deleting of information as a result of renewal procedure of active substances (Regulation (EU) No 1107/2009). EFSA makes no representations or warranties about the accuracy or suitability of any document, information, data provided in the Database. In case of discrepancy between the data provided in the original scientific output (DARs/RARs) and that in this database, preference shall be given to the former. This database does not disclose any commercially sensitive or otherwise confidential information. Unless otherwise stated, the owners of the data compiled in this database are the applicants under Regulation (EU) No 1107/2009, and by acceiding the Database you acknowledge that agreement for reuse of these data should be sought from them. The information provided in the Database and related materials are not intended to constitute advice of any kind or the rendering of consulting, or other professional services of any kind. Acceding the Database does not establish any contractual relationship with EFSA. Users are advised to consult with an attorney, food consultant or other professional to determine what may be best for your individual needs. By acceding the Database, you also acknowledge that the documents, data or information made available by EFSA may contain inaccuracies or errors. The content of the information provided is for your information and use only. It may be subject to change at any time and without prior notice by EFSA.
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.