15 Feb 2022, 18:17
Highlights from Day 1, BOG 1:
Community of Practice:
Thoughts about community
Community of Practice:
Thoughts about community
- AOP development is a big task and Community is a network to get advice and draw from experience
- A way to implement the ICCVAM roadmap goal - communication between developers and users
- Opportunity for developers of test methods and AOPs to understand needs of Regulatory users
- Cross- and Interdisciplinary network of collaborators outside of other colleague networks
- A well-connected community can drive change in ways that individuals cannot
- Need to develop standardized approaches
- Identifying needs that appear across disciplines
- Logical synthesis of information to define causation, essentiality and quantitative relationships between measurable events
- Synthesis and gap analysis that can inform and expedite needed lab research
- AOPs are a means to provide regulators with quick direction and comprehensive review of specific connections between available data
- Current science incentives are based on novelty, not review and synthesis
- Funded projects are necessary
- Can fit an AOP as a milestone within a larger funded project / unmet need
- AOP development is ideal (skill/timeframe) for postdoc projects
- Efforts are underway to generate "stubs" or AOP hypotheses to identify AOP needs - these could become funded postdocs
- Smaller units (e.g. a single KE) could be ideal for shorter time frames / earlier education stages
- Wiki development does not reward work - OECD review and journal reports are a great solution
- Link to AOPs from relevant Pubmed/Pubchem pages - need to reconcile ontologies?
- Improved search - consolidated search box with advanced search term selection (Author, keyword, number)
- Hide orphan AOPs by default to prevent users from being discouraged when first visiting the wiki by finding empty AOPs with great titles