Purpose

Define user requirements for a standalone FUZKK utility that accepts laboratory CSV data, evaluates the records using limits embedded in code, and produces LabWare-compatible JSON.

Scope

The utility is intended for preliminary QC/QA review, integration testing, LIMS/LabWare flow and evidence-trail preparation. Final release decisions remain under the laboratory's validated procedure and responsible personnel.

Users

QC analyst, QA reviewer, CSV/validation engineer, LIMS/LabWare integration engineer, responsible laboratory specialist.

User requirements

1. The utility shall run without arguments and print its self-description, a built-in input.csv example from GetDemoData(), and demo evaluation for the embedded records.
2. The utility shall run with two arguments: input.csv output.json.
3. The utility shall not read input.csv and shall not write output.json when started without arguments.
4. CSV numeric values shall be parsed using CultureInfo.InvariantCulture.
5. Output shall be generated as LabWare-compatible JSON with Header, Samples, Results, Status, StatusCode, ErrorMessage, Description and DescriptionEN.
6. For PASS records, ErrorMessage shall be an empty string.
7. Embedded limits shall follow this priority: Ph. Eur. → British Pharmacopoeia / UK implementation → EAEU / regional requirements → EMA/ICH/EU guidance → USP fallback.
8. If an exact monograph is not known, strict standard API limits are used where applicable: assay 98–102%, total impurities ≤1.0%, individual impurity ≤0.5%.
9. For biologics and mAb-like products, aggregation, sterility and endotoxin checks shall be included where relevant to the utility purpose.
10. If a parameter may arrive in different units, the unit shall be represented as a separate input field or explicitly reflected in the input.csv field name.

Input CSV

BatchNumber,ProductName,Carbonyl_Shift_ppm,Amide_Band_Wavenumber,Open_Ring_Percent,Intact_Ring_Percent,Storage_Temp_C,Storage_Humidity_Percent,Days_In_Storage,Min_Intact_Ring_Percent
RING-2026-001,Amoxicillin Trihydrate,178.5,1770.0,0.3,99.7,25.0,40.0,30,99.0
RING-2026-002,Ceftriaxone Sodium,179.0,1775.0,0.1,99.9,20.0,30.0,60,99.0
RING-2026-003,6-APA (Improperly Stored),176.0,1750.0,5.5,94.5,35.0,70.0,90,99.0

input.csv fields

Utility description

Beta-Lactam Ring Integrity Checker — Beta-Lactam Ring Integrity Analyzer

Beta-Lactam Ring Integrity Checker — Beta-Lactam Ring Integrity Analyzer

ℹ️ Utility controls structural integrity of antibiotic core:
• Intact ring % (≥99%)
• Hydrolyzed form % (≤1%)
• Spectroscopic markers (NMR/IR)
• Storage risk assessment

⚠️ CRITICAL: Ring rupture means loss of activity!
Hydrolyzed forms are strong allergens.

Usage:
BetaLactamRingIntegrityChecker.exe → demo mode (console output)
BetaLactamRingIntegrityChecker.exe input.csv output.json → evaluate your data

Input format:
BatchNumber,ProductName,Carbonyl_Shift_ppm,Amide_Band_Wavenumber,Open_Ring_Percent,Intact_Ring_Percent,Storage_Temp_C,Storage_Humidity_Percent,Days_In_Storage,Min_Intact_Ring_Percent

Example:
RING-2026-001,Amoxicillin Trihydrate,178.5,1770.0,0.3,99.7,25.0,40.0,30,99.0

— WHY IS THIS NEEDED?
Ring integrity control is critical for all beta-lactam antibiotics (Shyndec, Sinopharm):
• Beta-lactam ring is the active center responsible for binding to bacterial enzymes
• Ring hydrolysis (due to moisture, heat, pH) leads to formation of penicilloic acid
• Penicilloic acid has no antibacterial activity but is a potent allergen
• Spectroscopic methods (NMR, IR) allow precise distinction between intact and open rings

⚠️ CRITICAL:
• Intact ring ≥99% — standard for high-quality intermediates and APIs
• Hydrolysis ≤1% — strict safety limit
• Carbonyl chemical shift in NMR must match reference (±0.1 ppm)
• Storage conditions (humidity <50%, temperature <25°C) are critical for stability

