Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Dicom archive] Module should use site-based permissions #6981

Open
nicolasbrossard opened this issue Sep 4, 2020 · 5 comments
Open

[Dicom archive] Module should use site-based permissions #6981

nicolasbrossard opened this issue Sep 4, 2020 · 5 comments
Assignees
Labels
Category: Bug PR or issue that aims to report or fix a bug Module: dicom_archive PR or issue related to dicom_archive module

Comments

@nicolasbrossard
Copy link
Contributor

Describe the bug
Currently, if you have access to the DICOM archive module, you can see all DICOM archives, even those not associated to your site(s). It would make more sense if the DICOM archive module used site-based permissions, just like the MRI violations and imaging browser modules.

@nicolasbrossard nicolasbrossard added the Category: Bug PR or issue that aims to report or fix a bug label Sep 4, 2020
@nicolasbrossard nicolasbrossard added this to the 24.0.0 milestone Sep 4, 2020
@nicolasbrossard nicolasbrossard changed the title Dicom archive permissions should be site-based [Dicom archive] Module should use site-based permissions Sep 4, 2020
@cmadjar
Copy link
Collaborator

cmadjar commented Sep 17, 2020

@nicolasbrossard I think this is by design that you can see all DICOM archives. The reason for it is in case an archive is not associated to a site (aka - invalid patient name that does not allow to associate the study to a candidate/visit).

If I remember correctly, I believe the site-based permissions were added at some point but then some DICOM studies did not show in the DICOM archive module because of the lack of site associated to the study and then it was removed but I am not entirely sure that my memory is fully correct though ;).

@nicolasbrossard
Copy link
Contributor Author

nicolasbrossard commented Oct 2, 2020

@cmadjar The way I implemented this in the MRI violations module is that if a violation is not associated to any site, everybody can see it. Maybe we can do the same thing here to be consistent?

@cmadjar
Copy link
Collaborator

cmadjar commented Oct 2, 2020

@nicolasbrossard smart :). Is that something you can work on eventually? Otherwise we'll find someone else to do it. Just let us know.

@nicolasbrossard
Copy link
Contributor Author

@cmadjar Yeah, I can do this.

@ridz1208 ridz1208 removed this from the 24.0.0 milestone May 12, 2022
@regisoc regisoc mentioned this issue Apr 4, 2023
14 tasks
@nicolasbrossard
Copy link
Contributor Author

This still needs to be done as of 2024SEP18.

@driusan driusan added the Module: dicom_archive PR or issue related to dicom_archive module label Jan 21, 2025
@ridz1208 ridz1208 assigned ridz1208 and unassigned nicolasbrossard Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Bug PR or issue that aims to report or fix a bug Module: dicom_archive PR or issue related to dicom_archive module
Projects
None yet
Development

No branches or pull requests

4 participants