EpoetinBetaQualityChecker

Epoetin Beta

API assay biologics biosimilars endotoxins fixed-dose combinations generics impurities

Epoetin Beta Quality Checker — Biologic Drug (Erythropoietin Beta) (Ph. Eur., USP, ICH Q6B)

ℹ️ The utility checks specific activity, aggregates (PRCA risk), high sialylation, HCP, DNA, sterility.
ℹ️ Does not use machine learning — rule-based logic only.
⚠️ CRITICAL! Aggregates ≤2%, Activity 80k-120k IU/mg, Acidic Variants 45-75%, Sterility!

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

Input format:
BatchNumber,Protein_Concentration_mgPerMl,Specific_Activity_IU_per_mg,Total_Potency_IU_per_ml,pH_Value,Osmolality_mOsm_kg,Aggregate_Percent_SEC,Fragment_Percent_SEC,Acidic_Variants_Percent_IEC,Basic_Variants_Percent_IEC,Main_Peak_Percent_IEC,Host_Cell_Protein_ppm,Residual_DNA_ngPerMl,Subvisible_Particles_2_10_um,Subvisible_Particles_10_25_um,Subvisible_Particles_gt_25_um,SterilityTest,Endotoxin_EU_ml

Example:
EPO-BETA-2026-001,1.0,98000,4000,6.6,295,0.7,0.4,60.0,8.0,32.0,35,1.8,2800,320,10,0,0.02

— WHY IS THIS NEEDED?
Epoetin beta — recombinant human erythropoietin (produced in CHO cells):
• Differs from alfa-form by higher sialic acid content (higher % of acidic variants), providing slightly longer half-life.
• Specific Activity (IU/mg): Key efficacy parameter. Determined by bioassay.
• Aggregates (HMW): Critical safety parameter. Risk of Pure Red Cell Aplasia (PRCA) if aggregates present.
• Glycosylation (Acidic Variants): Beta form characterized by shift towards more acidic isoforms (45-75%). Low value may indicate manufacturing issue or instability.
• Process Impurities: HCP and DNA must be removed to trace levels.
• Sterility and Endotoxins: Absolutely mandatory.
⚠️ CRITICAL:
• Specific Activity: 80,000 – 120,000 IU/mg
• Aggregates: ≤ 2.0% (strict limit due to PRCA risk)
• Acidic Variants (IEC): 45–75% (indicator of high sialylation typical for Beta)
• HCP: ≤ 100 ppm
• DNA: ≤ 10 ng/mL
• Sterility and Endotoxins: Mandatory
• Particles >25 µm: ≤ 60 counts/mL
⚠️ Note: Utility adapted for epoetin beta specifics, setting higher lower limits for acidic variants compared to alfa-form. Aggregate control remains priority #1. Glycosylation profile directly affects pharmacokinetics: insufficient sialylation leads to rapid clearance and lack of therapeutic effect in anemic patient.

input.csv

BatchNumber,Protein_Concentration_mgPerMl,Specific_Activity_IU_per_mg,Total_Potency_IU_per_ml,pH_Value,Osmolality_mOsm_kg,Aggregate_Percent_SEC,Fragment_Percent_SEC,Acidic_Variants_Percent_IEC,Basic_Variants_Percent_IEC,Main_Peak_Percent_IEC,Host_Cell_Protein_ppm,Residual_DNA_ngPerMl,Subvisible_Particles_2_10_um,Subvisible_Particles_10_25_um,Subvisible_Particles_gt_25_um,SterilityTest,Endotoxin_EU_ml
EPO-BETA-2026-001,1.0,98000,4000,6.6,295,0.7,0.4,60.0,8.0,32.0,35,1.8,2800,320,10,0,0.02

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: EpoetinBetaQualityCheckerAPI / object: Epoetin BetaCategory: Global API

1. Scope

The Epoetin Beta Quality Checker utility is used for Epoetin Beta. 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

Tags: API, assay, biologics, biosimilars, endotoxins, fixed-dose combinations, generics, impurities, market map, sterility

2. Execution modes

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

3. Key controlled areas

assay / content
microbiology and pathogens
pH and physicochemical parameters
activity, decay and radiochemical purity

4. Domain limits and critical parameters

