Abstract

Organization of existing and emerging toxicological knowledge into adverse outcome pathway (AOP) descriptions can facilitate greater application of mechanistic data, including those derived through high-throughput in vitro, high content omics and imaging, and biomarker approaches, in risk-based decision making. The previously ad hoc process of AOP development is being formalized through development of internationally harmonized guidance and principles. The goal of this article was to outline the information content desired for formal AOP description and some rules of thumb and best practices intended to facilitate reuse and connectivity of elements of an AOP description in a knowledgebase and network context. For example, key events (KEs) are measurements of change in biological state that are indicative of progression of a perturbation toward a specified adverse outcome. Best practices for KE description suggest that each KE should be defined as an independent measurement made at a particular level of biological organization. The concept of “functional equivalence” can help guide both decisions about how many KEs to include in an AOP and the specificity with which they are defined. Likewise, in describing both KEs and evidence that supports a causal linkage or statistical association between them (ie, a key event relationship; KER), best practice is to build from and contribute to existing KE or KER descriptions in the AOP knowledgebase rather than creating redundant descriptions. The best practices proposed address many of the challenges and uncertainties related to AOP development and help promote a consistent and reliable, yet flexible approach.JRC.H.1-Water Resource

Similar works

Full text

thumbnail-image

JRC Publications Repository

redirect
Last time updated on 08/06/2016

This paper was published in JRC Publications Repository.

Having an issue?

Is data on this page outdated, violates copyrights or anything else? Report the problem now and we will take corresponding actions after reviewing your request.