PackageIntegrityLeakTestQualityChecker

Package Integrity & Leak Test

LabEx laboratory QC CSV→JSON URS & FS utilities / cleanroom
Open selection
Package Integrity & Leak Test Quality Checker — Control of Package Integrity (CCIT)

ℹ️  Utility checks compliance of leak test results with USP <1207> requirements:
   • Measured leak value must be strictly below the established Reject Limit.
   • Supported methods: HVLD (High Voltage Leak Detection), Vacuum Decay, Pressure Decay.

⚠️  CRITICAL: Exceeding the limit means breach of package barrier function!
   Product is considered non-sterile and must be immediately quarantined.

Usage:
 PackageIntegrityLeakTestQualityChecker.exe                            → demo mode (console output)
 PackageIntegrityLeakTestQualityChecker.exe input.csv output.json      → evaluate your data

Input format:
BatchNumber,MeasuredLeakValue,RejectLimit,TestMethod

Example:
 CCIT-VIAL-2026-001,1.5,5.0,HVLD

— WHY IS THIS NEEDED?
Container Closure Integrity Testing (CCIT) replaces traditional dye immersion testing.
• USP <1207> recommends use of deterministic physicochemical methods (HVLD, vacuum decay).
• Allows detection of microscopic defects (cracks, seal failures, cap defects) invisible to visual inspection.
• Non-destructive method allows product retention if test is passed.
• Automation eliminates risk of missing defective units.

⚠️  CRITICAL:
• Reject Limit must be established based on method validation and critical defect size.
• For HVLD: high conductivity may indicate electrolyte outside vial (leak) or electrode contamination.
• For Vacuum/Pressure Decay: pressure stability over time is key indicator.
• Instrument calibration must be performed using artificial defects of known size.

Key features:
• Verification of measured parameters against safety limits.
• Support for various leak detection technologies.
• Generation of clear PASS/FAIL status for quality management systems.

Critical parameters:
• Leak Value: < Reject Limit

💡 Usage tips:
1. Regularly clean contact surfaces (for HVLD) or chamber seals (for vacuum methods).
2. Check instrument with "zero" sample (dummy) before starting series.
3. Account for ambient temperature and humidity influence on sensor sensitivity.
4. For highly conductive products, use pressure-based methods rather than current-based.
5. Save signal graphs (if available) for investigating questionable results.

⚠️ Note: Unlike Dye Ingress test, which is probabilistic and destructive, these methods are deterministic, quantitative, and allow 100% automated inline control.

input.csv

BatchNumber,MeasuredValue,RejectLimit,TestMethod
CCIT-VIAL-2026-001,1.5,5.0,HVLD
CCIT-VIAL-2026-002,2.1,5.0,HVLD
CCIT-FAIL-2026-003,8.5,5.0,HVLD
CCIT-BAG-2026-001,8.0,10.0,VacuumDecay

URS & FS — Package Integrity & Leak Test

This document describes the user requirements and functional specification for PackageIntegrityLeakTestQualityChecker. 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

IDRequirementCriticalityAcceptance criterion
URS-001The utility shall accept input.csv with approved columns: BatchNumber, MeasuredValue, RejectLimit, TestMethod.HighThe CSV file is processed without manual header editing.
URS-002The utility shall perform deterministic evaluation for “Package Integrity & Leak Test” without machine learning.HighThe same input data produce the same JSON result.
URS-003The utility shall validate mandatory fields, numeric formats, flags, ranges and domain plausibility.HighSchema and conversion errors are explicitly reported.
URS-004The utility shall generate output.json with PASS / WARNING / FAIL statuses, source values, warnings and failures.HighThe JSON result is suitable for review, deviation investigation and integration.
URS-005The documentation shall support IQ/OQ/PQ or CSV/CSA verification.MediumURS/FS, CSV/JSON contract and test scenarios are supplied with the utility.

input.csv contract

#FieldSamplePurpose
1BatchNumberCCIT-VIAL-2026-001Input parameter for deterministic QC evaluation.
2MeasuredValue1.5Input parameter for deterministic QC evaluation.
3RejectLimit5.0Input parameter for deterministic QC evaluation.
4TestMethodHVLDInput parameter for deterministic QC evaluation.

FS — Functional Specification

IDFunctionImplementation
FS-001CSV importRead input.csv; validate header, column count and encoding.
FS-002Schema validationCheck required fields and permitted input values.
FS-003Rule engineApply domain rules, limits and system suitability/specification checks described in the source utility description.
FS-004Status aggregationProduce final status: FAIL for critical failure, WARNING for non-critical deviation, PASS for conformance.
FS-005JSON exportWrite 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 FAIL or 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.

Open

LabEx QC Suite

LabEx package for laboratory QC methods: chromatography, spectroscopy, microbiology, sterility, endotoxins, particles, dissolution, water, cleanrooms and sample preparation.

Open

Radiology QC Suite

QC package for radiology and diagnostic imaging: radiopharmaceuticals, PET/SPECT, contrast media, iodinated and gadolinium products, plus particle, sterility and endotoxin checks.

Open