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

Viewer Integration Docs say 'you need to add the four following properties', but I see 3 #597

Open
sscotti opened this issue Oct 7, 2024 · 1 comment

Comments

@sscotti
Copy link

sscotti commented Oct 7, 2024

Describe the bug. What happened?

See this page for the documentation: WEASIS Integration

It mentions the settings below, but says there are 4 properties.

IID_PATIENT_URL=weasis://$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "patientID={{patientID}}" --query-ext "&includedefaults=false" -H "Authorization: Bearer {{access_token}}"
IID_STUDY_URL=weasis://$dicom:rs --url "{{qidoBaseURL}}{{qidoBasePath}}" -r "studyUID={{studyUID}}" --query-ext "&includedefaults=false" -H "Authorization: Bearer {{access_token}}"
IID_URL_TARGET=_self

What version of Weasis are you running?

It says at least dcm4chee-arc-light 5.22.2 and Weasis 3.6.0.

On which system the problem occurs?

Linux

Relevant log output

There is no associated log output.  I am trying to configure DCM4CHEE to use my local install if WEASIS on a MacBook Pro running a Dockerized version of DCM4CHEE on the MBP.  After making those changes in the web interface (not the .env file), the Viewer button does appear in the GUI, and clicking on that launches WEASIS, but I must have something not quite correct because nothing happens after WEASIS is launched.  I mostly point out that the docs say 4, while I see 3 properties.  And BTW, when I tried setting those in the .env file they did not seem to get set, but that is probably some issue on my end,

Additional contextual elements

No response

@nroduit
Copy link
Owner

nroduit commented Oct 8, 2024

Yes, that will certainly change over time. However, you can suggest corrections in the documentation using the edit button in the top right-hand corner.

For this type of problem, it's usually enough to look at the logs to find the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants