BortezomibQualityChecker
Bortezomib
Bortezomib Quality Checker — Proteasome Inhibitor (Ph. Eur., USP)
ℹ️ The utility checks assay, deboronated impurity, sterility, endotoxins, reconstitution time.
ℹ️ Does not use machine learning — rule-based logic only.
⚠️ CRITICAL! Deboronation ≤0.5%. Sterility mandatory. Endotoxins ≤1.0 EU/mg!
Usage:
BortezomibQualityChecker.exe → demo mode
BortezomibQualityChecker.exe input.csv output.json → evaluate data
Input format:
BatchNumber,Assay_Percent,Specific_Rotation,Melting_Point_Min,Melting_Point_Max,Deboronated_Bortezomib_Percent,Boronic_Acid_Impurity_Percent,Total_Impurities_Percent,Loss_On_Drying_Percent,Residual_Solvent_Methanol_ppm,Residual_Solvent_Acetonitrile_ppm,Heavy_Metals_ppm,Sulfated_Ash_Percent,SterilityTest,Bacterial_Endotoxins_EU_per_mg,Reconstitution_Time_Seconds,Clarity_of_Solution,Microbial_Count_TAMC,Microbial_Count_TYMC,EColi_Detected,Salmonella_Detected
Example:
BOR-LYO-2026-001,99.4,-60.5,132,136,0.15,0.05,0.3,0.6,500,100,5,0.05,0,0.2,30,0,10,2,0,0
— WHY IS THIS NEEDED?
Bortezomib — proteasome inhibitor for multiple myeloma (released as lyophilizate for injection):
• Structure contains boronic acid, critical for proteasome binding. Hydrolysis leads to boron loss (deboronation), forming inactive acid. Control of deboronated impurity (≤0.5%) is priority.
• Lyophilized form requires strict residual moisture (LOD) control for storage stability.
• As parenteral drug, requires absolute sterility and low endotoxin levels (<1.0 EU/mg).
• Reconstitution time should be rapid for clinical convenience.
⚠️ CRITICAL:
• Assay: 98–102% (anhydrous basis)
• Deboronated Bortezomib: ≤ 0.5% (inactive impurity)
• Loss on Drying: ≤ 1.0%
• Sterility: No growth (mandatory!)
• Bacterial Endotoxins: ≤ 1.0 EU/mg
• Reconstitution Time: ≤ 60 sec
• Solution Clarity: Mandatory
⚠️ Note: Utility places special emphasis on specific bortezomib degradation (deboronation). Exceeding this impurity level means loss of therapeutic activity. Sterility and endotoxin control are critical for safety of oncology patients.
input.csv
BatchNumber,Assay_Percent,Specific_Rotation,Melting_Point_Min,Melting_Point_Max,Deboronated_Bortezomib_Percent,Boronic_Acid_Impurity_Percent,Total_Impurities_Percent,Loss_On_Drying_Percent,Residual_Solvent_Methanol_ppm,Residual_Solvent_Acetonitrile_ppm,Heavy_Metals_ppm,Sulfated_Ash_Percent,SterilityTest,Bacterial_Endotoxins_EU_per_mg,Reconstitution_Time_Seconds,Clarity_of_Solution,Microbial_Count_TAMC,Microbial_Count_TYMC,EColi_Detected,Salmonella_Detected BOR-LYO-2026-001,99.4,-60.5,132,136,0.15,0.05,0.3,0.6,500,100,5,0.05,0,0.2,30,0,10,2,0,0
URS & FS — user requirements and functional specification
This document defines user requirements and functional specification for the quality-control utility. It supports deployment discussion, IQ/OQ preparation and QC workflow integration.
1. Scope
The Bortezomib Quality Checker utility is used for Bortezomib. The actual input.csv is the source of truth for the input structure; control criteria are defined by the executable and the domain description.
The utility does not use machine learning; decisions are produced by deterministic rules.
Categories: Global API expansion
Tags: antivirals, API, biologics, endotoxins, essential medicines, global market, impurities, injectables, microbiology, oncology, sterility
2. Execution modes
BortezomibQualityChecker.exe → demo mode BortezomibQualityChecker.exe input.csv output.json → evaluate data
3. Key controlled areas
- assay / content
- purity and impurities
- residual solvents
- microbiology and pathogens
- heavy metals / elemental impurities
- pH and physicochemical parameters
4. Domain limits and critical parameters
- ⚠️ CRITICAL! Deboronation ≤0.5%. Sterility mandatory. Endotoxins ≤1.0 EU/mg!
- Structure contains boronic acid, critical for proteasome binding. Hydrolysis leads to boron loss (deboronation), forming inactive acid. Control of deboronated impurity (≤0.5%) is priority.
- As parenteral drug, requires absolute sterility and low endotoxin levels (<1.0 EU/mg).
- ⚠️ CRITICAL:
- Assay: 98–102% (anhydrous basis)
- Deboronated Bortezomib: ≤ 0.5% (inactive impurity)
- Loss on Drying: ≤ 1.0%
- Sterility: No growth (mandatory!)
- Bacterial Endotoxins: ≤ 1.0 EU/mg
- Reconstitution Time: ≤ 60 sec
- Solution Clarity: Mandatory
- ⚠️ Note: Utility places special emphasis on specific bortezomib degradation (deboronation). Exceeding this impurity level means loss of therapeutic activity. Sterility and endotoxin control are critical for safety of oncology patients.
5. URS — user requirements
| ID | Requirement | Criticality | Acceptance criterion |
|---|---|---|---|
| URS-001 | The system shall accept an input.csv file for Bortezomib with the exact columns listed in the “Input data contract” section. | High | A file with the correct header is processed without manual editing; missing mandatory columns produce FAIL/import error. |
| URS-002 | The system shall support execution without arguments in demo mode and execution with input.csv output.json for user data. | Medium | Both execution scenarios produce a predictable result or clear diagnostic error. |
| URS-003 | The system shall perform rule-based controls for: assay / content, purity and impurities, residual solvents, microbiology and pathogens, heavy metals / elemental impurities, pH and physicochemical parameters. | High | Each controlled parameter receives a status and message; the result does not depend on hidden Excel formulas or ML. |
| URS-004 | The system shall preserve traceability between batch/lot, source values, applied rules and final verdict. | High | Output includes batch identifier, source values, parameter statuses and critical findings. |
| URS-005 | The system shall generate machine-readable output.json for LIMS/ELN/MES, batch record and QA/QC review. | High | JSON contains overall status, check array, warnings, failures and source-file reference. |
| URS-006 | The system shall support use in the client validation package: URS/FS, IQ/OQ preparation, installation and operational scenario checks. | High | The document, test scenarios and reproducible CSV/JSON flow are suitable for audit and internal approval. |
| URS-007 | The system shall clearly separate technical data errors from specification nonconformities. | Medium | Schema/type errors are not mixed with pharmacopoeial deviations and are reported separately. |
6. input.csv data contract
The source of truth for the input schema is the actual input.csv header. Column names are technical identifiers and are not translated.
| # | Column | Type | Unit | Description | Sample | Control rule |
|---|---|---|---|---|---|---|
| 1 | BatchNumber | identifier | as specified | Batch Number | BOR-LYO-2026-001 | mandatory field; used for batch/lot traceability |
| 2 | Assay_Percent | decimal | % | Assay % | 99.4 | numeric value; compared with assay/purity limit from specification or method |
| 3 | Specific_Rotation | decimal | as specified | Specific Rotation | -60.5 | mandatory numeric value; rule comparison is performed by the utility |
| 4 | Melting_Point_Min | decimal | °C | Melting Point Min | 132 | mandatory numeric value; rule comparison is performed by the utility |
| 5 | Melting_Point_Max | decimal | °C | Melting Point Max | 136 | mandatory numeric value; rule comparison is performed by the utility |
| 6 | Deboronated_Bortezomib_Percent | decimal | % | Deboronated Bortezomib % | 0.15 | mandatory numeric value; rule comparison is performed by the utility |
| 7 | Boronic_Acid_Impurity_Percent | decimal | % | Boronic Acid Impurity % | 0.05 | numeric value; compared with individual or total impurity limit |
| 8 | Total_Impurities_Percent | decimal | % | Total Impurities % | 0.3 | mandatory numeric value; rule comparison is performed by the utility |
| 9 | Loss_On_Drying_Percent | decimal | % | Loss On Drying % | 0.6 | mandatory numeric value; rule comparison is performed by the utility |
| 10 | Residual_Solvent_Methanol_ppm | decimal | ppm | Residual Solvent Methanol ppm | 500 | numeric value; checked as residual solvent against the applicable limit |
| 11 | Residual_Solvent_Acetonitrile_ppm | decimal | ppm | Residual Solvent Acetonitrile ppm | 100 | numeric value; checked as residual solvent against the applicable limit |
| 12 | Heavy_Metals_ppm | decimal | ppm | Heavy Metals ppm | 5 | numeric value; checked as elemental/metal impurity |
| 13 | Sulfated_Ash_Percent | decimal | % | Sulfated Ash % | 0.05 | mandatory numeric value; rule comparison is performed by the utility |
| 14 | SterilityTest | boolean / flag | 0/1 | Sterility Test | 0 | valid flag required; prohibited organisms and growth are normally expected as 0 / absent |
| 15 | Bacterial_Endotoxins_EU_per_mg | decimal | EU/ml | Bacterial Endotoxins EU per mg | 0.2 | numeric value; critical safety attribute compared with endotoxin limit |
| 16 | Reconstitution_Time_Seconds | decimal | as specified | Reconstitution Time Seconds | 30 | mandatory numeric value; rule comparison is performed by the utility |
| 17 | Clarity_of_Solution | decimal | as specified | Clarity of Solution | 0 | mandatory numeric value; rule comparison is performed by the utility |
| 18 | Microbial_Count_TAMC | decimal | as specified | Microbial Count TAMC | 10 | numeric value; compared with microbiological limits |
| 19 | Microbial_Count_TYMC | decimal | as specified | Microbial Count TYMC | 2 | numeric value; compared with microbiological limits |
| 20 | EColi_Detected | boolean / flag | 0/1 | EColi Detected | 0 | valid flag required; prohibited organisms and growth are normally expected as 0 / absent |
| 21 | Salmonella_Detected | boolean / flag | 0/1 | Salmonella Detected | 0 | valid flag required; prohibited organisms and growth are normally expected as 0 / absent |
CSV example
BatchNumber,Assay_Percent,Specific_Rotation,Melting_Point_Min,Melting_Point_Max,Deboronated_Bortezomib_Percent,Boronic_Acid_Impurity_Percent,Total_Impurities_Percent,Loss_On_Drying_Percent,Residual_Solvent_Methanol_ppm,Residual_Solvent_Acetonitrile_ppm,Heavy_Metals_ppm,Sulfated_Ash_Percent,SterilityTest,Bacterial_Endotoxins_EU_per_mg,Reconstitution_Time_Seconds,Clarity_of_Solution,Microbial_Count_TAMC,Microbial_Count_TYMC,EColi_Detected,Salmonella_Detected BOR-LYO-2026-001,99.4,-60.5,132,136,0.15,0.05,0.3,0.6,500,100,5,0.05,0,0.2,30,0,10,2,0,0
7. FS — functional specification
| ID | Function | Implementation description |
|---|---|---|
| FS-001 | CLI entry point | The executable BortezomibQualityChecker.exe supports demo mode and input.csv output.json processing mode. |
| FS-002 | CSV parser | The import module reads CSV, validates header, column presence/order, value count and encoding. Decimal values are expected with a dot separator. |
| FS-003 | Field conversion | Each column is converted to the expected type: identifier, text, decimal number, date/time or boolean flag. |
| FS-004 | Domain rule engine | For Bortezomib, explicit rules are applied: range, minimum, maximum, absence of prohibited flag, data completeness or calculation-based check. |
| FS-005 | Criticality handling | Critical violations produce FAIL; non-critical deviations and incomplete data produce WARNING; full conformance produces PASS. |
| FS-006 | JSON writer | output.json stores overall status, per-parameter results, source values, warnings, failures and diagnostic messages. |
| FS-007 | Integration contract | The CSV → JSON format is stable for invocation from LIMS/ELN/MES, scheduled task or wrapper service. |
| FS-008 | Error handling | Schema error, missing file, non-numeric value or JSON write failure returns diagnosable error without silent PASS. |
8. output.json contract
The output file must be suitable for automated processing, audit review and correlation with the source input.csv row.
{
"utility": "BortezomibQualityChecker",
"api": "Bortezomib",
"batchNumber": "BOR-LYO-2026-001",
"overallStatus": "PASS|WARNING|FAIL",
"checkedAtUtc": "2026-05-18T00:00:00Z",
"checks": [
{
"parameter": "BatchNumber",
"value": "BOR-LYO-2026-001",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Assay_Percent",
"value": "99.4",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Specific_Rotation",
"value": "-60.5",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Melting_Point_Min",
"value": "132",
"unit": "°C",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Melting_Point_Max",
"value": "136",
"unit": "°C",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Deboronated_Bortezomib_Percent",
"value": "0.15",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Boronic_Acid_Impurity_Percent",
"value": "0.05",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Total_Impurities_Percent",
"value": "0.3",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
}
],
"criticalFindings": [],
"sourceFile": "input.csv"
}9. OQ/PQ test scenarios
| ID | Scenario | Expected result |
|---|---|---|
| TC-001 | Valid CSV with expected header and sample row | All rows are processed; output contains PASS/WARNING/FAIL and parameter-level detail. |
| TC-002 | A mandatory input.csv column is missing | Import is rejected or the row receives FAIL with schema reference. |
| TC-003 | A numeric field contains text or a blank value | Type conversion error is recorded; the result is not hidden as PASS. |
| TC-004 | A parameter is outside specification or critical limit | Critical parameters produce FAIL; non-critical deviations produce WARNING according to the rule. |
| TC-005 | Positive pathogen/microbiological flag or microbiological limit excursion | Critical FAIL is produced with the offending parameter. |
| TC-007 | Residual solvent above applicable limit | FAIL is produced with solvent name and measured value. |
10. QA/QC, CSV and change control
- Before production use, the client records executable version, checksum, specification/monograph version, test CSV, expected JSON and IQ/OQ results.
- Column names must not be changed without updating the validator and test scenarios.
- The source CSV, output.json and utility version should be stored together as an evidence package.
- Any change in control rules must go through change control and repeated OQ scenario verification.
Included in packages
Australia: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenBrazil: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenCanada: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenChina: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenFrance: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenGermany: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenIran: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenItaly: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenJapan: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenMexico: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenRussia: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenSaudi Arabia: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenSouth Korea: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenTurkey: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenUnited Kingdom: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenUnited States: national essential medicines QC package
QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.
OpenWorld API Extension QC Suite
Extended package for 130 additional high-demand APIs and biological products prepared as a market-coverage backlog.
Open