PETCTCrossCalibrationChecker

FS — Functional Specification

1. Run PETCTCrossCalibrationChecker.exe in demonstration mode or with input.csv output.json arguments.
2. Read UTF-8 CSV and map columns to the data contract.
3. Convert values to the expected types and validate mandatory fields.
4. Perform calculations and rule checks for “PET/CT and Dose-Calibrator Cross-Calibration”.
5. Create individual checks and derive the overall status from the worst result.
6. Write machine-readable output.json; populate errors when a valid calculation cannot be produced.

input.csv example

StudyID,PhantomType,DoseCalibratorActivityMBq,CalibrationTime,ScanStartTime,MeasuredActivityConcentrationBQ_per_ML,PhantomVolumeML,PatientWeightKg,DecayCorrectedDoseMBq
QC-PET-2026-001,NEMA_Image_Quality,100.0,2026-07-22 08:00:00,2026-07-22 09:00:00,28500.0,3000.0,0.0,0.0
QC-PET-2026-002,Jaszczak_Photon,50.0,2026-07-22 10:00:00,2026-07-22 10:30:00,14000.0,1500.0,0.0,0.0
QC-PET-2026-003,Cylinder_Uniform,80.0,2026-07-22 12:00:00,2026-07-22 13:00:00,20000.0,4000.0,0.0,0.0

Minimum output.json structure

{
  "utility": "PETCTCrossCalibrationChecker",
  "source": "input.csv",
  "status": "PASS|WARNING|FAIL",
  "derivedValues": {},
  "checks": [
    {
      "parameter": "example",
      "value": 0,
      "limit": "configured profile",
      "status": "PASS",
      "message": "criterion satisfied"
    }
  ],
  "errors": []
}

Minimum OQ scenarios

• A row within the approved profile shall return PASS.
• A non-critical limit violation shall return WARNING or a review status.
• A critical violation shall return FAIL or the applicable operational decision.
• A missing column, invalid type or impossible date shall populate errors and shall not return PASS.

Before operational use

• Reconcile formulas and limits with manufacturer documentation and the approved SOP.
• Fix the scanner model, software version and profile version.
• After an executable, formula or profile change, repeat affected tests.
• Retain the source CSV and JSON result together.