Annex F Basic Directory Information Object Definition (Normative)

F.1 SCOPE OF THE BASIC DIRECTORY INFORMATION IOD

The Basic Directory Information Object Definition may be used for DICOM Media Storage (See PS 3.10) and the Media Storage Service Class (See PS 3.4). It is an abstraction of the information to:

a. Identify a File-set

b. Provide a directory which facilitates access to the information stored in the files of a File-set based on key medical information. Such a directory facility relies on a hierarchical information model of medical summary information referencing the content of the Files stored in a File-set on a storage medium. Standardizing such a directory function is a key element to facilitate the interchange of medical imaging data and is intended to support the complete range of modality imaging information.

Note: The directory information has been defined so that a future version of this Part may be extended to support the distribution of the directory information among a logical tree of several files (with the DICOMDIR file at its root). However in this version of this Part, the entire directory information is specified to be stored in a single File with a DICOMDIR File ID.

[pic]Figure F.1-1 THE DICOMDIR FILE. A CENTRAL ROLE IN A DICOM FILE-SET

Notes: 1. Whether a single File-set or multiple File-sets are allowed on a formatted Physical Media is defined by the Media Format specification (used for each specific Physical Media) in PS 3.12.

2. The DICOMDIR File is identified by a single component File ID, DICOMDIR. Other files in the File-set may have File IDs made of a single component (e.g. "ABGT" in the figure above) or multiple components (e.g. AB\12 or AB\CDE\FI) not to exceed 8 components (See PS 3.10).

This Basic Directory Information Object:

a. is based on a structure of basic medical information. It is not a file system directory such as the one which may be used by the Media Format Layer;

b. is simple enough to meet the requirements of elementary Media Interchange applications;

c. is efficient in supporting update to the directory on rewritable media without a complete rewrite of the entire DICOMDIR File;

d. is extendible for specific applications with specialized selection keys in addition to the standard keys;

e. does not mandate any relationship between the hierarchy of the medical information in the DICOM Directory and the hierarchy of the File ID Components;

Note: Such an independence between the structure of the file identifiers, from which no semantical information shall be inferred, and the DICOM Directory which conveys medical imaging information, ensures that the broadest inter-operability is possible between conforming DICOM media storage implementations.

F.2 Basic directory IOD overview

The general organization of the Basic Directory IOD is introduced in this Section. A simple example is also provided to illustrate the application of this organization.

F.2.1 Basic directory IOD organization

The Basic Directory IOD organization is based on a hierarchy of Directory Entities. At the origin of this inverted tree is a root Directory Entity. Each Directory Entity includes one or more Directory Records which in turn, may each reference a lower level Directory Entity.

Directory Records serve to reference objects stored in the Files of the File-set. The organization of the Directory is depicted by the Basic Directory IOD entity/relationship model presented in Figure F.2-1.

Each Directory Record, irrespective of the Directory Entity it is included in, contains four types of information:

a. A reference to a lower level Directory Entity or Referenced Directory Entity. This reference may be absent if such a lower level Directory Entity does not exist for an instance of a directory record;

b. A reference to a File of the File-set in which is stored a "Referenced Object" (formally called in DICOM a Referenced SOP Instance). This reference may be absent if no File is referenced. Files may be referenced directly by their File ID;

c. A set of "selection keys," specific to a Referenced Object, which will allow its selection among all the records included in a given Directory Entity;

d. A mechanism to chain the various Directory Records which belong to the same Directory Entity.

This generic content of a Directory Record is further specialized based on its specific type in the context the Basic Directory IOD Information Model specified in Section F.4 (e.g., a Study Record, a Series Record, etc.). A Directory Entity may include Directory Records of different Types. By standardizing a number of specific Directory Records (see Section F.5) in the context of the Basic Directory IOD Information Model, one allows the definition of a variety of directory contents while maintaining a framework for interoperability.

[pic]

Figure F.2-1 BASIC DIRECTORY INFORMATION OBJECT E-R MODEL

To facilitate the management and update of the Directory Information a number of rules are defined:

