M.3 STD-GEN-BD and STD-GEN-SEC-BD Profile Classes
Prev | M General Purpose BD With Compression Interchange Profiles (Normative) |

## M.3 STD-GEN-BD and STD-GEN-SEC-BD Profile Classes

### M.3.1 SOP Classes and Transfer Syntaxes

This Application Profile is based on the Media Storage Service Class with the Interchange Option (see PS3.4).

Table M.3-1. STD-GEN-BD and STD-GEN-SEC-BD SOP Classes and Transfer Syntaxes

Information Object Definition | SOP Class UID | Transfer Syntax and UID | FSC Requirement | FSR Requirement | FSU Requirement
--- | --- | --- | --- | --- | ---
Basic Directory | 1.2.840.10008.1.3.10 | Explicit VR Little Endian Uncompressed 1.2.840.10008.1.2.1 | Mandatory | Mandatory | Mandatory
Composite IODs for which a Media Storage SOP Class is defined in PS3.4 | See PS3.4 | Explicit VR Little Endian Uncompressed 1.2.840.10008.1.2.1 | Defined in Conformance Statement | Mandatory for all SOP Classes defined in Conformance Statement | Defined in Conformance Statement
Composite IODs for which a Media Storage SOP Class is defined in PS3.4 | See PS3.4 | JPEG Lossless Process 14 (selection value 1) 1.2.840.10008.1.2.4.70 | Defined in Conformance Statement | Mandatory for JPEG profiles for all SOP Classes defined in Conformance Statement | Defined in Conformance Statement
Composite IODs for which a Media Storage SOP Class is defined in PS3.4 | See PS3.4 | JPEG Lossy, Baseline Sequential with Huffman Coding (Process 1) 1.2.840.10008.1.2.4.50 | Defined in Conformance Statement | Mandatory for JPEG profiles for all SOP Classes defined in Conformance Statement | Defined in Conformance Statement
Composite IODs for which a Media Storage SOP Class is defined in PS3.4 | See PS3.4 | JPEG Extended (Process 2 & 4): Default Transfer Syntax for Lossy JPEG 12 Bit Image Compression (Process 4 only) 1.2.840.10008.1.2.4.51 | Defined in Conformance Statement | Mandatory for JPEG profiles for all SOP Classes defined in Conformance Statement | Defined in Conformance Statement
Composite IODs for which a Media Storage SOP Class is defined in PS3.4 | See PS3.4 | JPEG 2000 Image Compression (Lossless Only) 1.2.840.10008.1.2.4.90 | Defined in Conformance Statement | Mandatory for J2K profiles for all SOP Classes defined in Conformance Statement | Defined in Conformance Statement
Composite IODs for which a Media Storage SOP Class is defined in PS3.4 | See PS3.4 | JPEG 2000 Image Compression 1.2.840.10008.1.2.4.91 | Defined in Conformance Statement | Mandatory for J2K profiles for all SOP Classes defined in Conformance Statement | Defined in Conformance Statement
Multi-frame Composite IODs for which a Media Storage SOP Class is defined in PS3.4 | See PS3.4 | MPEG2 Main Profile @ Main Level 1.2.840.10008.1.2.4.100 | Defined in Conformance Statement | Mandatory for all SOP Classes defined in Conformance Statement | Defined in Conformance Statement
Multi-frame Composite IODs for which a Media Storage SOP Class is defined in PS3.4 | See PS3.4 | MPEG2 Main Profile @ High Level 1.2.840.10008.1.2.4.101 | Defined in Conformance Statement | Mandatory for all SOP Classes defined in Conformance Statement | Defined in Conformance Statement
Multi-frame Composite IODs for which a Media Storage SOP Class is defined in PS3.4 | See PS3.4 | MPEG-4 AVC/H.264 High Profile / Level 4.1 1.2.840.10008.1.2.4.102 | Defined in Conformance Statement | Mandatory for all SOP Classes defined in Conformance Statement | Defined in Conformance Statement
Multi-frame Composite IODs for which a Media Storage SOP Class is defined in PS3.4 | See PS3.4 | MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1 1.2.840.10008.1.2.4.103 | Defined in Conformance Statement | Mandatory for all SOP Classes defined in Conformance Statement | Defined in Conformance Statement

The SOP Classes and corresponding Transfer Syntax supported by this Application Profile are specified in the Table M.3-1. The supported Storage SOP Class(es) shall be listed in the Conformance Statement using a table of the same form.

### M.3.2 Physical Medium and Medium Format

The STD-GEN-BD and STD-GEN-SEC-BD application profiles require any of the 120 mm BD media, as defined in PS3.12.

### M.3.3 Directory Information in DICOMDIR

Conformant Application Entities shall include in the DICOMDIR File the Basic Directory IOD containing Directory Records at the Patient and the subsidiary Study and Series levels, appropriate to the SOP Classes in the File Set.

All DICOM files in the File Set incorporating SOP Instances defined for the specific Application Profile shall be referenced by Directory Records.

### Note

DICOMDIRs with no directory information are not allowed by this Application Profile.

All implementations shall include the DICOM Media Storage Directory in the DICOMDIR file. There shall only be one DICOMDIR file per File Set. The DICOMDIR file shall be in the root directory of the medium. The Patient ID at the patient level shall be unique for each patient directory record in one File Set.

#### M.3.3.1 Additional Keys

File Set Creators and Updaters are required to generate the mandatory elements specified in PS3.3.

Table H.3-2 specifies the additional associated keys that shall also be applicable to the profiles defined in this Annex. At each directory record level other additional data elements can be added, but it is not required that File Set Readers be able to use them as keys. Refer to the Basic Directory IOD in PS3.3.

### M.3.4 Other Parameters

#### M.3.4.1 Multi-frame JPEG Format

The JPEG encoding of pixel data shall use Interchange Format (with table specification) for all frames.

### M.3.5 Security Parameters

The STD-GEN-SEC-BD application profiles require that all DICOM Files in the File-set including the DICOMDIR be Secure DICOM Files encapsulated in accordance with the requirements of the Basic DICOM Media Security Profile as defined in PS3.15.

### Note

These Application Profiles do not place any consistency restrictions on the use of the Basic DICOM Media Security Profile with different DICOM Files of one File-set. For example, readers should not assume that all Files in the File-set can be decoded by the same set of recipients. Readers should also not assume that all secure Files use the same approach (hash key or digital signature) to ensure integrity or carry the same originators' signatures.

Prev | Up |
M.2 Clinical Context | Home |