BacterialCountBioburdenChecker
Bacterial Count Bioburden
Vet veterinary veterinary vaccines animal health adjuvants aquaculture batch release CSV→JSON
Open selectionUtility description: Bacterial Count Bioburden
Bacterial Count Bioburden Checker — Control of Microbial Bioburden
ℹ️ Utility assesses the level of microbial bioburden in non-sterile pharmaceutical products according to Ph. Eur. 2.6.12 and USP <61>:
• TAMC (Total Aerobic Microbial Count): Total number of aerobic bacteria.
• TYMC (Total Yeasts and Molds Count): Total number of yeasts and molds.
• Recovery Efficiency: Confirmation that the method allows detection of microorganisms present in the product.
• Incubation Conditions: Strict control of culture growth time.
⚠️ CRITICAL:
• Exceeding established limits (e.g., 100 CFU/g for TAMC) indicates unsatisfactory raw material quality or hygiene violations in production.
• Recovery efficiency below 50% means the method is unsuitable for this product without modification (neutralization of antimicrobial properties).
Usage:
BacterialCountBioburdenChecker.exe → demo mode (console output)
BacterialCountBioburdenChecker.exe input.csv output.json → evaluate your data
Input format:
BatchNumber,ProductName,TAMC_CFU_per_unit,TYMC_CFU_per_unit,SampleWeight_g,DilutionFactor,IncubationDays_TAMC,IncubationDays_TYMC,RecoveryEfficiency_Percent
Example:
BB-001,Cream,50.0,10.0,1.0,10.0,3,5,85.0
— WHY IS THIS NEEDED?
Bioburden control is necessary to ensure microbiological quality of non-sterile products.
High levels of microorganisms can lead to product spoilage, reduced preservative efficacy, and patient health risks.
Results are also used for validation of sterilization processes (if the product undergoes terminal sterilization).
⚠️ CRITICAL:
• Limits depend on route of administration and product type (oral, topical, rectal, etc.).
• Membrane filtration method is preferred for products with antimicrobial activity.
• Neutralization: If product contains preservatives, neutralizers must be used in the culture medium.
• Incubation: TAMC is incubated at 30-35°C (3-5 days), TYMC at 20-25°C (5-7 days).
Key features:
• Verification of compliance with TAMC and TYMC limits
• Method validity control via recovery efficiency
• Incubation condition check
• Generation of reports for microbiology lab and LIMS LabWare
• Compliance with GMP and Pharmacopoeia requirements
Critical parameters:
• TAMC: ≤ 100 CFU/g (for topical products)
• TYMC: ≤ 10 CFU/g (for topical products)
• Recovery Efficiency: ≥ 50%
• TAMC Incubation Days: 3–5
• TYMC Incubation Days: 5–7
💡 Usage tips:
1. Sampling: Must be representative and performed aseptically.
2. Homogenization: Thoroughly homogenize sample with diluent to release microorganisms.
3. Colony Counting: Use only plates with colony counts between 10 and 300 (or up to 250 per USP) for accuracy.
4. Interpretation: If growth is too abundant (TNTC), repeat test with higher dilution.
5. Trends: Analyze bioburden data dynamically for early detection of production process issues.
⚠️ Note: Bioburden is an indicator of process "cleanliness" before sterilization or final control. For non-sterile products, it is one of the main release criteria.input.csv
BatchNumber,ProductName,TAMC_CFU_per_unit,TYMC_CFU_per_unit,SampleWeight_g,DilutionFactor,IncubationDays_TAMC,IncubationDays_TYMC,RecoveryEfficiency_Percent BB-2026-CREAM-001,Hydrocortisone Cream,50.0,10.0,1.0,10.0,3,5,85.0 BB-2026-SYRUP-002,Cough Syrup,20.0,5.0,10.0,1.0,4,6,90.0 BB-2026-FAIL-003,Herbal Powder,150.0,25.0,1.0,100.0,3,5,40.0
URS & FS — User Requirements and Functional Specification
This document describes the controlled interface and behaviour of BacterialCountBioburdenChecker for Bacterial Count Bioburden Checker.
Domain limits and critical parameters
Key fragments from the source description are shown below. Before production use, limits must be verified against the approved specification, registration dossier and local SOPs.
- ℹ️ Utility assesses the level of microbial bioburden in non-sterile pharmaceutical products according to Ph. Eur. 2.6.12 and USP <61>:
- ⚠️ CRITICAL:
- • Exceeding established limits (e.g., 100 CFU/g for TAMC) indicates unsatisfactory raw material quality or hygiene violations in production.
- • Limits depend on route of administration and product type (oral, topical, rectal, etc.).
- • Neutralization: If product contains preservatives, neutralizers must be used in the culture medium.
- • Verification of compliance with TAMC and TYMC limits
- • Compliance with GMP and Pharmacopoeia requirements
- Critical parameters:
- • TAMC: ≤ 100 CFU/g (for topical products)
- • TYMC: ≤ 10 CFU/g (for topical products)
- • Recovery Efficiency: ≥ 50%
- 1. Sampling: Must be representative and performed aseptically.
- 3. Colony Counting: Use only plates with colony counts between 10 and 300 (or up to 250 per USP) for accuracy.
URS — User Requirements Specification
| ID | Requirement | Criticality | Acceptance criterion |
|---|---|---|---|
| URS-001 | The utility shall accept an input.csv file for Bacterial Count Bioburden Checker with headers defined in the data contract. | High | The file is processed without manual header editing. |
| URS-002 | The utility shall perform deterministic QC evaluation without machine learning and without probabilistic conformance decisions. | High | Identical input data, rule version and configuration produce reproducible results. |
| URS-003 | The utility shall validate mandatory fields, data types, ranges, units and domain plausibility. | High | Schema, conversion and range errors are explicitly reported. |
| URS-004 | The utility shall apply domain limits and rules from the description, approved specification, registration dossier and local SOPs. | High | Each check has PASS/WARNING/FAIL and a clear message. |
| URS-005 | The utility shall generate output.json with machine-readable results, source values, warnings, failures and critical findings. | High | JSON is suitable for LIMS/ELN/MES integration and QA/QC review. |
| URS-006 | The utility shall preserve traceability between batch/sample, input file, applied rules and final status. | High | Output contains identifiers, checked parameters and audit metadata. |
| URS-007 | The documentation shall support IQ/OQ/PQ, CSV/CSA and review by internal QA or inspectors. | Medium | URS, FS, input/output contract and test scenarios are supplied with the utility. |
| URS-008 | The utility shall be used as a QC decision-support tool and not as a substitute for approved specifications and QA/QP release decision. | Medium | Documentation states change control and limit-verification expectations. |
input.csv contract
| # | Field | Type | Sample | Purpose |
|---|---|---|---|---|
| 1 | BatchNumber | string / controlled vocabulary | BB-2026-CREAM-001 | Batch or lot identifier used for traceability. |
| 2 | ProductName | string / controlled vocabulary | Hydrocortisone Cream | Product or dosage-form name under evaluation. |
| 3 | TAMC_CFU_per_unit | string / controlled vocabulary | 50.0 | Count parameter used for microbiological, particulate or cellular control. |
| 4 | TYMC_CFU_per_unit | string / controlled vocabulary | 10.0 | Count parameter used for microbiological, particulate or cellular control. |
| 5 | SampleWeight_g | string / controlled vocabulary | 1.0 | Sample or laboratory specimen identifier. |
| 6 | DilutionFactor | decimal | 10.0 | Controlled input parameter for deterministic QC rules. |
| 7 | IncubationDays_TAMC | integer / decimal | 3 | Time parameter for process, incubation, storage or analytical workflow. |
| 8 | IncubationDays_TYMC | integer / decimal | 5 | Time parameter for process, incubation, storage or analytical workflow. |
| 9 | RecoveryEfficiency_Percent | decimal | 85.0 | Recovery; indicator of analytical validity. |
BatchNumber,ProductName,TAMC_CFU_per_unit,TYMC_CFU_per_unit,SampleWeight_g,DilutionFactor,IncubationDays_TAMC,IncubationDays_TYMC,RecoveryEfficiency_Percent BB-2026-CREAM-001,Hydrocortisone Cream,50.0,10.0,1.0,10.0,3,5,85.0 BB-2026-SYRUP-002,Cough Syrup,20.0,5.0,10.0,1.0,4,6,90.0 BB-2026-FAIL-003,Herbal Powder,150.0,25.0,1.0,100.0,3,5,40.0
Input validation rules
| ID | Field | Rule | Criticality |
|---|---|---|---|
| VR-001 | BatchNumber | The field shall match an approved dictionary or accepted string representation. | High |
| VR-002 | ProductName | The field shall match an approved dictionary or accepted string representation. | High |
| VR-003 | TAMC_CFU_per_unit | The field shall match an approved dictionary or accepted string representation. | High |
| VR-004 | TYMC_CFU_per_unit | The field shall match an approved dictionary or accepted string representation. | Medium |
| VR-005 | SampleWeight_g | The field shall match an approved dictionary or accepted string representation. | Medium |
| VR-006 | DilutionFactor | The field shall match an approved dictionary or accepted string representation. | Medium |
| VR-007 | IncubationDays_TAMC | The field shall match an approved dictionary or accepted string representation. | Medium |
| VR-008 | IncubationDays_TYMC | The field shall match an approved dictionary or accepted string representation. | Medium |
| VR-009 | RecoveryEfficiency_Percent | The field shall match an approved dictionary or accepted string representation. | Medium |
FS — Functional Specification
| ID | Function | Implementation |
|---|---|---|
| FS-001 | CLI execution | Support execution modes: demo mode without arguments and production mode input.csv output.json. |
| FS-002 | CSV import | Read input.csv in UTF-8/CSV-compatible format and validate header and expected columns. |
| FS-003 | Schema validation | Check mandatory fields, column count, unknown key fields and empty mandatory values. |
| FS-004 | Type conversion | Convert numeric, flag and text values; invalid format is recorded as a row-level error. |
| FS-005 | Domain rule engine | Apply rules for Bacterial Count Bioburden Checker, including critical limits from the description and approved specification. |
| FS-006 | Status aggregation | Produce final status: FAIL for critical failure, WARNING for non-critical deviation, PASS for conformance. |
| FS-007 | JSON export | Write output.json with detailed checks, source values, warnings, failures and critical findings. |
| FS-008 | Audit support | Keep result structure suitable for review, deviation investigation and calculation reproduction. |
| FS-009 | Integration contract | Support the scenario LIMS/ELN/MES → input.csv → utility → output.json → portal/admin review. |
| FS-010 | Error handling | Return explicit messages for missing file, empty CSV, invalid schema, output write failure and invalid format. |
Example output.json
{
"utilityId": "bacterialcountbioburdenchecker",
"utilityFolder": "BacterialCountBioburdenChecker",
"package": "Vet",
"overallStatus": "PASS|WARNING|FAIL",
"sourceFile": "input.csv",
"processedAtUtc": "2026-06-10T00:00:00Z",
"checks": [
{
"parameter": "BatchNumber",
"value": "BB-2026-CREAM-001",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-001"
},
{
"parameter": "ProductName",
"value": "Hydrocortisone Cream",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-002"
},
{
"parameter": "TAMC_CFU_per_unit",
"value": "50.0",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-003"
},
{
"parameter": "TYMC_CFU_per_unit",
"value": "10.0",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-004"
},
{
"parameter": "SampleWeight_g",
"value": "1.0",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-005"
},
{
"parameter": "DilutionFactor",
"value": "10.0",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-006"
},
{
"parameter": "IncubationDays_TAMC",
"value": "3",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-007"
},
{
"parameter": "IncubationDays_TYMC",
"value": "5",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-008"
},
{
"parameter": "RecoveryEfficiency_Percent",
"value": "85.0",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-009"
}
],
"criticalFindings": [],
"warnings": [],
"audit": {
"inputHash": "sha256:<calculated at runtime>",
"rulesVersion": "<utility executable version>",
"documentation": "BacterialCountBioburdenChecker.documentation.html"
}
}
Traceability matrix
| URS | FS | Test | Evidence |
|---|---|---|---|
| URS-001 | FS-001, FS-002 | OQ-001 | Verify execution and import of valid input.csv. |
| URS-002 | FS-005, FS-006 | OQ-004 | Repeat the same dataset and compare output.json. |
| URS-003 | FS-003, FS-004, FS-010 | OQ-002, OQ-003 | Verify missing columns and invalid types. |
| URS-004 | FS-005, FS-006 | OQ-004, PQ-001 | Verify critical deviations on real/boundary data. |
| URS-005 | FS-007, FS-009 | OQ-005 | Verify JSON schema and downstream-system suitability. |
| URS-006 | FS-008 | OQ-006 | Verify identifiers and audit metadata. |
| URS-007 | FS-008, FS-010 | IQ-001, OQ-007 | Verify documentation completeness and control evidence. |
| URS-008 | FS-005, FS-008 | PQ-002 | Verify review workflow and no replacement of QA decision. |
IQ/OQ/PQ test scenarios
| ID | Scenario | Expected result |
|---|---|---|
| IQ-001 | Verify executable, input.csv, documentation and checksum availability. | Delivery set is complete; version is recorded. |
| OQ-001 | Valid sample row from input.csv. | PASS or acceptable WARNING according to rules. |
| OQ-002 | Remove a mandatory CSV column. | Schema error or FAIL with missing-column reference. |
| OQ-003 | Place a non-numeric value into a numeric field. | Type-conversion error with row/field reference. |
| OQ-004 | Set a critical parameter outside the limit. | FAIL and critical finding. |
| OQ-005 | Verify output.json structure. | All mandatory sections are present and JSON is valid. |
| OQ-006 | Verify batch/sample traceability. | Input and result identifiers match. |
| PQ-001 | Verify 3–5 real user batches/samples. | Result is confirmed by QC/QA review. |
| PQ-002 | Verify deviation workflow and manual QA decision. | Utility supports review but does not replace approved decision. |
QA/QC and change control
- Do not rename columns without updating validator, documentation and test set.
- Retain
input.csv,output.json, executable version and checksum. - Before production use, perform IQ/OQ/PQ or equivalent CSV/CSA verification.
- Critical limits shall be verified against the approved specification, registration dossier and local SOPs.
- The utility provides structured QC decision support; final release decision remains with QA/QP and approved procedures.
Included in packages
Infectious Diseases QC Suite
QC utility package for infectious diseases: antibacterial, antiviral, antifungal and antiparasitic products, microbiology, sterility, endotoxins, viral safety and vaccine release checks.
OpenVet — Veterinary QC Utilities
Vet is designed for veterinary pharmaceuticals and vaccines: adjuvants, antigens, autogenous vaccines, aquaculture, feed/premixes, antimicrobial and antiparasitic products, sterility and batch release.
Open