a. Any Lower-Level Directory Entity shall be referenced by at most one higher-level Directory Record. Not allowing multiple higher-level Directory Records to reference the same Lower-Level Directory Entity simplifies the management of the deletion (or inactivation) of Directory Records and Lower-Level Directory Entities and associated Directory Records

b. Any Directory Record shall belong to a single Directory Entity. This rule and the above rule, makes the Basic Directory IOD itself strictly hierarchical

c. All files referenced by a Directory shall be present in the same File-Set to which the directory belongs

d. Non-DICOM files which are not referenced by the Directory may be included in the File-set space. The means of access to such Files and the semantics associated with their absence from the Directory is beyond the scope of the DICOM Standard

e. If a DICOMDIR contains a Directory Information Module, all DICOM Files of the File-set shall be referenced by a Directory Record

f. Any File of the File-set shall be directly referenced by at most one Directory Record of the Directory.

Note: Referenced Files may contain SOP Instances of SOP Classes which provide the means to reference by UIDs other SOP Instances which may not be stored in files of the same File-set.

F.2.2 Example of a directory

The example provided in this Section is only one simple example of a possible directory content and organization. This Section is not normative in nature. Therefore, this example is not meant to specify a conformant directory nor to restrict the range of possible directory organizations supported by this Part of the DICOM Standard.

The overall organization is illustrated at a logical level in Section F.2.2.1. The actual structure of the content is discussed in Section F.2.2.2. Two Annexes of PS 3.10 provide example where further details of the encoding of the file content is depicted.

F.2.2.1 Illustration of the Overall Directory Organization

A simple directory content is used as an example of Directory organization. It is depicted by Figure F.2-2. The left hand side part of Figure F.2-2 depicts the various Objects stored in Files of the File-set. The right hand side presents an example of organization of the directory which facilitates access to the Files of the File-set.

This example shows how stored Files are referenced by Directory Records which are grouped into Directory Entities. The two Study Directory Records (Study 1 and Study 2) are part of the Directory Entity relative to the Patient A.

Thin curved lines depict the referencing mechanism based on File IDs which allow reference to Files containing stored objects. Thick curved lines depict the internal referencing mechanisms which support the reference to a lower-level Directory Entity by a Directory Record,.

Keys which are used to select a specific Directory Record from among the Directory Records of a Directory Entity are not shown on Figure F.2-2.

One may note in this example that certain Directory Records such as the Series Directory Records do not reference Files containing stored objects. Other Directory Records such as the Image Directory Records do not reference lower level Directory Entities. However, a number of Directory Records reference both one lower level Directory Entity and one File containing a stored object. This flexibility allows the definition of a variety of directories.

[pic]

Figure F.2-2EXAMPLE OF A DIRECTORY ORGANIZATION AND CONTENT

F.2.2.2 Example of a DICOMDIR File Structure

Based on the example discussed in Section F.2.2.1, the internal data structure used by the Basic Directory IOD is depicted in Figure F.2-3. It shows a set of Directory Records where each Directory Record is linked by three different types of "referencing" mechanisms:

a. The chaining of Directory Records to form a Directory Entity. In particular, this facilitates the addition of new Directory Records at the level of any Directory Entity by placing them at the end of the DICOMDIR File. On Figure F.2-3, these chainings are shown by dotted lines:

1. #1 shows the chaining of the Directory Records forming the root Directory Entity

2. #2 shows the chaining of the Directory Records for the Directory Entity related to Patient A

3. #3 shows the chaining of the Directory Records for the Directory Entity related to Study 1

4. #4 shows the chaining of the Directory Records for the Directory Entity related to Series 1

b. Thick curved lines depict the reference by a Directory Record to a lower level Directory Entity

c. Thin curved lines depict the reference by a Directory Record to a stored file containing a SOP Class

This example of a DICOMDIR File structure shows one example of a specific order of the Directory Records. Other orderings of Directory Records could result in a functionally equivalent directory.

[pic]

Figure F.2-3EXAMPLE OF DATA STRUCTURE FOR THE DICOM DIRECTORY INFORMATION

F.3 Basic directory information object definition

This IOD is based on the Directory Information organization introduced in Section F.2. The model for this Basic Directory IOD is described Section F.2.1 by the Entity/Relationship model in Figure F.2-1. The rules specified in Section F.2.1 apply to this Information Object Definition.

F.3.1 Module table

The Basic Directory IOD includes the Modules specified by Table F.3-1.

Table F.3-1BASIC DIRECTORY IOD MODULES

Module Reference Usage Module Description
File-set Identification F.3.2.1 M File-set identification information
Directory Information F.3.2.2 U Directory Information followed by a Sequence of Directory Records. Note: The Directory Information Module is optional. This Directory Information Module should be present in all but primitive environments where a directory is not needed. In this case, only the File-set Identification Information is present.

F.3.2 Modules of the basic directory information object

Attributes of the Basic Directory IOD are defined with a Type designation which indicates if a specific Attribute is required for all Media Storage Operations (See Section 5, Conventions).

F.3.2.1 File-set Identification Module

Table F.3-2FILE-SET IDENTIFICATION MODULE

Attribute Name Tag Type Attribute Description
File-set ID (0004,1130) 2 User or implementation specific Identifier (up to 16 characters). For definition, see PS 3.10. The File-set ID is intended to be a short human readable label to easily (but not necessarily uniquely) identify a specific File-set to facilitate operator manipulation of the physical media on which the File-set is stored. Assignment of Value and semantics are environment specific.
File-set Descriptor File ID (0004,1141) 3 ID of a File (in the same File-set) used for user comments related to the File-set (e.g. a readme file). The Specific Character set used may be specified in the Specific Character Set of the File-set Descriptor File (0004,1142). Note: This File is not DICOM formatted (no Preamble, nor DICM Prefix and Meta Information).
Specific Character Set of File-set Descriptor File (0004,1142) 1C Character set used in the File-set Descriptor File with a File ID as specified in File-set Descriptor File ID (0004,1141). Required to specify the expanded or replacement character set. If absent, only the Basic Graphic set is used. See C.12.1.1.2 for Defined Terms.

Note: Every File-set is assigned a File-set UID when created. The File-set UID need not be duplicated as a Type 1 Attribute of the File-set Identification Module. It is conveyed as the SOP Instance UID of the Basic Directory IOD. It is included in the DICOMDIR File Meta Information (See PS 3.10)

F.3.2.2 Directory Information Module

This Module contains a sequence of Directory Records forming one or more Directory Entities. This Module defines at least one Directory Entity, the Root Directory Entity (which may be empty). Each Directory Record is composed of Directory Elements (marked by a ">"). They include:

a. an offset pointer to another Directory Record of the Same Directory Entity

b. an offset pointer to a lower level Directory Entity

c. a Referenced File pointed to by the Directory Record

d. a set of keys representative of the information contained in the Referenced File

Table F.3-3DIRECTORY INFORMATION MODULE

