PreservativeContentChecker

Preservative Content

Vet veterinary veterinary vaccines animal health adjuvants aquaculture batch release CSV→JSON

Utility description: Preservative Content

Preservative Content Checker — Control of Preservative Content

ℹ️ Utility assesses quantitative content of antimicrobial preservatives in multi-dose dosage forms (eye drops, injections, nasal sprays) according to Ph. Eur. and USP requirements:
• Quantitative Determination: Usually by HPLC or GC.
• Specification Limits: Typically 90-110% of declared amount.
• pH Control: Critical as activity of many preservatives (e.g., benzoic acid) depends on dissociation degree.
• Preservative Types: Benzyl alcohol, Phenol, Metacresol, Benzalkonium chloride, Thimerosal, etc.

⚠️ CRITICAL:
• Content below lower limit does not ensure protection against microbial growth upon multiple use of the vial.
• Exceeding upper limit can lead to local or systemic toxic effects (irritation, hemolysis).
• Preservatives may sorb onto packaging materials (rubber, plastic), reducing their concentration over time.

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

Input format:
BatchNumber,ProductName,PreservativeName,MeasuredContent_mg_per_ml,TargetContent_mg_per_ml,MinLimit_mg_per_ml,MaxLimit_mg_per_ml,pH

Example:
PRES-001,Insulin,Metacresol,2.8,3.0,2.7,3.3,7.2

— WHY IS THIS NEEDED?
Multi-dose containers are at risk of contamination every time they are opened.
Preservatives are necessary to ensure microbiological cleanliness throughout shelf life after opening.
Quantitative control guarantees that preservative dose is sufficient for efficacy but safe for the patient.

⚠️ CRITICAL:
• Efficacy (PET): Quantitative content does not always correlate with efficacy. Antimicrobial Preservative Effectiveness Test (Ph. Eur. 5.1.3) is additionally performed.
• Compatibility: Preservatives may interact with API or excipients (e.g., oxidation).
• Assay Method: Must be specific and separate preservative from product peaks.
• Stability: Preservative concentration must remain within specification until end of shelf life.

Key features:
• Verification of content compliance with specification
• Deviation from target value control
• Consideration of pH effect on stability/activity
• Generation of reports for QC and LIMS LabWare
• Compliance with GMP and Pharmacopoeia requirements

Critical parameters:
• Preservative Content: 90–110% of declared
• pH: In optimal range for given preservative type

💡 Usage tips:
1. Standards: Use certified reference standards of specific preservative.
2. Sample Preparation: Protein precipitation may be required before supernatant analysis for protein drugs.
3. Adsorption: Consider potential preservative loss on filters during sample preparation.
4. Interference: Check for absence of product peak overlap with preservative peak in chromatogram.
5. Trends: Track preservative concentration decrease in batches with different storage times.

⚠️ Note: For some modern biologics, preservative-free formulations are preferred using single-dose containers. But for classic pharmaceuticals, this control remains mandatory.

input.csv

BatchNumber,ProductName,PreservativeName,MeasuredContent_mg_per_ml,TargetContent_mg_per_ml,MinLimit_mg_per_ml,MaxLimit_mg_per_ml,pH
PRES-2026-MDV-001,Insulin Glargine,Metacresol,2.8,3.0,2.7,3.3,7.2
PRES-2026-EYE-002,Timolol Eye Drops,Benzalkonium Chloride,0.10,0.10,0.09,0.11,6.5
PRES-2026-FAIL-003,Vaccine Multi-dose,Phenol,4.0,5.0,4.5,5.5,7.0

URS & FS — User Requirements and Functional Specification

This document describes the controlled interface and behaviour of PreservativeContentChecker for Preservative Content Checker.

