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,Clavulanate_Potency_Percent,Initial_Potency_Percent,Clavulanate_Aldehyde_Percent,Clavulanic_Acid_Percent,Unknown_Impurities_Percent,Temperature_C,Humidity_Percent,pH_Value,Storage_Days,Min_Potency_Percent,Max_Aldehyde_Percent
CLAV-STAB-2026-001,Potassium Clavulanate,96.5,100.0,0.2,1.5,1.8,25.0,40.0,6.8,30,90.0,0.5
CLAV-STAB-2026-002,Amox/Clav Dry Powder,92.0,100.0,0.8,3.0,4.2,30.0,55.0,6.5,90,90.0,0.5
CLAV-STAB-2026-003,Clavulanate Solution (Unstable),85.0,100.0,2.5,8.0,4.5,25.0,0.0,5.0,7,90.0,0.5

input.csv fields

Utility description

Clavulanate Stability Degradation Monitor — Clavulanate Stability and Degradation Monitor

Clavulanate Stability Degradation Monitor — Clavulanate Stability and Degradation Monitor

ℹ️ Utility controls stability of highly unstable inhibitor:
• Remaining potency (≥90%)
• Clavulanate aldehyde (≤0.5%)
• pH and humidity impact
• Degradation kinetics

⚠️ CRITICAL: Clavulanate rapidly degrades forming toxic aldehyde!
Requires strict pH control and lyophilization.

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

Input format:
BatchNumber,ProductName,Clavulanate_Potency_Percent,Initial_Potency_Percent,Clavulanate_Aldehyde_Percent,Clavulanic_Acid_Percent,Unknown_Impurities_Percent,Temperature_C,Humidity_Percent,pH_Value,Storage_Days,Min_Potency_Percent,Max_Aldehyde_Percent

Example:
CLAV-STAB-2026-001,Potassium Clavulanate,96.5,100.0,0.2,1.5,1.8,25.0,40.0,6.8,30,90.0,0.5

— WHY IS THIS NEEDED?
Clavulanate stability control is critical for combined antibiotics (Shyndec, Sinopharm):
• Clavulanic acid is one of the most unstable beta-lactam compounds
• Degradation produces clavulanate aldehyde, which is toxic and mutagenic
• Stability strongly depends on pH (optimum 6.0-7.5) and humidity
• In aqueous solutions degrades in hours/days, in solid form — months/years
• Strict monitoring required to ensure safety and efficacy until end of shelf life

⚠️ CRITICAL:
• Potency loss ≤10% over shelf life
• Clavulanate aldehyde ≤0.5% (strict toxicological limit)
• pH control in range 6.0-7.5 to minimize hydrolysis
• Lyophilization (freeze-drying) often necessary for stabilization
• Avoid high temperatures and humidity

Key features:
• Degradation kinetics tracking over time
• Specific control of toxic aldehyde
• Storage condition impact assessment (temperature, humidity, pH)
• Instability risk calculation

Critical parameters:
• Remaining Potency: ≥90%
• Clavulanate Aldehyde: ≤0.5%
• pH: 6.0–7.5
• Risk Score: <5

💡 Usage tips:
1. Use stabilized forms (e.g., with sodium silicate) for tests
2. Perform accelerated stability testing (40°C/75% RH) for shelf-life prediction
3. Control aldehyde by HPLC with derivatization or LC-MS
4. For solutions, prepare immediately before use
5. Store raw material at temperature not above 25°C in airtight containers

⚠️ Note: Unlike other antibiotics where degradation leads only to loss of activity, clavulanate decay creates a new hazard — toxic products. The utility helps balance between inhibitor efficacy and patient safety.

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,Clavulanate_Potency_Percent,Initial_Potency_Percent,Clavulanate_Aldehyde_Percent,Clavulanic_Acid_Percent,Unknown_Impurities_Percent,Temperature_C,Humidity_Percent,pH_Value,Storage_Days,Min_Potency_Percent,Max_Aldehyde_Percent
CLAV-STAB-2026-001,Potassium Clavulanate,96.5,100.0,0.2,1.5,1.8,25.0,40.0,6.8,30,90.0,0.5
CLAV-STAB-2026-002,Amox/Clav Dry Powder,92.0,100.0,0.8,3.0,4.2,30.0,55.0,6.5,90,90.0,0.5
CLAV-STAB-2026-003,Clavulanate Solution (Unstable),85.0,100.0,2.5,8.0,4.5,25.0,0.0,5.0,7,90.0,0.5

Output JSON

{
  "Header": {
    "UtilityName": "Clavulanate_Stability_Degradation_Monitor",
    "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
        }
      ]
    }
  ]
}