Attribute Name Tag Type Attribute Description
Offset of the First Directory Record of the Root Directory Entity (0004,1200) 1 Offset of the first byte (of the Item Data Element) of the first Directory Record of the Root Directory Entity. This Offset is a number of bytes starting with the first byte of the File Meta Information. When the Root Directory Entity contains no Directory Record, this offset shall be set to 00000000H. Note: This offset includes the File Preamble and the DICM Prefix.
Offset of the Last Directory Record of the Root Directory Entity (0004,1202) 1 Offset of the first byte (of the Item Data Element) of the last Directory Record of the Root Directory Entity. This Offset is a number of bytes starting with the first byte of the File Meta Information. When the Root Directory Entity contains no Directory Record, this offset shall be set to 00000000H. Note: This offset includes the File Preamble and the DICM Prefix.
File-set Consistency Flag (0004,1212) 1 Enumerated Value: 0000H: no known inconsistencies The value FFFFH shall never be sent. Note: Formerly, this Attribute was intended to signal that the directory was in an inconsistent state with a value of FFFFH. This usage has been retired. See PS 3.3 2008.
Directory Record Sequence (0004,1220) 2 Sequence of zero or more Items where each Item contains a Directory Record by including the Directory Elements from (0004,1400) to (0004,1511) and Record selection Keys as defined below (marked with a >). A zero length Value indicates that no Directory Records are contained in the Root Directory Entity.
>Offset of the Next Directory Record (0004,1400) 1 Offset of the first byte (of the Item Data Element) of the next Directory Record of the same Directory Entity. This Offset is an unsigned integer representing a number of bytes starting with the first byte of the File Meta-information. A zero offset shall be used to mean that there is no other Directory Record in this Directory Entity. This Offset may be used to keep an inactive Record (0004,1410) chained with the next Directory Record of the same Directory Entity. Note: This offset includes the File Preamble and the DICM Prefix.
>Record In-use Flag (0004,1410) 1 Enumerated Value: FFFFH = record is in use. The value 0000H shall never be sent. Note: Formerly, this Attribute was intended to facilitate the deletion of files, with a value 0000H signally an inactive record. This usage has been retired. See PS 3.3 2008. Other Values are reserved and shall not be set by File-set Creators, but if present shall be interpreted as FFFFH by File-set Readers or Updaters.
>Offset of Referenced Lower-Level Directory Entity (0004,1420) 1 Offset of the first byte (of the Item Data Element) of the first Directory Record of the Referenced Lower Level Directory Entity. This Offset is a number of bytes starting with the first byte of the File Meta Information. When no lower-level Directory Entity (containing at least one Directory Record) is referenced, this Attribute shall have a Value of 00000000H. Note: This offset includes the File Preamble and the DICM Prefix.
>Directory Record Type (0004,1430) 1 Defines a specialized type of Directory Record by reference to its position in the Media Storage Directory Information Model (see Section F.4). Enumerated Values (see Section F.5): PATIENT STUDY SERIES IMAGE RT DOSE RT STRUCTURE SET RT PLAN RT TREAT RECORD PRESENTATION WAVEFORM SR DOCUMENT KEY OBJECT DOC SPECTROSCOPY RAW DATA REGISTRATION FIDUCIAL HANGING PROTOCOL ENCAP DOC HL7 STRUC DOC VALUE MAP STEREOMETRIC PALETTE IMPLANT IMPLANT GROUP IMPLANT ASSY MEASUREMENT SURFACE PRIVATE = Privately defined record hierarchy position. Type shall be defined by Private Record UID (0004,1432). Notes: 1. Enumerated Values PRINT QUEUE, FILM SESSION, FILM BOX, and IMAGE BOX were previously defined in DICOM for this Attribute. They are now retired. See PS3.3-1998. 2. Enumerated Values OVERLAY, MODALITY LUT, VOI LUT, CURVE, TOPIC, VISIT, RESULTS, INTERPRETATION, STUDY COMPONENT and STORED PRINT were previously defined in DICOM for this Attribute. They are now retired. See PS3.3-2004. 3. Enumerated Value MRDR was previously defined in DICOM for this Attribute, to allow indirect reference to a File by multiple Directory Records. It is now retired. FSUs and FSRs are unlikely to be capable of supporting this mechanism. See PS3.3-2004.
>Private Record UID (0004,1432) 1C Required if the Directory Record Type (0004,1430) is of Value PRIVATE. This UID is used to define a non-standard type of Directory Record by reference to its position in a private extension to the Basic Directory IOD Information Model (see Section F.5). This UID shall be registered according to the procedures defined in PS 3.5. Its meaning may or may not be specified in a Conformance Statement.
>Referenced File ID (0004,1500) 1C A Multiple Value (See PS 3.5) which represents the ordered components of the File ID containing a "referenced object" or Referenced SOP Instance. A maximum of 8 components, each from 1 to 8 characters shall be used (see Section 8.2). Note: The Referenced File ID provides the means to "locate" the File through the DICOM File Service provided by the Media Format Layer. All referenced Files shall be with the File-set to which the Directory belongs. Any File within the File-set (to which the Directory belongs) shall be referenced by at most one Directory Record. When the Directory Record does not reference any SOP Instance this attribute shall not be present.
>Referenced SOP Class UID in File (0004,1510) 1C Unique ID for the SOP Class of the Instance stored in the referenced File. Required if the Directory Record references a SOP Instance.
>Referenced SOP Instance UID in File (0004,1511) 1C Unique Identifier for the SOP Instance stored in the referenced file. Required if the Directory Record references a SOP Instance.
>Referenced Transfer Syntax UID in File (0004,1512) 1C Unique Identifier for the Transfer Syntax used to encode the Instance stored in the referenced file. Required if the Directory Record references a SOP Instance.
>Referenced Related General SOP Class UID in File (0004,151A) 1C Unique ID for the Related General SOP Class(es) related to the SOP Class of the Instance stored in the referenced file. Required if the Directory Record references a SOP Instance that encodes the Related General SOP Class UID (0008,001A). Note: This may be useful to an FSR that does not support the SOP Class of the referenced Instance, but which does support one of the Related General SOP Classes.
>Record Selection Keys See F.5 See F.5 A number of DICOM Data Elements which contain specific keys defined for each type of Directory Record (0004,1430) defined in Section F.5.

