OmalizumabQualityChecker

Omalizumab

antivirals API biologics endotoxins essential medicines global market impurities injectables

Omalizumab Quality Checker — Biologic Drug (Anti-IgE mAb) (Ph. Eur., USP)

ℹ️ The utility checks aggregates, potency, glycosylation, HCP, sterility, endotoxins, particles.
ℹ️ Does not use machine learning — rule-based logic only.
⚠️ CRITICAL! Aggregates ≤1.0%. Sterility mandatory. Endotoxins ≤1.0 EU/mg!

Usage:
OmalizumabQualityChecker.exe → demo mode
OmalizumabQualityChecker.exe input.csv output.json → evaluate data

Input format:
BatchNumber,Protein_Concentration_mgPerMl,Potency_Percent,pH_Value,Osmolality_mOsm_kg,Aggregate_Percent_SEC,Fragment_Percent_SEC,Acidic_Variants_Percent_IEC,Basic_Variants_Percent_IEC,Glycosylation_G0F_Percent,Host_Cell_Protein_ppm,Residual_DNA_ngPerMl,Protein_A_Leaching_ngPerMl,SterilityTest,Endotoxin_EU_per_mg,Subvisible_Particles_2_10_um,Subvisible_Particles_10_25_um,Subvisible_Particles_gt_25_um,Appearance_Score

Example:
OMA-BIO-2026-001,125.5,96.5,6.0,290,0.4,0.25,18.5,6.5,25.0,16,1.4,2.9,0,0.11,1080,108,7,0

— WHY IS THIS NEEDED?
Omalizumab — fully human IgG1κ monoclonal antibody against IgE for asthma and chronic urticaria treatment:
• Administered subcutaneously, so sterility and endotoxin requirements are maximum. Risk of anaphylactic reactions requires special aggregate control.
• Aggregates (HMW): Critical parameter. Aggregates can cause severe immune responses, including anaphylaxis. Limit is strict (≤1.0%).
• Potency: Measured by ability to bind IgE. Deviation leads to treatment inefficacy.
• Glycosylation: Sugar profile is critical for antibody stability and pharmacokinetics.
• Process Impurities: HCP (CHO cell proteins), DNA, and Protein A must be removed to trace levels.
• Particles: Subvisible particles are dangerous for injection, so control is strict.
⚠️ CRITICAL:
• Protein Concentration: 120.0–130.0 mg/mL (for 125 mg/mL form)
• Potency: 80–120% of standard
• Aggregates: ≤ 1.0%
• Glycosylation (G0F etc.): Within specified range (e.g., 10-40%)
• HCP: ≤ 50 ppm
• DNA: ≤ 10 ng/mL
• Sterility: No growth
• Endotoxins: ≤ 1.0 EU/mg
• Particles >25 µm: ≤ 60 counts/mL
• Appearance: Clear, colorless
️ Note: Utility accounts for therapeutic antibody specifics. Aggregate control is critical due to anaphylaxis risk with anti-IgE agents. Sterility is absolute requirement. Deamidation (acidic peaks) controlled as stability marker during storage.

input.csv

BatchNumber,Protein_Concentration_mgPerMl,Potency_Percent,pH_Value,Osmolality_mOsm_kg,Aggregate_Percent_SEC,Fragment_Percent_SEC,Acidic_Variants_Percent_IEC,Basic_Variants_Percent_IEC,Glycosylation_G0F_Percent,Host_Cell_Protein_ppm,Residual_DNA_ngPerMl,Protein_A_Leaching_ngPerMl,SterilityTest,Endotoxin_EU_per_mg,Subvisible_Particles_2_10_um,Subvisible_Particles_10_25_um,Subvisible_Particles_gt_25_um,Appearance_Score
OMA-BIO-2026-001,125.5,96.5,6.0,290,0.4,0.25,18.5,6.5,25.0,16,1.4,2.9,0,0.11,1080,108,7,0

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.

