- Regulators expect biosimilar elastomeric closures to meet originator-level requirements for functional suitability, extractables and leachables (E&L), and container closure integrity (CCI).
- Supplier data can inform risk assessment but cannot replace system-level, product-specific testing; the applicant retains regulatory responsibility.
- Format migration (e.g., to prefilled syringes or autoinjectors) or changes in elastomer formulation/coating can invalidate existing E&L data and require requalification.
- Adopt a platform approach and finalize closure choices early to minimize requalification effort and simplify dual-market filings.
Regulatory expectations
Elastomeric closures for biosimilars must meet the same core principles as originator products: functional suitability, extractables and leachables (E&L), and container closure integrity (CCI). USP <382> outlines functional suitability assessment for injectable elastomers, and agencies (FDA, EMA, CDSCO) expect applicants to justify elastomer selection and demonstrate suitability across the product lifecycle.
Evidence and responsibility
Supplier-generated data can support early risk assessment but do not replace system-level, product-specific evaluation of the assembled container-closure system; regulatory responsibility remains with the applicant and grows with multi-format or multi-market programs.
Key program vulnerabilities
Two common exposures are format migration—where changes in elastomer formulation, coating, or manufacturing between presentations (e.g., to prefilled syringes or autoinjectors) can invalidate existing E&L data—and dual-market filings, which require coherent E&L and CCI strategies adaptable to different agency expectations and robust change control and documentation.
Platform approach and timing
Establishing elastomer components, manufacturing standards, E&L characterization, and supplier relationships on a platform basis can reduce requalification when formulations/coatings and specs remain unchanged; closure decisions are most flexible early in development, so pressure-test strategy and documentation before committing timelines.
