C.3 General Class Profile

C.3.1 Abstract and Transfer Syntaxes

Application Profiles in this class, STD-US, shall support the appropriate Information Object Definitions (IOD) and Transfer Syntaxes for the Media Storage SOP Class in the following table. In the role of FS-Updater or FS-Creator the application can choose one of the three possible transfer Syntaxes to create an IOD. In the role of FS-Reader an application shall support all transfer Syntaxes defined for the STD-US application profile.

Table C.3-1ULTRASOUND ABSTRACT AND TRANSFER SYNTAXES

Information Object Definition SOP Class UID Transfer Syntax Transfer Syntax UID
DICOM Media Storage Directory 1.2.840.10008.1.3.10 Explicit VR Little Endian Uncompressed 1.2.840.10008.1.2.1 (see PS 3.10 section 8.6)
Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Explicit VR Little Endian Uncompressed 1.2.840.10008.1.2.1
Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 RLE Lossless Image Compression 1.2.840.10008.1.2.5
Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 JPEG Lossy, Baseline Sequential with Huffman Coding (Process 1) 1.2.840.10008.1.2.4.50
Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 Explicit VR Little Endian Uncompressed 1.2.840.10008.1.2.1
Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 RLE Lossless Image Compression 1.2.840.10008.1.2.5
Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 JPEG Lossy, Baseline Sequential with Huffman Coding (Process 1) 1.2.840.10008.1.2.4.50

C.3.1.1 Ultrasound Single and Multi-frame Pixel Formats Supported

The STD-US application profile requires that all ultrasound image objects only be stored using the values described in PS 3.3 US Image Module and the specializations used for the Ultrasound Single and Multi-Frame IODs.

In the role of FS-Updater or FS-Creator the application can choose any of the supported Photometric Interpretations described in PS 3.3 US Image Module to create an IOD. In the role of FS-Reader, an application shall support all Photometric Interpretations described in PS 3.3 US Image Module.

Table C.3-2 describes restrictions on the use of various Transfer Syntaxes with the supported Photometric Interpretations for both single and multi-frame images.

Table C.3-2DEFINED PHOTOMETRIC INTERPRETATION AND TRANSFER SYNTAX PAIRS

Photometric Interpretation Value Transfer Syntax Transfer Syntax UID
MONOCHROME2 Uncompressed RLE Lossless Image Compression 1.2.840.10008.1.2.1 1.2.840.10008.1.2.5
RGB Uncompressed RLE Lossless Image Compression 1.2.840.10008.1.2.1 1.2.840.10008.1.2.5
PALETTE COLOR Uncompressed RLE Lossless Image Compression 1.2.840.10008.1.2.1 1.2.840.10008.1.2.5
YBR_FULL RLE Lossless Image Compression 1.2.840.10008.1.2.5
YBR_FULL_422 Uncompressed JPEG Lossy 1.2.840.10008.1.2.1 1.2.840.10008.1.2.4.50
YBR_PARTIAL_422 Uncompressed JPEG Lossy 1.2.840.10008.1.2.1 1.2.840.10008.1.2.4.50

C.3.2 Physical Media And Media Formats

An ultrasound application profile class may be supported by any one of the media described in Table C.3-3.

Table C.3-3MEDIA CLASSES

Media Media Classes Media Format PS 3.12
2.3GB 90mm MOD MOD23-90 DOS, unpartitioned (removable media) Annex Q
CD-R CDR ISO/IEC 9660 Annex F
DVD-RAM DVD-RAM UDF1.5 Annex J
120 mm DVD DVD UDF or ISO 9660 Annex P

Note: Media Classes FLOP, MOD128, MOD230, MOD540, MOD640, MOD650, MOD12 AND MOD23 were previously defined but have been retired. See PS 3.11 2004.

C.3.3 DICOMDIR

The Directory shall include Directory Records of PATIENT, STUDY, SERIES, IMAGE corresponding to the information object files in the File Set. All DICOM files in the File Set incorporating SOP Instances (Information Objects) defined for the specific Application Profile shall be referenced by Directory Records. At the image level each file contains a single ultrasound image object or a single ultrasound multi-frame image object as defined in PS 3.3 of the standard.

NOTE: For all media selected in this Application Profile Class, STD-US, the following applies as defined in PS 3.12.

All implementations should include the DICOM Media Storage Directory in the DICOMDIR file. There should only be one DICOMDIR file on a single media. The DICOMDIR file should be found in the root directory of the media. For the case of double-sided MOD media, there shall be a DICOMDIR on each side of the media.

On a single media the patient ID key at the patient level shall be unique for each patient directory record.

C.3.3.1 Additional Keys

File Set Creators and Updaters are only required to generate mandatory elements specified in PS 3.10. At each directory record level any additional data elements can be added as keys, but is not required by File Set Readers to be able to use them as keys.

C.3.3.2 File Component lDs

Note: File Component IDs should be created using a random number filename to minimize File Component ID collisions as described in PS 3.12. The FS-Updater should check the existence of a Component ID prior to creating that ID. Should an ID collision occur, the FS-Updater should try another ID.