⏱ In-Use Stability After Reconstitution
This simulation evaluates the stability of a reconstituted drug product from the moment it is opened until its intended use to ensure safety and efficacy.
The Sealed Product — Living Inside Its Primary Expiry Date
Before it is ever touched by a clinician, a parenteral drug product exists in a stable, closed system. A lyophilized cake or a sterile liquid sits behind an intact stopper and crimp seal, stored exactly as its label prescribes, degrading so slowly that regulators can assign it a shelf-life measured in months or years. This is the baseline against which every subsequent handling step will be judged — and it is a fundamentally more forgiving state than anything that follows reconstitution.
- 18–36 mo: Typical unopened shelf-life (refrigerated biologic, sealed)
- Intact: Container closure integrity (stopper + aluminum crimp seal)
- <0.5%/mo: Degradation rate (sealed, cold) (potency loss, typical mAb)
- N₂ or vacuum: Headspace condition (oxidative stress minimized)
Why the sealed state is stability-favorable
An unopened, unreconstituted vial benefits from several protective conditions simultaneously:
• No dilution or reconstitution stress: lyophilized product has no bulk water available to drive hydrolysis, deamidation, or aggregation — these pathways require a mobile aqueous phase • Inert headspace: many vials are filled under nitrogen or partial vacuum, starving the product of the oxygen needed for oxidative degradation of susceptible residues (methionine, tryptophan, cysteine) • Sterility barrier intact: the stopper-vial interface, validated for container closure integrity (CCI) by helium leak or dye ingress testing, keeps the fill sterile with essentially zero bioburden ingress risk for the labeled shelf-life • Controlled, monitored storage: shelf-life stability programs (ICH Q1A) study the sealed configuration under long-term (recommended storage), intermediate, and accelerated conditions — the resulting expiry date assumes the container is never opened
Shelf-life stability vs. in-use stability — two different questions
It is tempting to treat the printed expiry date as the only number that matters, but it answers a narrower question than clinicians need. Shelf-life stability asks: "how long can this sealed container sit on a shelf before it must not be dispensed?" In-use stability asks something else entirely: "once this container has been opened, punctured, or reconstituted, how long can the resulting preparation be handled before it must be administered or discarded?"
These two numbers are studied separately, reported separately, and printed separately on the label — because the physical and biological realities they govern are not the same.
A vial can be well within its 24-month shelf-life and still be unsafe to use six hours after reconstitution. The printed expiry date and the in-use period are independent constraints — the product must satisfy both simultaneously, and the shorter of the two always governs.
Reconstitution and First Puncture — Where the In-Use Clock Begins
The moment a needle passes through a septum, or diluent is injected into a lyophilized cake, everything changes. A closed, chemically inert system becomes an open, aqueous, biologically exposed one. This single event — reconstitution, or the very first puncture of a multi-dose vial — is the regulatory and physical starting line for an entirely new stability clock that runs in parallel with, and independently of, the primary expiry date.
- Breached: Sterility barrier status (first needle pass or dilution)
- T = 0: New clock start (in-use period begins here)
- 1–20 mL: Typical reconstitution volume (WFI, saline, or proprietary diluent)
- <30 min: Time to first dose (typical) (clinical workflow target)
What actually changes at the moment of reconstitution
Reconstitution is not a cosmetic step — it converts the product into a physically and chemically distinct system:
• Bulk water is introduced: hydrolysis, deamidation of Asn/Gln residues, and disulfide scrambling become kinetically accessible in a way they never were in the dry cake • Concentration and pH shift locally: as lyophilized cake dissolves, transient micro-regions of high concentration and altered pH can drive aggregation before the solution fully equilibrates • Mechanical stress is introduced: swirling or shaking to dissolve the cake generates air-liquid interfaces and shear — both known drivers of protein aggregation and sub-visible particle formation • The sterility barrier is breached: for single-use biologics, this preparation now typically contains no antimicrobial preservative — any bioburden introduced during the puncture has no chemical defense and can proliferate • For multi-dose vials, the same puncture event recurs with every subsequent dose withdrawal, and each one is a fresh opportunity for microbial ingress
Single-use vs. multi-dose — two very different risk profiles
The design intent of the container fundamentally changes what happens after this event:
Single-use / single-dose products: reconstituted once, the entire contents withdrawn for one patient (or one infusion bag), and the vial discarded. No antimicrobial preservative is typically included (per USP <1> and most regulatory guidance, preservatives are discouraged in single-dose parenterals because they add unnecessary excipient exposure). The in-use period here is driven almost entirely by chemical and physical stability, plus the modest microbial risk of a single needle entry under aseptic technique.
Multi-dose products: formulated with an antimicrobial preservative (e.g. benzyl alcohol, phenol, m-cresol) specifically because the vial will be punctured repeatedly over days to weeks. The in-use period here must account for cumulative puncture risk and the preservative's ability to keep pace with it — a fundamentally microbiological question layered on top of the chemical one.
Regulatory guidance treats "time zero" for the in-use clock as the moment of first needle entry or diluent addition — not the moment the product happens to be dispensed to the patient. Any delay between reconstitution and administration counts against the in-use period, which is why clinical workflows are designed to minimize it.
Tracking Potency Loss, Aggregation, and Particulates Across the In-Use Window
Once reconstituted, the product is placed into a formal in-use stability study that mimics real handling: held at the temperatures and light exposures a clinical setting would actually use, then pulled at defined intervals and tested by orthogonal methods. The goal is to find the point at which chemical degradation or physical instability first becomes detectable — well before it becomes clinically meaningful — and to back off from that point with margin.
- 0, 4, 8, 24, 48 h: Typical test intervals (plus longer excursion arms)
- RP-HPLC / SEC: Potency assay (vs. reference standard)
- USP <788>: Sub-visible particle limit (≥10 µm and ≥25 µm counts)
- ≥90%: Acceptable potency floor (of labeled strength, typical)
What gets measured, and why each test exists
A chemical/physical in-use study is a multi-attribute panel run in parallel, not a single pass/fail number:
• Potency / assay (RP-HPLC, ELISA, cell-based bioassay): quantifies intact, active drug relative to a reference standard — captures chemical degradation (hydrolysis, oxidation, deamidation) that reduces the fraction of correctly-folded, active molecule • Size-exclusion chromatography (SEC): detects soluble aggregates (dimers, high-molecular-weight species) forming as the reconstituted solution ages — aggregation is often the fastest-moving attribute post-reconstitution • Sub-visible particulate counting (USP <788>, light obscuration): counts particles ≥10 µm and ≥25 µm per container — rising counts signal early-stage aggregation or precipitation before it is visible to the eye • Visual inspection: turbidity, discoloration, precipitate, or visible particulates under defined lighting — the simplest and often earliest clinical red flag • pH and osmolality drift: confirms the diluent and drug product have not shifted the solution outside its stable range
Each interval sample is tested by all of these in parallel, generating a degradation-vs-time curve for every attribute.
Worst-case study design — simulating the clinic, not the lab bench
A well-designed in-use study deliberately stresses the product harder than routine handling should, so the resulting limit carries real margin:
• Temperature arms: both the labeled storage condition (e.g. 2–8°C) and a realistic room-temperature excursion (20–25°C) are studied — many products are reconstituted in a pharmacy and then held at ambient temperature during transport and administration • Light exposure: photosensitive molecules are studied under both protected (foil-wrapped) and ambient room light conditions to capture accidental light exposure • Container and diluent realism: the actual clinical diluent (saline vs. dextrose), the actual infusion bag or syringe material, and realistic fill volumes are used — leachables and adsorption to plastic surfaces are real risk factors • Agitation/transport simulation: some protocols include simulated transport vibration, since aggregation-prone biologics are sensitive to mechanical stress during courier transit between sites
The in-use period assigned to a product is set at the earliest time point, across all attributes and all studied conditions, at which any result first fails its acceptance criterion — then a safety margin is typically subtracted. A single fast-moving attribute (often aggregation, not potency) is usually what defines the limit, not chemical assay decline.
Preservative Effectiveness and Bioburden Across Repeated Punctures
For multi-dose vials, the in-use question is not only "does the molecule stay intact?" but "does the formulation stay sterile enough, dose after dose, needle stick after needle stick, for the entire labeled in-use period?" This is tested formally with preservative effectiveness testing (USP <51> / Ph. Eur. 5.1.3) and simulated-use bioburden challenge studies that mimic exactly the clinical handling the vial will see.
- USP <51>: Preservative effectiveness test (antimicrobial effectiveness testing)
- up to 20–100×: Typical puncture simulation (needle entries over in-use period)
- ≥1.0 log by 7d: Log-reduction requirement (bacteria) (no increase through 28d (Category 1))
- Benzyl alcohol, phenol, m-cresol: Common preservatives (multi-dose parenteral formulations)
USP <51> — challenging the formulation with real organisms
Preservative effectiveness testing directly inoculates the finished formulation with defined challenge organisms and tracks their survival over time:
• Challenge panel: typically includes Staphylococcus aureus, Pseudomonas aeruginosa, Escherichia coli, Candida albicans, and Aspergillus brasiliensis — a representative spread of Gram-positive and Gram-negative bacteria, yeast, and mold • Inoculum: each organism added at 10⁵–10⁶ CFU/mL to separate containers of the actual product • Sampling schedule: viable counts performed at 0, 6–7, 14, and 28 days (USP Category 1, injectable products) • Acceptance criteria (Category 1, parenterals): bacterial counts must not increase and must show ≥1.0 log reduction by 7 days, ≥3.0 log reduction by 14 days, and no increase from the 14-day count through 28 days; yeast and mold counts must not increase from the initial count through 28 days • A formulation that fails these criteria cannot rely on its preservative system to support a multi-dose claim at the studied concentration
Simulated-use puncture studies — bioburden under real clinical handling
Beyond the static USP <51> challenge, many multi-dose in-use programs run a dynamic simulated-use study that mimics the actual dosing pattern:
• Vials are punctured repeatedly with fresh needles at realistic intervals (e.g. once or twice daily) over the full proposed in-use period • A small, controlled microbial challenge is sometimes introduced at select punctures to model accidental contamination from imperfect aseptic technique • Bioburden is sampled after each puncture or at defined intervals, tracking whether the preservative system suppresses any introduced organisms back toward baseline before the next entry • The septum itself is inspected: repeated punctures through the same limited coring zone can, in the worst case, compromise the reseal integrity of the elastomer, so puncture-site condition is tracked alongside microbial counts
A preservative system is not a sterility guarantee — it is a kinetic race. It must knock down a plausible contamination event faster than that contamination can grow to a clinically relevant level before the next dose is withdrawn. The maximum number of punctures and the maximum in-use duration are both set so that this race is won with margin, every single time.
Setting the In-Use Period — A Mandatory Label Instruction, Distinct From Expiry
All three data streams — chemical/physical stability, microbiological control, and (for multi-dose products) preservative performance under repeated puncture — converge into a single set of numbers: a maximum in-use time paired with a required storage condition. This is not a suggestion. It becomes a mandatory instruction printed on the label and in prescribing information, legally and clinically binding in a way distinct from, and layered on top of, the primary expiry date.
- 4–24 h: Typical single-use in-use limit (refrigerated, chemistry-driven)
- 4–6 h: Typical RT excursion limit (ambient, faster degradation)
- 28 days: Typical multi-dose in-use limit (preservative-supported, refrigerated)
- 20–50%: Margin applied to failure point (safety factor below first failure)
From data to a defensible number
Determining the final in-use period is a deliberately conservative exercise:
1. Overlay every attribute's degradation curve — potency, aggregation, particulates, pH, and (for multi-dose) bioburden/preservative performance — on a single timeline for each studied storage condition 2. Identify the earliest time point, across all attributes and conditions, at which any result first approaches or crosses its acceptance criterion 3. Apply a safety margin below that point — accounting for assay variability, real-world handling variance, and the fact that clinical storage is rarely as tightly controlled as a stability chamber 4. Express the result as a matched pair: a maximum duration AND the storage condition it applies to (e.g. "24 hours at 2–8°C" and, separately, "6 hours at room temperature (20–25°C)" if the product is later warmed for administration) 5. For multi-dose products, add the maximum number of punctures or withdrawals validated by the simulated-use study as an additional constraint alongside the time/temperature limit
Why this belongs on the label, separately from the expiry date
The primary expiry date answers "can this sealed container still be dispensed?" The in-use statement answers a completely different, time-critical question that a nurse or pharmacist must apply at the point of care: "now that I have opened/reconstituted/punctured this vial, how long do I personally have before it is no longer usable?"
Because this decision happens in real time, away from the pharmacy stability files, regulatory guidance (ICH Q1A, USP General Notices, FDA labeling guidance) requires the in-use period to be stated explicitly and unambiguously in the product labeling — not left to be inferred from the general expiry date. A product can be fully within its 24-month shelf-life and simultaneously past its in-use limit; both must be checked before every administration.
The in-use statement is the last stability decision made before a dose reaches a patient — and unlike the expiry date, it is enforced by clinical staff reading a label under time pressure, not by a pharmacy inventory system. That is precisely why in-use stability studies are designed with generous safety margins: the number on the label has to be simple, memorable, and safe under real-world conditions, not just technically correct in a controlled study.
This simulation evaluates the stability of a reconstituted drug product from the moment it is opened until its intended use to ensure safety and efficacy.
2D · HTML5 Canvas 2D · 60 FPS target · runs fully client-side, no install