XX.1 REQUEST AND RESPONSE PARAMETERS

XX.1.1 Request Parameters

The new service based on WS should continue to support all the request parameters defined by WADO, for maintaining backward compatibility with the present URI based WADO, including the options to return either native DICOM objects or a rendered object (JPEG, PDF etc.). These are summarized as below:

Table XX.1-1 Summary of DICOM/Rendered URI based WADO Parameters

Parameter Allowed for Requirement in Request
requestType DICOM & Rendered Required
studyUID DICOM & Rendered Required
seriesUID DICOM & Rendered Required
objectUID DICOM & Rendered Required
contentType DICOM & Rendered Optional
charset DICOM & Rendered Optional
anonymize DICOM Optional
annotation Rendered Optional
Rows, columns Rendered Optional
region Rendered Optional
windowCenter, windowWidth Rendered Optional
imageQuality DICOM & Rendered Optional
presentationUID Rendered Optional
presentationSeriesUID Rendered Optional
transferSyntax DICOM Optional
frameNumber DICOM & Rendered Optional

For the WS “DICOM Requester” transaction, the parameters will be the following:

Table XX.1-2 Summary of “DICOM Requester” WADO-WS Parameters

Parameter Requirement in Request Multiplicity
StudyRequest Required One
>SeriesRequest Required One or more
>>DocumentRequest Required One or more
>>>RepositoryUniqueId Optional One
>>>DocumentUniqueId Required One
>>>HomeCommunityId Optional One
>>>FrameNumber Optional One
>>>Anonymize Optional One
>>>TransferSyntaxUIDList Optional One
>>>>TransferSyntaxUID Required One or more

Table XX.1-3 Summary of “Rendered Requester” WADO-WS Parameters

Parameter Requirement in Request Multiplicity
StudyRequest Required One
>SeriesRequest Required One or more
>>DocumentRequest Required One or more
>>>RepositoryUniqueId Optional One
>>>DocumentUniqueId Required One
>>>HomeCommunityId Optional One
>>>Annotation Optional One
>>>Rows / Columns Optional One
>>>Region Optional One
>>>WindowCenter/ WindowWidth Optional One
>>>ImageQuality Optional One
>>>PresentationUID Optional One
>>>PresentationSeriesUID Optional One
>>>FrameNumber Optional One
>>>Anonymize Optional One
>>>ContentTypeList Required One
>>>>ContentType Required One or more
>>>CharsetList Optional One
>>>>Charset Required One or more

Table XX.1-4 Summary of “Metadata Requester” WADO-WS Parameters

Parameter Requirement in Request Multiplicity
StudyRequest Required One
>SeriesRequest Required One or more
>>DocumentRequest Required One or more
>>>RepositoryUniqueId Optional One
>>>DocumentUniqueId Required One
>>>HomeCommunityId Optional One
>>>Anonymize Optional One
>>>XPath Required One

XX.1.2 Response parameters

In the URI based WADO, the response is the single payload returned in the HTTP Get response. It may be the DICOM object in a DICOM format or in a rendered format.

In the Web Services implementation, for the “DICOM Requester” and the “Rendered Requester” transactions, one or more DICOM objects are returned using the MTOM/XOP mechanism as well as associated metadata.

For the “Metadata Requester” transaction, the response will contain the an XML encoded part containing the information selected from the retrieved objects header using the “XPath” filter as described in the Native DICOM Model defined in PS3.19.