C.34.2 Protocol Context Module

C.34.2 Protocol Context Module (Current)
Prev	C.34 Procedure Protocol Modules	Next

Table C.34.2-1 specifies the Attributes of the Protocol Context Module, which describe the context in which the described Protocol is defined or performed. This Module is applicable to defined and performed procedure protocols.

Details like the Potential Reasons for Procedure Code Sequence (0018,9909) or the Protocol Planning Information (0018,990F) may be copied from the defined protocol into the performed protocol to support quality assurance activities like checking whether the contents of the Reason for Requested Procedure Code Sequence (0040,100A) recorded in the performed protocol are consistent with the contents of the Potential Reasons for Procedure Code Sequence (0018,9909).

Table C.34.2-1. Protocol Context Module Attributes

Attribute Name	Tag	Type	Attribute Description
Custodial Organization Sequence	(0040,A07C)	3	Custodial organization for this Protocol Instance. Represents the organization that is currently in charge of maintaining this protocol Instance. Note This may or may not be identical to the Institution identified in the General Equipment Module. This may or may not be the Institution that originally created this Instance. Only a single Item is permitted in this Sequence.
>Institution Name	(0008,0080)	2	Name of Custodial Institution or Organization.
>Institution Code Sequence	(0008,0082)	2	Coded identifier of Custodial Institution or Organization. Zero or one Item shall be included in this Sequence.
>>Include Table 8.8-1 “Code Sequence Macro Attributes”			No Baseline CID is defined.
Responsible Group Code Sequence	(0008,0220)	2	The department, unit or service that is responsible for the management of this Protocol. See Section C.34.2.3. Zero or more Items shall be included in this Sequence.
>Include Table 8.8-1 “Code Sequence Macro Attributes”			BCID 7030 “Institutional Department/Unit/Service”.
Protocol Name	(0018,1030)	1	Name for this Protocol.
Potential Scheduled Protocol Code Sequence	(0018,9906)	3	A list of Protocol Codes for which this Protocol may be considered a match. One or more Items are permitted in this Sequence.
>Include Table 8.8-1 “Code Sequence Macro Attributes”
Potential Requested Procedure Code Sequence	(0018,9907)	3	A list of Procedure Codes for which this Protocol may be considered a match. One or more Items are permitted in this Sequence.
>Include Table 8.8-1 “Code Sequence Macro Attributes”			No Baseline CID is defined.
Potential Reasons for Procedure	(0018,9908)	3	List of reasons deemed appropriate by the Protocol author for a procedure using this Protocol Each reason shall be encoded in a separate value of this multi-value Attribute. Note One of the reasons listed here may be encoded in Reason for the Requested Procedure (0040,1002) within Instances generated from running the Protocol.
Potential Reasons for Procedure Code Sequence	(0018,9909)	3	List of reasons deemed appropriate by the Protocol author for a procedure using this Protocol. One or more Items are permitted in this Sequence. Note One of the reasons listed here may be encoded in Reason for Requested Procedure Code Sequence (0040,100A) within Instances generated from running the Protocol.
>Include Table 8.8-1 “Code Sequence Macro Attributes”			No Baseline CID is defined.
Potential Diagnostic Tasks	(0018,990A)	3	List of diagnostic tasks deemed appropriate by the Protocol author for a procedure using this Protocol. E.g., detect collections of blood, identify brain masses.
Contraindications Code Sequence	(0018,990B)	3	List of reasons for which the authors of the Protocol deemed it contraindicated. Note Constraints on values of patient demographic Attributes such as sex, age or weight are addressed separately in the Patient Specification Module. See Section C.34.5. One or more Items are permitted in this Sequence.
>Include Table 8.8-1 “Code Sequence Macro Attributes”			BCID 1200 “Contraindications For CT Imaging”. BCID 1201 “Contraindications For XA Imaging”.
Predecessor Protocol Sequence	(0018,990E)	3	Defined or Performed Procedure Protocol Instances from which this Defined Procedure Protocol was derived. See Section C.34.2.1. This Attribute is not present in Performed Procedure Protocol Instances since the Referenced Defined Protocol Sequence (0018,990C) is used instead. One or more Items are permitted in this Sequence.
>Include Table 10-11 “SOP Instance Reference Macro Attributes”
Content Creator's Name	(0070,0084)	1	Name of the most recent person (such as a technologist or physician) to significantly modify the content of this SOP Instance. Note For a Performed Protocol object, this is generally the operator who was the last one to interact with the protocol before it was performed. A history of editors is not recorded here. Such information might conceivably be recovered by reviewing the Attribute value of other Instances such as those referenced in Predecessor Protocol Sequence (0018,990E).
Content Creator's Identification Code Sequence	(0070,0086)	3	Identification of the most recent person to significantly modify the content of this SOP Instance. Only a single Item is permitted in this Sequence.
>Include Table 10-1 “Person Identification Macro Attributes”
Protocol Design Rationale	(0018,9910)	3	Explanation of the rationale behind the selected parameter values or changes to them.
Protocol Planning Information	(0018,990F)	3	Description of details and activities related to planning the execution of this Protocol. See Section C.34.2.2.
Instance Creation Date	(0008,0012)	1	Date the Protocol SOP Instance was created.
Instance Creation Time	(0008,0013)	1	Time the Protocol SOP Instance was created.

C.34.2.1 Predecessor Protocol Sequence

A Protocol may be a derivation of another Protocol (the "predecessor"). For example, a Protocol may be originally published as a non-model-specific Protocol for a certain purpose. Subsequently, a new Protocol may be derived from the original by making it specific to a certain model of scanner. Derivation may involve adjusting constraints or specifying additional constraints. If a Protocol no longer satisfies any of the indications of the Predecessor Protocol from which it was derived, the Predecessor shall not be referenced in this Sequence.

Note

Including predecessor information makes it possible to filter a set of Protocols, for example to list all Protocols that are derived versions of a certain known Protocol (e.g., ACRIN 6678), or list only the one that has been specialized for a specific model of equipment.

Sites that receive a generic Protocol might create a specialized variant to fit their local practice and avoid the tech having to make selections/changes each time it is used.

Only the immediate predecessor shall be referenced, but more than one predecessor may be referenced if multiple distinct predecessors were merged.