DICOM Standard Browser

Note

• The profile shall be of the Input Device class, i.e., header bytes 12 through15, Profile Device/Class Signature, shall be "scnr"

• The color space of the input shall be RGB, i.e., header bytes 16 through 19, Color Space Signature, shall be "RGB", regardless of the Photometric Interpretation of the image pixel data prior to decompression

• PCS shall be CIELab or CIEXYZ, i.e., header bytes 20 through 23, Profile Connection Space, shall be either "Lab" or "XYZ".

  Note

  1. In the case of a PCS of CIELab, the profile will contain an N-component LUT-based AtoB0Tag, since three-component matrix based transformations are only possible with a PCS of CIEXYZ. A three-component matrix based transformation might be used to define a well-known rather than device-specific profile for such spaces as sRGB.

  2. Selection of a PCS of CIELab or CIEXYZ within the ICC profile does not impact the DICOM encoding, since all color management systems support both.

• The Rendering Intent should be Perceptual.

  Note

  1. The rendering intent specifies how rendering will take place when the ICC Input Profile is linked with another Profile for the purpose of display.

  2. A perceptual rendering intent implies that AtoB0Tag and BtoA0Tag tags will be present in the profile. The AtoB0Tag allows mapping from the input values to the PCS. The BtoA0Tag allows mapping from the PCS to the input values, though this is not required for the color rendering pipeline defined in PS3.4.

• All LUTs should be represented as 16 bit values, using tag type lut16Type, for greater precision.

• The chromaticAdaptationTag should be set if the actual illumination source is not D50.

  Note

  See the discussion of white point in PS3.4.