What is ICCVAM for, anymore?
By Yiguang Zhu | October 1st, 2026
The ICCVAM Authorization Act of 2000 made the Interagency Coordinating Committee on the Validation of Alternative Methods (ICCVAM) a permanent interagency committee within the National Institute of Environmental Health Sciences (NIEHS), building on the alternative-methods mandate created by the NIH Revitalization Act of 1993 and the ad hoc ICCVAM process that produced the committee’s 1997 validation report. ICCVAM sits within the National Toxicology Program (NTP), is supported by the NTP Interagency Center for the Evaluation of Alternative Toxicological Methods (NICEATM), and draws its members from federal agencies that generate, require, or use toxicity data. Its statutory functions include reviewing new methods, harmonizing protocols across agencies, and facilitating validation and regulatory acceptance. The Act requires relevant agencies to review ICCVAM test recommendations within 180 days, respond in writing, and adopt them unless a statutory ground for refusal applies, while preserving each agency’s final authority over implementation. Congress therefore created ICCVAM not as a temporary panel for a single problem, but as a continuing institutional home for cross-agency validation.
That institutional design matters.
Leadership rotates among senior representatives of member agencies, including EPA, FDA, CPSC, USDA, and others, while NICEATM provides scientific and administrative support from NIEHS. No single regulatory agency owns the process. The structure was designed to reduce duplicative review and let agencies share validation evidence and experience. NICEATM has supplied much of ICCVAM’s practical scientific capacity. That cross-agency function is especially important now: ICCVAM’s 2024 framework offers shared validation principles even as implementation increasingly proceeds through agency-specific programs.
The committee's understanding of its mission has shifted over time. Its 1997 report, Validation and Regulatory Acceptance of Toxicological Test Methods, reflected a case-by-case, endpoint-oriented model of validation and regulatory acceptance. ICCVAM leadership later reconsidered this strategy. In a 2013 commentary, 15 Years Out: Reinventing ICCVAM, NIEHS Director Linda Birnbaum argued that the committee had to align with the 2007 National Research Council vision of a faster, more human-relevant toxicology. The 2018 Strategic Roadmap responded by organizing ICCVAM’s work around three goals: connecting end users with method developers, fostering flexible practices to establish confidence in new methods, and encouraging agencies and industry to adopt them. The 2024 report, Validation, Qualification, and Regulatory Acceptance of New Approach Methodologies moved away from replacing one in vivo test with one alternative method and toward flexible, fit-for-purpose confidence assessment for a defined context of use.
Scientifically, this shift was necessary. Institutionally, however, it changed how ICCVAM’s coordinating authority operates. The earlier model produced method-specific recommendations that entered the Act’s statutory review-and-response process. The current model provides shared vocabulary for confidence building, validation, qualification, and context of use, but the 2024 report does not establish legally enforceable responsibilities. ICCVAM’s concepts therefore spread even as implementation becomes increasingly agency-specific.
FDA’s 2025 roadmap calls for a stepwise reduction of animal testing in preclinical safety studies, and CDER’s 2026 draft guidance frames NAM validation around context of use, human biological relevance, technical characterization, and fit-for-purpose performance. That is ICCVAM's vocabulary, printed under FDA's letterhead. The EPA continues to run its own NAMs Work Plan, developed under its TSCA mandate to reduce vertebrate animal testing, with its own scientific confidence framework and its own list of accepted methods. NIH has said it will no longer develop funding opportunities focused exclusively on animal models and has launched a new Office of Research Innovation, Validation, and Application (ORIVA) to coordinate human-based approaches across its portfolio.
These efforts draw on the 2024 ICCVAM document, but none treats it as the cross-agency standard. ICCVAM’s institutional setting has also shifted. In June 2026, NIH moved NICEATM from NTP into ORIVA within the NIH Office of the Director, where it continues to support ICCVAM’s validation and coordination functions. The move followed the appointment of Dr. Nicole Kleinstreuer, one of ICCVAM’s most visible leaders, to a senior coordinating role in the NIH Office of the Director. Together, these changes place much of the federal leadership on NAMs within a broader NIH-wide structure even as agencies continue to develop their own programs.
The deeper problem is that roadmap- and guidance-based policymaking leaves NAMs policy inherently fragile. New administrations and agency leaders can revise or deprioritize these instruments. NAMs policy can therefore shift with political transitions rather than develop within a stable statutory framework. Yet statutory change can also fall short without implementation mechanisms. The FDA Modernization Act 2.0, enacted in December 2022, replaced the statutory reference to “preclinical tests (including tests on animals)” with the broader category of “nonclinical tests,” which may include animal, non-animal, and human biology-based methods. The Act removed a statutory barrier but did not require FDA to revise its regulations accordingly. Implementation therefore proceeded largely through guidance and agency initiatives while regulatory language lagged behind the statutory change. Congress has since sought to close that gap. The Senate passed one version of the FDA Modernization Act 3.0 in December 2025, and the House passed a companion in July 2026.
ICCVAM should remain in place. It still has a statutory mandate, member agencies, and a 2024 consensus framework for NAM validation. What is absent is a central cross-agency validation process. ICCVAM can serve as the coordinating body for that process. Re-centering validation through ICCVAM would be practical. A consensus framework would reduce duplicative validation and give agencies, developers, and sponsors a shared reference point. ICCVAM’s statutory mandate can provide continuity for that function even as leadership, priorities, and the administrative placement of its support structure change. Coordinating agency validation efforts through ICCVAM would support more stable implementation, more consistent validation practice, and concrete progress toward broader NAMs use.
The views expressed do not necessarily reflect the official policy or position of Johns Hopkins University or Johns Hopkins Bloomberg School of Public Health.
