WADO-RS Rendered response

210 views
Skip to first unread message

Samuel Choi

unread,
Aug 22, 2022, 7:06:37 AM8/22/22
to Orthanc Users
Hello,

We are working on implementing WADO-RS and have some questions.

Referring to the DICOM Standard Part 18, 2022b, WADO-RS Rendered/Thumbnail resource payloads are described as follows:

10.4.3.3.3 Rendered Resource Payload​
The payload for a Rendered Resource (see Section 10.4.1.1.3) shall contain a rendering of all valid Instances of the Composite SOP​ classes for which conformance is claimed, e.g., origin server shall be able to render all Photometric Interpretations that are defined​ in the IOD for that SOP class. The content type of the response payload shall be a Rendered Media Type.​

10.4.3.3.4 Thumbnail Resource Payload​
The payload for a Thumbnail Resource (see Section 10.4.1.1.4) shall contain a meaningful representation in a Rendered Media Type.​ The origin server will determine what constitutes a meaningful representation. The Thumbnail shall not contain any Patient Identifying​ Information. Only a single image shall be returned.​


Here, I guess that WADO-RS Thumbnail returns ONLY ONE image, even if a study has 100 images and <service>/studies/{StudyInstanceUID>/thumbnail was called.

However, <service>/studies/{StudyInstanceUID}/rendered is called, I think we need to respond with 100 rendered images in 100 multipart messages, with headers like multipart/related; type=image/jpeg? Is my understanding correct?

But, when I try to call the Orthanc server, it returns only one image with headers like image/jpeg. Am I missing something? Or do they have some bugs?

Thanks in advance.

Samuel

Alain Mazy

unread,
Aug 29, 2022, 10:52:41 AM8/29/22
to Samuel Choi, Orthanc Users
Hi Samuel,

Indeed, your understanding seems correct (at least, I have the same understanding) so this can be considered as a bug.

I've added a TODO to handle it (no idea when this will be done).

Best regards,

Alain.



--
You received this message because you are subscribed to the Google Groups "Orthanc Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orthanc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/orthanc-users/ceb1273b-f99b-49f4-9d7c-9826169285dan%40googlegroups.com.

Samuel Choi

unread,
Aug 29, 2022, 8:44:47 PM8/29/22
to Orthanc Users
Hi Alain,

If my and your understanding is correct, I feel we should send the request with the Accept header 'multipart/related; type=image/jpeg', not just simple 'image/jpeg', to get multiple rendered resources in response.
But in DICOM Standards I couldn't find anything about requesting rendered resources with 'Accept: multipart/related; type=xxx' header. It seems that the DICOM Standards in this section were not written very clear.

What do you think of this?

Samuel

2022년 8월 29일 월요일 오후 11시 52분 41초 UTC+9에 alain...@osimis.io님이 작성:

Alain Mazy

unread,
Aug 30, 2022, 2:38:49 AM8/30/22
to Samuel Choi, Orthanc Users
Yes, your proposal makes sense.  I'll check in details when working on this.

Reply all
Reply to author
Forward
0 new messages