ParticleCountInjectionUSP788QualityChecker
Particle Count Injection USP <788>
LabEx laboratory QC CSV→JSON URS & FS utilities / cleanroom
Open selectionParticle Count Injection USP <788> Quality Checker — Control of Subvisible Particles in Injections ℹ️ Utility checks compliance of subvisible particle content with USP <788> requirements: • For small volumes (<100 mL): ≤6000 particles/container (≥10 µm), ≤600 particles/container (≥25 µm) • For large volumes (≥100 mL): ≤25 particles/mL (≥10 µm), ≤3 particles/mL (≥25 µm) ⚠️ CRITICAL: Exceeding particle limits can cause embolism or inflammatory reaction! Requires use of Light Obscuration method or microscopy. Usage: ParticleCountInjectionUSP788QualityChecker.exe → demo mode (console output) ParticleCountInjectionUSP788QualityChecker.exe input.csv output.json → evaluate your data Input format: BatchNumber,SampleVolumeMl,ParticlesGe10um,ParticlesGe25um,LimitType Example: INJ-SVP-2026-001,10.0,500,50,PerContainer — WHY IS THIS NEEDED? Control of mechanical inclusions is critical for safety of parenteral products. • USP <788> regulates permissible levels of particle contamination. • Light Obscuration method is the primary quantitative method. • Distinction between SVP (Small Volume Parenterals) and LVP (Large Volume Parenterals) is important for correct limit application. • Automation eliminates manual calculation and table comparison errors. ⚠️ CRITICAL: • Sample must be degassed to exclude air bubbles, which are counted as particles. • Diluent must be particle-free (filtered). • Instrument must be calibrated using standard spheres (NIST traceable). • If results exceed limits, confirmatory test by microscopic method is performed. Key features: • Automatic limit selection based on volume type (SVP/LVP). • Verification of both particle sizes (10 and 25 µm). • Generation of PASS/FAIL status for QC reports. Critical parameters: • Particles ≥10 µm: Within Limit • Particles ≥25 µm: Within Limit 💡 Usage tips: 1. Thoroughly clean instrument sensor between samples to avoid cross-contamination. 2. Perform test in Class A laminar flow hood to exclude background contamination. 3. Use correct instrument sensitivity threshold settings. 4. For viscous products, dilution with filtered solvent may be required. 5. Record background count of solvent before starting series. ⚠️ Note: USP <788> applies only to solutions intended for intravascular administration. For suspensions or emulsions, other assessment methods apply.
input.csv
BatchNumber,VolumeMl,ParticlesGe10,ParticlesGe25,LimitType INJ-SVP-2026-001,10.0,500,50,PerContainer INJ-LVP-2026-001,500.0,15.0,1.5,PerMl INJ-FAIL-2026-001,10.0,7000,800,PerContainer
URS & FS — Particle Count Injection USP <788>
This document describes the user requirements and functional specification for ParticleCountInjectionUSP788QualityChecker. The utility is intended for QC laboratory use as a rule-based check of data prepared from an instrument, LIMS, ELN, MES or an approved input.csv.
URS — User Requirements Specification
| ID | Requirement | Criticality | Acceptance criterion |
|---|---|---|---|
| URS-001 | The utility shall accept input.csv with approved columns: BatchNumber, VolumeMl, ParticlesGe10, ParticlesGe25, LimitType. | High | The CSV file is processed without manual header editing. |
| URS-002 | The utility shall perform deterministic evaluation for “Particle Count Injection USP <788>” without machine learning. | High | The same input data produce the same JSON result. |
| URS-003 | The utility shall validate mandatory fields, numeric formats, flags, ranges and domain plausibility. | High | Schema and conversion errors are explicitly reported. |
| URS-004 | The utility shall generate output.json with PASS / WARNING / FAIL statuses, source values, warnings and failures. | High | The JSON result is suitable for review, deviation investigation and integration. |
| URS-005 | The documentation shall support IQ/OQ/PQ or CSV/CSA verification. | Medium | URS/FS, CSV/JSON contract and test scenarios are supplied with the utility. |
input.csv contract
| # | Field | Sample | Purpose |
|---|---|---|---|
| 1 | BatchNumber | INJ-SVP-2026-001 | Input parameter for deterministic QC evaluation. |
| 2 | VolumeMl | 10.0 | Input parameter for deterministic QC evaluation. |
| 3 | ParticlesGe10 | 500 | Input parameter for deterministic QC evaluation. |
| 4 | ParticlesGe25 | 50 | Input parameter for deterministic QC evaluation. |
| 5 | LimitType | PerContainer | Input parameter for deterministic QC evaluation. |
FS — Functional Specification
| ID | Function | Implementation |
|---|---|---|
| FS-001 | CSV import | Read input.csv; validate header, column count and encoding. |
| FS-002 | Schema validation | Check required fields and permitted input values. |
| FS-003 | Rule engine | Apply domain rules, limits and system suitability/specification checks described in the source utility description. |
| FS-004 | Status aggregation | Produce final status: FAIL for critical failure, WARNING for non-critical deviation, PASS for conformance. |
| FS-005 | JSON export | Write machine-readable output.json for LIMS/ELN/MES and QA/QC review. |
OQ/PQ scenarios
- OQ-001: a valid sample row shall be processed without schema error.
- OQ-002: a missing mandatory column shall produce a schema error.
- OQ-003: a non-numeric value in a numeric field shall produce a conversion error.
- OQ-004: a critical parameter outside the limit shall produce
FAILor a critical finding. - PQ-001: user real batches shall be checked with retention of
input.csv,output.json, utility version and checksum.
Included in packages
Biopharmaceuticals Extended QC Suite
Extended QC utility coverage for mAbs, biosimilars, proteins, insulins, vaccines, mRNA/LNP, HCP, sterile release, microbiology, water, cleanroom and stability workflows.
OpenLabEx QC Suite
LabEx package for laboratory QC methods: chromatography, spectroscopy, microbiology, sterility, endotoxins, particles, dissolution, water, cleanrooms and sample preparation.
Open