Key features:
• Integration of spectroscopic data (NMR/IR) with chemical analysis
• Direct calculation of hydrolyzed form percentage
• Degradation risk assessment during storage based on temperature and humidity
• Support for various beta-lactam classes (penicillins, cephalosporins)

Critical parameters:
• Intact Ring: ≥99%
• Open Ring (Hydrolysate): ≤1%
• Carbonyl Shift Deviation: ≤0.1 ppm
• Stability Risk Score: <10

💡 Usage tips:
1. Use 13C NMR for most accurate determination of carbonyl group state
2. IR spectroscopy is useful for rapid screening (~1770 cm-1 band)
3. Avoid prolonged exposure of samples to air moisture during preparation
4. Control solution pH as acidic and alkaline media accelerate hydrolysis
5. For unstable compounds (e.g., carbapenems), requirements may be even stricter

⚠️ Note: Unlike other impurities, beta-lactam ring hydrolysis is an irreversible degradation process of the active molecule itself. The utility helps identify not only current state but also predict risk of further degradation if storage conditions are violated.

Traceability and limitations

• The URS is used as the source document for functional specification, CSV review and later validation work.
• This document does not replace an approved pharmacopoeial monograph, validated analytical method or internal product specification.
• For product-specific limits, the approved customer specification takes priority.

The functional specification describes the behaviour of the standalone FUZKK console utility, input-data format, evaluation algorithm and output JSON structure.

Functional flow

1. Main() checks the number of arguments.
2. If no arguments are provided: PrintHello() prints the description and built-in input.csv example, then RunDemoEvaluation() executes Evaluate() over GetDemoData() and prints demo JSON.
3. If two arguments are provided: RunWithFiles(input.csv, output.json) reads CSV, evaluates each record and writes LabWare-compatible JSON.
4. LoadData() uses CultureInfo.InvariantCulture and shall not be called in no-arguments mode.
5. Evaluate() returns a named tuple with BatchNumber, ProductName, Parameters, CriticalFailCount, WarningCount, Recommendation and RecommendationEN.
6. GetIssues() builds messages for ErrorMessage in WARNING/FAIL cases.

Evaluation rules

• PASS: CriticalFailCount = 0 and WarningCount = 0.
• WARNING: CriticalFailCount = 0 and WarningCount > 0.
• FAIL: CriticalFailCount > 0.
• ERROR: exception during reading or processing.
• ErrorMessage remains empty for PASS.
• Limits are embedded in Program.cs; no external limit configuration is required.

Input and fields

BatchNumber,ProductName,Carbonyl_Shift_ppm,Amide_Band_Wavenumber,Open_Ring_Percent,Intact_Ring_Percent,Storage_Temp_C,Storage_Humidity_Percent,Days_In_Storage,Min_Intact_Ring_Percent
RING-2026-001,Amoxicillin Trihydrate,178.5,1770.0,0.3,99.7,25.0,40.0,30,99.0
RING-2026-002,Ceftriaxone Sodium,179.0,1775.0,0.1,99.9,20.0,30.0,60,99.0
RING-2026-003,6-APA (Improperly Stored),176.0,1750.0,5.5,94.5,35.0,70.0,90,99.0

Output JSON

{
  "Header": {
    "UtilityName": "BetaLactam_Ring_Integrity_Checker",
    "Version": "1.0.0",
    "Timestamp": "UTC",
    "InstrumentID": "FUZKK-QC-WORKSTATION",
    "OperatorID": "Admin"
  },
  "Samples": [
    {
      "SampleID": "from BatchNumber",
      "BatchNumber": "from CSV",
      "ProductName": "from CSV",
      "TestName": "utility-specific test",
      "AnalysisCode": "utility-specific code",
      "Status": "PASS | WARNING | FAIL | ERROR",
      "StatusCode": "1 | 2 | 0 | -1",
      "ErrorMessage": "",
      "Description": "Russian recommendation",
      "DescriptionEN": "English recommendation",
      "Results": [
        {
          "ParameterName": "parameter",
          "ResultValue": 0.0,
          "UnitOfMeasure": "unit",
          "SpecificationLimit": "limit",
          "IsWithinSpec": true
        }
      ]
    }
  ]
}