# 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:** 1\
**Showing post:** 5

<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.

---

_[View the full topic](https://discourse.slicer.org/t/2023-09-26-weekly-meeting/31894)._