This analysis demonstrates QSPR predicts retention of host cell proteins in chromatography, highlighting its potential for biopharmaceutical applications.
BACKGROUND Selecting an optimal chromatography resin during biopharmaceutical downstream process development is a great challenge. This is especially the case for recombinant subunit vaccines, where product properties vary greatly and recovery often involves cell lysis, which yields a complex mixture of different host cell materials. Host cell protein (HCP) impurities may remain similar for platform processes, but their critical impact on separation efficiency is relative to specific product properties. Therefore, every process needs to be designed per product. Prior knowledge on the elution behavior of HCPs would support the identification of critical compounds. However, determining chromatographic behavior of HCPs experimentally is a time‐consuming approach. RESULTS In this work, we leverage quantitative structure–property relationship (QSPR) models calibrated with retention data of 13 commercial proteins, collected at pH 7, 8, 9 and 10 to predict the anion‐exchange retention of Escherichia coli HCPs. These models use features calculated from the molecular structure to describe protein behavior, like chromatographic retention. A multilinear regression model containing two features (isoelectric point and sum of negative surface electrostatics) was able to predict the retention times of 288 HCPs accurately (error ≤ 5%). Moreover, we identified the key attributes missing in the training dataset, which is important to increase model performance in the future. CONCLUSION This work showcases how chromatographic data obtained using commercial proteins can be translated to a clarified E. coli lysate to accelerate chromatography resin selection for new products.
No takes yet. Share an insight, caveat, or question.
Neijenhuis et al. (2025) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: