ThunbergFritillaryBulbQualityChecker
Thunberg Fritillary Bulb
Thunberg Fritillary Bulb Quality Checker — Quality control of Zhe Bei Mu bulbs
ℹ️ The utility checks steroidal alkaloids content (as peimine), loss on drying, total ash, and ash insoluble in HCl.
ℹ️ Related to universal utilities: HerbalDrugQualityChecker, ImpurityThresholdChecker.
Usage:
ThunbergFritillaryBulbQualityChecker.exe → demo mode (console output)
ThunbergFritillaryBulbQualityChecker.exe input.csv output.json → evaluate your data
Input format:
BatchNumber,Alkaloids_percent,LossOnDrying_percent,TotalAsh_percent,AshInsolubleInHCl_percent
Example:
THU20250110,0.85,10.5,7.8,1.3
📌 Analytical method: HPLC determination of steroidal alkaloids (peimine, thiazine). Ph. Eur. 2568 requirements: alkaloids ≥0.8%, loss on drying ≤12.0%, total ash ≤8.0%, ash insoluble in HCl ≤1.5%.
⚠️ Note: Zhe Bei Mu is used in Traditional Chinese Medicine as an expectorant and antitussive. Alkaloids provide anti-inflammatory and mucolytic effects.
input.csv
BatchNumber,Alkaloids_percent,LossOnDrying_percent,TotalAsh_percent,AshInsolubleInHCl_percent THU20250110,0.85,10.5,7.8,1.3
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 Thunberg Fritillary Bulb Quality Checker utility is used for Thunberg Fritillary Bulb. 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: Herbal pharmacopoeia
Tags: ash, BHP, botanical, herbal, impurities, loss on drying, markers
2. Execution modes
ThunbergFritillaryBulbQualityChecker.exe → demo mode (console output) ThunbergFritillaryBulbQualityChecker.exe input.csv output.json → evaluate your data
3. Key controlled areas
Key control areas are defined by the input.csv columns and the implemented utility rules.
4. Domain limits and critical parameters
- ⚠️ Note: Zhe Bei Mu is used in Traditional Chinese Medicine as an expectorant and antitussive. Alkaloids provide anti-inflammatory and mucolytic effects.
5. URS — user requirements
| ID | Requirement | Criticality | Acceptance criterion |
|---|---|---|---|
| URS-001 | The system shall accept an input.csv file for Thunberg Fritillary Bulb 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: input.csv 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 | THU20250110 | mandatory field; used for batch/lot traceability |
| 2 | Alkaloids_percent | decimal | % | Alkaloids percent | 0.85 | mandatory numeric value; rule comparison is performed by the utility |
| 3 | LossOnDrying_percent | decimal | % | Loss On Drying percent | 10.5 | mandatory numeric value; rule comparison is performed by the utility |
| 4 | TotalAsh_percent | decimal | % | Total Ash percent | 7.8 | mandatory numeric value; rule comparison is performed by the utility |
| 5 | AshInsolubleInHCl_percent | decimal | % | Ash Insoluble In HCl percent | 1.3 | mandatory numeric value; rule comparison is performed by the utility |
CSV example
BatchNumber,Alkaloids_percent,LossOnDrying_percent,TotalAsh_percent,AshInsolubleInHCl_percent THU20250110,0.85,10.5,7.8,1.3
7. FS — functional specification
| ID | Function | Implementation description |
|---|---|---|
| FS-001 | CLI entry point | The executable ThunbergFritillaryBulbQualityChecker.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 Thunberg Fritillary Bulb, 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": "ThunbergFritillaryBulbQualityChecker",
"api": "Thunberg Fritillary Bulb",
"batchNumber": "THU20250110",
"overallStatus": "PASS|WARNING|FAIL",
"checkedAtUtc": "2026-05-18T00:00:00Z",
"checks": [
{
"parameter": "BatchNumber",
"value": "THU20250110",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Alkaloids_percent",
"value": "0.85",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "LossOnDrying_percent",
"value": "10.5",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "TotalAsh_percent",
"value": "7.8",
"unit": "%",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "AshInsolubleInHCl_percent",
"value": "1.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. |
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 Herbal Pharmacopoeia QC Suite
Large utility package for herbal drugs, botanicals and phytopharmaceutical monographs.
Open