SucralfateQualityChecker
Sucralfate
Sucralfate Quality Checker — Gastroprotective Agent (Ph. Eur., USP)
ℹ️ The utility checks aluminum/sulfate content, loss on ignition, heavy metals, arsenic, lead.
ℹ️ Does not use machine learning — rule-based logic only.
⚠️ CRITICAL! Sulfate 25-30%. Arsenic ≤3 ppm. Lead ≤10 ppm!
Usage:
SucralfateQualityChecker.exe → demo mode
SucralfateQualityChecker.exe input.csv output.json → evaluate data
Input format:
BatchNumber,Aluminum_Oxide_Equivalent_Percent,Sulfate_Percent,Loss_On_Ignition_Percent,Arsenic_ppm,Heavy_Metals_As_Pb_ppm,Lead_ppm,Chloride_Percent,Iron_Fe_Percent,pH_Value_Suspension,Particle_Size_Distribution_Um,SterilityTest,Bacterial_Endotoxins_EU_per_g,Microbial_Count_TAMC,Microbial_Count_TYMC,EColi_Detected,Salmonella_Detected,Residual_Solvent_Water_Percent
Example:
SUC-SUB-2026-001,15.0,27.5,17.5,1.0,20.0,5.0,0.2,0.05,8.0,0.0,0,0.1,50,10,0,0,5.0
— WHY IS THIS NEEDED?
Sucralfate — aluminum-sucrose sulfate complex:
• Stoichiometry: Since it is not a pure substance, sulfate content (25–30%) and aluminum oxide equivalent (13–17%) are critical. Deviation indicates incorrect complex composition.
• Loss on Ignition: Control of mass loss (15–20%) ensures correct moisture content and absence of excess impurities.
• Toxic Elements: As a drug acting in the GI tract, trace absorption is possible. Limits for arsenic (≤3 ppm), lead (≤10 ppm), and heavy metals (≤40 ppm) are strictly regulated.
• Microbiology: Standard limits for non-sterile products, but strict requirements for E. coli and Salmonella.
⚠️ CRITICAL:
• Al2O3 Equivalent: 13–17%
• Sulfate Content: 25–30% (Critical!)
• Loss on Ignition: 15–20%
• Arsenic: ≤ 3 ppm (Toxic)
• Heavy Metals (as Pb): ≤ 40 ppm (Toxic)
• Lead: ≤ 10 ppm (Toxic)
• Chlorides: ≤ 0.5%
• Iron: ≤ 0.1%
• Suspension pH: 7.0–9.0
• Water: ≤ 10%
• Sterility: No growth (for injection)
• Endotoxins: ≤ 0.5 EU/g (Critical for injection)
• Microbiology: standard limits
⚠️ Note: Utility focuses on specific parameters of the complex compound: stoichiometric purity (sulfate/aluminum) and absence of toxic elements. Deviation in sulfate content is a sign of falsification or incorrect synthesis.
input.csv
BatchNumber,Aluminum_Oxide_Equivalent_Percent,Sulfate_Percent,Loss_On_Ignition_Percent,Arsenic_ppm,Heavy_Metals_As_Pb_ppm,Lead_ppm,Chloride_Percent,Iron_Fe_Percent,pH_Value_Suspension,Particle_Size_Distribution_Um,SterilityTest,Bacterial_Endotoxins_EU_per_g,Microbial_Count_TAMC,Microbial_Count_TYMC,EColi_Detected,Salmonella_Detected,Residual_Solvent_Water_Percent SUC-SUB-2026-001,15.0,27.5,17.5,1.0,20.0,5.0,0.2,0.05,8.0,0.0,0,0.1,50,10,0,0,5.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 Sucralfate Quality Checker utility is used for Sucralfate. 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, heavy metals, impurities, injectables, medical gases, microbiology, oncology
2. Execution modes
SucralfateQualityChecker.exe → demo mode SucralfateQualityChecker.exe input.csv output.json → evaluate data
3. Key controlled areas
- residual solvents
- microbiology and pathogens
- heavy metals / elemental impurities
- pH and physicochemical parameters
4. Domain limits and critical parameters
- ⚠️ CRITICAL! Sulfate 25-30%. Arsenic ≤3 ppm. Lead ≤10 ppm!
- Toxic Elements: As a drug acting in the GI tract, trace absorption is possible. Limits for arsenic (≤3 ppm), lead (≤10 ppm), and heavy metals (≤40 ppm) are strictly regulated.
- ⚠️ CRITICAL:
- Al2O3 Equivalent: 13–17%
- Sulfate Content: 25–30% (Critical!)
- Loss on Ignition: 15–20%
- Arsenic: ≤ 3 ppm (Toxic)
- Heavy Metals (as Pb): ≤ 40 ppm (Toxic)
- Lead: ≤ 10 ppm (Toxic)
- Chlorides: ≤ 0.5%
- Iron: ≤ 0.1%
- Suspension pH: 7.0–9.0
- Water: ≤ 10%
- Sterility: No growth (for injection)
- Endotoxins: ≤ 0.5 EU/g (Critical for injection)
- Microbiology: standard limits
- ⚠️ Note: Utility focuses on specific parameters of the complex compound: stoichiometric purity (sulfate/aluminum) and absence of toxic elements. Deviation in sulfate content is a sign of falsification or incorrect synthesis.
5. URS — user requirements
| ID | Requirement | Criticality | Acceptance criterion |
|---|---|---|---|
| URS-001 | The system shall accept an input.csv file for Sucralfate 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: 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 | SUC-SUB-2026-001 | mandatory field; used for batch/lot traceability |
| 2 | Aluminum_Oxide_Equivalent_Percent | decimal | % | Aluminum Oxide Equivalent % | 15.0 | numeric value; checked as elemental/metal impurity |
| 3 | Sulfate_Percent | decimal | % | Sulfate % | 27.5 | mandatory numeric value; rule comparison is performed by the utility |
| 4 | Loss_On_Ignition_Percent | decimal | % | Loss On Ignition % | 17.5 | mandatory numeric value; rule comparison is performed by the utility |
| 5 | Arsenic_ppm | decimal | ppm | Arsenic ppm | 1.0 | numeric value; checked as elemental/metal impurity |
| 6 | Heavy_Metals_As_Pb_ppm | decimal | ppm | Heavy Metals As Pb ppm | 20.0 | numeric value; checked as elemental/metal impurity |
| 7 | Lead_ppm | decimal | ppm | Lead ppm | 5.0 | numeric value; checked as elemental/metal impurity |
| 8 | Chloride_Percent | decimal | % | Chloride % | 0.2 | mandatory numeric value; rule comparison is performed by the utility |
| 9 | Iron_Fe_Percent | decimal | % | Iron Fe % | 0.05 | mandatory numeric value; rule comparison is performed by the utility |
| 10 | pH_Value_Suspension | decimal | pH | p H Value Suspension | 8.0 | mandatory numeric value; rule comparison is performed by the utility |
| 11 | Particle_Size_Distribution_Um | decimal | µm | Particle Size Distribution Um | 0.0 | mandatory numeric value; rule comparison is performed by the utility |
| 12 | SterilityTest | boolean / flag | 0/1 | Sterility Test | 0 | valid flag required; prohibited organisms and growth are normally expected as 0 / absent |
| 13 | Bacterial_Endotoxins_EU_per_g | decimal | EU/ml | Bacterial Endotoxins EU per g | 0.1 | numeric value; critical safety attribute compared with endotoxin limit |
| 14 | Microbial_Count_TAMC | decimal | as specified | Microbial Count TAMC | 50 | numeric value; compared with microbiological limits |
| 15 | Microbial_Count_TYMC | decimal | as specified | Microbial Count TYMC | 10 | numeric value; compared with microbiological limits |
| 16 | EColi_Detected | boolean / flag | 0/1 | EColi Detected | 0 | valid flag required; prohibited organisms and growth are normally expected as 0 / absent |
| 17 | Salmonella_Detected | boolean / flag | 0/1 | Salmonella Detected | 0 | valid flag required; prohibited organisms and growth are normally expected as 0 / absent |
| 18 | Residual_Solvent_Water_Percent | decimal | % | Residual Solvent Water % | 5.0 | numeric value; checked as residual solvent against the applicable limit |
CSV example
BatchNumber,Aluminum_Oxide_Equivalent_Percent,Sulfate_Percent,Loss_On_Ignition_Percent,Arsenic_ppm,Heavy_Metals_As_Pb_ppm,Lead_ppm,Chloride_Percent,Iron_Fe_Percent,pH_Value_Suspension,Particle_Size_Distribution_Um,SterilityTest,Bacterial_Endotoxins_EU_per_g,Microbial_Count_TAMC,Microbial_Count_TYMC,EColi_Detected,Salmonella_Detected,Residual_Solvent_Water_Percent SUC-SUB-2026-001,15.0,27.5,17.5,1.0,20.0,5.0,0.2,0.05,8.0,0.0,0,0.1,50,10,0,0,5.0
7. FS — functional specification
| ID | Function | Implementation description |
|---|---|---|
| FS-001 | CLI entry point | The executable SucralfateQualityChecker.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 Sucralfate, 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": "SucralfateQualityChecker",
"api": "Sucralfate",
"batchNumber": "SUC-SUB-2026-001",
"overallStatus": "PASS|WARNING|FAIL",
"checkedAtUtc": "2026-05-18T00:00:00Z",
"checks": [
{
"parameter": "BatchNumber",
"value": "SUC-SUB-2026-001",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Aluminum_Oxide_Equivalent_Percent",
"value": "15.0",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Sulfate_Percent",
"value": "27.5",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Loss_On_Ignition_Percent",
"value": "17.5",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Arsenic_ppm",
"value": "1.0",
"unit": "ppm",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Heavy_Metals_As_Pb_ppm",
"value": "20.0",
"unit": "ppm",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Lead_ppm",
"value": "5.0",
"unit": "ppm",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Chloride_Percent",
"value": "0.2",
"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.