MUCalculatorVerifier

MU Calculator Verifier

activity brachytherapy dosimetry source calibration TG-43

MU Calculator Verifier — Independent Monitor Unit Check (AAPM TG-40)

ℹ️  The utility performs independent manual calculation of Monitor Units (MU) based on basic dosimetric parameters and compares result with Treatment Planning System (TPS) data.
ℹ️  Uses simplified formula: MU = Dose / (Output * TPR/TMR * Wedge * Tray).
ℹ️  Processing: only the FIRST record in input.csv file.
⚠️  Critical for safety! Data entry errors in TPS (wrong field, forgotten wedge) are frequent causes of incidents. Independent check is the last line of defense.

Usage:
  MUCalculatorVerifier.exe                            → demo mode
  MUCalculatorVerifier.exe input.csv output.json      → check data (first record only)

Input format:
PatientID,FieldName,PrescribedDoseGy,DepthCm,FieldSizeX,FieldSizeY,SSD,TPR_TMR,OutputFactor,WedgeFactor,TrayFactor,TPS_MU

Example (dose in Gy, sizes in cm):
PT-2026-BREAST-01,R_Tang_Med,2.0,1.5,10.0,15.0,100.0,0.985,1.02,0.75,1.0,268.5

— WHY IS THIS NEEDED?
Before each RT course, medical physicist must verify MU independently from TPS.
• Human factor: operator might select wrong wedge profile or field size.
• Algorithmic errors: TPS might incorrectly account for heterogeneities in simple cases.
• Comparison reveals discrepancies >2-3% requiring investigation.
• Automation speeds up routine check, eliminating calculator and paper tables.
⚠️ CRITICAL:
• Tolerance on difference: typically ≤2% (Warning), ≤3% (Fail).
• Factors (Output, TMR) must be taken from current measured tables for specific linac.
• Presence of wedges, blocks, or trays must be accounted by multipliers (<1.0).
Critical parameters:
• MU Difference: <2% (OK), 2-3% (Warning), >3% (Fail)
• Factor input accuracy: impact is directly linear
• SSD/TMR accounting: correct calculation methodology selected
⚠️ Note: Utility automatically calculates expected MU and compares with plan. If discrepancy >3%, issues FAIL status with recommendation to prohibit treatment. Result includes status and bilingual recommendation (RU/EN).

input.csv

PatientID,FieldName,PrescribedDoseGy,DepthCm,FieldSizeX,FieldSizeY,SSD,TPR_TMR,OutputFactor,WedgeFactor,TrayFactor,TPS_MU
PT-2026-BREAST-01,R_Tang_Med,2.0,1.5,10.0,15.0,100.0,0.985,1.02,0.75,1.0,268.5

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: MUCalculatorVerifierAPI / object: MU Calculator VerifierCategory: Radiation physics

1. Scope

The MU Calculator Verifier utility is used for MU Calculator Verifier. 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: Radiation physics

Tags: activity, brachytherapy, dosimetry, source calibration, TG-43

2. Execution modes

MUCalculatorVerifier.exe                            → demo mode
MUCalculatorVerifier.exe input.csv output.json      → check data (first record only)

3. Key controlled areas

pH and physicochemical parameters
activity, decay and radiochemical purity

4. Domain limits and critical parameters

