| DICOM PS3.3 2024d - Information Object Definitions |
|---|
Table C.38.1-1 specifies the Attributes of the Inventory Module.
The Attributes of the Information Entities of the Inventory Information Model (such as Study, Series, Patient, etc. - see Section 7.13.6) are hierarchically encoded within Sequence Attributes in this Module.
Table C.38.1-1. Inventory Module Attributes
|
With Content Time (0008,0033), time point at which the Inventory creation began. See Section C.38.1.1.1. |
|||
|
With Content Date (0008,0023), time point at which the Inventory creation began. See Section C.38.1.1.1. |
|||
|
Include Table C.38.2-1 “Scope of Inventory Macro Attributes” |
Selection parameters for the studies that are included in the inventory. See Section C.38.1.1.2. |
||
|
UID of the transaction that initiated creation of this Inventory SOP Instance. Required if Inventory creation was initiated by a transaction of the Inventory Creation SOP Class. May be present otherwise to identify a local user-initiated or system-initiated Inventory creation. |
|||
|
Description of the content of this Inventory SOP Instance, such as limitation of the scope of this Instance within the Scope of Inventory. |
|||
|
Degree of completion of Inventory with respect to the defined Scope of Inventory. See Section C.38.1.1.3. |
|||
|
Number of Items in the Inventoried Studies Sequence (0008,0423) in this SOP Instance. |
|||
|
Total number of Items in the Inventoried Studies Sequence (0008,0423) in this SOP Instance and in SOP Instances referenced in the Incorporated Inventory Instance Sequence (0008,0422). |
|||
|
Baseline end point(s) for network protocols to access incorporated Inventory SOP Instances. See Section C.38.1.1.4. |
|||
|
>Include Table C.38.2-4 “Access End Points Macro Attributes” |
|||
|
Baseline end point(s) for network protocols to access inventoried Study-related SOP Instances. See Section C.38.1.1.4. |
|||
|
>Include Table C.38.2-4 “Access End Points Macro Attributes” |
|||
|
Inventory SOP Instances whose content is included by reference. See Section C.38.1.1.5. |
|||
|
>Include Table C.38.2-3 “Inventory Reference Macro Attributes” |
|||
|
Records of Studies whose Attribute values match the Scope of Inventory. See Section C.38.1.1.6. |
|||
|
Character Set that expands or replaces the Basic Graphic Set for this Item. Required if an extended or replacement character set, other than those specified in the top level Data Set of the Inventory, is used in the Study level Attributes. May be present otherwise. |
|||
|
All of the distinct values used for Modality (0008,0060) in the Series of the Study. |
|||
|
DateTime of creation of the Inventory information for this Item. All Study Attributes in this Sequence Item are correct as of this DateTime. The value shall be at or after the Content Date (0008,0023) and Content Time (0008,0033) of this Inventory SOP Instance. NoteThis Attribute may be used for Study record reconciliation. See Section YYYY.7.10 in PS3.17. |
|||
|
Flag that this Study is not to be used for operational purposes. See Section C.38.1.2.2. Required if this Study is not to be used for operational purposes. May be present otherwise. |
|||
|
Reason the Study was removed from operational use. Required if Removed from Operational Use (0008,0405) value is Y. |
|||
|
Defined Context Group DCID 7031 Reason for Removal from Operational Use. |
|||
|
Count of stored Series in Study. See Section C.38.1.2.3. |
|||
|
Count of stored SOP Instances in Study. See Section C.38.1.2.3. |
|||
|
DateTime of last update to Study instances or metadata managed in the storage system. See Section C.38.1.2.1. |
|||
|
Anatomic regions and body parts examined in the study. See Section C.38.1.2.4. |
|||
|
Identification of the physician(s) reading the Study. One or more Items are permitted in this Sequence. If more than one Item, the number and order shall correspond to the value of Name of Physician(s) Reading Study (0008,1060), if present. |
|||
|
>>Include Table 10-1 “Person Identification Macro Attributes” |
|||
|
Identification of the consulting physician(s). One or more Items are permitted in this Sequence. If more than one Item, the number and order shall correspond to the value of Consulting Physician's Name (0008,009C), if present. |
|||
|
>>Include Table 10-1 “Person Identification Macro Attributes” |
|||
|
Names of the physician(s) who are responsible for overall Patient care at time of Study. |
|||
|
Identification of the physician(s) who are responsible for overall Patient care at time of Study. One or more Items are permitted in this Sequence. If more than one Item, the number and order shall correspond to the value of Physician(s) of Record (0008,1048), if present. |
|||
|
>>Include Table 10-1 “Person Identification Macro Attributes” |
|||
|
>Include Table C.12.1.1.9-1 “Original Attributes Macro Attributes” |
Recording of prior Attribute values and provenance of metadata changes at the Study level. See Section C.38.1.2.5. |
||
|
AE Title from which this Study may be retrieved. Required if SOP Instances for this Study may be retrieved using a C-MOVE or C-GET based SOP Class (see PS3.4) and Study Access End Points Sequence (0008,0421) does not include Retrieve AE Title (0008,0054). May be present otherwise. |
|||
|
Base URI of the origin server to retrieve Study data through the Studies Service (see Section 10 “Studies Service and Resources” in PS3.18). Required if SOP Instances for this Study may be retrieved using the web-based Studies Service (see PS3.18) and Study Access End Points Sequence (0008,0421) does not include Retrieve URL (0008,1190). May be present otherwise. |
|||
|
Base URI for accessing SOP Instances for this Study through a non-DICOM protocol. See Section C.38.1.2.6. |
|||
|
Specifies how rapidly the SOP Instances for this Study become available for transmission after a retrieval request. See Section C.38.1.2.9. |
|||
|
Non-DICOM protocol methods to access the set of stored SOP Instances for this Study. Note"File Set" as used here may not be identical to the File-set concept defined in PS3.10 and used in Storage Media File-set ID (0088,0130). |
|||
|
Access URI for a folder containing all SOP Instances for this Study. See Section C.38.1.2.7. |
|||
|
Access URI for a container file containing all SOP Instances for this Study. See Section C.38.1.2.7. |
|||
|
Type of container file. See Section C.38.1.2.8 for Defined Terms. |
|||
|
A human readable Identifier that identifies the Storage Media on which the Study resides. |
|||
|
Identifier of the Assigning Authority that issued the Accession Number (0008,0050). |
|||
|
>>Include Table 10-17 “HL7v2 Hierarchic Designator Macro Attributes” |
|||
|
>>Include Table 10-1 “Person Identification Macro Attributes” |
|||
|
>Include Table 10-18 “Issuer of Patient ID Macro Attributes” |
Identifier of the Assigning Authority that issued the Patient ID (0010,0020). |
||
|
Identification numbers or codes used to identify the Patient. |
|||
|
>>Include Table 10-18 “Issuer of Patient ID Macro Attributes” |
Identifier of the Assigning Authority that issued the Patient ID (0010,0020). |
||
|
Records of Series whose Study and Series Attribute values match the Scope of Inventory. See Section C.38.2.1.1.2 for conditions with RELATIONAL matching for Scope of Inventory in which only matching Series will be included in the Inventory. Required if Inventory Level (0008,0403) has value SERIES or INSTANCE. |
|||
|
Character Set that expands or replaces the Basic Graphic Set for this Item. Required if an extended or replacement character set, other than those specified or implied for the Study level Attributes, is used in the Series level Attributes. May be present otherwise. |
|||
|
Type of device, process or method that originally acquired or produced the data used to create the Instances in this Series. |
|||
|
Flag that this Series is not to be used for operational purposes. See Section C.38.1.2.2. Required if this Series is not to be used for operational purposes, and Removed from Operational Use (0008,0405) Attribute at Study level does not have the value Y. May be present otherwise. |
|||
|
Reason the Series was removed from operational use. Required if Removed from Operational Use (0008,0405) value is Y. |
|||
|
>>>Include Table 8.8-1 “Code Sequence Macro Attributes” |
Defined Context Group DCID 7031 Reason for Removal from Operational Use. |
||
|
Identification of the part of the body examined. See Section C.38.1.3.2. |
|||
|
Attributes from the Imaging Service Request. See Section C.38.1.3.3. |
|||
|
>>Include Table C.12.1.1.9-1 “Original Attributes Macro Attributes” |
Recording of prior Attribute values and provenance of metadata changes at the Series level. See Section C.38.1.2.5. |
||
|
Base URI for accessing SOP Instances within this Series through a non-DICOM protocol. See Section C.38.1.2.6. |
|||
|
Specifies how rapidly the Series becomes available for transmission after a retrieval request. See Section C.38.1.2.9. |
|||
|
Non-DICOM protocol methods to access the set of stored SOP Instances comprising this Series. Note"File Set" as used here may not be identical to the File-set concept defined in PS3.10 and used in Storage Media File-set ID (0088,0130). |
|||
|
Access URI for a folder containing all SOP Instances for the Series. See Section C.38.1.3.1. |
|||
|
Access URI for a container file containing all SOP Instances for the Series. See Section C.38.1.3.1. |
|||
|
Type of container file. See Section C.38.1.2.8 for Defined Terms. |
|||
|
A human readable Identifier that identifies the Storage Media on which the Series resides. |
|||
|
Records of SOP Instances whose Study, Series and Instance Attribute values match the Scope of Inventory. See Section C.38.2.1.1.2 for conditions with RELATIONAL matching for Scope of Inventory in which only matching SOP Instances will be included in the Inventory. |
|||
|
Character Set that expands or replaces the Basic Graphic Set for this Item. Required if an extended or replacement character set, other than those specified or implied for the Series level Attributes, is used in the Instance level Attributes. May be present otherwise. |
|||
|
Uniquely identifies a Related General SOP Class for the SOP Class of the inventoried Instance. |
|||
|
The date that creation of the content of the inventoried SOP Instance started. |
|||
|
The time that creation of the content of the inventoried SOP Instance started. |
|||
|
Offset from UTC to the timezone for all DA and TM Attributes present in the inventoried Instance, and for all DT Attributes present in the inventoried Instance that do not contain an explicitly encoded timezone offset. See Section C.12.1.1.8. |
|||
|
Number of pixel matrix rows in the inventoried Image SOP Instance. |
|||
|
Number of pixel matrix columns in the inventoried Image SOP Instance. |
|||
|
Number of bits allocated for each pixel sample in the inventoried Image SOP Instance. |
|||
|
The date and time at which the root Content Item of the inventoried Document SOP Instance was completed. |
|||
|
A coded description of the content or type of the inventoried SOP Instance. |
|||
|
>>>>Include Table 8.8-1 “Code Sequence Macro Attributes” |
|||
|
Attributes of the Template that describes the content structure and constraints for the inventoried Document SOP Instance. |
|||
|
Identifier of the Template as defined by the Mapping Resource (0008.0105). |
|||
|
Requested Procedures that were fulfilled (completely or partially) by the inventoried Document SOP Instance. |
|||
|
>>>>Include Table C.17-3c “Referenced Request Macro Attributes” |
|||
|
Identifier for the physical container that contains the specimen(s) imaged in the inventoried SOP Instance. See Section C.7.6.22.1.1. NoteNot to be confused with a container file as described in Section P.1.2. |
|||
|
Identifiers for the specimen(s) imaged in the inventoried SOP Instance. See Section C.7.6.22.1.1. |
|||
|
A departmental information system identifier for the Specimen. |
|||
|
A label that is used to identify the inventoried SOP Instance. |
|||
|
A description of the content of the inventoried SOP Instance. |
|||
|
Date on which the inventoried Presentation State SOP Instance was created. |
|||
|
Time at which the inventoried Presentation State SOP Instance was created. |
|||
|
Name of operator who created the content of the inventoried SOP Instance. |
|||
|
Flag that the inventoried SOP Instance is not to be used for operational purposes. See Section C.38.1.2.2. Required if this SOP Instance is not to be used for operational purposes, and Removed from Operational Use (0008,0405) Attribute at Study or Series level does not have the value Y. May be present otherwise. |
|||
|
Reason the SOP Instance was removed from operational use. Required if Removed from Operational Use (0008,0405) value is Y. |
|||
|
>>>>Include Table 8.8-1 “Code Sequence Macro Attributes” |
|||
|
>>>Include Table C.12.1.1.9-1 “Original Attributes Macro Attributes” |
Recording of prior Attribute values and provenance of metadata changes at the Instance level. See Section C.38.1.2.5. |
||
|
Specifies how rapidly the Instance becomes available for transmission after a retrieval request. See Section C.38.1.2.9. |
|||
|
Non-DICOM protocol methods to access the SOP Instance in the DICOM File Format. See Section C.38.1.4.2 and Section C.38.1.4.3. |
|||
|
>>>>Include Table C.38.2-2 “Stored File Access Macro Attributes” |
|||
|
The date and time until which the SOP Instance is expected to be available and after which SOP Instance is expected to be unavailable via this non-DICOM protocol URI. See Section C.38.1.4.4. |
|||
|
A human readable Identifier that identifies the Storage Media on which the Instance resides. |
|||
|
Reference to an alternate encoding of the inventoried SOP Instance. See Section C.38.1.4.5. |
|||
|
Unique identifier of the Series of the alternate representation. Required if the alternate representation is in a different Series than the inventoried SOP Instance. |
|||
|
SOP Instance UID of the alternate representation SOP Instance. |
|||
|
>>>>>Include Table 8.8-1 “Code Sequence Macro Attributes” |
BCID 7205 “Purpose of Reference to Alternate Representation” |
||
Content Date (0008,0023) and Content Time (0008,0033) establish thetime point at which began the creation of the Inventory for which this SOP Instance is the root. Conceptually, all Studies received by the storage system before this DateTime, and that match the specified Scope of Inventory key Attributes, are included in the Inventory, and all Patient and Study updates through this DateTime have been applied to the Attributes as recorded in the Inventory SOP Instance(s).
While Content Date and Time specify the nominal time for creation of the Inventory, each Study record has its own Item Inventory DateTime (0008,0404) that specifies the time of creation of that record, and its Attribute values are accurate as of that time.
Whether Studies and updates received after Content Date and Timemight be included in the Inventory is implementation specific.
The Content Date and Time of SOP Instances included by reference in the Incorporated Inventory Instance Sequence (0008,0422) may differ from the values of this SOP Instance.
The Scope of Inventory Sequence (0008,0400) specifies the matching rules for values of Attributes that select Studies to be included in the Inventory. It specifies the selection parameters for the current Inventory SOP Instance and all its subsidiary incorporated Instances referenced in the Incorporated Inventory Instance Sequence (0008,0422). The Scope of Inventory Sequence (0008,0400) within those subsidiary incorporated Instances is relevant only to their respective sub-trees, and may differ.
For example, an Inventory SOP Instance may specify in its Scope of Inventory that it includes studies from the years 2015-2019, but it does that by linking five subsidiary Inventory SOP Instances, one for each year, and which each specifies in its Scope of Inventory the year to which it applies.
While all Studies included in the Inventory will be within the Scope of Inventory, there may be Studies that match the Scope of Inventory that are not included in the Inventory if the Inventory is incomplete. The content of an Inventory SOP Instance, together with its subsidiary incorporated Instances, is complete with respect to the Scope of Inventory only if Inventory Completion Status (0008,0426) has the value COMPLETE.
Inventory Completion Status (0008,0426) is the status of the Inventory represented by this SOP Instance, including all SOP Instances referenced in the Incorporated Inventory Instance Sequence (0008,0422). The status is defined with respect to the Scope of Inventory as of the Content Date (0008,0023) and Content Time (0008,0033), for the repository system identified in the General Equipment Module (see Section C.7.5.1).
Enumerated Values:
All Studies matching the Scope of Inventory are included in the Inventory SOP Instance and its subsidiary Incorporated Inventory SOP Instances
Production of the Inventory failed; some Studies matching the Scope of Inventory might not be included in the Inventory
Production of the Inventory was canceled; some Studies matching the Scope of Inventory might not be included in the Inventory
Production of the inventory is incomplete; some Studies matching the Scope of Inventory might not be included in the Inventory
An Inventory may be COMPLETE and have no Study records, i.e., for the Repository identified in the General Equipment Module, at the Content Date and Content Time, no Studies match the Scope of Inventory.
The reason for a value other than COMPLETE may be described in Inventory Instance Description (0008,0402).
COMPLETE, FAILURE, and CANCELED are statuses for the corresponding terminal states of the Inventory production process (see Section KK.2.1.1 “Inventory Production States” in PS3.4). PARTIAL is a status representing continuing Inventory production, and this SOP Instance might be expected to be referenced in the Incorporated Inventory Instance Sequence (0400, 06x2) of the SOP Instance at the root of an Inventory tree.
See additional explanatory information and examples of use in Section YYYY.3.3.1 “Scope and Completion Status” in PS3.17.
The Inventory includes Attributes describing the available network access protocol(s) for referenced SOP Instances. The Inventory Access End Points Sequence (0008,0420) provides the default end points, i.e., network addresses, for access to Inventory SOP Instances referenced in the Incorporated Inventory Instance Sequence (0008,0422). The Study Access End Points Sequence (0008,0421) provides the default end points for access to Study-related SOP Instances referenced in the Inventoried Studies Sequence (0008,0423).
These default end points apply only to references within the current SOP Instance; they do not set defaults for references within Inventory SOP Instances referenced in the Incorporated Inventory Instance Sequence (0008,0422).
For implementation specific reasons, the content of an Inventory may be divided into more than one Inventory SOP Instance. The Inventory SOP Instances are organized as a tree of referenced SOP Instances, with one SOP Instance as the root. The Incorporated Inventory Instance Sequence (0008,0422) specifies the links from an Inventory SOP Instance to its subsidiary Instances in the tree. The Incorporated Inventory Instance Sequence (0008,0422) definition recursively includes itself, thus allowing representation of the complete tree of referenced Inventory SOP Instances.
Inventory SOP Instances that are incorporated by reference shall have the same Inventory Level (0008,0403) as the current SOP Instance.
The inclusion of an Inventory SOP Instance reference in the Incorporated Inventory Instance Sequence (0008,0422) means that the Items of the Inventoried Studies Sequence (0008,0423) in that referenced SOP Instance are logically included in the current SOP Instance. Therefore, all inventoried Studies in the referenced SOP Instances shall be within the Scope of Inventory of the current SOP Instance. However, the Item Inventory DateTime (0008,0404) of those Study records may be prior to the Content Date (0008,0023) and Content Time (0008,0033) of the current SOP Instance.
Reasons for splitting an Inventory might include practical limits on the maximum size of an individual SOP Instance, parallel processing across multiple separate subsystems, or reuse of historical Inventories. See Section YYYY.3.3 “Inventory Instance Tree” in PS3.17.
These requirements apply to every Inventory SOP Instance. Thus, each Inventory SOP Instance will include in its Incorporated Inventory Instance Sequence (0008,0422) the complete tree of references to the subtree of which it is the root.
The Inventoried Studies Sequence (0008,0423) references Studies whose Attributes match the Scope of Inventory. Within the tree of incorporated Inventory SOP Instances, a given Study may be referenced multiple times among the Inventoried Studies Sequence (0008,0423) Items. The Items may have different content, but each Item shall have a complete record of the contents of the Study as known by the creator of that Item.
Differences in content may occur due to changes to the metadata or content (SOP Instances) of the Study during the production of the Inventory, or due to different Series of a Study being stored on different media, or for other reasons. The application using an Inventory may need to reconcile such multiple occurrences (see Section YYYY.7.10 “Study Record Reconciliation” in PS3.17).
If there are multiple records for a Study among the tree of incorporated SOP Instances, the Total Number of Study Records (0008,0428) value will reflect the number of records, not the number of unique Study UIDs.
Study Update DateTime (0008,041F) is the DateTime of the last update to Study contents (SOP Instances) or to Study metadata within the repository system. Metadata may change either due to coercion of Study related data (Patient ID, Study Description, Accession Number, etc.) to correspond with values set by the enterprise or department master information system (HIS / EMR / RIS), or due to other updates applied by the repository system.
As this is an Attribute of the Study as managed within the repository system, the initial Study Update DateTime (0008,041F) is the time that the Study was first received in the repository system, and is updated upon each new SOP Instance received for the Study, as well as for updates of patient, procedure, and other metadata.
This Attribute, like Number of Study Related Series (0020,1206) and Number of Study Related Instances (0020,1208), is defined at the Study level of the Inventory Information Model, but is not part of the Study Attributes in SOP Instances. It is an Attribute that may be managed by the repository system, and might not have a value for some or all of the Studies in the Inventory.
Study Update DateTime (0008,041F) is not the time of last user access to the Study contents.
The Removed from Operational Use (0008,0405) Attribute is defined at the Study, Series, and Instance levels. A value of Y indicates the inventoried Study, Series, or Instance has been removed from operational use related to patient care, although it may be retained in the repository system for other reasons (e.g., for audit of patient radiation exposure). At the Study and Series level, the Attribute indicates whether the entire Study or Series has been removed from operational use. A value of Y at the Study level supersedes any value specified for subsidiary Series and Instances, and a value of Y at the Series level supersedes any value specified for subsidiary Instances.
The meaning of "operational use related to patient care" is implementation or site specific, but generally includes diagnostic, clinical, and therapeutic uses, as well as administrative uses necessary for providing care (e.g., insurance authorization).
Studies, Series, or Instances might be marked as removed from operational use by actions associated with the processing of specific Key Object Selection Document SOP Instances, e.g., in accordance with [IHE RAD TF-1] Image Object Change Management Integration Profile (IOCM). Those Key Object Selection Document SOP Instances, and their Series, may themselves be marked as removed from operational use. The Context Group for Reason for Removal Code Sequence (0008,0406) includes the Key Object Selection Concept Codes specified in IOCM.
An image SOP Instance might be marked as removed from operational use because it has been replaced by a different (e.g., compressed) encoding of the image (see Section C.38.1.4.5).
The content of the Inventory might not match the information obtained through the Query/Retrieve Service since Studies, Series, or Instances in Inventory SOP Instances marked as removed from operational use might not appear in Query/Retrieve responses (e.g., see [IHE RAD TF-2] Section 4.66.4.1.3.1 Access to Rejected Instances).
While defined in this specification at the Study, Series, and Instance levels, an Application Entity might not manage this Attribute at some, or any, of those levels. E.g., an AE may only manage this Attribute at the Instance level, and is not required to infer a value for the Series or Study level.
If the Application Entity retains records of deleted Studies, Series, or Instances, even though the actual Instances are physically deleted, it may include those records in the Inventory with an appropriate Reason for Removal Code Sequence (0008,0406) value. Such instances may have an Instance Availability (0008,0056) value "UNAVAILABLE" (see Section C.38.1.2.9).
Number of Study Related Series (0020,1206) and Number of Study Related Instances (0020,1208) shall give accurate counts of Series and SOP Instances stored in the repository, respectively. The counts of Series and Instances shall include those that are marked as removed from operational use.
These counts are not the number of Items in the Inventoried Series Sequence (0008,0424) and Inventoried Instances Sequence (0008,0425). Those Sequence Attributes may be absent depending on the value of Inventory Level (0008,0403). Further, if the Scope of Inventory indicates Relational matching to the Series or Instance level (see Section C.38.2.1.1.2), only Series and Instances matching the Scope of Inventory will be included in the Inventoried Series Sequence (0008,0424) and Inventoried Instances Sequence (0008,0425), and others present in the repository but not matching will not be recorded in the Inventory.
The Anatomic Regions in Study Code Sequence (0008,0063) consolidates the values of Anatomic Region Sequence (0008,2218) and Body Part Examined (0018,0015) in the SOP Instances of this Study. Recognized values of Body Part Examined can be transcoded to equivalent codes, such as by using the tables of Annex L “Correspondence of Anatomic Region Codes and Body Part Examined Defined Terms” in PS3.16, or by implementation- or site-specific mappings for locally defined terms.
The Original Attributes Sequence (0400,0561) is defined at each of the Study, Series, and Instance levels in the Inventory IOD.
Within the Inventoried Studies Sequence (0008,0423), i.e., at the Study level, the Original Attributes Sequence (0400,0561) may be used to record the prior values of updated Study, Patient, and Imaging Study Request Attributes for the referenced Study, and the provenance of such updates (see Section C.12.1.1.9). Within the Inventoried Series Sequence (0400,06x4), i.e., at the Series level, and within the Inventoried Instances Sequence (0008,0425), i.e., at the Instance level, the Original Attributes Sequence may be used to record the prior values of updated Series and Instance Attributes, respectively, and the provenance of such updates (see Section YYYY.7.9.1 “Original Attributes Sequence” in PS3.17).
In the context of an Inventory SOP Instance, the "top level Data Set" in the definition of the Original Attributes Sequence (0400,0561) is the top level Data Set of the SOP Instances of the inventoried Study.
The Original Attributes Sequences (0400,0561) in the Inventory SOP Instance might not be identical to the Original Attributes Sequence (0400,0561) in the individual SOP Instances of the Study, and updates recorded in either location are valid (see Section C.38.1.4.3).
While defined in this specification at the Study, Series, and Instance levels, an Application Entity might manage the Original Attributes Sequence (0400,0561) at only the Instance level. In such case, changes to Study, Patient, Imaging Study Request, and Series Attributes would be recorded at the Instance level for all affected SOP Instances.
Stored Instance Base URI (0008,0407) is defined at the Inventory, Study, and Series levels in the Inventory IOD.
Stored Instance Base URI (0008,0407) contains an [RFC3986] base URI that may be merged with relative path reference URIs for non-DICOM protocol access to SOP Instances of the Study or Series (see Section P.2.1). The Stored Instance Base URI (0008,0407) at the Study level establishes the default base URI for all relative path reference URIs in the Study, overriding a value specified at the Inventory level. Stored Instance Base URI (0008,0407) at the Series level establishes the default base URI for all relative path reference URIs in that Series overriding a value specified at the Inventory or Study level.
At the Inventory level, Stored Instance Base URI (0008,0407) is specified in the Study Access End Points Sequence (0008,0421), setting the default base URI value for all Study records in the current Inventory SOP Instance. See Section C.38.1.1.4.
Stored Instance Base URI (0008,0407) is optional, and if not present the values of Folder Access URI (0008,0408) and File Access URI (0008,0409) at the Study level must be complete URIs. If Stored Instance Base URI (0008,0407) is present, those other Attributes may still provide complete URIs, rather than relative paths to be merged with the Base URI.
See example uses of base URI and relative path reference URI in Section YYYY.7.2 “Using Non-DICOM Protocols” in PS3.17.
For any relative path reference URI, the base URI is the one specified in its level, if present, or successively at the next higher levels, until a Stored Instance Base URI (0008,0407) Attribute is present with a value.
If all of the stored SOP Instances of the Study, as identified in this Item, are in the DICOM File Format accessible through a non-DICOM protocol, and all the files are catalogued in a single folder (see Section P.1.3), Folder Access URI (0008,0408) provides the URI for protocol operations on that folder.
If all of the stored SOP Instances of the Study, as identified in this Item, are in a single container file as specified in Section P.1.2, File Access URI (0008,0409) provides the URI for accessing that file.
Folder Access URI (0008,0408) and/or File Access URI (0008,0409) may be a relative path reference beginning with the single-dot-segment "./" (see Section P.2.1). In this case, the URI is merged with the Stored Instance Base URI (0008,0407) applicable to this Study (see Section C.38.1.2.6).
See Section C.38.1.4.3 for requirements on applying metadata from the Inventory SOP Instance to stored SOP Instances of the Study.
The Study may be inventoried in more than one Item (see Section C.38.1.1.6). Only the SOP Instances identified within this Item (and its subsidiary Inventoried Instances Sequence (0008,0425) Attributes) need to be included in the folder or container file.
Stored SOP Instances from other Studies may be present in the folder or container file; the only requirement is that all of the identified SOP Instances of this Study are included.
If the SOP Instances of the Study are split across different container files, e.g., Series 1 and 2 in one container and Series 3 in a different container, then the conditional requirement for File Access URI (0008,0409) is not met and that Attribute is not used. However, if both of those container files are in the same folder, then Folder Access URI (0008,0408) may be present.
Files other than stored SOP Instances may be present in the folder or container file, e.g., reports in a non-DICOM file format.
These URIs provide complete access paths to the referenced folders and files, unlike the Retrieve URL (0008,1190) for the Studies Service (Section 10 “Studies Service and Resources” in PS3.18), which requires composition of the URI using the Study, Series, and/or SOP Instance UIDs.
Container File Type (0008,040A) identifies the type of container file accessible through the File Access URI (0008,0409).
Defined Terms:
see Section P.1.2.1
see Section P.1.2.2
see Section P.1.2.3
see Section P.1.2.4
see Section P.1.2.5
Single SOP Instance in DICOM File Format (see Section 7 “DICOM File Format” in PS3.10), not in a container
Instance Availability (0008,0056) is defined at each of the Study, Series, and Instance levels in the Inventory IOD. It specifies how rapidly the Study, Series, or Instance becomes available for transmission after a retrieval request. For a Study or Series, when some Instances are less rapidly available than others, the value is the availability of the least rapidly available.
Enumerated Values:
See also Section C.4.1.1.3.2 “Response Identifier Structure” in PS3.4.
A Study, Series, or Instance that is UNAVAILABLE may also be marked as removed from operational use with Reason for Removal Code Sequence (0008,0406) value (130752, DCM, "Data Not Accessible from Storage").
If all of the stored SOP Instances of the Series are in the DICOM File Format accessible through a non-DICOM protocol, and all the files are catalogued in a single folder (see Section P.1.3), Folder Access URI (0008,0408) provides the URI for protocol operations on that folder.
If all of the stored SOP Instances of the Series are in a single container file as specified in Section P.1.2, File Access URI (0008,0409) provides the URI for accessing that file.
Folder Access URI (0008,0408) and/or File Access URI (0008,0409) may be a relative path reference beginning with the single-dot-segment "./" (see Section P.2.1). In this case, the URI is merged with the Stored Instance Base URI (0008,0407) applicable to this Series (see Section C.38.1.2.6).
See also Section C.38.1.2.7 and its associated notes.
Defined Terms for Body Part Examined (0018,0015) are found in Annex L “Correspondence of Anatomic Region Codes and Body Part Examined Defined Terms” in PS3.16.
Recognized values of Body Part Examined (0018,0015) can be transcoded to their equivalent codes, such as by using the tables of Annex L “Correspondence of Anatomic Region Codes and Body Part Examined Defined Terms” in PS3.16 or by implementation-specific or site-specific mappings for locally defined terms. Those codes may beadded to the Study level Attribute Anatomic Regions in Study Code Sequence (0008,0063) (see Section C.38.1.2.4).
Request Attributes Sequence (0040,0275) may be used to support Series that are related to multiple Imaging Service Requests.
See, for example, [IHE RAD TF-2] Section 4.6.4.1.2.3 Relationship between Scheduled and Performed Procedure Steps.
This Module identifies Type 3 Attributes at the Instance level, some of which are applicable only to certain SOP Classes of inventoried SOP Instances. These Attributes may still be critical for certain repository uses, such as query for SOP Instances with certain characteristics.
Support of some IHE Profiles requires some of these Attributes. See, for example, [IHE RAD TF-2]:
A recommended best practice is for the Inventory to include all Attributes supported by the implementation as Matching or Return Keys for Query/Retrieve SOP Classes (see Annex C “Query/Retrieve Service Class (Normative)” in PS3.4).
See also Section YYYY.3.5 “Additional Data Elements” in PS3.17.
A repository system may store a SOP Instance on multiple storage devices (e.g., fast short-term media and slower long-term media), or with different Transfer Syntaxes. The SOP Instance may therefore be accessible through a non-DICOM protocol at multiple URIs. The File Access Sequence (0008,041A) provides one Item for each URI (see Section P.1.1). A URI relative path reference within this Sequence shall be relative to the Stored Instance Base URI (0008,0407) applicable to the Series (see Section C.38.1.2.6).
A stored SOP Instance accessible through a non-DICOM protocol shall be conformant to its IOD and to the DICOM File Format. However, some Attributes might not have current values (e.g., Patient Name may have been corrected or changed after the Instance was stored). The current values are encoded in the Inventory SOP Instance. For all Attributes defined in the IOD of the stored SOP Instance, and for which values are recorded in the Inventory, the values in the Inventory are authoritative and are imputed to the SOP Instance.
Items of the Original Attributes Sequences (0400,0561) in the Inventory at the Study, Series, and Instance levels (see Section C.38.1.2.5) are additive to any Items in the Original Attributes Sequence (0400,0561) of the stored SOP Instance.
SOP Instances accessed through DICOM protocols are expected to have current values in all Attributes.
Depending on its function, and application accessing a stored SOP Instance through a non-DICOM protocol may not require updated metadata, e.g., if it is only accessing the pixel data for a machine learning process. Hence, there is no normative requirement that such an application must use metadata from the Inventory SOP Instance, only that the metadata is imputed (conceptually ascribed) to the SOP Instance.
Attributes that are not defined in the IOD of the stored SOP Instance, but that are defined in the Inventory IOD, include Study level summary Attributes, such as Modalities in Study (0008,0061) and Number of Study Related Instances (0020,1208), and access Attributes, such as Retrieve AE Title (0008,0054), Stored Instance Base URI (0008,0407), and File Access URI (0008,0409). These Attributes are not to be imputed to the stored SOP Instance.
Attributes that are not defined in the Inventory IOD, but that are defined in the IOD of the stored SOP Instance, may be included in the Inventory SOP Instance, especially if they have been updated, such as change of an SR Concept Name Code Sequence (0040,A043) from a SNOMED RT to a SNOMED CT coded concept. See Section YYYY.3.5 “Additional Data Elements” in PS3.17. These Attributes are to be imputed to the stored SOP Instance.
An Inventory SOP Instance with Inventory Level (0008,0403) STUDY or SERIES does not include potentially updated metadata for lower levels of the information model. Users of such Inventories that access stored SOP Instances using a non-DICOM protocol, e.g., through the File Set Access Sequence (0008,0419) Attributes at the Study or Series level, should ensure that potentially outdated metadata is acceptable for their purposes.
An empty Type 2 Attribute in an Inventory SOP Instance, e.g., Patient's Birth Date (0010,0030), implies that an empty value should be imputed to the referenced stored SOP Instances. A creator of an Inventory SOP Instance should ensure that empty Type 2 Attributes are appropriately conveying the semantics that the value is unknown, and any value in the stored SOP Instances will be overridden.
As described in Section C.12.1.1.9, when performing a coercion, correction or conversion of SOP Instance Attributes, the application may add an Item to the Original Attributes Sequence (0400,0561) describing the provenance of the change, but preserving any existing Items in the Sequence. Thus, changes to Study, Patient, or Imaging Service Request Attributes recorded in the Inventory may have the provenance of those changes recorded in the Original Attributes Sequence (0400,0561) at the Study level, changes to Series or Instance Attributes may have their provenance recorded in the Original Attributes Sequence (0400,0561) at the Series or Instance level, respectively. When those changes are applied to the stored SOP Instances of the Study, all Items in the Original Attributes Sequence (0400,0561) in the Inventory at the Study, Series, and Instance levels are added to the Original Attributes Sequence (0400,0561) of the stored SOP Instances. See Section YYYY.7.9.1 “Original Attributes Sequence” in PS3.17.
A repository system may store a SOP Instance in a temporary location (e.g., on fast short-term media). If such storage has a scheduled or expected expiration time, it may be identified in the Expiration DateTime (0008,0416) Attribute. This is not a guaranteed expiration time; the SOP Instance may become unavailable at the access URI at an earlier or later time. This Expiration DateTime (0008,0416) applies only to this non-DICOM protocol access; SOP Instances may continue to be accessible through other DICOM or non-DICOM access methods.
Alternate Representation Sequence (0008,3001) encodes a reference to an alternate encoding of the inventoried SOP Instance. This alternate encoding may utilize a different SOP Class or Transfer Syntax, but the alternate encoding of an image shall be the same image although it may have different image quality characteristics.
The Alternate Representation Sequence (0008,3001) allows the Inventory record of an original image to reference a lossy compressed alternate representation, and vice versa.
See also Section C.6.1.1.5.1 “Alternate Representation Sequence” in PS3.4.
An original SOP Instance that has been operationally replaced by an alternate encoded SOP Instance, and the original then deleted, may still have its Inventory record retained to provide forward referential resolution throughthe Alternate Representation Sequence (0008,3001) for other SOP Instances that reference the original. This record may have Instance Availability (0008,0056) set to UNAVAILABLE (see Section C.38.1.2.9), and/or may also be marked as removed from operational use with Reason for Removal Code Sequence (0008,0406) value (130754, DCM, "Replaced by Alternate Representation") (see Section C.38.1.2.2).
| DICOM PS3.3 2024d - Information Object Definitions |
|---|