Utility: OmalizumabQualityCheckerAPI / object: OmalizumabCategory: Global API expansion

1. Scope

The Omalizumab Quality Checker utility is used for Omalizumab. 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: Global API expansion

Tags: antivirals, API, biologics, endotoxins, essential medicines, global market, impurities, injectables, oncology, sterility

2. Execution modes

OmalizumabQualityChecker.exe                            → demo mode
OmalizumabQualityChecker.exe input.csv output.json      → evaluate data

3. Key controlled areas

assay / content
microbiology and pathogens
pH and physicochemical parameters

4. Domain limits and critical parameters

⚠️ CRITICAL! Aggregates ≤1.0%. Sterility mandatory. Endotoxins ≤1.0 EU/mg!
Aggregates (HMW): Critical parameter. Aggregates can cause severe immune responses, including anaphylaxis. Limit is strict (≤1.0%).
⚠️ CRITICAL:
Protein Concentration: 120.0–130.0 mg/mL (for 125 mg/mL form)
Potency: 80–120% of standard
Aggregates: ≤ 1.0%
Glycosylation (G0F etc.): Within specified range (e.g., 10-40%)
HCP: ≤ 50 ppm
DNA: ≤ 10 ng/mL
Sterility: No growth
Endotoxins: ≤ 1.0 EU/mg
Particles >25 µm: ≤ 60 counts/mL
Appearance: Clear, colorless
️ Note: Utility accounts for therapeutic antibody specifics. Aggregate control is critical due to anaphylaxis risk with anti-IgE agents. Sterility is absolute requirement. Deamidation (acidic peaks) controlled as stability marker during storage.

Limits stated in the description must be verified against the current approved specification, pharmacopoeial monograph and registration dossier before production use.

5. URS — user requirements

ID	Requirement	Criticality	Acceptance criterion
URS-001	The system shall accept an `input.csv` file for Omalizumab 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: assay / content, 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	`OMA-BIO-2026-001`	mandatory field; used for batch/lot traceability
2	`Protein_Concentration_mgPerMl`	decimal	mg/ml	Protein Concentration mg per Ml	`125.5`	numeric value; compared with assay/purity limit from specification or method
3	`Potency_Percent`	decimal	%	Potency %	`96.5`	mandatory numeric value; rule comparison is performed by the utility
4	`pH_Value`	decimal	pH	p H Value	`6.0`	mandatory numeric value; rule comparison is performed by the utility
5	`Osmolality_mOsm_kg`	decimal	mOsm/kg	Osmolality m Osm kg	`290`	mandatory numeric value; rule comparison is performed by the utility
6	`Aggregate_Percent_SEC`	decimal	%	Aggregate % SEC	`0.4`	mandatory numeric value; rule comparison is performed by the utility
7	`Fragment_Percent_SEC`	decimal	%	Fragment % SEC	`0.25`	mandatory numeric value; rule comparison is performed by the utility
8	`Acidic_Variants_Percent_IEC`	decimal	%	Acidic Variants % IEC	`18.5`	mandatory numeric value; rule comparison is performed by the utility
9	`Basic_Variants_Percent_IEC`	decimal	%	Basic Variants % IEC	`6.5`	mandatory numeric value; rule comparison is performed by the utility
10	`Glycosylation_G0F_Percent`	decimal	%	Glycosylation G0 F %	`25.0`	mandatory numeric value; rule comparison is performed by the utility
11	`Host_Cell_Protein_ppm`	decimal	ppm	Host Cell Protein ppm	`16`	mandatory numeric value; rule comparison is performed by the utility
12	`Residual_DNA_ngPerMl`	decimal	as specified	Residual DNA ng per Ml	`1.4`	mandatory numeric value; rule comparison is performed by the utility
13	`Protein_A_Leaching_ngPerMl`	decimal	as specified	Protein A Leaching ng per Ml	`2.9`	mandatory numeric value; rule comparison is performed by the utility
14	`SterilityTest`	boolean / flag	0/1	Sterility Test	`0`	valid flag required; prohibited organisms and growth are normally expected as 0 / absent
15	`Endotoxin_EU_per_mg`	decimal	EU/ml	Endotoxin EU per mg	`0.11`	numeric value; critical safety attribute compared with endotoxin limit
16	`Subvisible_Particles_2_10_um`	decimal	µm	Subvisible Particles 2 10 um	`1080`	mandatory numeric value; rule comparison is performed by the utility
17	`Subvisible_Particles_10_25_um`	decimal	µm	Subvisible Particles 10 25 um	`108`	mandatory numeric value; rule comparison is performed by the utility
18	`Subvisible_Particles_gt_25_um`	decimal	µm	Subvisible Particles gt 25 um	`7`	mandatory numeric value; rule comparison is performed by the utility
19	`Appearance_Score`	decimal	as specified	Appearance Score	`0`	mandatory numeric value; rule comparison is performed by the utility

CSV example

BatchNumber,Protein_Concentration_mgPerMl,Potency_Percent,pH_Value,Osmolality_mOsm_kg,Aggregate_Percent_SEC,Fragment_Percent_SEC,Acidic_Variants_Percent_IEC,Basic_Variants_Percent_IEC,Glycosylation_G0F_Percent,Host_Cell_Protein_ppm,Residual_DNA_ngPerMl,Protein_A_Leaching_ngPerMl,SterilityTest,Endotoxin_EU_per_mg,Subvisible_Particles_2_10_um,Subvisible_Particles_10_25_um,Subvisible_Particles_gt_25_um,Appearance_Score
OMA-BIO-2026-001,125.5,96.5,6.0,290,0.4,0.25,18.5,6.5,25.0,16,1.4,2.9,0,0.11,1080,108,7,0

7. FS — functional specification

ID	Function	Implementation description
FS-001	CLI entry point	The executable `OmalizumabQualityChecker.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 Omalizumab, 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": "OmalizumabQualityChecker",
  "api": "Omalizumab",
  "batchNumber": "OMA-BIO-2026-001",
  "overallStatus": "PASS|WARNING|FAIL",
  "checkedAtUtc": "2026-05-18T00:00:00Z",
  "checks": [
    {
      "parameter": "BatchNumber",
      "value": "OMA-BIO-2026-001",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Protein_Concentration_mgPerMl",
      "value": "125.5",
      "unit": "mg/ml",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Potency_Percent",
      "value": "96.5",
      "unit": "%",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "pH_Value",
      "value": "6.0",
      "unit": "pH",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Osmolality_mOsm_kg",
      "value": "290",
      "unit": "mOsm/kg",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Aggregate_Percent_SEC",
      "value": "0.4",
      "unit": "%",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Fragment_Percent_SEC",
      "value": "0.25",
      "unit": "%",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Acidic_Variants_Percent_IEC",
      "value": "18.5",
      "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

Australia: national essential medicines QC package

QC utility package aligned with the country essential/reimbursed medicines list analogue and cross-checked against WHO EML. Only utilities already present in the portal are included; the package is a validation/discussion starting map, not an official registry copy.

OmalizumabQualityChecker

input.csv

1. Scope

2. Execution modes

3. Key controlled areas

4. Domain limits and critical parameters

5. URS — user requirements

6. input.csv data contract

CSV example

7. FS — functional specification

8. output.json contract

9. OQ/PQ test scenarios

10. QA/QC, CSV and change control

Included in packages

Australia: national essential medicines QC package

Biopharmaceuticals Core QC Suite

Biopharmaceuticals Extended QC Suite

Canada: national essential medicines QC package

France: national essential medicines QC package

Germany: national essential medicines QC package

Immunology QC Suite

Italy: national essential medicines QC package

Japan: national essential medicines QC package

Russia: national essential medicines QC package

Saudi Arabia: national essential medicines QC package

South Korea: national essential medicines QC package

United Kingdom: national essential medicines QC package

United States: national essential medicines QC package

World API Extension QC Suite