OfloxacinOrnidazoleQualityChecker
Ofloxacin Ornidazole
Ofloxacin Ornidazole Quality Checker — Combo Antibiotic/Antiprotozoal
ℹ️ The utility checks content of both APIs, nitro-impurities, synchronous dissolution.
ℹ️ Does not use machine learning — rule-based logic only.
⚠️ CRITICAL! Ornidazole impurities ≤0.2%. Dissolution ≥80% in 30 min!
Usage:
OfloxacinOrnidazoleQualityChecker.exe → demo mode
OfloxacinOrnidazoleQualityChecker.exe input.csv output.json → evaluate data
Input format:
BatchNumber,Ofloxacin_Content_Percent,Ornidazole_Content_Percent,Ofloxacin_Impurity_A_Percent,Ofloxacin_Enantiomer_Percent,Ofloxacin_Total_Impurities_Percent,Ornidazole_Impurity_A_Percent,Ornidazole_Total_Impurities_Percent,Total_All_Impurities_Percent,Loss_On_Drying_Percent,Heavy_Metals_ppm,Dissolution_Ofloxacin_30min_Percent,Dissolution_Ornidazole_30min_Percent,Weight_Variation_RSD,Microbial_Count_TAMC,Microbial_Count_TYMC,EColi_Detected,Salmonella_Detected
Example:
OFL-ORN-2026-001,98.5,99.1,0.05,0.02,0.2,0.08,0.3,0.5,0.4,6,88.0,92.0,2.5,30,8,0,0
— WHY IS THIS NEEDED?
Ofloxacin + Ornidazole combination used for mixed bacterial and protozoal infections:
• Ofloxacin (fluoroquinolone) and Ornidazole (nitroimidazole) have different chemical properties and stability profiles.
• Ornidazole may contain toxic nitro-impurities requiring strict control.
• Synchronous release of both components important for comprehensive therapeutic effect.
• Drug taken as course, so heavy metal and microbiology control important.
⚠️ CRITICAL:
• Content of both APIs: 95–105%
• Ornidazole Impurities: ≤ 0.2% (nitro-group toxicity)
• Total Impurities: ≤ 1.0%
• Dissolution: ≥ 80% in 30 min for both components
• Heavy Metals: ≤ 10 ppm
• Microbiology: absence of pathogens
⚠️ Note: Utility focuses on balance of two different antibiotic classes in one tablet. Control of ornidazole nitro-impurities critical due to potential mutagenicity. Dissolution synchronicity ensures simultaneous action on aerobic bacteria and anaerobes/protozoa.
input.csv
BatchNumber,Ofloxacin_Content_Percent,Ornidazole_Content_Percent,Ofloxacin_Impurity_A_Percent,Ofloxacin_Enantiomer_Percent,Ofloxacin_Total_Impurities_Percent,Ornidazole_Impurity_A_Percent,Ornidazole_Total_Impurities_Percent,Total_All_Impurities_Percent,Loss_On_Drying_Percent,Heavy_Metals_ppm,Dissolution_Ofloxacin_30min_Percent,Dissolution_Ornidazole_30min_Percent,Weight_Variation_RSD,Microbial_Count_TAMC,Microbial_Count_TYMC,EColi_Detected,Salmonella_Detected OFL-ORN-2026-001,98.5,99.1,0.05,0.02,0.2,0.08,0.3,0.5,0.4,6,88.0,92.0,2.5,30,8,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 Ofloxacin Ornidazole Quality Checker utility is used for Ofloxacin Ornidazole. 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
Tags: antibiotics, API, assay, biosimilars, dissolution, fixed-dose combinations, generics, heavy metals, impurities, market map, microbiology, solid dosage
2. Execution modes
OfloxacinOrnidazoleQualityChecker.exe → demo mode OfloxacinOrnidazoleQualityChecker.exe input.csv output.json → evaluate data
3. Key controlled areas
- assay / content
- purity and impurities
- dissolution / disintegration
- microbiology and pathogens
- heavy metals / elemental impurities
4. Domain limits and critical parameters
- ⚠️ CRITICAL! Ornidazole impurities ≤0.2%. Dissolution ≥80% in 30 min!
- ⚠️ CRITICAL:
- Content of both APIs: 95–105%
- Ornidazole Impurities: ≤ 0.2% (nitro-group toxicity)
- Total Impurities: ≤ 1.0%
- Dissolution: ≥ 80% in 30 min for both components
- Heavy Metals: ≤ 10 ppm
- Microbiology: absence of pathogens
- ⚠️ Note: Utility focuses on balance of two different antibiotic classes in one tablet. Control of ornidazole nitro-impurities critical due to potential mutagenicity. Dissolution synchronicity ensures simultaneous action on aerobic bacteria and anaerobes/protozoa.
5. URS — user requirements
| ID | Requirement | Criticality | Acceptance criterion |
|---|---|---|---|
| URS-001 | The system shall accept an input.csv file for Ofloxacin Ornidazole 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, dissolution / disintegration, microbiology and pathogens, heavy metals / elemental impurities. | 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 | OFL-ORN-2026-001 | mandatory field; used for batch/lot traceability |
| 2 | Ofloxacin_Content_Percent | decimal | % | Ofloxacin Content % | 98.5 | numeric value; compared with assay/purity limit from specification or method |
| 3 | Ornidazole_Content_Percent | decimal | % | Ornidazole Content % | 99.1 | numeric value; compared with assay/purity limit from specification or method |
| 4 | Ofloxacin_Impurity_A_Percent | decimal | % | Ofloxacin Impurity A % | 0.05 | numeric value; compared with individual or total impurity limit |
| 5 | Ofloxacin_Enantiomer_Percent | decimal | % | Ofloxacin Enantiomer % | 0.02 | mandatory numeric value; rule comparison is performed by the utility |
| 6 | Ofloxacin_Total_Impurities_Percent | decimal | % | Ofloxacin Total Impurities % | 0.2 | mandatory numeric value; rule comparison is performed by the utility |
| 7 | Ornidazole_Impurity_A_Percent | decimal | % | Ornidazole Impurity A % | 0.08 | numeric value; compared with individual or total impurity limit |
| 8 | Ornidazole_Total_Impurities_Percent | decimal | % | Ornidazole Total Impurities % | 0.3 | mandatory numeric value; rule comparison is performed by the utility |
| 9 | Total_All_Impurities_Percent | decimal | % | Total All Impurities % | 0.5 | mandatory numeric value; rule comparison is performed by the utility |
| 10 | Loss_On_Drying_Percent | decimal | % | Loss On Drying % | 0.4 | mandatory numeric value; rule comparison is performed by the utility |
| 11 | Heavy_Metals_ppm | decimal | ppm | Heavy Metals ppm | 6 | numeric value; checked as elemental/metal impurity |
| 12 | Dissolution_Ofloxacin_30min_Percent | decimal | % | Dissolution Ofloxacin 30min % | 88.0 | numeric value; dissolution/disintegration profile checked according to method |
| 13 | Dissolution_Ornidazole_30min_Percent | decimal | % | Dissolution Ornidazole 30min % | 92.0 | numeric value; dissolution/disintegration profile checked according to method |
| 14 | Weight_Variation_RSD | decimal | as specified | Weight Variation RSD | 2.5 | mandatory numeric value; rule comparison is performed by the utility |
| 15 | Microbial_Count_TAMC | decimal | as specified | Microbial Count TAMC | 30 | numeric value; compared with microbiological limits |
| 16 | Microbial_Count_TYMC | decimal | as specified | Microbial Count TYMC | 8 | numeric value; compared with microbiological limits |
| 17 | EColi_Detected | boolean / flag | 0/1 | EColi Detected | 0 | valid flag required; prohibited organisms and growth are normally expected as 0 / absent |
| 18 | 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,Ofloxacin_Content_Percent,Ornidazole_Content_Percent,Ofloxacin_Impurity_A_Percent,Ofloxacin_Enantiomer_Percent,Ofloxacin_Total_Impurities_Percent,Ornidazole_Impurity_A_Percent,Ornidazole_Total_Impurities_Percent,Total_All_Impurities_Percent,Loss_On_Drying_Percent,Heavy_Metals_ppm,Dissolution_Ofloxacin_30min_Percent,Dissolution_Ornidazole_30min_Percent,Weight_Variation_RSD,Microbial_Count_TAMC,Microbial_Count_TYMC,EColi_Detected,Salmonella_Detected OFL-ORN-2026-001,98.5,99.1,0.05,0.02,0.2,0.08,0.3,0.5,0.4,6,88.0,92.0,2.5,30,8,0,0
7. FS — functional specification
| ID | Function | Implementation description |
|---|---|---|
| FS-001 | CLI entry point | The executable OfloxacinOrnidazoleQualityChecker.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 Ofloxacin Ornidazole, 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": "OfloxacinOrnidazoleQualityChecker",
"api": "Ofloxacin Ornidazole",
"batchNumber": "OFL-ORN-2026-001",
"overallStatus": "PASS|WARNING|FAIL",
"checkedAtUtc": "2026-05-18T00:00:00Z",
"checks": [
{
"parameter": "BatchNumber",
"value": "OFL-ORN-2026-001",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Ofloxacin_Content_Percent",
"value": "98.5",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Ornidazole_Content_Percent",
"value": "99.1",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Ofloxacin_Impurity_A_Percent",
"value": "0.05",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Ofloxacin_Enantiomer_Percent",
"value": "0.02",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Ofloxacin_Total_Impurities_Percent",
"value": "0.2",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Ornidazole_Impurity_A_Percent",
"value": "0.08",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Ornidazole_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-006 | Insufficient dissolution or excessive disintegration time | FAIL/WARNING is produced according to method criticality. |
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
Gastroenterology QC Suite
QC package for gastroenterology: PPIs, antiemetics, prokinetics, IBD medicines, laxatives, enzymes and GI anti-infectives.
OpenGlobal API & Biosimilars QC Suite
Package for high-demand global APIs, generics and biosimilars, including fixed-dose combinations and biological products.
OpenInfectious Diseases QC Suite
QC utility package for infectious diseases: antibacterial, antiviral, antifungal and antiparasitic products, microbiology, sterility, endotoxins, viral safety and vaccine release checks.
OpenOphthalmology QC Suite
QC package for ophthalmology: eye drops, antiglaucoma agents, antibiotics, sterile solutions, osmolality, pH, particles and preservatives.
OpenUrology QC Suite
QC package for urology: BPH, urolithiasis, overactive bladder, urinary-tract infection medicines and supporting antimicrobial QC checks.
Open