Character set with which the returned object s is to be encoded, as defined in the IETF RFC2616. This parameter is OPTIONAL for URI based mode, and for the WS mode “Rendered Requester” and shall not be present in the other WS mode transactions .
The parameter name shall be “charset” for URI based mode, and “CharsetList” containing one or more elements “Charset” for the WS mode .
For the URI mode, the value shall be a list of character sets, separated by a "," character, and potentially associated with relative degree of preference, as specified in IETF RFC2616.
In URI based mode, t T he Web Client may provide a list of character sets it supports in the "Accept-charset" field of the Get method. If this field is present, the value of the charset parameter of the request shall be one of the values specified in it.
The Web Server may or may not support character set conversion. If character set conversion is supported:
text based DICOM objects retrieved other than as application/dicom MIME type (e.g., text/plain) may be returned in the requested character set (converted if necessary)
DICOM objects retrieved as application/dicom MIME type have all contained strings returned in the requested character set (converted if necessary) and the Specific Character Set (0008,0005) updated (if necessary)
Notes: 1. The IANA Character Set registrations specify names and multiple aliases for most character sets. The standard value for use in WADO is the one marked by IANA as "preferred for MIME." If IANA has not marked one of the aliases as "preferred for MIME", the name used in DICOM shall be the value used for WADO.
2. The table in Annex D provides an informative mapping of some IANA values to DICOM Specific Character Set Defined Terms.