BiotinQualityChecker
Biotin
Biotin Quality Checker — Vitamin B7, Vitamin H (Ph. Eur. 2.2.7)
ℹ️ The utility checks assay, melting point, optical rotation, pH, impurities, residual solvents.
ℹ️ Does not use machine learning — rule-based logic only.
⚠️ Critical for vitamin products, dietary supplements, parenteral nutrition.
Usage:
BiotinQualityChecker.exe → demo mode (console output)
BiotinQualityChecker.exe input.csv output.json → evaluate your data
Input format:
BatchNumber,AssayPercent,MeltingPoint,OpticalRotation,pH,LossOnDrying,HeavyMetals,ImpurityA,ImpurityB,TotalImpurities,EthanolPPM,AcetonePPM,DichloromethanePPM,ClarityNTU,ColorAPHA
Example:
BT-2026-001,99.5,230.5,90.5,5.2,0.3,10,0.2,0.1,0.3,1000,500,200,3,40
— WHY IS THIS NEEDED?
Biotin (vitamin B7, vitamin H) is a water-soluble vitamin critical for:
• Metabolism of fats, carbohydrates, and amino acids
• Glucose and fatty acid synthesis
• Skin, hair, and nail health
• Parenteral nutrition (especially for preterm infants)
Critical parameters:
• Assay 98.0–102.0% (on dried basis)
• Melting point 228–232°C (with decomposition)
• Optical rotation +88° to +92° (in 1% solution in 0.1M NaOH)
• pH 4.5–6.5 (in 1% solution)
• Impurities: biotin-D-sulfoxide ≤0.5%, biotin-R-sulfoxide ≤0.5%, total ≤1.0%
• Heavy metals ≤20 ppm (as lead)
• Residual solvents (ethanol, acetone, dichloromethane)
Monograph compliance is mandatory for registration.
input.csv
BatchNumber,AssayPercent,MeltingPoint,OpticalRotation,pH,LossOnDrying,HeavyMetals,ImpurityA,ImpurityB,TotalImpurities,EthanolPPM,AcetonePPM,DichloromethanePPM,ClarityNTU,ColorAPHA BT-2026-001,99.5,230.5,90.5,5.2,0.3,10,0.2,0.1,0.3,1000,500,200,3,40
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 Biotin Quality Checker utility is used for Biotin. 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, Vitamins and minerals
Tags: API, assay, British Pharmacopoeia, heavy metals, impurities, minerals, monographs, premix, residual solvents, specification, vitamins, water quality
2. Execution modes
BiotinQualityChecker.exe → demo mode (console output) BiotinQualityChecker.exe input.csv output.json → evaluate your data
3. Key controlled areas
- assay / content
- purity and impurities
- residual solvents
- heavy metals / elemental impurities
- pH and physicochemical parameters
4. Domain limits and critical parameters
- ⚠️ Critical for vitamin products, dietary supplements, parenteral nutrition.
- Critical parameters:
- Assay 98.0–102.0% (on dried basis)
- Melting point 228–232°C (with decomposition)
- Optical rotation +88° to +92° (in 1% solution in 0.1M NaOH)
- pH 4.5–6.5 (in 1% solution)
- Impurities: biotin-D-sulfoxide ≤0.5%, biotin-R-sulfoxide ≤0.5%, total ≤1.0%
- Heavy metals ≤20 ppm (as lead)
- Residual solvents (ethanol, acetone, dichloromethane)
5. URS — user requirements
| ID | Requirement | Criticality | Acceptance criterion |
|---|---|---|---|
| URS-001 | The system shall accept an input.csv file for Biotin 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, 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 | BT-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 | MeltingPoint | decimal | °C | Melting Point | 230.5 | mandatory numeric value; rule comparison is performed by the utility |
| 4 | OpticalRotation | decimal | as specified | Optical Rotation | 90.5 | mandatory numeric value; rule comparison is performed by the utility |
| 5 | pH | decimal | pH | p H | 5.2 | mandatory numeric value; rule comparison is performed by the utility |
| 6 | LossOnDrying | decimal | as specified | Loss On Drying | 0.3 | mandatory numeric value; rule comparison is performed by the utility |
| 7 | HeavyMetals | decimal | as specified | Heavy Metals | 10 | numeric value; checked as elemental/metal impurity |
| 8 | ImpurityA | decimal | as specified | Impurity A | 0.2 | numeric value; compared with individual or total impurity limit |
| 9 | ImpurityB | decimal | as specified | Impurity B | 0.1 | numeric value; compared with individual or total impurity limit |
| 10 | TotalImpurities | decimal | as specified | Total Impurities | 0.3 | mandatory numeric value; rule comparison is performed by the utility |
| 11 | EthanolPPM | decimal | ppm | Ethanol PPM | 1000 | numeric value; checked as residual solvent against the applicable limit |
| 12 | AcetonePPM | decimal | ppm | Acetone PPM | 500 | numeric value; checked as residual solvent against the applicable limit |
| 13 | DichloromethanePPM | decimal | ppm | Dichloromethane PPM | 200 | mandatory numeric value; rule comparison is performed by the utility |
| 14 | ClarityNTU | decimal | as specified | Clarity NTU | 3 | 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 |
CSV example
BatchNumber,AssayPercent,MeltingPoint,OpticalRotation,pH,LossOnDrying,HeavyMetals,ImpurityA,ImpurityB,TotalImpurities,EthanolPPM,AcetonePPM,DichloromethanePPM,ClarityNTU,ColorAPHA BT-2026-001,99.5,230.5,90.5,5.2,0.3,10,0.2,0.1,0.3,1000,500,200,3,40
7. FS — functional specification
| ID | Function | Implementation description |
|---|---|---|
| FS-001 | CLI entry point | The executable BiotinQualityChecker.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 Biotin, 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": "BiotinQualityChecker",
"api": "Biotin",
"batchNumber": "BT-2026-001",
"overallStatus": "PASS|WARNING|FAIL",
"checkedAtUtc": "2026-05-18T00:00:00Z",
"checks": [
{
"parameter": "BatchNumber",
"value": "BT-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": "MeltingPoint",
"value": "230.5",
"unit": "°C",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "OpticalRotation",
"value": "90.5",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "pH",
"value": "5.2",
"unit": "pH",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "LossOnDrying",
"value": "0.3",
"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": "ImpurityA",
"value": "0.2",
"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
British Pharmacopoeia Monographs QC Suite
Utility package for British Pharmacopoeia monographs covering drug substances, APIs and finished products.
OpenDiabetes QC Suite
QC package for diabetes medicines: insulins, metformin, SGLT2/DPP-4/GLP-1 products, glucagon and supporting dosage-form quality checks.
OpenVitamins & Minerals QC Suite
Quality-control package for vitamins, minerals, premixes and nutrient substances.
Open