F.4 Basic directory IOD information model

The Basic Directory IOD Information Model defines the relationship between the various types of Directory Records that may be used in constructing DICOM Directories. This model is based on the DICOM Application Model defined in this part of the DICOM Standard. Entities in this Model correspond to Directory Records (DR). These are shown as rectangular boxes. Each Directory Record in this model is part of a Directory Entity (not shown except for the Root Entity) which is referenced by a Directory Record of a higher-level Directory Entity (e.g., a Study Directory Record references a Directory Entity which includes Directory Records describing the content of the Study).

Each Directory Record has a number of mandatory and optional keys which are not shown on this model. They are defined in Section F.5. Conventions used are those used by this part of the DICOM Standard. The model is depicted as an entity/relationship model in Figure F.4-1. These Directory Record relationships are fully specified in Table F.4-1.

Table F.4-1RELATIONSHIP BETWEEN DIRECTORY RECORDS

Directory Record Type Section Directory Record Types which may be included in the next lower-level directory Entity
(Root Directory Entity) PATIENT, HANGING PROTOCOL, PALETTE, IMPLANT, IMPLANT ASSY, IMPLANT GROUP, PRIVATE
PATIENT F.5.1 STUDY, HL7 STRUC DOC, PRIVATE
STUDY F.5.2 SERIES, PRIVATE
SERIES F.5.3 IMAGE, RT DOSE, RT STRUCTURE SET, RT PLAN, RT TREAT RECORD, PRESENTATION, WAVEFORM, SR DOCUMENT, KEY OBJECT DOC, SPECTROSCOPY, RAW DATA, REGISTRATION, FIDUCIAL, ENCAP DOC, VALUE MAP, STEREOMETRIC, PLAN, MEASUREMENT, SURFACE, PRIVATE
IMAGE F.5.4 PRIVATE
RT DOSE F.5.19 PRIVATE
RT STRUCTURE SET F.5.20 PRIVATE
RT PLAN F.5.21 PRIVATE
RT TREAT RECORD F.5.22 PRIVATE
PRESENTATION F.5.23 PRIVATE
WAVEFORM F.5.24 PRIVATE
SR DOCUMENT F.5.25 PRIVATE
KEY OBJECT DOC F.5.26 PRIVATE
SPECTROSCOPY F.5.27 PRIVATE
RAW DATA F.5.28 PRIVATE
REGISTRATION F.5.29 PRIVATE
FIDUCIAL F.5.30 PRIVATE
HANGING PROTOCOL F.5.31 PRIVATE
ENCAP DOC F.5.32 PRIVATE
HL7 STRUC DOC F.5.33 PRIVATE
VALUE MAP F.5.34 PRIVATE
STEREOMETRIC F.5.35 PRIVATE
PALETTE F.5.36 PRIVATE
IMPLANT F.5.37 PRIVATE
IMPLANT ASSY F.5.38 PRIVATE
IMPLANT GROUP F.5.39 PRIVATE
PLAN F.5.40 PRIVATE
MEASUREMENT F.5.41 PRIVATE
SURFACE F.5.42 PRIVATE
PRIVATE F.6.1 PRIVATE, (any of the above as privately defined)

