StaffDoseTracker

Staff Dose Tracker

activity brachytherapy dosimetry source calibration TG-43

Staff Dose Tracker — Occupational Dose Monitoring (NRB/ICRP)

ℹ️ The utility analyzes individual occupational doses, comparing them with established limits (quarterly and annual) per NRB-99/2009 and ICRP recommendations.
ℹ️ Identifies hazardous trends (consecutive dose increases) and approaching limits.
ℹ️ Processing: only the FIRST record in input.csv file.
⚠️ Critical for radiation safety! Exceeding dose limits leads to legal liability and health risks for staff.

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

Input format:
EmployeeID,FullName,Category,DoseQuarterMsv,DoseYearMsv,LimitQuarterMsv,LimitYearMsv,ConsecutiveIncreases

Example (Category A, limit 20 mSv/year):
EMP-2026-042,Ivanov I.I.,A,4.8,12.5,5.0,20.0,2

— WHY IS THIS NEEDED?
Radiation Safety Officer must monthly monitor doses of all Group A employees.
• Exceeding quarterly limit (typically 1/4 of annual) requires immediate intervention.
• Accumulation >75% of annual limit requires work schedule revision.
• Dose increase for several consecutive months may indicate procedure violations or shielding failure.
• Automation eliminates risk of missing critical values in paper logs.
⚠️ CRITICAL:
• Annual limit for Group A: 20 mSv (average over 5 years, max 50 mSv in single year).
• Quarterly limit: typically 1/4 of annual (5 mSv).
• Trend: 3 months increase — warning, 5 months — critical situation.
• Category B (staff in supervised area): limits significantly lower (1/10 of Group A).
Critical parameters:
• Usage %: >90% quarter (Warn), >100% (Fail)
• Usage %: >75% year (Warn), >100% (Fail)
• Trend: ≥3 months increase (Warn), ≥5 months (Fail)
⚠️ Note: Utility automatically calculates limit usage percentage and assigns FAIL status on any exceedance. Result includes status and bilingual recommendation (RU/EN).

input.csv

EmployeeID,FullName,Category,DoseQuarterMsv,DoseYearMsv,LimitQuarterMsv,LimitYearMsv,ConsecutiveIncreases
EMP-2026-042,Ivanov I.I.,A,4.8,12.5,5.0,20.0,2

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: StaffDoseTrackerAPI / object: Staff Dose TrackerCategory: Radiation physics

1. Scope

The Staff Dose Tracker utility is used for Staff Dose Tracker. 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

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

3. Key controlled areas

activity, decay and radiochemical purity

4. Domain limits and critical parameters

⚠️ Critical for radiation safety! Exceeding dose limits leads to legal liability and health risks for staff.
Accumulation >75% of annual limit requires work schedule revision.
⚠️ CRITICAL:
Annual limit for Group A: 20 mSv (average over 5 years, max 50 mSv in single year).
Quarterly limit: typically 1/4 of annual (5 mSv).
Trend: 3 months increase — warning, 5 months — critical situation.
Category B (staff in supervised area): limits significantly lower (1/10 of Group A).
Critical parameters:
Usage %: >90% quarter (Warn), >100% (Fail)
Usage %: >75% year (Warn), >100% (Fail)
Trend: ≥3 months increase (Warn), ≥5 months (Fail)
⚠️ Note: Utility automatically calculates limit usage percentage and assigns FAIL status on any exceedance. 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 Staff Dose Tracker 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: 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	`EmployeeID`	text	as specified	Employee ID	`EMP-2026-042`	mandatory value; format and acceptability are checked by the utility
2	`FullName`	text	as specified	Full Name	`Ivanov I.I.`	mandatory value; format and acceptability are checked by the utility
3	`Category`	text	as specified	Category	`A`	mandatory value; format and acceptability are checked by the utility
4	`DoseQuarterMsv`	decimal	as specified	Dose Quarter Msv	`4.8`	mandatory numeric value; rule comparison is performed by the utility
5	`DoseYearMsv`	decimal	as specified	Dose Year Msv	`12.5`	mandatory numeric value; rule comparison is performed by the utility
6	`LimitQuarterMsv`	decimal	as specified	Limit Quarter Msv	`5.0`	mandatory numeric value; rule comparison is performed by the utility
7	`LimitYearMsv`	decimal	as specified	Limit Year Msv	`20.0`	mandatory numeric value; rule comparison is performed by the utility
8	`ConsecutiveIncreases`	decimal	as specified	Consecutive Increases	`2`	mandatory numeric value; rule comparison is performed by the utility

CSV example

EmployeeID,FullName,Category,DoseQuarterMsv,DoseYearMsv,LimitQuarterMsv,LimitYearMsv,ConsecutiveIncreases
EMP-2026-042,Ivanov I.I.,A,4.8,12.5,5.0,20.0,2

7. FS — functional specification

ID	Function	Implementation description
FS-001	CLI entry point	The executable `StaffDoseTracker.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 Staff Dose Tracker, 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": "StaffDoseTracker",
  "api": "Staff Dose Tracker",
  "batchNumber": "",
  "overallStatus": "PASS|WARNING|FAIL",
  "checkedAtUtc": "2026-05-18T00:00:00Z",
  "checks": [
    {
      "parameter": "EmployeeID",
      "value": "EMP-2026-042",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "FullName",
      "value": "Ivanov I.I.",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Category",
      "value": "A",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "DoseQuarterMsv",
      "value": "4.8",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "DoseYearMsv",
      "value": "12.5",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "LimitQuarterMsv",
      "value": "5.0",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "LimitYearMsv",
      "value": "20.0",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "ConsecutiveIncreases",
      "value": "2",
      "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

Ophthalmology QC Suite

QC package for ophthalmology: eye drops, antiglaucoma agents, antibiotics, sterile solutions, osmolality, pH, particles and preservatives.

Open

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

RPH workflow: stability, storage, decay and waste

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

Open