Материал: part03

F.5.40 Plan Directory Record Definition​

TheDirectoryRecordisbasedonthespecificationofSectionF.3.ItisidentifiedbyaDirectoryRecordTypeofValue"PLAN".TableF.5-​ 40 lists the set of keys with their associated Types for such a Directory Record Type. The description of these keys may be found in​ the Modules related to the Plan IEs of RT Plan IOD and RT Ion Plan IOD. This Directory Record shall be used to reference one of​ the class of Plan SOP Instances having a Modality (0008,0060) of "PLAN", such as the RT Beams Delivery Instruction IOD. This type​ ofDirectoryRecordmayreferenceaLower-LevelDirectoryEntitythatincludesoneormoreDirectoryRecordsasdefinedinTableF.4-​ 1.​

Table F.5-40. Plan Keys​

Note​

BecauseReferencedSOPInstanceUIDinFile(0004,1511)maybeusedasa"pseudo"DirectoryRecordKey(seeTableF.3-​ 3), it is not duplicated in this list of keys.​

F.5.41 Measurement Directory Record Definition​

TheDirectoryRecordisbasedonthespecificationofSectionF.3.ItisidentifiedbyaDirectoryRecordTypeofValue"MEASUREMENT".​ Table F.5-41 lists the set of keys with their associated Types for such a Directory Record Type. The description of these keys may​ be found in the Modules related to the Measurements IE of the Measurement IODs. This Directory Record shall be used to reference​ a Measurement SOP Instance. This type of Directory Record may reference a Lower-Level Directory Entity that includes one or more​ Directory Records as defined in Table F.4-1.​

Table F.5-41. Measurement Keys​

Note​

Because(0004,1511)ReferencedSOPInstanceUIDinFilemaybeusedasa"pseudo"DirectoryRecordKey(seeTableF.3-​ 3), it is not duplicated in this list of keys.​

F.5.42 Surface Directory Record Definition​

The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "SURFACE".​ Table F.5-42 lists the set of keys with their associated Types for such a Directory Record Type. The description of these keys may​ be found in the Modules related to the Surface IE of the Surface Segmentation IOD. This Directory Record shall be used to reference​ a Surface Segmentation SOP Instance. This type of Directory Record may reference a Lower-Level Directory Entity that includes one​ or more Directory Records as defined in Table F.4-1.​

- Standard -​

DICOM PS3.3 2020a - Information Object Definitions​ Page 1697​

Table F.5-42. Surface Keys​

Note​

Because(0004,1511)ReferencedSOPInstanceUIDinFilemaybeusedasa"pseudo"DirectoryRecordKey(seeTableF.3-​ 3), it is not duplicated in this list of keys.​

F.5.43 Surface Scan Mesh Directory Record Definition​

The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "SURFACE​ SCAN". Table F.5-43 lists the set of keys with their associated Types for such a Directory Record Type. The description of these keys​ may be found in the Modules related to the Surface IE of the Surface Scan Mesh and Surface Scan Point Cloud IODs. This Directory​ Record shall be used to reference a Surface Scan Mesh SOP Instance. This type of Directory Record may reference a Lower-Level​ Directory Entity that includes one or more Directory Records as defined in Table F.4-1.​

Table F.5-43. Surface Scan Keys​

Note​

Because(0004,1511)ReferencedSOPInstanceUIDinFilemaybeusedasa"pseudo"DirectoryRecordKey(seeTableF.3-​ 3), it is not duplicated in this list of keys.​

F.5.44 Tractography Results Directory Record Definition​

The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "TRACT".​ Table F.5-44 lists the set of keys with their associated Types for such a Directory Record Type. The description of these keys may​ be found in the Modules related to the Tractography Results IE of the Tractography Results IOD. This Directory Record shall be used​ to reference a Tractography Results SOP Instance. This type of Directory Record may reference a Lower-Level Directory Entity that​ includes one or more Directory Records as defined in Table F.4-1.​

Table F.5-44. Tractography Results Keys​

- Standard -​

Note​

Because(0004,1511)ReferencedSOPInstanceUIDinFilemaybeusedasa"pseudo"DirectoryRecordKey(seeTableF.3-​ 3), it is not duplicated in this list of keys.​

F.5.45 Content Assessment Results Directory Record Definition​

