TRTDosimetryCalculator

TRT Dosimetry Calculator

activity brachytherapy dosimetry radiopharma source calibration TG-43

TRT Dosimetry Calculator — Theranostics Dosimetry (MIRD/EANM)

ℹ️ The utility calculates absorbed dose in target organs and OARs based on planar/SPECT imaging data (MIRD method).
ℹ️ Computes effective half-life (Teff), cumulated activity, and dose per cycle/GBq.
ℹ️ Processing: only the FIRST record in input.csv file.
⚠️ Critical for personalized therapy! Allows adapting next cycle activity to patient-specific kinetics, avoiding toxicity (kidneys, bone marrow).

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

Input format:
PatientID,Radionuclide,TargetOrgan,AdministeredActivityMBq,TimePoint1Hr,Activity1MBq,TimePoint2Hr,Activity2MBq,TimePoint3Hr,Activity3MBq,MassKg,SValueGyPerBqS

Example (kidneys, Lu-177, 3 points):
PT-2026-NET-07,Lu177,Kidneys,7400.0,4.0,250.0,24.0,180.0,72.0,90.0,0.30,4.5e-06

— WHY IS THIS NEEDED?
In Lu-177/Ac-225 therapy, clearance kinetics vary significantly between patients.
• Standard fixed dose may be toxic for patients with slow clearance.
• Calculating Teff and integral activity allows precise dose determination in Gy.
• Comparison with limits (e.g., 23 Gy for kidneys) decides fate of next cycle.
• Automation eliminates manual curve integration errors.
⚠️ CRITICAL:
• Minimum 3 measurement points for reliable washout phase approximation.
• S-coefficients must match organ mass and nuclide (OLINDA/IDAC).
• Error in time input distorts Teff exponentially.
• Dose limits: Kidneys (~23 Gy cumulative), Bone Marrow (~2 Gy/cycle).
Critical parameters:
• Effective Half-Life (Teff): must be < physical half-life
• Absorbed Dose: comparison with toxicity threshold
• S-Value: correctness of units (Gy/Bq·s)
⚠️ Note: Utility warns about anomalously high Teff or dose. Result includes status (PASS/WARNING/FAIL) and recommendation for activity adjustment in RU/EN.

input.csv

PatientID,Radionuclide,TargetOrgan,AdministeredActivityMBq,TimePoint1Hr,Activity1MBq,TimePoint2Hr,Activity2MBq,TimePoint3Hr,Activity3MBq,MassKg,SValueGyPerBqS
PT-2026-NET-07,Lu177,Kidneys,7400.0,4.0,250.0,24.0,180.0,72.0,90.0,0.30,4.5e-06

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: TRTDosimetryCalculatorAPI / object: TRT Dosimetry CalculatorCategory: Radiation physics

1. Scope

The TRT Dosimetry Calculator utility is used for TRT Dosimetry Calculator. 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, radiopharma, source calibration, TG-43

2. Execution modes

