Anti-drug Antibody Validation Testing and Reporting Harmonization
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
Evolving immunogenicity assay performance expectations and a lack of harmonized anti-drug antibody validation testing and reporting tools have resulted in significant time spent by health authorities and sponsors on resolving filing queries. Following debate at the American Association of Pharmaceutical Sciences National Biotechnology Conference, a group was formed to address these gaps. Over the last 3 years, 44 members from 29 organizations (including 5 members from Europe and 10 members from FDA) discussed gaps in understanding immunogenicity assay requirements and have developed harmonization tools for use by industry scientists to facilitate filings to health authorities. Herein, this team provides testing and reporting strategies and tools for the following assessments: (1) pre-study validation cut point; (2) in-study cut points, including procedures for applying cut points to mixed populations; (3) system suitability control criteria for in-study plate acceptance; (4) assay sensitivity, including the selection of an appropriate low positive control; (5) specificity, including drug and target tolerance; (6) sample stability that reflects sample storage and handling conditions; (7) assay selectivity to matrix components, including hemolytic, lipemic, and disease state matrices; (8) domain specificity for multi-domain therapeutics; (9) and minimum required dilution and extraction-based sample processing for titer reporting.
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.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
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 it