Notes: 1. Directory Record Types PRINT QUEUE, FILM SESSION, FILM BOX, and IMAGE BOX were previously defined in DICOM. They have been retired. See PS 3.3-1998.

2. Directory Record Types OVERLAY, MODALITY LUT, VOI LUT, CURVE, TOPIC, VISIT, RESULTS, INTERPRETATION, STUDY COMPONENT, STORED PRINT and MRDR were previously defined in DICOM. They have been retired. See PS 3.3-2004.

F.5 Definition of specific directory records

The following Sections specify a number of Directory Records which were introduced by the Basic Directory IOD Information Model presented in Section F.4. For each one, it identifies the SOP Classes which may be referenced and the related mandatory keys. Keys are assigned a Type designation which indicates if it is required for all Media Storage Operations of the Directory (See Section 5, Conventions).

Type 2 and Type 3 Keys may be changed to Type 1 and Type 2 or 3 respectively by Application Profiles defined in PS 3.11 of the DICOM standard. 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.

[pic]

Figure F.4-1BASIC DIRECTORY IOD INFORMATION MODEL

Note: Normalized Print media storage was previously defined in DICOM. It is now retired. See PS3.3 -1998.

F.5.1 Patient 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 "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-1PATIENT 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 IOD or 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.

F.5.2 Study 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 "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-2STUDY 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 IOD or 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.

F.5.3 Series 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 "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-3SERIES 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.
>Include ‘Image Pixel Macro’ Table C.7-11b See Section F.7 of this Part.
Any other Attribute of the Series IE Modules 3

F.5.4 Image 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 "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-4IMAGE 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.
>Include ‘Image Pixel Macro’ Table C.7-11b See Section F.7 of this Part.
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.

F.5.5 Standalone overlay directory record definition

Retired. See PS 3.3-2004.

F.5.6 Standalone modality LUT directory record definition

Retired. See PS 3.3-2004.

F.5.7 Standalone VOI LUT directory record definition

Retired. See PS 3.3-2004.

F.5.8 Standalone curve directory record definition

Retired. See PS 3.3-2004.

F.5.9 Topic directory record definition

Retired. See PS 3.3-2004.

F.5.10 Visit directory record definition

Retired. See PS 3.3-2004.

F.5.11 Results directory record definition

Retired. See PS 3.3-2004.

F.5.12 Interpretation directory record definition

Retired. See PS 3.3-2004.

F.5.13 Study component directory record definition

Retired. See PS 3.3-2004.

F.5.14 Print Queue Directory Record Definition

This section was previously defined in DICOM. It is now retired. See PS 3.3-1998.

F.5.15 Film session directory record definition

This section was previously defined in DICOM. It is now retired. See PS 3.3-1998.

F.5.16 Film box directory record definition

This section was previously defined in DICOM. It is now retired. See PS 3.3-1998.

F.5.17 Basic image box directory record definition

This section was previously defined in DICOM. It is now retired. See PS 3.3-1998.

F.5.18 Stored Print Directory Record Definition

Retired. See PS 3.3-2004.

F.5.19 RT Dose Directory Record Definition

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.
>Include ‘Image Pixel Macro’ Table C.7-11b See Section F.7 of this part.
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.

F.5.20 RT Structure Set Directory Record Definition

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.

F.5.21 RT Plan Directory Record Definition

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.

F.5.22 RT Treatment Record Directory Record Definition

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.

F.5.23 Presentation State 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 "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 IODs. This Directory Record shall be used to reference a Softcopy Presentation State Storage 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-23PRESENTATION 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. Note: This date may be different from the date that the DICOM SOP Instance was created, since the presentation state information contained may have been recorded earlier.
Presentation Creation Time (0070,0083) 1 Time at which this presentation was created. Note: This time may be different from the time that the DICOM SOP Instance was created, since the presentation state information contained may have been recorded earlier.
Include Content Identification Macro Table 10-12
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 ‘SOP Instance Reference Macro' Table 10-11
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 the Blending Sequence (0070,0402) attribute.
>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 ‘SOP Instance Reference Macro' Table 10-11
Any other Attribute of the Presentation 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.

