Documentation: Context nodes specify the clinical and organizational situation in which the following guideline recommendations are to be applied.

Superclasses

• Activity_Graph_Node

Subclasses

• None

Types

• :STANDARD-CLASS

Template Slots
	Slot Name	Documentation	Type	Cardinality
	clinical_context	The specific clinical setting, roles, and resources that must be in place for this guideline to be applied in a particular context.	Clinical_Context	0:1
	description	A paragraph describing the nature of the instance	String	0:1
	informatics_context	The informatics resources required in order for this guideline to be executable at a given site. This context is not supplied by the guideline encoder; rather, it is generated automatically following completion of guideline encoding.	Informatics_Context	0:1
	label	Each instance has a unique label that can be assigned by the guideline modeler. The label should be descriptive of the guideline element. Labels have no programmatic meaning.A short human readable string indicating the content of the instancehuman-readable string for the instance	String	0:1
	new_session	Indicates whether this node marks the start of a new session.	Boolean	1:1
	precondition	Criteria that must be true in order for this processing to be activated.	Criterion	0:1
	references	References to evidence supporting these recommendations.Sources of information regarding this concept-to-concept relationship.	Supplemental_Material	0:*
	scheduling_constraint	Criteria which must be true in order for a particular Activity Graph node to be activated. IMP: Don't worry about it for now. Do not use unless there is no other way	Criterion	0:1
	subguideline	An Activity Graph or Decision Map that is executed as a part of this step.	Subguideline	0:1
	transition_restriction	Specifies control information in relation to activities preceding and following a given activity graph node. It has two elements: Join Constraint and Split Constraint. Join Constraint may be AND (all incoming transitions must be evaluated to true before this node may commence) or XOR (only one incoming transition must evaluate to true). Split Constraint may be AND (all following transitions must be evaluated) or XOR (outgoing transitions are evaluated until one evaluates to true; that target node and no other is activated).Specifies control information in relation to activities preceding and following a given activity graph node. It has two elements: Join Constraint may be AND (all preceding nodes must be evaluated before this node may commence) or XOR (only one preceding node must complete). In all cases, the transition restriction must evaluate to true before the node may be activated. Split Constraint may be AND (all following nodes must be evaluated) or XOR (outgoing transitions are evaluated until one evaluates to true; the target node and no other is activated).	Transitin_Restriction	0:1
	triggering_events	The computer-based events that trigger evaluation of this Context node.	Event	0:*

Own Slots
	Slot Name	Value
	:ROLE	Concrete
	:SLOT-CONSTRAINTS

  ^ back to top