SourceStrengthLogger

1. Scope

The Source Strength Logger utility is used for Source Strength Logger. 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

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

3. Key controlled areas

• pH and physicochemical parameters
• activity, decay and radiochemical purity
• stability / expiry

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

SourceID,Radionuclide,InitialActivity,CalibrationDate,CheckDate,MeasuredActivity,CumulativeHoursUsed,MaxAllowedHours,ExpiryDate
IR192-HDR-9988,Ir192,370.0,2026-01-01T00:00:00Z,2026-05-01T10:00:00Z,115.0,3900,4000,2026-05-20T00:00:00Z

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": "SourceStrengthLogger",
  "api": "Source Strength Logger",
  "batchNumber": "",
  "overallStatus": "PASS|WARNING|FAIL",
  "checkedAtUtc": "2026-05-18T00:00:00Z",
  "checks": [
    {
      "parameter": "SourceID",
      "value": "IR192-HDR-9988",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "Radionuclide",
      "value": "Ir192",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "InitialActivity",
      "value": "370.0",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "CalibrationDate",
      "value": "2026-01-01T00:00:00Z",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "CheckDate",
      "value": "2026-05-01T10:00:00Z",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "MeasuredActivity",
      "value": "115.0",
      "unit": "as specified",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "CumulativeHoursUsed",
      "value": "3900",
      "unit": "h",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result"
    },
    {
      "parameter": "MaxAllowedHours",
      "value": "4000",
      "unit": "h",
      "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.