Hi everyone,
I keep seeing excellent AI integrations land in Slicer as one-off extensions -
the torchvulkan / GPU TotalSegmentator thread, MONAI-Label, per-model
segmentation extensions. Each of them re-solves the same plumbing: run a model,
get a result, show it in the scene. I would like to propose using the standard
that already exists for exactly this plumbing - DICOMweb UPS-RS (PS3.18 section 11).
The loop:
1. The user selects data in Slicer and triggers a task.
2. Slicer, as the Task Requester, creates a UPS workitem on the DICOMweb origin (POST /workitems), naming the study/series as the input.
3. Any Task Performer - TotalSegmentator, MONAI, NVIDIA, clinfer, whatever -
claims the workitem (Change State to IN PROGRESS), runs, writes its result
back as DICOM SEG / SR / PR via STOW-RS, and marks it COMPLETED.
4. Slicer subscribes (PS3.18 11.10/11.11, N-EVENT-REPORT over the event channel), sees COMPLETED, and loads the result over WADO-RS into the scene.
No vendor-specific glue anywhere: the workitem is the contract. The same
performer works from Weasis, from OHIF, from Slicer, unchanged.
This is not hypothetical. The full loop already runs end-to-end against an open
DICOMweb origin (Clarus) with an open performer (clinfer), driven from the
Weasis viewer - screenshots in this Weasis PR comment:
Question for the Slicer community: would a UPS-RS User Agent extension for Slicer be useful - a worklist module that does the create / claim / subscribe / load loop, so any performer plugs in through one standard interface instead of each shipping its own workflow? Would the MONAI-Label / TotalSegmentator / NVIDIA AIAA folks see value in a common task contract?
I am happy to write the extension (Python, standard-only) and test it against Clarus and dcm4chee-arc as the origins, keeping it dependency-minimal.