ChromiumChlorideQualityChecker
Chromium Chloride
Chromium Chloride Quality Checker — Chromium Chloride Hexahydrate (Ph. Eur. 2.4.x)
ℹ️ The utility checks assay, water content, metal impurities, heavy metals, pH, clarity.
ℹ️ Does not use machine learning — rule-based logic only.
⚠️ Critical for chromium preparations, dietary supplements, parenteral nutrition.
Usage:
ChromiumChlorideQualityChecker.exe → demo mode (console output)
ChromiumChlorideQualityChecker.exe input.csv output.json → evaluate your data
Input format:
BatchNumber,AssayPercent,WaterContent,HeavyMetals,Arsenic,Lead,Iron,Nickel,Copper,Zinc,Sulfates,Fluorides,pH,ClarityNTU,ColorAPHA,EthanolPPM,AcetonePPM
Example:
CRCL-2026-001,99.5,30.2,10,1.5,5,0.005,0.003,0.002,0.004,0.03,30,3.0,2,40,800,500
— WHY IS THIS NEEDED?
Chromium chloride hexahydrate is an inorganic chromium(III) compound used in:
• Parenteral nutrition (chromium source for glucose metabolism)
• Dietary supplements for metabolic support
• Pharmaceutical substances
Critical parameters:
• Assay 98.0–102.0% (on anhydrous basis)
• Water content 28.0–32.0% (for hexahydrate, Karl Fischer method)
• Heavy metals ≤20 ppm (as lead)
• Arsenic ≤3 ppm
• Lead ≤10 ppm
• Metal impurities: iron, nickel, copper, zinc ≤0.01% each
• Sulfates ≤0.05%
• Fluorides ≤50 ppm
• pH 2.0–4.0 (for 5% solution)
• Clarity ≤5 NTU
• Color ≤50 APHA
Monograph compliance is mandatory for registration.
input.csv
BatchNumber,AssayPercent,WaterContent,HeavyMetals,Arsenic,Lead,Iron,Nickel,Copper,Zinc,Sulfates,Fluorides,pH,ClarityNTU,ColorAPHA,EthanolPPM,AcetonePPM CRCL-2026-001,99.5,30.2,10,1.5,5,0.005,0.003,0.002,0.004,0.03,30,3.0,2,40,800,500
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 Chromium Chloride Quality Checker utility is used for Chromium Chloride. 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: Vitamins and minerals
Tags: assay, heavy metals, impurities, minerals, premix, specification, vitamins, water quality
2. Execution modes
ChromiumChlorideQualityChecker.exe → demo mode (console output) ChromiumChlorideQualityChecker.exe input.csv output.json → evaluate your data
3. Key controlled areas
- assay / content
- residual solvents
- heavy metals / elemental impurities
- pH and physicochemical parameters
4. Domain limits and critical parameters
- ⚠️ Critical for chromium preparations, dietary supplements, parenteral nutrition.
- Critical parameters:
- Assay 98.0–102.0% (on anhydrous basis)
- Water content 28.0–32.0% (for hexahydrate, Karl Fischer method)
- Heavy metals ≤20 ppm (as lead)
- Arsenic ≤3 ppm
- Lead ≤10 ppm
- Metal impurities: iron, nickel, copper, zinc ≤0.01% each
- Sulfates ≤0.05%
- Fluorides ≤50 ppm
- pH 2.0–4.0 (for 5% solution)
- Clarity ≤5 NTU
- Color ≤50 APHA
5. URS — user requirements
| ID | Requirement | Criticality | Acceptance criterion |
|---|---|---|---|
| URS-001 | The system shall accept an input.csv file for Chromium Chloride 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, residual solvents, 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 | CRCL-2026-001 | mandatory field; used for batch/lot traceability |
| 2 | AssayPercent | decimal | % | Assay % | 99.5 | numeric value; compared with assay/purity limit from specification or method |
| 3 | WaterContent | decimal | as specified | Water Content | 30.2 | numeric value; compared with assay/purity limit from specification or method |
| 4 | HeavyMetals | decimal | as specified | Heavy Metals | 10 | numeric value; checked as elemental/metal impurity |
| 5 | Arsenic | decimal | as specified | Arsenic | 1.5 | numeric value; checked as elemental/metal impurity |
| 6 | Lead | decimal | as specified | Lead | 5 | numeric value; checked as elemental/metal impurity |
| 7 | Iron | decimal | as specified | Iron | 0.005 | mandatory numeric value; rule comparison is performed by the utility |
| 8 | Nickel | decimal | as specified | Nickel | 0.003 | mandatory numeric value; rule comparison is performed by the utility |
| 9 | Copper | decimal | as specified | Copper | 0.002 | mandatory numeric value; rule comparison is performed by the utility |
| 10 | Zinc | decimal | as specified | Zinc | 0.004 | mandatory numeric value; rule comparison is performed by the utility |
| 11 | Sulfates | decimal | as specified | Sulfates | 0.03 | mandatory numeric value; rule comparison is performed by the utility |
| 12 | Fluorides | decimal | as specified | Fluorides | 30 | mandatory numeric value; rule comparison is performed by the utility |
| 13 | pH | decimal | pH | p H | 3.0 | mandatory numeric value; rule comparison is performed by the utility |
| 14 | ClarityNTU | decimal | as specified | Clarity NTU | 2 | mandatory numeric value; rule comparison is performed by the utility |
| 15 | ColorAPHA | decimal | as specified | Color APHA | 40 | mandatory numeric value; rule comparison is performed by the utility |
| 16 | EthanolPPM | decimal | ppm | Ethanol PPM | 800 | numeric value; checked as residual solvent against the applicable limit |
| 17 | AcetonePPM | decimal | ppm | Acetone PPM | 500 | numeric value; checked as residual solvent against the applicable limit |
CSV example
BatchNumber,AssayPercent,WaterContent,HeavyMetals,Arsenic,Lead,Iron,Nickel,Copper,Zinc,Sulfates,Fluorides,pH,ClarityNTU,ColorAPHA,EthanolPPM,AcetonePPM CRCL-2026-001,99.5,30.2,10,1.5,5,0.005,0.003,0.002,0.004,0.03,30,3.0,2,40,800,500
7. FS — functional specification
| ID | Function | Implementation description |
|---|---|---|
| FS-001 | CLI entry point | The executable ChromiumChlorideQualityChecker.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 Chromium Chloride, 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": "ChromiumChlorideQualityChecker",
"api": "Chromium Chloride",
"batchNumber": "CRCL-2026-001",
"overallStatus": "PASS|WARNING|FAIL",
"checkedAtUtc": "2026-05-18T00:00:00Z",
"checks": [
{
"parameter": "BatchNumber",
"value": "CRCL-2026-001",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "AssayPercent",
"value": "99.5",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "WaterContent",
"value": "30.2",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "HeavyMetals",
"value": "10",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Arsenic",
"value": "1.5",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Lead",
"value": "5",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Iron",
"value": "0.005",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Nickel",
"value": "0.003",
"unit": "as specified",
"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-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
Diabetes QC Suite
QC package for diabetes medicines: insulins, metformin, SGLT2/DPP-4/GLP-1 products, glucagon and supporting dosage-form quality checks.
OpenRadiology QC Suite
QC package for radiology and diagnostic imaging: radiopharmaceuticals, PET/SPECT, contrast media, iodinated and gadolinium products, plus particle, sterility and endotoxin checks.
OpenVitamins & Minerals QC Suite
Quality-control package for vitamins, minerals, premixes and nutrient substances.
Open