TRTDosimetryCalculator.exe                            → demo mode
TRTDosimetryCalculator.exe input.csv output.json      → calculate 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 personalized therapy! Allows adapting next cycle activity to patient-specific kinetics, avoiding toxicity (kidneys, bone marrow).
⚠️ CRITICAL:
Minimum 3 measurement points for reliable washout phase approximation.
S-coefficients must match organ mass and nuclide (OLINDA/IDAC).
Error in time input distorts Teff exponentially.
Dose limits: Kidneys (~23 Gy cumulative), Bone Marrow (~2 Gy/cycle).
Critical parameters:
Effective Half-Life (Teff): must be < physical half-life
Absorbed Dose: comparison with toxicity threshold
S-Value: correctness of units (Gy/Bq·s)
⚠️ Note: Utility warns about anomalously high Teff or dose. Result includes status (PASS/WARNING/FAIL) and recommendation for activity adjustment in 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 TRT Dosimetry Calculator 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-NET-07`	mandatory value; format and acceptability are checked by the utility
2	`Radionuclide`	text	as specified	Radionuclide	`Lu177`	mandatory value; format and acceptability are checked by the utility
3	`TargetOrgan`	text	as specified	Target Organ	`Kidneys`	mandatory value; format and acceptability are checked by the utility
4	`AdministeredActivityMBq`	decimal	MBq	Administered Activity MBq	`7400.0`	mandatory numeric value; rule comparison is performed by the utility
5	`TimePoint1Hr`	decimal	as specified	Time Point1 Hr	`4.0`	mandatory numeric value; rule comparison is performed by the utility
6	`Activity1MBq`	decimal	MBq	Activity1 MBq	`250.0`	mandatory numeric value; rule comparison is performed by the utility
7	`TimePoint2Hr`	decimal	as specified	Time Point2 Hr	`24.0`	mandatory numeric value; rule comparison is performed by the utility
8	`Activity2MBq`	decimal	MBq	Activity2 MBq	`180.0`	mandatory numeric value; rule comparison is performed by the utility
9	`TimePoint3Hr`	decimal	as specified	Time Point3 Hr	`72.0`	mandatory numeric value; rule comparison is performed by the utility
10	`Activity3MBq`	decimal	MBq	Activity3 MBq	`90.0`	mandatory numeric value; rule comparison is performed by the utility
11	`MassKg`	decimal	as specified	Mass Kg	`0.30`	mandatory numeric value; rule comparison is performed by the utility
12	`SValueGyPerBqS`	decimal	as specified	SValue Gy per Bq S	`4.5e-06`	mandatory numeric value; rule comparison is performed by the utility

CSV example

PatientID,Radionuclide,TargetOrgan,AdministeredActivityMBq,TimePoint1Hr,Activity1MBq,TimePoint2Hr,Activity2MBq,TimePoint3Hr,Activity3MBq,MassKg,SValueGyPerBqS
PT-2026-NET-07,Lu177,Kidneys,7400.0,4.0,250.0,24.0,180.0,72.0,90.0,0.30,4.5e-06

7. FS — functional specification

ID	Function	Implementation description
FS-001	CLI entry point	The executable `TRTDosimetryCalculator.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 TRT Dosimetry Calculator, 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": "TRTDosimetryCalculator",
  "api": "TRT Dosimetry Calculator",
  "batchNumber": "",
  "overallStatus": "PASS|WARNING|FAIL",
  "checkedAtUtc": "2026-05-18T00:00:00Z",
  "checks": [
    {
      "parameter": "PatientID",
      "value": "PT-2026-NET-07",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Radionuclide",
      "value": "Lu177",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "TargetOrgan",
      "value": "Kidneys",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "AdministeredActivityMBq",
      "value": "7400.0",
      "unit": "MBq",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "TimePoint1Hr",
      "value": "4.0",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Activity1MBq",
      "value": "250.0",
      "unit": "MBq",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "TimePoint2Hr",
      "value": "24.0",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Activity2MBq",
      "value": "180.0",
      "unit": "MBq",
      "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-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

Radiation Physics QC Suite

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

Open

Radiology QC Suite

QC package for radiology and diagnostic imaging: radiopharmaceuticals, PET/SPECT, contrast media, iodinated and gadolinium products, plus particle, sterility and endotoxin checks.

Open

RPH organ/system: bone and musculoskeletal

Bone scintigraphy, MDP/PYP, marrow, bone-pain palliation, skeletal metastases and radiosynovectomy.

Open

RPH organ/system: oncology and theranostics

Tumour imaging, PSMA/FAPI/receptor tracers, immuno-PET, targeted radionuclide therapy and radioembolization.

Open

RPH organ/system: renal and urinary

Renography, GFR/ERPF, renal uptake, DMSA/MAG3/DTPA and bladder-related workflows.

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: imaging QC and quantitative interpretation

Acquisition, uptake, clearance, perfusion, transit, ejection fraction, segmentation and quantitative imaging.

Open

RPH workflow: instruments, devices and radiation safety

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

Open

RPH workflow: stability, storage, decay and waste

Kinetic stability, shelf life, decay correction, expiry, storage, trend and radioactive waste.

Open