# 2023.09.26 Weekly Meeting

**URL:** <https://discourse.slicer.org/t/2023-09-26-weekly-meeting/31894>\
**Category:** Weekly meetings\
**Created:** [September 25, 2023, 5:36pm UTC](https://discourse.slicer.org/t/2023-09-26-weekly-meeting/31894 "2023-09-25T17:36:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sam\_Horvath](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/sam_horvath/32/3092_2.png) [@Sam\_Horvath](https://discourse.slicer.org/u/Sam_Horvath)\
**Post date:** [September 25, 2023, 5:36pm UTC](https://discourse.slicer.org/t/2023-09-26-weekly-meeting/31894/1 "2023-09-25T17:36:37Z")

</div>

Tomorrow, we will be having our next weekly hangout at **10:00 AM ET until 11:00 AM ET**

Anyone is welcome to join to ask questions at [https://bit.ly/slicer-googlemeet-hosted-by-kitware](https://bit.ly/slicer-googlemeet-hosted-by-kitware)

* * *

> **Weekly Meeting**
>
> **Starts:** September 26, 2023, 10:00am (America/New\_York)\
> **Link:** <https://bit.ly/slicer-googlemeet-hosted-by-kitware>

**Agenda:**

- [Extension dashboard status](https://slicer.cdash.org/index.php?project=SlicerPreview#!#Extensions-Nightly)

Please post to this thread to put a topic on the agenda! We will try to prioritize agenda items during the meeting.

* * *

Thanks  
Sam and J-Christophe

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [September 25, 2023, 5:44pm UTC](https://discourse.slicer.org/t/2023-09-26-weekly-meeting/31894/2 "2023-09-25T17:44:18Z")

</div>

We should talk over the [mac extension packaging issues](https://discourse.slicer.org/t/new-extensions-can-not-work-on-slicer-5-4-0-on-macos/31535).

---

<div class="post-metadata">

**Author:** ![tom.birdsong](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/tom.birdsong/32/11860_2.png) [@tom.birdsong](https://discourse.slicer.org/u/tom.birdsong)\
**Post date:** [September 25, 2023, 5:45pm UTC](https://discourse.slicer.org/t/2023-09-26-weekly-meeting/31894/3 "2023-09-25T17:45:36Z")

</div>

I propose two (unrelated) agenda topics:

- Considerations for extending DICOMweb STOW-RS support in 3D Slicer
- Standardizing scene data representation with [OpenUSD](https://openusd.org/release/index.html)
  - Following [VTK Discourse discussion](https://discourse.vtk.org/t/openusd-support/12198)

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [September 26, 2023, 1:21pm UTC](https://discourse.slicer.org/t/2023-09-26-weekly-meeting/31894/4 "2023-09-26T13:21:40Z")

</div>

FYI, Slicer already supports STOW-RS - Slicer can push DICOM information objects to a DICOMweb server: right-click on the item to send in the DICOM browser and choose “Send to DICOM server” and DICOMweb protocol.

Also note that a completely new, patient-centered (typical in clinical use) visual DICOM browser (with real-time thumbnail display, simultaneous local and remote content display) is almost ready (see development branch [here](https://github.com/Punzo/CTK/tree/addDICOMVisualNavigation)). It uses backgrund tasks for all local and remote data parsing, sending, and receiving. It currently uses classic DIMSE protocol, but it is designed to be extensible with DICOMweb protocol. The main question is if we want to add DICOMweb networking classes to CTK in C++ (this would be ideal, but it seems hat DCMTK does not support DICOMweb; so we would need to look for another C++ implementation or implement it ourselves) or add wrapper for a Python DICOMweb toolkit (but it may complicate multithreading and adds Python dependency for a core feature).

---

<div class="post-metadata">

**Author:** ![tom.birdsong](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/tom.birdsong/32/11860_2.png) [@tom.birdsong](https://discourse.slicer.org/u/tom.birdsong)\
**Post date:** [September 26, 2023, 1:32pm UTC](https://discourse.slicer.org/t/2023-09-26-weekly-meeting/31894/5 "2023-09-26T13:32:57Z")

</div>

> FYI, Slicer already supports STOW-RS

Thanks @lassoan , and yes, very helpful to see this laid out in your earlier [Discourse post](https://discourse.slicer.org/t/new-dicomweb-features-launch-slicer-from-web-browser-and-download-upload-data-sets-to-the-cloud-using-dicomweb/17811) as well!

On my side I’d like to understand current capabilities and obstacles and possibly extend existing STOW-RS support for the following limited features:

- Authentication for STOW-RS communication, possibly adding or extending UI elements for this
- Uniform DICOM series UID and series instance numbering for generating DICOM instances within a single Slicer session

Happy to chat further this morning.