A.35.7 Procedure Log Information Object Definition

A.35.7.1 Procedure Log Information Object Description

The Procedure Log IOD is intended for the representation of reports or logs of time-stamped events occurring during an extended diagnostic or interventional procedure, typical of the cardiac catheterization lab.

A.35.7.2 Procedure Log IOD Entity-Relationship Model

The E-R Model in Section A.1.2 of this Part applies to the Procedure Log IOD. Table A.35.7-1 specifies the Modules of the Procedure Log IOD.

Note: Unlike some other SR IODs, the Frame of Reference IE is critical to the synchronized time stamping of events in the Procedure Log IOD and to multi-modality coordination.

A.35.7.3 Procedure Log IOD Module Table

Table A.35.7-1PROCEDURE LOG IOD MODULES

IE Module Reference Usage
Patient Patient C.7.1.1 M
Clinical Trial Subject C.7.1.3 U
Study General Study C.7.2.1 M
Clinical Trial Study C.7.2.3 U
Series SR Document Series C.17.1 M
Clinical Trial Series C.7.3.2 U
Frame of Reference Synchronization C.7.4.2 M
Equipment General Equipment C.7.5.1 M
Document SR Document General C.17.2 M
SR Document Content C.17.3 M
SOP Common C.12.1 M

A.35.7.3.1 Procedure Log IOD Content Constraints

A.35.7.3.1.1 Template

The document may be constructed from Baseline TID 3001 "Procedure Log" (defined in PS3.16) invoked at the root node.

Note: This template defines a container (the root) with subsidiary content items, each of which represents a single procedure log entry. There is a defined recording observer (the person responsible for recording the log, generally a technician or nurse). The log entries follow a canonical model of a coded log entry type (the concept name of the content item), the value associated with the concept name as one of the SR Value Types, and optionally a subsidiary free text comment and/or an identifier of the author or device source of the log entry (which may be other than the recording observer).

A.35.7.3.1.2 Observation DateTime

Each Item in the Content Sequence (0040,A730) of the SR Document Content Module that is a target of a "CONTAINS" relationship from the root node, i.e., the first level Log Content Items, shall include the Observation DateTime (0040,A032) as a Type 1 attribute. This attribute shall represent the DateTime at which the event recorded in the Content Item occurred, not the time at which the Item was recorded.

The first level Procedure Log Content Items in the Content Sequence shall be strictly ordered by monotonically increasing Observation DateTime (0040,A032) values.

The Observation DateTime (0040,A032) shall be specified to a precision of one second or finer.

A.35.7.3.1.3 Value Type

Value Type (0040,A040) in the Content Sequence (0040,A730) of the SR Document Content Module is constrained to the following Enumerated Values (see Table C.17-7 for Value Type definitions):

CODE

CONTAINER

COMPOSITE

DATETIME

DATE

IMAGE

NUM

PNAME

TEXT

TIME

UIDREF

WAVEFORM

A.35.7.3.1.4 Relationship Constraints

Relationships between Content Items in the content of this IOD shall be conveyed in the by-value mode. See Table C.17-8 for Relationship Type definitions.

Notes: 1. Relationships by-reference are forbidden. Therefore, Referenced Content Item Identifier (0040,DB73) is not present in any of the Content Items within the SR Document Content Module.2. CONTAINERs are not permitted as a target of any relationship.

Table A.35.7-2 specifies the relationship constraints of this IOD.

Table A.35.7-2RELATIONSHIP CONTENT CONSTRAINTS FOR PROCEDURE LOG IOD

Source Value Type Relationship Type (Enumerated Values) Target Value Type
CONTAINER CONTAINS TEXT, CODE, NUM, PNAME, COMPOSITE, IMAGE, WAVEFORM
any type HAS OBS CONTEXT TEXT, CODE, NUM, DATETIME, UIDREF, PNAME
CONTAINER, IMAGE, WAVEFORM, COMPOSITE HAS ACQ CONTEXT TEXT, CODE, NUM, DATETIME, DATE, TIME, UIDREF, PNAME
any type HAS CONCEPT MOD TEXT, CODE
any type (except CONTAINER) HAS PROPERTIES TEXT, CODE, NUM, DATETIME, UIDREF, PNAME
TEXT, CODE, NUM INFERRED FROM IMAGE, WAVEFORM, COMPOSITE