Overview

Unlike replacement slots, information slots are added to an expression template purely to provide metadata about how the template should be processed. When an expression template is processed, the information contained in the information slots is used and then the information slot itself is removed.

...

Information slots may include either a cardinality constraint or a slot name (or both). In the following sections, we describe how each of these may be used in an information slot.

Cardinality

One of the important roles of an information slot is to specify the cardinality of the expression part that follows. A cardinality constraint states the minimum and maximum number of times that the focus concept, relationship group or attribute name-value pair that follows may be repeated in an expression that is generated from the given template.

...

   	[[1..3]] [[+id (< 404684003 |Clinical finding|: [0..0] 363698007 |Finding site| = * ) @finding]]: 
      		[[1..1]] 363698007 |Finding site|  =  
         
			[[+id (<< 442083009 |Anatomical or acquired body structure|) @site ]]

...

   	40733004 |Infectious disease| + 66091009 |Congenital disease|: 363698007 |Finding site| = 39607008 |Lung structure|

Please note that when two or more concepts are used to replace a focus concept slot in an expression template, a plus sign (‘+’

Default Cardinality

When a cardinality constraint is not provided in an information slot preceding a focus concept, relationship group or attribute name-value pair, the default cardinality that is assumed is  [[1is  1..*]]. This means that by default focus concepts, relationship groups and attribute name-value pairs must appear at least once in the resulting expression, but may also be repeated many times. The SNOMED CT concept model, if enforced, may also impose some additional cardinality constraints on the number of times an attribute may be repeated. However, these additional concept model rules are not directly implied by the expression template itself.

...

   	[[+id (<<71388002 |Procedure|)]]: 
      		{ 260686004 |Method| = [[+id (<< 129264002 |Action (qualifier value)|)]],
        			405813007 |Procedure site - Direct| = [[+id (<< 442083009 |Anatomical or acquired body structure (body structure)|)]] }

The above expression template is therefore equivalent to the following template, in which the cardinality of [[ 1..*]] is  is explicitly stated on the focus concept, the relationship group, and each attribute name-value pair.

   	[[1..*]] [[+id (<<71388002 |Procedure|)]]: 
      		[[1..*]] { [[1..*]] 260686004 |Method| = [[+id (<< 129264002 |Action (qualifier value)|)]],
                 					[[1..*]] 405813007 |Procedure site - Direct| = [[+id (<< 442083009 |Anatomical or acquired body structure (body structure)|)]] }

...

 	76193006 |Routinely scheduled operation| + 387713003 |Surgical procedure|: 
      {		{ 260686004 |Method| = 281615006 |Exploration|,
       			260686004 |Method| = 312250003 |Magnetic resonance imaging - action|,
       			405813007 |Procedure site - Direct| = 28273000 |Bile duct structure| },
      {		{ 260686004 |Method| = 129304002 |Excision|,
       			405813007 |Procedure site - Direct| = 28231008 |Gallbladder structure| }

Please note that if the international SNOMED CT concept model was enforced, the above expression would not be valid due to the

Slot Name

 Information slots can also be given a slot name, to allow the expression part that follows the slot (i.e. focus concept, relationship group, or attribute name-value pair) to be referenced. The most common use of information slot names is to support the process of populating the template (e.g. as part of a programmatic value replacement process).

...

   	71388002 |Procedure| : [[1..1 @mpGroup]]
      {		{ 260686004 |Method| = 312251004 |Computed tomography imaging action|,
         			405813007 |Procedure site - Direct| = [[+id (<<442083009 |Anatomical or acquired body structure|) @site]] }

...