The following Sections specify a number of Directory Records that were introduced by the Basic Directory IOD Information Model presented in Section F.4. For each one, it identifies the SOP Classes that may be referenced and the related mandatory keys. Keys are assigned a Type designation that indicates if it is required for all Media Storage Operations of the Directory (see Section 5).
Type 2 and Type 3 Keys may be changed to Type 1 and Type 2 or 3 respectively by Application Profiles defined in PS3.11. Keys based on Private Data Elements, or Private Keys may also be used in addition to Standard defined Keys. However such Private keys may be ignored by any File-set Reader or Updater.
Note
Normalized Print media storage was previously defined in DICOM. It is now retired. See PS3.3-1998.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "PATIENT." Table F.5-1 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 Patient IOD or the Patient IE of Image IODs. 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-1. Patient Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys |
|
Patient's Name |
(0010,0010) |
2 |
|
|
Patient ID |
(0010,0020) |
1 |
|
|
Any other Attribute of the Patient IE Modules |
3 |
||
For a given File-set, the Patient ID shall be unique. This means that it shall not appear in different Patient Directory Records.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "STUDY." Table F.5-2 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 Study IE of Composite IODs. 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. Only one Study Directory Record per Study Instance UID shall be present in a Basic Directory Instance; this implies that a study belongs to a single patient and shall be referenced only once for that patient.
Table F.5-2. Study Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys |
|
Study Date |
(0008,0020) |
1 |
|
|
Study Time |
(0008,0030) |
1 |
|
|
Study Description |
(0008,1030) |
2 |
|
|
Study Instance UID |
(0020,000D) |
1C |
Required only if (0004,1511) is absent (see Note). |
|
Study ID |
(0020,0010) |
1 |
|
|
Accession Number |
(0008,0050) |
2 |
|
|
Any other Attribute of the Study IE Modules |
3 |
||
Note
The Study Instance UID shall be present as a mandatory key only if no file is referenced by this Directory Record. In the case where this Directory Record references a file, the Directory Record contains in the Referenced SOP Instance UID in File (0004,1511). In this case (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3) and need not be duplicated.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "SERIES." Table F.5-3 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 Series IE and Equipment IE of Composite IODs. 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. Only one Series Directory Record per Series Instance UID shall be present in a Basic Directory Instance; this implies that a series belongs to a single study and shall be referenced only once for that study.
Table F.5-3. Series Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys |
|
Modality |
(0008,0060) |
1 |
|
|
Series Instance UID |
(0020,000E) |
1 |
|
|
Series Number |
(0020,0011) |
1 |
|
|
Icon Image Sequence |
(0088,0200) |
3 |
This Icon Image is representative of the Series. It may or may not correspond to one of the images of the Series. Only a single Item is permitted in this Sequence. |
|
See Section F.7. |
|||
|
Any other Attribute of the Series IE Modules |
3 |
||
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "IMAGE." Table F.5-4 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 Image IE of Image IODs. This Directory Record shall be used to reference an Image 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-4. Image Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Instance Number |
(0020,0013) |
1 |
|
|
Icon Image Sequence |
(0088,0200) |
3 |
This Icon Image is representative of the Image. Only a single Item is permitted in this Sequence. |
|
See Section F.7. |
|||
|
Any other Attribute of the Image IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
This section was previously defined in DICOM. It is now retired. See PS3.3-1998.
This section was previously defined in DICOM. It is now retired. See PS3.3-1998.
This section was previously defined in DICOM. It is now retired. See PS3.3-1998.
This section was previously defined in DICOM. It is now retired. See PS3.3-1998.
This Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "RT DOSE". Table F.5-19 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 Dose IE of the RT Dose IOD. This Directory Record shall be used to reference a RT Dose 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-19. RT Dose Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Instance Number |
(0020,0013) |
1 |
|
|
Dose Summation Type |
(3004,000A) |
1 |
|
|
Dose Comment |
(3004,0006) |
3 |
|
|
Icon Image Sequence |
(0088,0200) |
3 |
This Icon Image is representative of the RT Dose. Only a single Item is permitted in this Sequence. |
|
See Section F.7. |
|||
|
Any other Attribute of the Dose IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
This Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "RT STRUCTURE SET". Table F.5-20 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 Structure Set IE of the RT Structure Set IOD. This Directory Record shall be used to reference a RT Structure Set 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-20. RT Structure Set Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Instance Number |
(0020,0013) |
1 |
|
|
Structure Set Label |
(3006,0002) |
1 |
|
|
Structure Set Date |
(3006,0008) |
2 |
|
|
Structure Set Time |
(3006,0009) |
2 |
|
|
Any other Attribute of the Structure Set IE Modules |
3 |
||
Note
Because (0004,1511) Referenced SOP Instance UID in File may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
This Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "RT PLAN". Table F.5-21 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 IE of the RT Plan IOD. This Directory Record shall be used to reference a RT Plan 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-21. RT Plan Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys |
|
Instance Number |
(0020,0013) |
1 |
|
|
RT Plan Label |
(300A,0002) |
1 |
|
|
RT Plan Date |
(300A,0006) |
2 |
|
|
RT Plan Time |
(300A,0007) |
2 |
|
|
Any other Attribute of the Plan IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
This Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "RT TREAT RECORD". Table F.5-22 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 Treatment Record IE of the RT Treatment Record IODs. This Directory Record shall be used to reference an RT Beams Treatment Record SOP instance, RT Brachy Treatment Record SOP instance, or RT Treatment Summary Record 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-22. RT Treatment Record Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys |
|
Instance Number |
(0020,0013) |
1 |
|
|
Treatment Date |
(3008,0250) |
2 |
|
|
Treatment Time |
(3008,0251) |
2 |
|
|
Any other Attribute of the Treatment Record IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "PRESENTATION". Table F.5-23 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 Softcopy Presentation State Storage and Structured Display IODs. This Directory Record shall be used to reference a Softcopy Presentation State Storage SOP Instance or a Structured Display 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-23. Presentation Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Presentation Creation Date |
(0070,0082) |
1 |
Date on which this presentation was created. NoteThis date may be different from the date that the DICOM SOP Instance was created, since the presentation information contained may have been recorded earlier. |
|
Presentation Creation Time |
(0070,0083) |
1 |
Time at which this presentation was created. NoteThis time may be different from the time that the DICOM SOP Instance was created, since the presentation information contained may have been recorded earlier. |
|
Include Table 10-12 “Content Identification Macro Attributes” |
|||
|
Referenced Series Sequence |
(0008,1115) |
1C |
Sequence of Items where each Item includes the Attributes of one Series to which the Presentation applies. One or more Items shall be included in this Sequence. Required if the IOD of the Presentation SOP Instance referenced by this directory record includes the Presentation State Relationship Module. |
|
>Series Instance UID |
(0020,000E) |
1 |
Unique identifier of a Series that is part of this Study. |
|
>Referenced Image Sequence |
(0008,1140) |
1 |
Sequence of Items where each Item provides reference to an Image SOP Instance. One or more Items shall be included in this sequence. |
|
>>Include Table 10-11 “SOP Instance Reference Macro Attributes” |
|||
|
Blending Sequence |
(0070,0402) |
1C |
Sequence of Items where each Item includes the Attributes of a Study to which the Presentation applies. Only two Items shall be included in this sequence. Required if the SOP Instance referenced by this directory record includes Blending Sequence (0070,0402). |
|
>Study Instance UID |
(0020,000D) |
1 |
Unique identifier for a Study that contains the images to which the Presentation applies. |
|
>Referenced Series Sequence |
(0008,1115) |
1 |
Sequence of Items where each Item includes the Attributes of one Series to which the Presentation applies. Only a single item shall be included in this Sequence. |
|
>>Series Instance UID |
(0020,000E) |
1 |
Unique identifier of the Series |
|
>>Referenced Image Sequence |
(0008,1140) |
1 |
Sequence of Items where each Item provides reference to an Image SOP Instance to which the Presentation applies. One or more Items shall be included in this sequence. |
|
>>>Include Table 10-11 “SOP Instance Reference Macro Attributes” |
|||
|
Any other Attribute of the Presentation State IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "WAVEFORM". Table F.5-24 lists the set of keys with their associated Types for such a Directory Record Type. The description of these keys may be found in PS3.3 of the DICOM Standard in the Modules related to the Waveform IE. This Directory Record shall be used to reference a Waveform 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-24. Waveform Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Instance Number |
(0020,0013) |
1 |
|
|
Content Date |
(0008,0023) |
1 |
|
|
Content Time |
(0008,0033) |
1 |
|
|
Any other Attribute of the Waveform IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "SR DOCUMENT". Table F.5-25 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 Observation IE of Structured Report IOD. This Directory Record shall be used to reference an SR Document. 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-25. SR Document Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Instance Number |
(0020,0013) |
1 |
|
|
Completion Flag |
(0040,A491) |
1 |
|
|
Verification Flag |
(0040,A493) |
1 |
|
|
Content Date |
(0008,0023) |
1 |
|
|
Content Time |
(0008,0033) |
1 |
|
|
Verification DateTime |
(0040,A030) |
1C |
Most recent Date and Time of verification among those defined in the Verifying Observer Sequence (0040,A073). Required if Verification Flag (0040,A493) is VERIFIED. |
|
Concept Name Code Sequence |
(0040,A043) |
1 |
Code describing the concept represented by the root Content Item (Document Title). Only a single Item shall be included in this sequence. |
|
Content Sequence |
(0040,A730) |
1C |
Contains the Target Content Items that modify the Concept Name Code Sequence of the root Content Item (Document Title). One or more Items shall be included in this Sequence. All, and only, Content Items with the HAS CONCEPT MOD relationship from the root Content Item shall be included in this Sequence. Required if the root Content Item is the Source Content Item of HAS CONCEPT MOD relationships. |
|
>Relationship Type |
(0040,A010) |
1 |
Enumerated Values:
|
|
Any Attribute of the Document IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "KEY OBJECT DOC". Table F.5-25 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 Document IE of the Key Object Selection IOD. This Directory Record shall be used to reference a Key Object Selection Document. 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-26. Key Object Document Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Instance Number |
(0020,0013) |
1 |
|
|
Content Date |
(0008,0023) |
1 |
|
|
Content Time |
(0008,0033) |
1 |
|
|
Concept Name Code Sequence |
(0040,A043) |
1 |
Code describing the concept represented by the root Content Item (Document Title). Only a single Item shall be included in this sequence. |
|
Content Sequence |
(0040,A730) |
1C |
Contains the Target Content Items that modify the Concept Name Code Sequence of the root Content Item (Document Title). One or more Items shall be included in this Sequence. All, and only, Content Items with the HAS CONCEPT MOD relationship from the root Content Item shall be included in this Sequence. Required if the root Content Item is the Source Content Item of HAS CONCEPT MOD relationships. |
|
>Relationship Type |
(0040,A010) |
1 |
Enumerated Values:
|
|
Any Attribute of the Document IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "SPECTROSCOPY." Table F.5-27 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 MR Spectroscopy IE of MR Spectroscopy IODs. This Directory Record shall be used to reference a Spectroscopy 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-27. Spectroscopy Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Image Type |
(0008,0008) |
1 |
|
|
Content Date |
(0008,0023) |
1 |
|
|
Content Time |
(0008,0033) |
1 |
|
|
Instance Number |
(0020,0013) |
1 |
|
|
Referenced Image Evidence Sequence |
(0008,9092) |
1C |
Required if present in the spectroscopy instance. One or more Items shall be included in this sequence. |
|
>Include Table C.17-3 “Hierarchical SOP Instance Reference Macro Attributes” |
|||
|
Number of Frames |
(0028,0008) |
1 |
|
|
Rows |
(0028,0010) |
1 |
|
|
Columns |
(0028,0011) |
1 |
|
|
Data Point Rows |
(0028,9001) |
1 |
|
|
Data Point Columns |
(0028,9002) |
1 |
|
|
Icon Image Sequence |
(0088,0200) |
3 |
This Icon Image is representative of the Spectroscopy instance. Only a single Item is permitted in this Sequence. |
|
See Section F.7. |
|||
|
Any other Attribute of the MR Spectroscopy IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "RAW DATA." Table F.5-28 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 Raw Data IE of Raw Data IODs. This Directory Record shall be used to reference a Raw Data 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-28. Raw Data Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Content Date |
(0008,0023) |
1 |
|
|
Content Time |
(0008,0033) |
1 |
|
|
Instance Number |
(0020,0013) |
2 |
|
|
Icon Image Sequence |
(0088,0200) |
3 |
This Icon Image is representative of the Raw Data instance. Only a single Item is permitted in this Sequence. |
|
See Section F.7. |
|||
|
Any other Attribute of the Raw Data IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "REGISTRATION." Table F.5-29 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 Spatial Registration IE of the Spatial Registration IOD. This Directory Record shall be used to reference a Spatial Registration 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-29. Registration Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Content Date |
(0008,0023) |
1 |
The date the content creation started. |
|
Content Time |
(0008,0033) |
1 |
The time the content creation started. |
|
Include Table 10-12 “Content Identification Macro Attributes” |
|||
|
Any other Attribute of the Spatial Registration IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "FIDUCIAL." Table F.5-30 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 Spatial Fiducials IE of Spatial Fiducials IOD. This Directory Record shall be used to reference a Spatial Fiducials 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-30. Fiducial Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Content Date |
(0008,0023) |
1 |
The date the content creation started. |
|
Content Time |
(0008,0033) |
1 |
The time the content creation started. |
|
Include Table 10-12 “Content Identification Macro Attributes” |
|||
|
Any other Attribute of the Spatial Fiducials IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "HANGING PROTOCOL". Table F.5-31 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 Hanging Protocol IOD. This Directory Record shall be used to reference a Hanging Protocol 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-31. Hanging Protocol Keys
|
Attribute Name |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys |
|
Hanging Protocol Name |
(0072,0002) |
1 |
|
|
Hanging Protocol Description |
(0072,0004) |
1 |
|
|
Hanging Protocol Level |
(0072,0006) |
1 |
|
|
Hanging Protocol Creator |
(0072,0008) |
1 |
|
|
Hanging Protocol Creation DateTime |
(0072,000A) |
1 |
|
|
Hanging Protocol Definition Sequence |
(0072,000C) |
1 |
Sequence that defines the type of imaging studies to which this Hanging Protocol applies. One or more Items shall be included in this sequence. |
|
>Modality |
(0008,0060) |
1C |
Required if Anatomic Region Sequence (0008,2218) is not present. May be present otherwise. |
|
>Anatomic Region Sequence |
(0008,2218) |
1C |
One or more Items shall be included in this sequence. Required if Modality (0008,0060) is not present. May be present otherwise. |
|
>Laterality |
(0020,0060) |
2C |
Required if Anatomic Region Sequence (0008,2218) is present. |
|
>Procedure Code Sequence |
(0008,1032) |
2 |
Zero or more Items shall be included in this Sequence. |
|
>Reason for Requested Procedure Code Sequence |
(0040,100A) |
2 |
Zero or more Items shall be included in this sequence. |
|
Number of Priors Referenced |
(0072,0014) |
1 |
|
|
Hanging Protocol User Identification Code Sequence |
(0072,000E) |
2 |
Sequence that provides a coded identifier for the person, group, or site for which this Hanging Protocol was defined. Zero or one Item shall be included in this Sequence. |
|
Any other Attribute of the Hanging Protocol IOD |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "ENCAP DOC." Table F.5-32 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 Encapsulated Document IE of Encapsulated IODs. This Directory Record shall be used to reference an Encapsulated Document 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.
Note
Other Encapsulated Document SOP Classes may be added to the standard in the future and these will likely be referenced by this directory record. Therefore, the MIME Type should be checked rather than assuming that the referenced file contains PDF.
Table F.5-32. Encapsulated Document Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Content Date |
(0008,0023) |
2 |
The date the content creation started. |
|
Content Time |
(0008,0033) |
2 |
The time the content creation started. |
|
Instance Number |
(0020,0013) |
1 |
A number that identifies this instance |
|
Document Title |
(0042,0010) |
2 |
The title of the document. |
|
HL7 Instance Identifier |
(0040,E001) |
1C |
Instance Identifier from the referenced HL7 Structured Document, encoded as a UID (OID or UUID), concatenated with a caret ("^") and Extension value (if Extension is present in Instance Identifier). Required if encapsulated document is an HL7 Structured Document. |
|
Concept Name Code Sequence |
(0040,A043) |
2 |
A coded representation of the document title. Zero or one Item shall be included in this sequence. |
|
Baseline CID 7020 “Document Titles”. |
|||
|
MIME Type of Encapsulated Document |
(0042,0012) |
1 |
The type of the encapsulated document stream described using the MIME Media Type (see RFC 2046). |
|
Any other Attribute of the Encapsulated Document Module except Encapsulated Document (0042,0011) |
3 |
||
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "HL7 STRUC DOC".
Table F.5-33 lists the set of keys with their associated Types for such a Directory Record Type. This Directory Record shall be used to reference an HL7 Structured Document and any of its referenced content stored on the interchange media but not encapsulated in a DICOM SOP Instance. The document may be encoded as an XML document with in-line multimedia content, or may be encoded in a multi-part MIME wrapper (see PS3.10). 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-33. HL7 Structured Document Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
HL7 Instance Identifier |
(0040,E001) |
1 |
Instance Identifier from the referenced HL7 Structured Document, encoded as a UID (OID or UUID), concatenated with a caret ("^") and Extension value (if Extension is present in Instance Identifier). |
|
HL7 Document Effective Time |
(0040,E004) |
1 |
Effective Time from the referenced HL7 Structured Document |
|
HL7 Document Type Code Sequence |
(0040,E006) |
1C |
Document Type Code from the referenced HL7 Structured Document. Only a single Item shall be included in this Sequence. Required if the HL7 Structured Document contains a Document Type Code. |
|
No BCID defined |
|||
|
Document Title |
(0042,0010) |
1C |
Document Title from the referenced HL7 Structured Document. Required if the HL7 Structured Document contains a Document Title. |
Note
This directory record points to a CDA document that is stored on this media. The HL7 Document Effective Time and other information can be obtained from the CDA document.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "VALUE MAP." Table F.5-34 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 Real World Value Mapping IE of Real World Value Mapping IOD. This Directory Record shall be used to reference a Real World Value Mapping 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-34. Real World Value Mapping Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Content Date |
(0008,0023) |
1 |
The date the content creation started. |
|
Content Time |
(0008,0033) |
1 |
The time the content creation started. |
|
Include Table 10-12 “Content Identification Macro Attributes” |
|||
|
Any other Attribute of the Real World Value Mapping IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "STEREOMETRIC". Table F.5-35 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 Stereometric Relationship IE of Stereometric Relationship IOD. This Directory Record shall be used to reference a Stereometric Relationship 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-35. Stereometric Relationship Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Any other Attribute of the Stereometric Relationship IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "PALETTE". Table F.5-36 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 Color Palette IOD. This Directory Record shall be used to reference a Color Palette 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-36. Palette Keys
|
Attribute Name |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys |
|
Content Label |
(0070,0080) |
1 |
A label that is used to identify the palette. |
|
Content Description |
(0070,0081) |
2 |
A description of the content of the palette. |
|
Any other Attribute of the Color Palette IOD |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "IMPLANT". Table F.5-37 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 Generic Implant Template IOD. This Directory Record shall be used to reference a Generic Implant Template SOP Instance.
Table F.5-37. Implant Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Manufacturer |
(0008,0070) |
1 |
Name of the manufacturer that produces the implant. |
|
Implant Name |
(0022,1095) |
1 |
The (product) name of the implant. |
|
Implant Size |
(0068,6210) |
1C |
The size descriptor of the component. Required if present in the referenced instance. |
|
Implant Part Number |
(0022,1097) |
1 |
The (product) identifier of the implant. |
Note
Because (0004,1511) Referenced SOP Instance UID in File may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "IMPLANT ASSY". Table F.5-38 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 Implant Assembly Template IOD. This Directory Record shall be used to reference an Implant Assembly Template SOP Instance.
Table F.5-38. Implant Assembly Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Implant Assembly Template Name |
(0076,0001) |
1 |
A name given to the assembly described in this instance. |
|
Manufacturer |
(0008,0070) |
1 |
Name of the manufacturer that produces the implant. |
|
Procedure Type Code Sequence |
(0076,0020) |
1 |
A code describing the Intervention in which the implant is used. One or more Items shall be included in this sequence. |
Note
Because (0004,1511) Referenced SOP Instance UID in File may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "IMPLANT GROUP". Table F.5-39 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 Implant Template Group IOD. This Directory Record shall be used to reference an Implant Template Group SOP Instance.
Table F.5-39. Implant Group Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Implant Template Group Name |
(0078,0001) |
1 |
Name of this group |
|
Implant Template Group Description |
(0078,0010) |
3 |
Purpose or intent of this group. |
|
Implant Template Group Issuer |
(0078,0020) |
1 |
Person or Organization that issued this group. |
Note
Because (0004,1511) Referenced SOP Instance UID in File may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "PLAN". Table F.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 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-40. Plan Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Any other Attribute of the Plan IE Modules |
3 |
||
Note
Because Referenced SOP Instance UID in File (0004,1511) may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
The Directory Record is based on the specification of Section F.3. It is identified by a Directory Record Type of Value "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
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Content Date |
(0008,0023) |
1 |
The date the content creation started. |
|
Content Time |
(0008,0033) |
1 |
The time the content creation started. |
|
Include Table 10-12 “Content Identification Macro Attributes” |
|||
|
Any other Attribute of the Measurements IE Modules |
3 |
||
Note
Because (0004,1511) Referenced SOP Instance UID in File may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
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.
Table F.5-42. Surface Keys
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Content Date |
(0008,0023) |
1 |
The date the content creation started. |
|
Content Time |
(0008,0033) |
1 |
The time the content creation started. |
|
Include Table 10-12 “Content Identification Macro Attributes” |
|||
|
Any other Attribute of the Surface IE Modules |
3 |
||
Note
Because (0004,1511) Referenced SOP Instance UID in File may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.
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
|
Key |
Tag |
Type |
Attribute Description |
|---|---|---|---|
|
Specific Character Set |
(0008,0005) |
1C |
Required if an extended or replacement character set is used in one of the keys. |
|
Content Date |
(0008,0023) |
1 |
The date the content creation started. |
|
Content Time |
(0008,0033) |
1 |
The time the content creation started. |
|
Any other Attribute of the Surface IE Modules |
3 |
||
Note
Because (0004,1511) Referenced SOP Instance UID in File may be used as a "pseudo" Directory Record Key (see Table F.3-3), it is not duplicated in this list of keys.