HemagglutinationTiterChecker
Hemagglutination Titer
Vet veterinary veterinary vaccines animal health adjuvants aquaculture batch release CSV→JSON
Open selectionUtility description: Hemagglutination Titer
Hemagglutination Titer Checker — Control of Hemagglutination Titer (HA)
ℹ️ Utility assesses hemagglutinin activity in viral vaccines (mainly influenza) according to Ph. Eur. and WHO requirements:
• Hemagglutination Titer (HA Titer): Quantitative measure of virus ability to agglutinate red blood cells.
• Control Validity: Control serum titer must match expected value (within one dilution step).
• Agglutination Pattern: Check for absence of prozone effect (excess antibody/antigen) or weak reaction.
• RBC Type: Consideration of animal species (chicken, turkey, guinea pig) as sensitivity varies.
⚠️ CRITICAL:
• Low HA titer indicates low antigen content, reducing vaccine efficacy.
• Prozone effect can lead to false-negative results or underestimation of titer.
• Invalid serum control invalidates the entire test.
Usage:
HemagglutinationTiterChecker.exe → demo mode (console output)
HemagglutinationTiterChecker.exe input.csv output.json → evaluate your data
Input format:
BatchNumber,ProductName,MeasuredHATiter,MinRequiredHATiter,RBC_Type,ControlSerumTiter,ExpectedControlTiter,AgglutinationPattern
Example:
HA-001,Flu H1N1,256,128,1,64,64,Normal
— WHY IS THIS NEEDED?
For inactivated influenza vaccines, hemagglutinin content is a key indicator of antigen dose (typically 15 µg HA per strain).
HA test is used for antigen standardization before vaccine formulation and for stability control.
It is a rapid and inexpensive screening method, often used in pair with SRID (Single Radial Immunodiffusion).
⚠️ CRITICAL:
• RBC Sensitivity: Different virus strains agglutinate RBCs of different bird species better. Choosing correct RBC type is critical.
• Temperature: Test is usually performed at 4°C or room temperature depending on protocol.
• Incubation Time: Results must be read at strictly defined time before RBC sedimentation.
• Specificity: HA is not specific only to infectious virus; it measures all particles with hemagglutinin (including defective ones).
Key features:
• Verification of titer compliance with minimum requirements
• Test validation via control serum
• Detection of agglutination anomalies (prozone)
• Generation of reports for biocontrol departments and LIMS LabWare
• Compliance with Ph. Eur. and WHO requirements for influenza vaccines
Critical parameters:
• HA Titer: ≥ Declared value (e.g., 128 HAU)
• Control Deviation: ≤ 25%
• Pattern: Normal (no prozone)
💡 Usage tips:
1. RBC Suspension Preparation: Red blood cell concentration must be standard (usually 0.5-1.0%).
2. Shaking: Gentle shaking of the plate before reading is necessary to distinguish true agglutination from sediment.
3. Prozone Interpretation: If prozone is observed, the sample should be further diluted and test repeated.
4. Correlation with SRID: HA titer correlates with protein content, but SRID is a more specific method for quantifying immunogenic HA.
5. RBC Storage: Red blood cells must be fresh or properly stabilized (Alsever's solution).
⚠️ Note: Although HA is a standard test, for modern adjuvanted or recombinant vaccines, additional activity confirmation methods (e.g., neuraminidase activity or ELISA) may be required.input.csv
BatchNumber,ProductName,MeasuredHATiter,MinRequiredHATiter,RBC_Type,ControlSerumTiter,ExpectedControlTiter,AgglutinationPattern HA-FLU-2026-001,Influenza A/H1N1 Antigen,256,128,1,64,64,Normal HA-FLU-2026-002,Influenza B/Yamagata,128,128,2,32,32,Normal HA-FAIL-2026-003,Influenza A/H3N2,64,128,1,60,64,Prozone
URS & FS — User Requirements and Functional Specification
This document describes the controlled interface and behaviour of HemagglutinationTiterChecker for Hemagglutination Titer Checker.
Domain limits and critical parameters
Key fragments from the source description are shown below. Before production use, limits must be verified against the approved specification, registration dossier and local SOPs.
- ℹ️ Utility assesses hemagglutinin activity in viral vaccines (mainly influenza) according to Ph. Eur. and WHO requirements:
- • Control Validity: Control serum titer must match expected value (within one dilution step).
- ⚠️ CRITICAL:
- • RBC Sensitivity: Different virus strains agglutinate RBCs of different bird species better. Choosing correct RBC type is critical.
- • Incubation Time: Results must be read at strictly defined time before RBC sedimentation.
- • Compliance with Ph. Eur. and WHO requirements for influenza vaccines
- Critical parameters:
- • HA Titer: ≥ Declared value (e.g., 128 HAU)
- • Control Deviation: ≤ 25%
- 1. RBC Suspension Preparation: Red blood cell concentration must be standard (usually 0.5-1.0%).
- 5. RBC Storage: Red blood cells must be fresh or properly stabilized (Alsever's solution).
URS — User Requirements Specification
| ID | Requirement | Criticality | Acceptance criterion |
|---|---|---|---|
| URS-001 | The utility shall accept an input.csv file for Hemagglutination Titer Checker with headers defined in the data contract. | High | The file is processed without manual header editing. |
| URS-002 | The utility shall perform deterministic QC evaluation without machine learning and without probabilistic conformance decisions. | High | Identical input data, rule version and configuration produce reproducible results. |
| URS-003 | The utility shall validate mandatory fields, data types, ranges, units and domain plausibility. | High | Schema, conversion and range errors are explicitly reported. |
| URS-004 | The utility shall apply domain limits and rules from the description, approved specification, registration dossier and local SOPs. | High | Each check has PASS/WARNING/FAIL and a clear message. |
| URS-005 | The utility shall generate output.json with machine-readable results, source values, warnings, failures and critical findings. | High | JSON is suitable for LIMS/ELN/MES integration and QA/QC review. |
| URS-006 | The utility shall preserve traceability between batch/sample, input file, applied rules and final status. | High | Output contains identifiers, checked parameters and audit metadata. |
| URS-007 | The documentation shall support IQ/OQ/PQ, CSV/CSA and review by internal QA or inspectors. | Medium | URS, FS, input/output contract and test scenarios are supplied with the utility. |
| URS-008 | The utility shall be used as a QC decision-support tool and not as a substitute for approved specifications and QA/QP release decision. | Medium | Documentation states change control and limit-verification expectations. |
input.csv contract
| # | Field | Type | Sample | Purpose |
|---|---|---|---|---|
| 1 | BatchNumber | string / controlled vocabulary | HA-FLU-2026-001 | Batch or lot identifier used for traceability. |
| 2 | ProductName | string / controlled vocabulary | Influenza A/H1N1 Antigen | Product or dosage-form name under evaluation. |
| 3 | MeasuredHATiter | decimal | 256 | Controlled input parameter for deterministic QC rules. |
| 4 | MinRequiredHATiter | decimal | 128 | Controlled input parameter for deterministic QC rules. |
| 5 | RBC_Type | string / controlled vocabulary | 1 | Controlled input parameter for deterministic QC rules. |
| 6 | ControlSerumTiter | string / controlled vocabulary | 64 | Control point/control sample for assay run validity. |
| 7 | ExpectedControlTiter | decimal | 64 | Control point/control sample for assay run validity. |
| 8 | AgglutinationPattern | string / controlled vocabulary | Normal | Controlled input parameter for deterministic QC rules. |
BatchNumber,ProductName,MeasuredHATiter,MinRequiredHATiter,RBC_Type,ControlSerumTiter,ExpectedControlTiter,AgglutinationPattern HA-FLU-2026-001,Influenza A/H1N1 Antigen,256,128,1,64,64,Normal HA-FLU-2026-002,Influenza B/Yamagata,128,128,2,32,32,Normal HA-FAIL-2026-003,Influenza A/H3N2,64,128,1,60,64,Prozone
Input validation rules
| ID | Field | Rule | Criticality |
|---|---|---|---|
| VR-001 | BatchNumber | The field shall match an approved dictionary or accepted string representation. | High |
| VR-002 | ProductName | The field shall match an approved dictionary or accepted string representation. | High |
| VR-003 | MeasuredHATiter | The field shall match an approved dictionary or accepted string representation. | High |
| VR-004 | MinRequiredHATiter | The field shall match an approved dictionary or accepted string representation. | Medium |
| VR-005 | RBC_Type | The field shall match an approved dictionary or accepted string representation. | Medium |
| VR-006 | ControlSerumTiter | The field shall match an approved dictionary or accepted string representation. | Medium |
| VR-007 | ExpectedControlTiter | The field shall match an approved dictionary or accepted string representation. | Medium |
| VR-008 | AgglutinationPattern | The field shall match an approved dictionary or accepted string representation. | Medium |
FS — Functional Specification
| ID | Function | Implementation |
|---|---|---|
| FS-001 | CLI execution | Support execution modes: demo mode without arguments and production mode input.csv output.json. |
| FS-002 | CSV import | Read input.csv in UTF-8/CSV-compatible format and validate header and expected columns. |
| FS-003 | Schema validation | Check mandatory fields, column count, unknown key fields and empty mandatory values. |
| FS-004 | Type conversion | Convert numeric, flag and text values; invalid format is recorded as a row-level error. |
| FS-005 | Domain rule engine | Apply rules for Hemagglutination Titer Checker, including critical limits from the description and approved specification. |
| FS-006 | Status aggregation | Produce final status: FAIL for critical failure, WARNING for non-critical deviation, PASS for conformance. |
| FS-007 | JSON export | Write output.json with detailed checks, source values, warnings, failures and critical findings. |
| FS-008 | Audit support | Keep result structure suitable for review, deviation investigation and calculation reproduction. |
| FS-009 | Integration contract | Support the scenario LIMS/ELN/MES → input.csv → utility → output.json → portal/admin review. |
| FS-010 | Error handling | Return explicit messages for missing file, empty CSV, invalid schema, output write failure and invalid format. |
Example output.json
{
"utilityId": "hemagglutinationtiterchecker",
"utilityFolder": "HemagglutinationTiterChecker",
"package": "Vet",
"overallStatus": "PASS|WARNING|FAIL",
"sourceFile": "input.csv",
"processedAtUtc": "2026-06-10T00:00:00Z",
"checks": [
{
"parameter": "BatchNumber",
"value": "HA-FLU-2026-001",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-001"
},
{
"parameter": "ProductName",
"value": "Influenza A/H1N1 Antigen",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-002"
},
{
"parameter": "MeasuredHATiter",
"value": "256",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-003"
},
{
"parameter": "MinRequiredHATiter",
"value": "128",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-004"
},
{
"parameter": "RBC_Type",
"value": "1",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-005"
},
{
"parameter": "ControlSerumTiter",
"value": "64",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-006"
},
{
"parameter": "ExpectedControlTiter",
"value": "64",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-007"
},
{
"parameter": "AgglutinationPattern",
"value": "Normal",
"status": "PASS|WARNING|FAIL",
"message": "Deterministic rule-based check result",
"ruleReference": "FS-RULE-008"
}
],
"criticalFindings": [],
"warnings": [],
"audit": {
"inputHash": "sha256:<calculated at runtime>",
"rulesVersion": "<utility executable version>",
"documentation": "HemagglutinationTiterChecker.documentation.html"
}
}
Traceability matrix
| URS | FS | Test | Evidence |
|---|---|---|---|
| URS-001 | FS-001, FS-002 | OQ-001 | Verify execution and import of valid input.csv. |
| URS-002 | FS-005, FS-006 | OQ-004 | Repeat the same dataset and compare output.json. |
| URS-003 | FS-003, FS-004, FS-010 | OQ-002, OQ-003 | Verify missing columns and invalid types. |
| URS-004 | FS-005, FS-006 | OQ-004, PQ-001 | Verify critical deviations on real/boundary data. |
| URS-005 | FS-007, FS-009 | OQ-005 | Verify JSON schema and downstream-system suitability. |
| URS-006 | FS-008 | OQ-006 | Verify identifiers and audit metadata. |
| URS-007 | FS-008, FS-010 | IQ-001, OQ-007 | Verify documentation completeness and control evidence. |
| URS-008 | FS-005, FS-008 | PQ-002 | Verify review workflow and no replacement of QA decision. |
IQ/OQ/PQ test scenarios
| ID | Scenario | Expected result |
|---|---|---|
| IQ-001 | Verify executable, input.csv, documentation and checksum availability. | Delivery set is complete; version is recorded. |
| OQ-001 | Valid sample row from input.csv. | PASS or acceptable WARNING according to rules. |
| OQ-002 | Remove a mandatory CSV column. | Schema error or FAIL with missing-column reference. |
| OQ-003 | Place a non-numeric value into a numeric field. | Type-conversion error with row/field reference. |
| OQ-004 | Set a critical parameter outside the limit. | FAIL and critical finding. |
| OQ-005 | Verify output.json structure. | All mandatory sections are present and JSON is valid. |
| OQ-006 | Verify batch/sample traceability. | Input and result identifiers match. |
| PQ-001 | Verify 3–5 real user batches/samples. | Result is confirmed by QC/QA review. |
| PQ-002 | Verify deviation workflow and manual QA decision. | Utility supports review but does not replace approved decision. |
QA/QC and change control
- Do not rename columns without updating validator, documentation and test set.
- Retain
input.csv,output.json, executable version and checksum. - Before production use, perform IQ/OQ/PQ or equivalent CSV/CSA verification.
- Critical limits shall be verified against the approved specification, registration dossier and local SOPs.
- The utility provides structured QC decision support; final release decision remains with QA/QP and approved procedures.
Included in packages
Infectious Diseases QC Suite
QC utility package for infectious diseases: antibacterial, antiviral, antifungal and antiparasitic products, microbiology, sterility, endotoxins, viral safety and vaccine release checks.
OpenVet — Veterinary QC Utilities
Vet is designed for veterinary pharmaceuticals and vaccines: adjuvants, antigens, autogenous vaccines, aquaculture, feed/premixes, antimicrobial and antiparasitic products, sterility and batch release.
Open