DICOM PS3.17 2022d - Explanatory Information

YYYY.4.2 Inventory Creation Service

Creation of an inventory may be initiated by a transaction of the Inventory Creation SOP Class (see Section KK.2 “Inventory Creation SOP Class” in PS3.4). The initiation action for the Inventory specifies the requested Scope of Inventory and Inventory Level. Specific warnings and errors are defined for an SCP that cannot process the requested Scope of Inventory and Inventory Level (see Section KK.2.2.3 “Service Class Provider Behavior” in PS3.4).

The Inventory Creation SOP Class is in many ways similar to the Repository Query SOP Class (see Section YYYY.2). In both cases, the SCU requests a list of Studies, managed by the SCP, that match Key Attribute values. However, the Repository Query operates synchronously (i.e., the query and response occur on the same Association). The SCP is expected to respond within a typical transactional timeout period, and the SCU must interactively process responses and sequentially initiate queries to continue after partial completion responses (or errors).

In contrast, the Inventory Creation SOP Class operates asynchronously, as production of an enterprise-scale inventory of billions of objects may take considerable time (potentially many days). As an asynchronous process, multiple approaches are available to the SCP to manage the resource demands for Inventory production across a longer time scale and with non-critical priority. The results are stored in information objects that can be accessed asynchronously at the convenience of the SCU.

The mechanisms of the Inventory Creation SOP Class are similar to those of the Storage Commitment SOP Class (see Chapter CC). The SCU sends a request for the service to the SCP in an N-ACTION message, and the SCP asynchronously reports back status or completion using an N-EVENT-REPORT message.

The Inventory Creation SOP Class provides for regular reports on the status of inventory creation, at an interval specified by the SCU (see Section KK.2.2.2 “Service Class User Behavior” in PS3.4). This allows the SCU to ensure that the operation has not stalled. For example, such reporting might be desired for each 5% of process progress, and for an inventory that is expected to complete in one day, status reporting could be requested for 30-minute intervals. The SOP Class also allows the SCU to request a status report update at any time.

The Inventory Creation SOP Class allows production of an inventory to be paused and resumed. A pause may occur when resources necessary for Inventory production (database processing cycles, disk storage space, etc.) become temporarily unavailable, or when resource usage has reached a pre-set limit. For example, a system that allows a research application to create an Inventory might limit the initial result to some maximum number of Studies, and then pause for confirmation before proceeding. It is expected that some human intervention may be required before resuming inventory production.

Note that the Inventory Creation SOP Class does not use the Inventory IOD (Section A.88 “Inventory IOD” in PS3.3), but rather the Inventory Creation IOD (Section B.30 “Inventory Creation IOD” in PS3.3), which consists of the controls and statuses for production of an Inventory. However, both the Inventory IOD and the Inventory Creation IOD use many of the same Attributes, including the Scope of Inventory Sequence (0008,0400).

DICOM PS3.17 2022d - Explanatory Information