Domain limits URS input.csv FS IQ/OQ/PQ

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 quantitative content of antimicrobial preservatives in multi-dose dosage forms (eye drops, injections, nasal sprays) according to Ph. Eur. and USP requirements:
• Specification Limits: Typically 90-110% of declared amount.
• pH Control: Critical as activity of many preservatives (e.g., benzoic acid) depends on dissociation degree.
⚠️ CRITICAL:
• Content below lower limit does not ensure protection against microbial growth upon multiple use of the vial.
• Exceeding upper limit can lead to local or systemic toxic effects (irritation, hemolysis).
BatchNumber,ProductName,PreservativeName,MeasuredContent_mg_per_ml,TargetContent_mg_per_ml,MinLimit_mg_per_ml,MaxLimit_mg_per_ml,pH
• Efficacy (PET): Quantitative content does not always correlate with efficacy. Antimicrobial Preservative Effectiveness Test (Ph. Eur. 5.1.3) is additionally performed.
• Assay Method: Must be specific and separate preservative from product peaks.
• Stability: Preservative concentration must remain within specification until end of shelf life.
• Compliance with GMP and Pharmacopoeia requirements
Critical parameters:

URS — User Requirements Specification

ID	Requirement	Criticality	Acceptance criterion
URS-001	The utility shall accept an input.csv file for Preservative Content 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	`PRES-2026-MDV-001`	Batch or lot identifier used for traceability.
2	`ProductName`	string / controlled vocabulary	`Insulin Glargine`	Product or dosage-form name under evaluation.
3	`PreservativeName`	string / controlled vocabulary	`Metacresol`	Controlled input parameter for deterministic QC rules.
4	`MeasuredContent_mg_per_ml`	decimal	`2.8`	Volume/dose used for load, limit or release calculation.
5	`TargetContent_mg_per_ml`	decimal	`3.0`	Volume/dose used for load, limit or release calculation.
6	`MinLimit_mg_per_ml`	decimal	`2.7`	Volume/dose used for load, limit or release calculation.
7	`MaxLimit_mg_per_ml`	decimal	`3.3`	Volume/dose used for load, limit or release calculation.
8	`pH`	decimal	`7.2`	pH; parameter relevant to stability, compatibility and batch suitability.

BatchNumber,ProductName,PreservativeName,MeasuredContent_mg_per_ml,TargetContent_mg_per_ml,MinLimit_mg_per_ml,MaxLimit_mg_per_ml,pH
PRES-2026-MDV-001,Insulin Glargine,Metacresol,2.8,3.0,2.7,3.3,7.2
PRES-2026-EYE-002,Timolol Eye Drops,Benzalkonium Chloride,0.10,0.10,0.09,0.11,6.5
PRES-2026-FAIL-003,Vaccine Multi-dose,Phenol,4.0,5.0,4.5,5.5,7.0

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	`PreservativeName`	The field shall match an approved dictionary or accepted string representation.	High
VR-004	`MeasuredContent_mg_per_ml`	The field shall match an approved dictionary or accepted string representation.	Medium
VR-005	`TargetContent_mg_per_ml`	The field shall match an approved dictionary or accepted string representation.	Medium
VR-006	`MinLimit_mg_per_ml`	The field shall match an approved dictionary or accepted string representation.	Medium
VR-007	`MaxLimit_mg_per_ml`	The field shall match an approved dictionary or accepted string representation.	Medium
VR-008	`pH`	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 Preservative Content 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": "preservativecontentchecker",
  "utilityFolder": "PreservativeContentChecker",
  "package": "Vet",
  "overallStatus": "PASS|WARNING|FAIL",
  "sourceFile": "input.csv",
  "processedAtUtc": "2026-06-10T00:00:00Z",
  "checks": [
    {
      "parameter": "BatchNumber",
      "value": "PRES-2026-MDV-001",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-001"
    },
    {
      "parameter": "ProductName",
      "value": "Insulin Glargine",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-002"
    },
    {
      "parameter": "PreservativeName",
      "value": "Metacresol",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-003"
    },
    {
      "parameter": "MeasuredContent_mg_per_ml",
      "value": "2.8",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-004"
    },
    {
      "parameter": "TargetContent_mg_per_ml",
      "value": "3.0",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-005"
    },
    {
      "parameter": "MinLimit_mg_per_ml",
      "value": "2.7",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-006"
    },
    {
      "parameter": "MaxLimit_mg_per_ml",
      "value": "3.3",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-007"
    },
    {
      "parameter": "pH",
      "value": "7.2",
      "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": "PreservativeContentChecker.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

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

Immunology QC Suite

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

Open

Vet — 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