F.5.24 Waveform 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 "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 PS 3.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-24WAVEFORM 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.

F.5.25 SR Document 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 "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-25SR 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.
>Include Code Sequence Macro Table 8.8-1
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 Value: HAS CONCEPT MOD
>Include Document Content Macro Table C.17-5
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.

F.5.26 Key Object Document 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 "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-26KEY 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.
>Include Code Sequence Macro Table 8.8-1
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 Value: HAS CONCEPT MOD
>Include Document Content Macro Table C.17-5
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.

F.5.27 Spectroscopy 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 "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 Spectroscopy IE of 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-27SPECTROSCOPY 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 '’Hierarchical SOP Instance Reference Macro' Table C.17-3
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.
>Include Image Pixel Macro Table C.7-11b See Section F.7 of this Part.
Any other Attribute of the 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.

F.5.28 Raw Data 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 "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-28RAW 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.
>Include Image Pixel Macro Table C.7-11b See Section F.7 of this Part.
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.

F.5.29 Registration 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 "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-29REGISTRATION 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 Content Identification Macro Table 10-12
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.

F.5.30 Fiducial 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 "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-30FIDUCIAL 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 Content Identification Macro Table 10-12
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.

F.5.31 Hanging Protocol 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 “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 which 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.
>>Include Code Sequence Macro Table 8.8-1
>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.
>>Include Code Sequence Macro Table 8.8-1
>Reason for Requested Procedure Code Sequence (0040,100A) 2 Zero or more Items shall be included in this sequence.
>>Include Code Sequence Macro Table 8.8-1
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.
>Include Code Sequence Macro Table 8.8-1
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.

F.5.32 Encapsulated Document 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 "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-32Encapsulated 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.
>Include ‘Code Sequence Macro’ Table 8.8-1 1 Baseline Context Group 7020
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

F.5.33 HL7 Structured Document 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 "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-33HL7 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.
>Include ‘Code Sequence Macro’ Table 8.8-1 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.

F.5.34 Real World Value Mapping 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 "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-34REAL 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 Content Identification Macro Table 10-12
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.

F.5.35 Stereometric Relationship 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 "STEREOMETRIC." Table F.5-xx 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-35STEREOMETRIC 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.

F.5.36 Palette 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 “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 which 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.

F.5.37 Implant 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 "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-37IMPLANT 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.

F.5.38 Implant Assembly 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 „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-38IMPLANT 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.
>Include ‘Code Sequence Macro’ Table 8.8-1

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.

F.5.39 Implant Group 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 "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-39IMPLANT GROUP KEYS

Key Tag Type Attribute Description
Implant Template Group Name (0078,0000) 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.

F.5.40 Plan 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 "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 Instance-level IEs of Plan IODs. 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-40PLAN 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 Instance-level 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.

F.5.41 Measurement 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 "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 Measurement 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-41MEASUREMENT 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 Content Identification Macro Table 10-12
Any other Attribute of the Measurement 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.

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.

Table F.5-42SURFACE 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 Content Identification Macro Table 10-12
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.

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 Sections F.2 and 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 DICOM PS 3.10 conformance requirements. Thus a File-set Reader or File-set Updater which chooses to ignore such privately defined Directory Records will find a conformant Directory.

F.6.2 Multi-referenced file directory record definition

Retired. See PS 3.3-2004.

F.7 Icon Image Key Definition

An Icon Image may be used as a key representative of an Image, RT Dose, or Series in a corresponding Directory Record to allow an application to display icons which 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 which 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 Section 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 environments. 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. Pixel samples have a Value of either 1 or 8 for Bits Allocated (0028,0100) and Bits Stored (0028,0101). High Bit (0028,0102) shall have a Value of one less than the Value used in Bit Stored

d. Pixel Representation (0028,0103) shall used 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, an 8 Bit Allocated (0028,0100) shall be used