You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prostate gland measurements should always be part of the report. Those can be done as 3 uni-dimensional measurements, or as volumetric segmentation. It probably makes sense to have prostate gland measurement as a separate finding, instead of keeping it alongside the lesion findings. Once measurements are done, volume should be calculated automatically and listed somewhere next to the finding. If the measurement is done using uni-dimensional measurements, volume should be calculated using "the formula for a conventional prolate ellipse; (maximum AP diameter) x (maximum transverse diameter) x (maximum longitudinal diameter) x 0.52" (quoting from the PI-RADS guidelines).
Prostate gland measurements: widget should be similar to findings widget with the constraint that there is only one entry "Prostate" is allowed.
Two possible annotation types:
linear: guided workflow where the user gets instructions which measure to create one at a time until all three orientations are done
volumetric: DeepInfer and as a fallback use SurfaceCut/VolumeClip
The text was updated successfully, but these errors were encountered:
Prostate gland measurements should always be part of the report. Those can be done as 3 uni-dimensional measurements, or as volumetric segmentation. It probably makes sense to have prostate gland measurement as a separate finding, instead of keeping it alongside the lesion findings. Once measurements are done, volume should be calculated automatically and listed somewhere next to the finding. If the measurement is done using uni-dimensional measurements, volume should be calculated using "the formula for a conventional prolate ellipse; (maximum AP diameter) x (maximum transverse diameter) x (maximum longitudinal diameter) x 0.52" (quoting from the PI-RADS guidelines).
Two possible annotation types:
The text was updated successfully, but these errors were encountered: