ProteinResidueAnalyzer
Protein Residue Analyzer
Protein Residue Analyzer — Residual Protein and Allergen Analysis (Ph. Eur., USP)
ℹ️ The utility checks total protein, specific allergens, test validity (R², controls).
ℹ️ Does not use machine learning — rule-based logic only.
⚠️ CRITICAL! Total protein ≤ 10 ppm. Specific allergen ≤ 5 ppm. Test validity mandatory!
Usage:
ProteinResidueAnalyzer.exe → demo mode
ProteinResidueAnalyzer.exe input.csv output.json → evaluate data
Input format:
BatchNumber,Total_Protein_ppm,Specific_Allergen_ppm,Sample_Weight_mg,Dilution_Factor,Absorbance_OD,Standard_Curve_R2,Positive_Control_Recovery_Percent,Negative_Control_OD,LOD_ppm,LOQ_ppm,pH_Value,SterilityTest,Endotoxin_EU_ml,Test_Method
Example:
PROT-HA-2026-001,4.5,2.1,50.0,10.0,0.35,0.995,95.0,0.05,0.5,1.5,7.2,0,0.1,ELISA
— WHY IS THIS NEEDED?
Residual protein control critical for non-biofermented fillers (rooster comb derived) and collagen products:
• Residual protein — potent allergen, can cause anaphylactic shock on re-exposure
• Specific allergens (avian, bovine) require separate quantitative determination (ELISA)
• Analysis methods: ELISA, BCA, Lowry — all require strict calibration curve validation
⚠️ CRITICAL:
• Total Protein ≤ 10 ppm — safety standard for injectable HA forms
• Specific Allergen ≤ 5 ppm — stricter limit for species-specific proteins
• Test Validity: R² ≥ 0.98 (linearity), Positive Control recovery 70–130%, Negative Control clean
• If test invalid — result cannot be used for batch release
• Sterility and Endotoxins — mandatory accompanying parameters
⚠️ Note: Utility first checks analytical procedure validity. If calibration curve non-linear or controls fail, verdict is "INVALID". This prevents false release based on incorrect data. Separate control of total and specific protein allows precise allergy risk assessment. For biofermented HA, protein level usually below detection limit, but analysis still performed to confirm process purity.
input.csv
BatchNumber,Total_Protein_ppm,Specific_Allergen_ppm,Sample_Weight_mg,Dilution_Factor,Absorbance_OD,Standard_Curve_R2,Positive_Control_Recovery_Percent,Negative_Control_OD,LOD_ppm,LOQ_ppm,pH_Value,SterilityTest,Endotoxin_EU_ml,Test_Method PROT-HA-2026-001,4.5,2.1,50.0,10.0,0.35,0.995,95.0,0.05,0.5,1.5,7.2,0,0.1,ELISA
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 Protein Residue Analyzer utility is used for Protein Residue Analyzer. 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: Dermal fillers
Tags: dermal fillers, endotoxins, hyaluronic acid, particles, rheology, sterility
2. Execution modes
ProteinResidueAnalyzer.exe → demo mode ProteinResidueAnalyzer.exe input.csv output.json → evaluate data
3. Key controlled areas
- microbiology and pathogens
- pH and physicochemical parameters
4. Domain limits and critical parameters
- ⚠️ CRITICAL! Total protein ≤ 10 ppm. Specific allergen ≤ 5 ppm. Test validity mandatory!
- ⚠️ CRITICAL:
- Total Protein ≤ 10 ppm — safety standard for injectable HA forms
- Specific Allergen ≤ 5 ppm — stricter limit for species-specific proteins
- Test Validity: R² ≥ 0.98 (linearity), Positive Control recovery 70–130%, Negative Control clean
- If test invalid — result cannot be used for batch release
- Sterility and Endotoxins — mandatory accompanying parameters
- ⚠️ Note: Utility first checks analytical procedure validity. If calibration curve non-linear or controls fail, verdict is "INVALID". This prevents false release based on incorrect data. Separate control of total and specific protein allows precise allergy risk assessment. For biofermented HA, protein level usually below detection limit, but analysis still performed to confirm process purity.
5. URS — user requirements
| ID | Requirement | Criticality | Acceptance criterion |
|---|---|---|---|
| URS-001 | The system shall accept an input.csv file for Protein Residue Analyzer 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: microbiology and pathogens, 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 | PROT-HA-2026-001 | mandatory field; used for batch/lot traceability |
| 2 | Total_Protein_ppm | decimal | ppm | Total Protein ppm | 4.5 | mandatory numeric value; rule comparison is performed by the utility |
| 3 | Specific_Allergen_ppm | decimal | ppm | Specific Allergen ppm | 2.1 | mandatory numeric value; rule comparison is performed by the utility |
| 4 | Sample_Weight_mg | decimal | as specified | Sample Weight mg | 50.0 | mandatory numeric value; rule comparison is performed by the utility |
| 5 | Dilution_Factor | decimal | as specified | Dilution Factor | 10.0 | mandatory numeric value; rule comparison is performed by the utility |
| 6 | Absorbance_OD | decimal | as specified | Absorbance OD | 0.35 | mandatory numeric value; rule comparison is performed by the utility |
| 7 | Standard_Curve_R2 | decimal | as specified | Standard Curve R2 | 0.995 | mandatory numeric value; rule comparison is performed by the utility |
| 8 | Positive_Control_Recovery_Percent | boolean / flag | % | Positive Control Recovery % | 95.0 | mandatory numeric value; rule comparison is performed by the utility |
| 9 | Negative_Control_OD | boolean / flag | as specified | Negative Control OD | 0.05 | mandatory numeric value; rule comparison is performed by the utility |
| 10 | LOD_ppm | decimal | ppm | LOD ppm | 0.5 | mandatory numeric value; rule comparison is performed by the utility |
| 11 | LOQ_ppm | decimal | ppm | LOQ ppm | 1.5 | mandatory numeric value; rule comparison is performed by the utility |
| 12 | pH_Value | decimal | pH | p H Value | 7.2 | mandatory numeric value; rule comparison is performed by the utility |
| 13 | SterilityTest | boolean / flag | 0/1 | Sterility Test | 0 | valid flag required; prohibited organisms and growth are normally expected as 0 / absent |
| 14 | Endotoxin_EU_ml | decimal | as specified | Endotoxin EU ml | 0.1 | numeric value; critical safety attribute compared with endotoxin limit |
| 15 | Test_Method | text | as specified | Test Method | ELISA | mandatory value; format and acceptability are checked by the utility |
CSV example
BatchNumber,Total_Protein_ppm,Specific_Allergen_ppm,Sample_Weight_mg,Dilution_Factor,Absorbance_OD,Standard_Curve_R2,Positive_Control_Recovery_Percent,Negative_Control_OD,LOD_ppm,LOQ_ppm,pH_Value,SterilityTest,Endotoxin_EU_ml,Test_Method PROT-HA-2026-001,4.5,2.1,50.0,10.0,0.35,0.995,95.0,0.05,0.5,1.5,7.2,0,0.1,ELISA
7. FS — functional specification
| ID | Function | Implementation description |
|---|---|---|
| FS-001 | CLI entry point | The executable ProteinResidueAnalyzer.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 Protein Residue Analyzer, 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": "ProteinResidueAnalyzer",
"api": "Protein Residue Analyzer",
"batchNumber": "PROT-HA-2026-001",
"overallStatus": "PASS|WARNING|FAIL",
"checkedAtUtc": "2026-05-18T00:00:00Z",
"checks": [
{
"parameter": "BatchNumber",
"value": "PROT-HA-2026-001",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Total_Protein_ppm",
"value": "4.5",
"unit": "ppm",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Specific_Allergen_ppm",
"value": "2.1",
"unit": "ppm",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Sample_Weight_mg",
"value": "50.0",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Dilution_Factor",
"value": "10.0",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Absorbance_OD",
"value": "0.35",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Standard_Curve_R2",
"value": "0.995",
"unit": "as specified",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Positive_Control_Recovery_Percent",
"value": "95.0",
"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. |
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
Dermal Fillers QC Suite
Package for injectable implants and dermal fillers: hyaluronic acid, CaHA, PLLA, PMMA, collagen and related tests.
Open