PETACMapIntegrityChecker

FS — Functional Specification

1. Run PETACMapIntegrityChecker.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 Attenuation-Correction Map Integrity Check”.
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,PatientID,MinHU,MaxHU,MeanAirHU,MeanBoneHU,TruncationArtifactsCount,HasMetalImplants,BodyWidthCM,ScannerFOV_CM,InvalidVoxelsCount
PET-CT-2026-001,PAT-AC-001,-1020,2500,-998,850,0,false,45,70,0
PET-CT-2026-002,PAT-AC-002,-1024,3100,-950,900,2,false,75,70,0
PET-CT-2026-003,PAT-AC-003,-1020,2000,-1005,800,0,true,50,70,5

Minimum output.json structure

{
  "utility": "PETACMapIntegrityChecker",
  "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.