search

WUSTL-ClinicalDev / ClinicalTemplateReader

A public API to interpret Eclipse plan templates, objective templates, and clinical protocols and utilize the interpretation in the generation of automated plans.
Other
22 stars 3 forks source link

Varian Image Server #1

Open remsky opened 1 year ago

remsky commented 1 year ago

Hi, I'm having trouble determining what filepath/location to use for the "Varian Image Server" in your readme.txt example.

Is this an external/additional tool? Or a location created by Varians as a part of eclipse, and if so, can you provide any tips on locating it? Thanks for any help

mattcschmidt commented 1 year ago

Hi Remsky, I've seen another clinic that had issues with this before. Is your relative path of your clinical protocols different from \\va_data$\programdata\vision\tempaltes? I had another clinic, their path included va_data1$ instead of va_data$ and we had to come up with a custom fix for them. Are you using the code from nuget or did you download it from github (i.e. should I fix the nuget package to include this or can I show you how to fix it or should I provide an update) :D Thanks for reaching out.

remsky commented 1 year ago

No problem, thanks for writing this tool, I expect it to be very useful.

It was downloaded via github, and I'm actually not sure, and have been looking through the file structure and haven't been able to find the clinical protocols or va_data folder themselves (e.g. the value to set "server" in the Execute method to)

mattcschmidt commented 1 year ago

Do you have access to you VSP (Platform portal) you should be able to tell where the image file server is from there? Once you login to that web portal, you should be able to go to Administrative Service --> System Configurations and from there you can select Data Directories, that should have the path to your image server. Please let me know if you can find that and that is where the va_data$ share should be located. Keep in mind, Va_data$ is a hidden share, so even if you can find the server, you would have to manually type that into the address bar to access it.

Also, alllllll of your patient information lives in there, so be very careful when exploring that area. One wrong click and you negatively impact your users' ability to access patients across the board.