TheDirectoryRecordisbasedonthespecificationofSectionF.3.ItisidentifiedbyaDirectoryRecordTypeofValue"ASSESSMENT".​ Table F.5-45 lists the set of keys with their associated Types for such a Directory Record Type. The description of these keys may​ be found in the Modules related to the Content Assessment Results IOD. This Directory Record shall be used to reference a Content​ Assessment Results SOP Instance. This type of Directory Record may reference a Lower-Level Directory Entity that includes one or​ more Directory Records as defined in Table F.4-1.​

Table F.5-45. Content Assessment Results Directory Record Results Keys​

Note​

BecauseReferencedSOPInstanceUIDinFile(0004,1511)maybeusedasa"pseudo"DirectoryRecordKey(seeTableF.3-​ 3), it is not duplicated in this list of keys.​

F.5.46 Radiotherapy Directory Record Definition​

TheDirectoryRecordisbasedonthespecificationofSectionF.3.ItisidentifiedbyaDirectoryRecordTypeofValue"RADIOTHERAPY".​ Table F.5-46 lists the set of keys with their associated Types for such a Directory Record Type. The description of these keys may​ be found in the Modules related to the Instance-level IEs of the RT Second-Generation IODs. This Directory Record shall be used to​ reference one of the classes of RT Second-Generation SOP Instances having a Modality (0008,0060) of as defined in Section A.86.1.​ This type of Directory Record may reference a Lower-Level Directory Entity that includes one or more Directory Records as defined​ in Table F.4-1.​

Table F.5-46. Radiotherapy Keys​

- Standard -​

Note​

BecauseReferencedSOPInstanceUIDinFile(0004,1511)maybeusedasa"pseudo"DirectoryRecordKey(SeeTableF.3-​ 3), it is not duplicated in this list of keys.​

F.6 Special Directory Records​

F.6.1 Private Directory Record Definition​

Private Directory Records may also be used in addition to Standard defined Directory Records. Such Private Records shall follow the​ specification of Section F.2 and Section F.3. In addition, if created by File-set Creators they shall be proper extensions to the DICOM​ Basic Directory IOD Information Model specified in Section F.4. By proper extensions it is meant that any File-set Creator creating​ private Directory Records shall still meet the PS3.10 conformance requirements. Thus a File-set Reader or File-set Updater that​ chooses to ignore such privately defined Directory Records will find a conformant Directory.​

F.6.2 Multi-referenced File Directory Record Definition​

Retired. See PS3.3-2004.​

F.7 Icon Image Key Definition​

An Icon Image may be used as a key representative of an Image, RT Dose, Spectroscopy, Raw Data or Series in a corresponding​ Directory Record to allow an application to display icons that enable a user to select one or more from amongst several of them. It is​ based on the general purpose Image Pixel Macro (see Annex C).​

The Icon Image Key corresponds to Data Element (0088,0200). It is defined as a Sequence that contains a single Item encapsulating​ the Data Set made of the Data Elements of the Icon Image. The Data Elements are defined by the Image Pixel Macro (see Sec-​ tion C.7.6.3).​

The Image Pixel Macro usage is restricted in a few areas to facilitate general use in Directory Record across various modality envir-​ onments. These restrictions are:​

a.​Only monochrome and palette color images shall be used. Samples per Pixel (0028,0002) shall have a Value of 1, Photometric​ Interpretation (0028,0004) shall have a Value of either MONOCHROME 1, MONOCHROME 2 or PALETTE COLOR, Planar​ Configuration (0028,0006) shall not be present.​

Note​

True color icon images are not supported. This is due to the fact that the reduced size of the Icon Image makes the​ quality of a palette color image (with 256 colors) sufficient in most cases. This simplifies the handling of Icon Images by​ File-set Readers and File-set Updaters.​

b.​If an FSR/FSU supports Icons (i.e., does not ignore them) then it shall support at least a maximum size of 64 by 64 Icons. An​ FSC may write Icons of any size. Icons larger than 64 by 64 may be ignored by FSRs and FSUs unless specialized by Application​ Profiles.​

c.​PixelsamplesshallhaveaValueofeither1or8forBitsAllocated(0028,0100)andBitsStored(0028,0101).HighBit(0028,0102)​ shall have a Value of one less than the Value used in Bit Stored.​

d.​Pixel Representation (0028,0103) shall specify an unsigned integer representation (Value 0000H).​

e.​Pixel Aspect Ratio (0028,0034) shall have a Value of 1:1.​

f.​ If a Palette Color lookup Table is used, Bits Allocated (0028,0100) shall have a Value of 8.​

- Standard -​

- Standard -​