NeomycinSulfateQualityChecker
Neomycin Sulfate
Neomycin Sulfate Quality Checker — Neomycin sulfate quality assessment (BP/Ph. Eur. 0905)
ℹ️ The utility verifies that key parameters of neomycin sulfate comply with British and European Pharmacopoeia requirements.
ℹ️ Does not use machine learning — rule-based logic only.
ℹ️ Melting range is NOT APPLICABLE (substance decomposes).
Usage:
NeomycinSulfateQualityChecker.exe → demo mode (console output)
NeomycinSulfateQualityChecker.exe input.csv output.json → evaluate your data
Input format:
ProductName,BatchNumber,Appearance,Assay_percent,RelatedSubstances_TotalImpurities_percent,WaterContent_percent
Example:
Neomycin_Sulfate_API,B20250199,WhiteOrAlmostWhiteHygroscopicPowder,98.5,3.0,14.5
— WHY IS THIS NEEDED?
Neomycin sulfate is an aminoglycoside antibiotic used to treat skin, eye, and intestinal infections, and its quality directly impacts therapy efficacy and patient safety:
• Deviation in purity (Related Substances) may indicate toxic impurities or incorrect component ratios (neomycin B/C),
• Low assay poses a risk of insufficient drug concentration,
• Incorrect water content affects stability, hygroscopicity, and dosing accuracy,
• Appearance change indicates degradation or moisture uptake.
Compliance with BP/Ph. Eur. 0905 is mandatory for batch release.
input.csv
ProductName,BatchNumber,Appearance,Assay_percent,RelatedSubstances_TotalImpurities_percent,WaterContent_percent Neomycin_Sulfate_API,B20250199,WhiteOrAlmostWhiteHygroscopicPowder,98.5,3.0,14.5
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 Neomycin Sulfate Quality Checker utility is used for Neomycin Sulfate. 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: BP monographs
Tags: antibiotics, API, assay, British Pharmacopoeia, impurities, monographs, specification, water quality
2. Execution modes
NeomycinSulfateQualityChecker.exe → demo mode (console output) NeomycinSulfateQualityChecker.exe input.csv output.json → evaluate your data
3. Key controlled areas
- assay / content
- purity and impurities
- pH and physicochemical parameters
4. Domain limits and critical parameters
The source description does not contain a separate critical-limit list; rules implemented in the executable and defined by the CSV schema apply.
5. URS — user requirements
| ID | Requirement | Criticality | Acceptance criterion |
|---|---|---|---|
| URS-001 | The system shall accept an input.csv file for Neomycin Sulfate 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, 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 | ProductName | identifier | as specified | Product Name | Neomycin_Sulfate_API | mandatory value; format and acceptability are checked by the utility |
| 2 | BatchNumber | identifier | as specified | Batch Number | B20250199 | mandatory field; used for batch/lot traceability |
| 3 | Appearance | text | as specified | Appearance | WhiteOrAlmostWhiteHygroscopicPowder | mandatory value; format and acceptability are checked by the utility |
| 4 | Assay_percent | decimal | % | Assay percent | 98.5 | numeric value; compared with assay/purity limit from specification or method |
| 5 | RelatedSubstances_TotalImpurities_percent | decimal | % | Related Substances Total Impurities percent | 3.0 | numeric value; compared with individual or total impurity limit |
| 6 | WaterContent_percent | decimal | % | Water Content percent | 14.5 | numeric value; compared with assay/purity limit from specification or method |
CSV example
ProductName,BatchNumber,Appearance,Assay_percent,RelatedSubstances_TotalImpurities_percent,WaterContent_percent Neomycin_Sulfate_API,B20250199,WhiteOrAlmostWhiteHygroscopicPowder,98.5,3.0,14.5
7. FS — functional specification
| ID | Function | Implementation description |
|---|---|---|
| FS-001 | CLI entry point | The executable NeomycinSulfateQualityChecker.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 Neomycin Sulfate, 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": "NeomycinSulfateQualityChecker",
"api": "Neomycin Sulfate",
"batchNumber": "B20250199",
"overallStatus": "PASS|WARNING|FAIL",
"checkedAtUtc": "2026-05-18T00:00:00Z",
"checks": [
{
"parameter": "ProductName",
"value": "Neomycin_Sulfate_API",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "BatchNumber",
"value": "B20250199",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Appearance",
"value": "WhiteOrAlmostWhiteHygroscopicPowder",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Assay_percent",
"value": "98.5",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "RelatedSubstances_TotalImpurities_percent",
"value": "3.0",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "WaterContent_percent",
"value": "14.5",
"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. |
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
British Pharmacopoeia Monographs QC Suite
Utility package for British Pharmacopoeia monographs covering drug substances, APIs and finished products.
OpenENT QC Suite
QC package for ENT: nasal sprays, ear drops, local antiseptics, corticosteroids, antibiotics and upper-airway medicines.
OpenGastroenterology QC Suite
QC package for gastroenterology: PPIs, antiemetics, prokinetics, IBD medicines, laxatives, enzymes and GI anti-infectives.
OpenOphthalmology QC Suite
QC package for ophthalmology: eye drops, antiglaucoma agents, antibiotics, sterile solutions, osmolality, pH, particles and preservatives.
Open