MifepristoneQualityChecker

1. Scope

The Mifepristone Quality Checker utility is used for Mifepristone. 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: Contraceptives

Tags: assay, biologics, contraceptives, fixed-dose combinations, heavy metals, hormones, impurities, medical gases, residual solvents, solid dosage

2. Execution modes

MifepristoneQualityChecker.exe                            → demo mode (console output)
MifepristoneQualityChecker.exe input.csv output.json      → evaluate your data

3. Key controlled areas

• assay / content
• purity and impurities
• residual solvents
• heavy metals / elemental impurities
• pH and physicochemical parameters

5. URS — user requirements

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.

CSV example

BatchNumber,AssayPercent,SpecificRotation,MeltingPoint,UV240_300Ratio,Impurity11BetaHydroxy,Impurity17AlphaEpimer,TotalImpurities,LossOnDrying,HeavyMetals,ResidualSolvents,EthanolPPM,AcetonePPM,ClarityNTU,ColorAPHA
MIFE-2026-001,99.5,-50.0,197.5,2.0,0.2,0.1,0.4,0.3,5,1500,800,500,2,30

7. FS — functional specification

8. output.json contract

The output file must be suitable for automated processing, audit review and correlation with the source input.csv row.

{
  "utility": "MifepristoneQualityChecker",
  "api": "Mifepristone",
  "batchNumber": "MIFE-2026-001",
  "overallStatus": "PASS|WARNING|FAIL",
  "checkedAtUtc": "2026-05-18T00:00:00Z",
  "checks": [
    {
      "parameter": "BatchNumber",
      "value": "MIFE-2026-001",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "AssayPercent",
      "value": "99.5",
      "unit": "%",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "SpecificRotation",
      "value": "-50.0",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "MeltingPoint",
      "value": "197.5",
      "unit": "°C",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "UV240_300Ratio",
      "value": "2.0",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Impurity11BetaHydroxy",
      "value": "0.2",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Impurity17AlphaEpimer",
      "value": "0.1",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "TotalImpurities",
      "value": "0.4",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    }
  ],
  "criticalFindings": [],
  "sourceFile": "input.csv"
}

9. OQ/PQ test scenarios

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.