Software-assisted dosimetry in peptide receptor radionuclide therapy with (177)Lutetium-DOTATATE for various imaging scenarios

In peptide receptor radionuclide therapy (PRRT) of patients with neuroendocrine neoplasias (NENs), intratherapeutic dosimetry is mandatory for organs at risk (e.g. kidneys) and tumours. We evaluated commercial dosimetry software (Dosimetry Toolkit) using varying imaging scenarios, based on planar and/or tomographic data, regarding the differences in calculated organ/tumour doses and the use for clinical routines. A total of 16 consecutive patients with NENs treated by PRRT with Lu-177-DOTATATE were retrospectively analysed. Single-photon emission computed tomography (SPECT)/Iow-dose computed tomography (CT) of the thorax and abdomen and whole body (WB) scintigraphy were acquired up to 7 days p.i. (at a maximum of five imaging time points). Different dosimetric scenarios were evaluated: (1) a multi-SPECT-CT scenario using SPECT/CT only;(2) a planar scenario using WB scintigraphy only;and (3) a hybrid scenario using WB scintigraphy in combination with a single SPECT/low-dose CT. Absorbed doses for the kidneys, liver, spleen, lungs, bladder wall and tumours were calculated and compared for the three different scenarios. The mean absorbed dose for the kidneys estimated by the multi-SPECT-CT, the planar and the hybrid scenario was 0.5 +/- 0.2 Sv GBq(-1), 0.8 +/- 0.4 Sv GBq(-1) and 0.6 +/- 0.3 Sv GBq(-1), respectively. The absorbed dose for the residual organs was estimated higher by the planar scenario compared to the multi-SPECT-CT or hybrid scenario. The mean absorbed tumour doses were 2.6 +/- 1.5 Gy GBq(-1) for the multi-SPECT-CT, 3.1 +/- 2.2 Gy GBq(-1) for the hybrid scenario and 5.3 +/- 6.3 Gy GBq(-1) for the planar scenario. SPECT-based dosimetry methods determined significantly lower kidney doses than the WB scintigraphy-based method. Dosimetry based completely on SPECT data is time-consuming and tedious. Approaches combining SPECT/CT and WB scintigraphy have the potential to ensure compromise between accuracy and user-friendliness