Methods2AOP: A Collaboration to Strengthen the Integration of Test Methods into the Adverse Outcome Pathway Framework
Bibliographic record
Abstract
The Adverse Outcome Pathway (AOP) framework is a pivotal tool for organizing mechanistic knowledge and linking it to adverse outcomes of regulatory significance. However, the integration of test method information, particularly New Approach Methods (NAMs), within the central repository for AOP knowledge, (the AOP-Wiki), has been suboptimal, limiting the framework's utility for regulatory decision-making. The Methods2AOP collaboration, comprised of various international stakeholders, was established to address this gap and enhance the role of test methods within the AOP framework. This paper reviews their work emphasizing the importance of linking detailed test method information and conceptually proposes how it may be included in the AOP knowledgebase in alignment with existing assay documentation standards and governance frameworks. The Methods2AOP collaboration proposes using ontologies to standardize and structure information, thereby facilitating interoperability, enabling reusability, and establishing clear connections between test methods and Key Events (KEs). A conceptual model is presented to demonstrate qualitative similarities between concepts in key event components and structured methods information. The implementation of Methods2AOP recommendations would increase the clarity and transparency of method descriptions, which could support regulatory acceptance and a wider adoption of NAMs. The broad community of stakeholders impacted by this work stands to benefit from the Methods2AOP recommendations through enhanced regulatory decisions, increased visibility and scientific impact, new market opportunities, and the accelerated adoption of NAMs in regulatory affairs. In summary, the Methods2AOP collaboration presents a comprehensive effort to formally standardize the integration of test methods into the AOP framework, thereby fostering a more robust, and transparent system that aligns with the goals of the scientific and regulatory communities.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.188 | 0.159 |
| Meta-epidemiology (narrow) | 0.003 | 0.002 |
| Meta-epidemiology (broad) | 0.002 | 0.004 |
| Bibliometrics | 0.012 | 0.007 |
| Science and technology studies | 0.006 | 0.010 |
| Scholarly communication | 0.021 | 0.027 |
| Open science | 0.008 | 0.042 |
| Research integrity | 0.009 | 0.013 |
| Insufficient payload (model declined to judge) | 0.015 | 0.008 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".