Skip to content

A Science-Based Proposal for the Identification Threshold of Organic Impurities in Drug–Linker Intermediates Used to Produce Antibody–Drug Conjugates

Oct 2026 · Organic Process Research & Development · 19 references
Biosimilars and Bioanalytical Methods

Abstract

Abstract The identification threshold for organic impurities in drug–linker (D–L) intermediates used to manufacture antibody–drug conjugates (ADCs) remains undefined in the current regulatory landscape. Building on our previously established 1.0% w/w qualification threshold, we propose a science-based identification threshold of 0.25% w/w, derived through the simultaneous application of four independent quantitative criteria to a data set of 47 clinical-stage ADCs. The four criteria are (1) maintenance of a >200-fold safety margin relative to both the ICH Q3A allowable daily intake of 1.0 mg/day and the practical worst-case exposure from conventional small-molecule APIs; (2) preservation of a 5-fold safety-factored benchmark relative to the internal threshold of toxicological concern (iTTC) of 25 nmol/day for parenteral exposure; (3) maintenance of cumulative exposure below one-fifth of the ICH M7 acceptable lifetime dose of 38.3 mg over five years of dosing; and (4) a 1:4 identification-to-qualification ratio, more conservative than precedents for small molecules, peptides, and oligonucleotides. The convergence of these constraints uniquely defines 0.25% w/w as the value simultaneously satisfying all criteria, enabling efficient pharmaceutical development while ensuring patient safety across all oncological ADC indications. The proposed value is intended as a class-wide threshold. Higher product-specific thresholds, including 0.5% w/w and, where scientifically justified, values up to 1.0% w/w, may be considered when product-specific exposure calculations demonstrate compliance with the applicable criteria.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54

Trajectory Balance: Improved Credit Assignment in GFlowNets

It is proved that any global minimizer of the trajectory balance objective can define a policy that samples exactly from the target distribution, and empirically demonstrate the benefits of the trajectories balance objective for GFlowNet convergence, diversity of generated samples, and robustness to long action sequenc...

Esmeralda S. Whitammer, Moksh Jain, Emmanuel Bengio et al. · 302 citations · ⚡60

Related blog posts

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.