The DICOM AEs which claim conformance to this SOP Class as an SCU and/or an SCP shall support the Action Type and Action Information in the N-ACTION-RQ as specified in Table P.2-2.
Table P.2-2PROCEDURAL EVENT LOGGING ACTION INFORMATION
|Action Type Name||Action Type ID||Attribute||Tag||Requirement Type SCU/SCP|
|Record Procedural Event||1||Specific Character Set||(0008,0005)||1C/1C (Required if an extended or replacement character set is used)|
|Study Instance UID||(0020,000D)||2/2|
|Synchronization Frame of Reference UID||(0020,0200)||2/2|
|All other Attributes of the SR Document Content Module (PS3.3) using Procedure Log IOD Content Constraints||See Section P.22.214.171.124|
The SCU may provide Patient ID (0010,0020), Study Instance UID (0020,000D), Study ID (0020,0010), and/or Performed Location (0040,0243) attributes to allow the SCP to match the N-ACTION with a Study for which a procedure log is being created.
The Synchronization Frame of Reference UID (0020,0200) attribute identifies the temporal frame of reference for the Observation DateTime (0040,A032) attributes in the Procedural Event record. If the Observation DateTime attribute values are not synchronized in an identifiable Frame of Reference, the attribute shall be zero length.
The Procedural Event record shall be conveyed in a (top level) Content Item, and subsidiary Content Items, as specified by the SR Document Content Module definition in PS3.3.
The top level and subsidiary Content Items shall be constructed in accordance with the Procedure Log IOD Content Constraints of PS3.3.
Notes: 1. These constraints specify use of BTID 3001 Procedure Log defined in PS3.16, and specific particular use of the Observation DateTime (0040,A032) attributes.
2. TID 3001 requires the explicit identification of the Observer Context of the top level CONTAINER through TID 1002.
3. There may be multiple events (subsidiary Content Items) included in a single N-ACTION-RQ message.