DICOM Conformance

This page is a summary conformance statement for the Weasis viewer. It follows the order of a DICOM PS3.2 conformance statement but keeps one table per topic; it is not a formal PS3.2 document with association and negotiation tables. It applies to the Weasis releases documented on this site; a feature newer than the oldest documented release carries a version badge.

DICOM objects

Objects displayed

Weasis opens any file or network object below. A valid DICOM object that matches none of them is listed in the explorer as unsupported.

Objects created

Network services

DIMSE

Weasis acts as a Service Class User. Its only Service Class Provider role is the Storage SCP that receives the objects of a C-MOVE. DIMSE connections are not encrypted.

Configuration: DICOM explorer, Print, Dicomizer.

DICOMweb

HTTPS is supported, with OAuth 2.0 (Keycloak and Google templates) or custom HTTP headers for authentication. See DICOMweb configuration and DICOMweb archives.

Launch from an external system

Weasis can be started with a manifest that lists the studies to load and the archive to fetch them from, or with the parameters of the IHE Invoke Image Display profile. See Integration and the ViewerHub launch APIs.

Transfer syntaxes

• Read: the pixel data is decoded and displayed by Weasis.
• Write: the syntax can be selected in the Export dialog (see Export), or Weasis uses it when sending over the network or saving the objects it creates. When exporting with the original syntax kept, images are copied unchanged whatever their syntax.

Implicit VR Little Endian is not offered in the Export dialog. Weasis uses it in two cases: as the last fallback of a C-STORE send, when the receiving system accepts neither the syntax of the file nor Explicit VR Little Endian, and for the key object selections it creates.

Video transfer syntaxes are not decoded by Weasis. The video stream is extracted to a temporary file and opened with the default video player of the operating system. The file carries the extension of its container, .mpg for MPEG-2 and .mp4 for H.264 and HEVC since v4.8.0, so that the player recognizes the format.

Not supported

The following transfer syntaxes are not read: JPIP Referenced (1.2.840.10008.1.2.4.94, .95, .204, .205), Encapsulated Uncompressed Explicit VR Little Endian (1.2.840.10008.1.2.1.98), Deflated Image Frame Compression (1.2.840.10008.1.2.8.1) and the retired RFC 2557 MIME Encapsulation (1.2.840.10008.1.2.6.1).

Pixel data

Photometric interpretation

This table lists every Photometric Interpretation value defined by the standard, including the retired ones, and how Weasis reads it. The “Pixel data” column gives the encodings the standard allows for the value: native (uncompressed), encapsulated (compressed), or both. Compressed transfer syntaxes add their own restrictions, see PS3.5 section 8.2.

The standard also allows values it does not define when a transfer syntax supports them. Weasis cannot read an image with a value missing from this table, retired values included.

When a JPEG Baseline, Extended or Progressive image declares RGB but its JPEG stream carries luminance and chrominance (a JFIF header or component identifiers other than R, G, B), Weasis follows the stream and converts the colors to RGB.

Photometric interpretation written

Pixel data characteristics

• Bits Allocated 8, 16 and 32, signed and unsigned; 32-bit float pixel data (Parametric Maps).
• Both planar configurations (interleaved and separate planes).
• Single-frame and multi-frame objects; encapsulated multi-frame data with one or several fragments per frame.
• Modality LUT and rescale, VOI LUT and windows, presentation LUT shape, palette color lookup tables, and overlay planes.

Character sets

The Specific Character Set of each object is honored when decoding text attributes, including the ISO 2022 multi-byte sets and UTF-8. Text is displayed with the fonts of the operating system.

IHE profiles