⚠️ CRITICAL! Aggregates ≤2%, Activity 80k-120k IU/mg, Acidic Variants 45-75%, Sterility!
⚠️ CRITICAL:
Specific Activity: 80,000 – 120,000 IU/mg
Aggregates: ≤ 2.0% (strict limit due to PRCA risk)
Acidic Variants (IEC): 45–75% (indicator of high sialylation typical for Beta)
HCP: ≤ 100 ppm
DNA: ≤ 10 ng/mL
Sterility and Endotoxins: Mandatory
Particles >25 µm: ≤ 60 counts/mL
⚠️ Note: Utility adapted for epoetin beta specifics, setting higher lower limits for acidic variants compared to alfa-form. Aggregate control remains priority #1. Glycosylation profile directly affects pharmacokinetics: insufficient sialylation leads to rapid clearance and lack of therapeutic effect in anemic patient.

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 Epoetin Beta 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, activity, decay and radiochemical purity.	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	`EPO-BETA-2026-001`	mandatory field; used for batch/lot traceability
2	`Protein_Concentration_mgPerMl`	decimal	mg/ml	Protein Concentration mg per Ml	`1.0`	numeric value; compared with assay/purity limit from specification or method
3	`Specific_Activity_IU_per_mg`	decimal	as specified	Specific Activity IU per mg	`98000`	mandatory numeric value; rule comparison is performed by the utility
4	`Total_Potency_IU_per_ml`	decimal	IU/ml	Total Potency IU per ml	`4000`	mandatory numeric value; rule comparison is performed by the utility
5	`pH_Value`	decimal	pH	p H Value	`6.6`	mandatory numeric value; rule comparison is performed by the utility
6	`Osmolality_mOsm_kg`	decimal	mOsm/kg	Osmolality m Osm kg	`295`	mandatory numeric value; rule comparison is performed by the utility
7	`Aggregate_Percent_SEC`	decimal	%	Aggregate % SEC	`0.7`	mandatory numeric value; rule comparison is performed by the utility
8	`Fragment_Percent_SEC`	decimal	%	Fragment % SEC	`0.4`	mandatory numeric value; rule comparison is performed by the utility
9	`Acidic_Variants_Percent_IEC`	decimal	%	Acidic Variants % IEC	`60.0`	mandatory numeric value; rule comparison is performed by the utility
10	`Basic_Variants_Percent_IEC`	decimal	%	Basic Variants % IEC	`8.0`	mandatory numeric value; rule comparison is performed by the utility
11	`Main_Peak_Percent_IEC`	decimal	%	Main Peak % IEC	`32.0`	mandatory numeric value; rule comparison is performed by the utility
12	`Host_Cell_Protein_ppm`	decimal	ppm	Host Cell Protein ppm	`35`	mandatory numeric value; rule comparison is performed by the utility
13	`Residual_DNA_ngPerMl`	decimal	as specified	Residual DNA ng per Ml	`1.8`	mandatory numeric value; rule comparison is performed by the utility
14	`Subvisible_Particles_2_10_um`	decimal	µm	Subvisible Particles 2 10 um	`2800`	mandatory numeric value; rule comparison is performed by the utility
15	`Subvisible_Particles_10_25_um`	decimal	µm	Subvisible Particles 10 25 um	`320`	mandatory numeric value; rule comparison is performed by the utility
16	`Subvisible_Particles_gt_25_um`	decimal	µm	Subvisible Particles gt 25 um	`10`	mandatory numeric value; rule comparison is performed by the utility
17	`SterilityTest`	boolean / flag	0/1	Sterility Test	`0`	valid flag required; prohibited organisms and growth are normally expected as 0 / absent
18	`Endotoxin_EU_ml`	decimal	as specified	Endotoxin EU ml	`0.02`	numeric value; critical safety attribute compared with endotoxin limit

CSV example

BatchNumber,Protein_Concentration_mgPerMl,Specific_Activity_IU_per_mg,Total_Potency_IU_per_ml,pH_Value,Osmolality_mOsm_kg,Aggregate_Percent_SEC,Fragment_Percent_SEC,Acidic_Variants_Percent_IEC,Basic_Variants_Percent_IEC,Main_Peak_Percent_IEC,Host_Cell_Protein_ppm,Residual_DNA_ngPerMl,Subvisible_Particles_2_10_um,Subvisible_Particles_10_25_um,Subvisible_Particles_gt_25_um,SterilityTest,Endotoxin_EU_ml
EPO-BETA-2026-001,1.0,98000,4000,6.6,295,0.7,0.4,60.0,8.0,32.0,35,1.8,2800,320,10,0,0.02

7. FS — functional specification

ID	Function	Implementation description
FS-001	CLI entry point	The executable `EpoetinBetaQualityChecker.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 Epoetin Beta, 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": "EpoetinBetaQualityChecker",
  "api": "Epoetin Beta",
  "batchNumber": "EPO-BETA-2026-001",
  "overallStatus": "PASS|WARNING|FAIL",
  "checkedAtUtc": "2026-05-18T00:00:00Z",
  "checks": [
    {
      "parameter": "BatchNumber",
      "value": "EPO-BETA-2026-001",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Protein_Concentration_mgPerMl",
      "value": "1.0",
      "unit": "mg/ml",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Specific_Activity_IU_per_mg",
      "value": "98000",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Total_Potency_IU_per_ml",
      "value": "4000",
      "unit": "IU/ml",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "pH_Value",
      "value": "6.6",
      "unit": "pH",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Osmolality_mOsm_kg",
      "value": "295",
      "unit": "mOsm/kg",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Aggregate_Percent_SEC",
      "value": "0.7",
      "unit": "%",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Fragment_Percent_SEC",
      "value": "0.4",
      "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.
TC-008	Incorrect activity, reference time or radiochemical purity	FAIL/WARNING is produced with calculation traceability.

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

Biopharmaceuticals Core QC Suite

Focused QC utility package for biologic products: HCP, mAbs, biosimilars, proteins/peptides, sterility, endotoxins and key release checks.

Open

Biopharmaceuticals Extended QC Suite

Extended QC utility coverage for mAbs, biosimilars, proteins, insulins, vaccines, mRNA/LNP, HCP, sterile release, microbiology, water, cleanroom and stability workflows.

Open

Global API & Biosimilars QC Suite

Package for high-demand global APIs, generics and biosimilars, including fixed-dose combinations and biological products.

Open

Immunology QC Suite

QC utility package for immunology: monoclonal antibodies, biosimilars, immunomodulators, immunosuppressants, ELISA/SPR, HCP, protein characterization, sterility and pyrogen/release checks.

Open