⚠️ Critical for safety! Data entry errors in TPS (wrong field, forgotten wedge) are frequent causes of incidents. Independent check is the last line of defense.
Comparison reveals discrepancies >2-3% requiring investigation.
⚠️ CRITICAL:
Tolerance on difference: typically ≤2% (Warning), ≤3% (Fail).
Factors (Output, TMR) must be taken from current measured tables for specific linac.
Presence of wedges, blocks, or trays must be accounted by multipliers (<1.0).
Critical parameters:
MU Difference: <2% (OK), 2-3% (Warning), >3% (Fail)
Factor input accuracy: impact is directly linear
SSD/TMR accounting: correct calculation methodology selected
⚠️ Note: Utility automatically calculates expected MU and compares with plan. If discrepancy >3%, issues FAIL status with recommendation to prohibit treatment. Result includes status and bilingual recommendation (RU/EN).

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 MU Calculator Verifier 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: 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	`PatientID`	text	as specified	Patient ID	`PT-2026-BREAST-01`	mandatory value; format and acceptability are checked by the utility
2	`FieldName`	text	as specified	Field Name	`R_Tang_Med`	mandatory value; format and acceptability are checked by the utility
3	`PrescribedDoseGy`	decimal	as specified	Prescribed Dose Gy	`2.0`	mandatory numeric value; rule comparison is performed by the utility
4	`DepthCm`	decimal	as specified	Depth Cm	`1.5`	mandatory numeric value; rule comparison is performed by the utility
5	`FieldSizeX`	decimal	as specified	Field Size X	`10.0`	mandatory numeric value; rule comparison is performed by the utility
6	`FieldSizeY`	decimal	as specified	Field Size Y	`15.0`	mandatory numeric value; rule comparison is performed by the utility
7	`SSD`	decimal	as specified	SSD	`100.0`	mandatory numeric value; rule comparison is performed by the utility
8	`TPR_TMR`	decimal	as specified	TPR TMR	`0.985`	mandatory numeric value; rule comparison is performed by the utility
9	`OutputFactor`	decimal	as specified	Output Factor	`1.02`	mandatory numeric value; rule comparison is performed by the utility
10	`WedgeFactor`	decimal	as specified	Wedge Factor	`0.75`	mandatory numeric value; rule comparison is performed by the utility
11	`TrayFactor`	decimal	as specified	Tray Factor	`1.0`	mandatory numeric value; rule comparison is performed by the utility
12	`TPS_MU`	decimal	as specified	TPS MU	`268.5`	mandatory numeric value; rule comparison is performed by the utility

CSV example

PatientID,FieldName,PrescribedDoseGy,DepthCm,FieldSizeX,FieldSizeY,SSD,TPR_TMR,OutputFactor,WedgeFactor,TrayFactor,TPS_MU
PT-2026-BREAST-01,R_Tang_Med,2.0,1.5,10.0,15.0,100.0,0.985,1.02,0.75,1.0,268.5

7. FS — functional specification

ID	Function	Implementation description
FS-001	CLI entry point	The executable `MUCalculatorVerifier.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 MU Calculator Verifier, 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": "MUCalculatorVerifier",
  "api": "MU Calculator Verifier",
  "batchNumber": "",
  "overallStatus": "PASS|WARNING|FAIL",
  "checkedAtUtc": "2026-05-18T00:00:00Z",
  "checks": [
    {
      "parameter": "PatientID",
      "value": "PT-2026-BREAST-01",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "FieldName",
      "value": "R_Tang_Med",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "PrescribedDoseGy",
      "value": "2.0",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "DepthCm",
      "value": "1.5",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "FieldSizeX",
      "value": "10.0",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "FieldSizeY",
      "value": "15.0",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "SSD",
      "value": "100.0",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "TPR_TMR",
      "value": "0.985",
      "unit": "as specified",
      "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.

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

Radiation Physics QC Suite

Utilities for activity, dosimetry, brachytherapy sources, small-field corrections and TG-43 parameters.

Open

RPH use case: PET scanner state, gamma camera and radiation physics

The linked medical-device/radiation-physics layer: PET detector QC, normalization, AC map, cross-calibration, TOF, gamma-camera uniformity, source strength and staff dose.

Open

RPH workflow: dosimetry and therapy planning

Activity planning, absorbed dose, organ dose, lung shunt, preplanning and therapy verification.

Open

RPH workflow: instruments, devices and radiation safety

PET/gamma-camera state, calibration, detector QC, energy window, TOF, shielding and radiation safety.

Open