To avoid any confusion and misinterpretation Before a template can be processed, it is important that the input data is represented in a clear and unambiguous way that ease the interpretation of the input data and ensure correct processing of the expression template. Poorly represented input data may result in expressions that express a different meaning than intended, which can be critical if the resulting expressions are used for safety critical purposes (storage, communication, trigger decision support rules etc.)

Templates with Repeatability of Groups and Attributes

. This is required to ensure that the template is processed in the expected manner, and the intended results are produced. In this section, we explain some of the considerations in representing and preparing the input data for processing.

Input Data Representation

Template input data may be represented in a variety of forms, ranging from flat tabular structures to nested serializations. Irrespective of the format, however, it is important that there is no ambiguity as to how each piece of input data should be used to create the resulting expressions. This can be particularly challenging where repetition of relationship groups or attribute name-value pairs is required.

The UML diagram below illustrates the logical structure of expression template input data. Each set of Expression Template Input Data includes the data intended to be used to create one or more expressions. The data used to populate a single expression is referred to in this model as Expression Data. Each Expression Data (i.e. the data for a single expression), may include at most one Definition Status Slot (with a slot name and a definitionStatus value), zero or more Focus Concept Slots (each with a slotName and zero or more values), zero or more Relationship Group Slots (each with a group name), and zero or more ungrouped Attribute Name-Value Pair Slots (each with a name). Each Relationship Group Slot has zero or more Relationship Group Data instances in the input data. Each of these Relationship Group Data instances has input data for one to many Attribute Name-Value Pair Slots. And for each Attribute Name-Value Pair Slot within a Relationship Group Data instance, there are zero to many Attribute Name-Value Pair Data instances, each with at most one Attribute Name Slot (with name and value), and at most one Attribute Value Slot (with name and either a simple data value, or an Expression Data instance of its own).

Image Added

Input Data Examples

In this section, we provide some examples of unambiguous expression template input data, and discuss how this input data can be used to populate each expression.

Example 1

The expression template below is used to create expressions that represent a

When using expression templates, such as this one, in which attribute name-value pairs and relationship groups may In situations where the template allow for attribute-value pairs or relationships groups to be repeated, the input data should be explicit about about which attribute name-value pairs should be grouped together and which groups should be included in a single expression. 

	[[@Expression +tok ("===", "<<<") @DefStatus)]] [[+scg (<< 64572001 |Disease (disorder)||) @Disease]] : 
		[[@Group]] { 363698007 |Finding site (attribute)|  =  [[+ (<< 272673000 |Bone structure (body structure)| ) @Site]],
					   116676008 |Associated morphology (attribute)|  =  [[+ (<< 72704001 |Fracture (morphologic abnormality)| ) @Morphology]] }

To populate this template, the input data should be explicit about which data values are used to populate each slot, and how these values are grouped into relationship groups. The table below shows an abstract representation of some input data that may be used to process the expression template above. The relationship to the logical model above has bee noted in brackets under each column name. Please note that the first column is used to group together the data intended to populate each expression, and subsequent columns are named after the associated slot. Relationship group slots are used to group the data that is intended to populate this could be represented explicit like this:a single relationship group. Attribute name-value slots are not required in this example. They are are only required where both the attribute name and attribute value use a slot.

46866001 |Fracture of lower limb|

12611008 |Bone structure of tibia|

72704001 |Fracture|

92196005 |Benign neoplasm of lung| 

39607008 |Lung structure|

3898006 |Neoplasm, benign| 

92038006 |Benign neoplasm of bronchus|

955009 |Bronchial structure|

3898006 |Neoplasm, benign|

60667009 |Closed fracture of rib| 

113197003 |Bone structure of rib|

34305007 |Fracture, multiple, closed| 

36991002 |Closed fracture of upper limb|

371195002 |Bone structure of upper limb|

16119006 |Abscess of jaw|

70925003 |Bone structure of maxilla|

44132006 |Abscess|

109327001 |Abscess of facial bone|

128234004 |Disorder of maxilla|

64572001	=== 46866001 |Disease|Fracture :of {lower 
 limb|:
		{ 363698007 |Finding site| = 31276300812611008 |Bone structure of trunktibia|,
		  116676008 |Associated morphology |= 72704001 |Fracture| }

	<<< 92196005 |Benign neoplasm of lung| + 92038006 |Benign neoplasm of bronchus|:
		,
{ 363698007 |Finding site| = 8466700639607008 |BoneLung structure of cervical vertebra|,
		  116676008 |Associated morphology|  = 727040013898006 |FractureNeoplasm, benign| }

64572001 |Disease| : { 
  ,
		{ 363698007 |Finding site|  = (62413002955009 |BoneBronchial structure of radius| + 23416004 |Bone structure of ulna|),
		  116676008 |Associated morphology|  = 727040013898006 |FractureNeoplasm, benign| }

64572001 |Disease| : { 
	<<< 60667009 |Closed fracture of rib| + 
	36991002 |Closed fracture of upper limb| :
		{ 363698007 |Finding site| = 113197003 |Bone structure of rib|,
		  363698007 |Finding site| = 71341001371195002 |Bone structure of upper femurlimb|,
		  116676008 |Associated morphology|  = 7270400134305007 |Fracture, multiple, closed| }

	=== 16119006 |Abscess of jaw| + 
		109327001 |Abscess of facial bone| +
		128234004 |Disorder of maxilla|:
			{ 363698007 |Finding site| 

= 

70925003 |

Bone structure of 

maxilla|, 
			  116676008 |Associated morphology| 

= 

44132006 |

Abscess|

}

Cardinality Constraints on Groups

...

...

	[[

...

+id (<<  413350009 |Finding with explicit context| ) @Condition]]:
		[[ 1..2 @AFgroup ]] { [[1..

...

1]]  246090004 |Associated finding|  = ([[+id (<<  404684003 |Clinical finding| ) @Finding]]:
			[[0..1 @SSgroup]] { [[0..1

...

]]  246112005 |Severity|  = [[+id (<  272141005 |Severities| ) @Severity]],
								[[0..1]]  363698007 |Finding site|  = 

...

[[+id (

...

<  

...

91723000 |

...

Anatomical structure| ) @Site]] }),
						[[1..1]]  408732007 |Subject relationship context|  = [[+id (<  444148008 

...

|Person in family of subject| ) @Relationship]],
						[[1..1]]  408731000 |Temporal context|   = [[+id (<  410510008 |Temporal context value| ) @Time]],
						[[1..1]]  408729009 |Finding context|   = [[+id (

...

<  

...

410514004 |

...

Finding context value| ) 

...

@Context]] }

In this situation, processing the template against the input data  would result in a processing error, because the first expression would not be valid. the expression template allow for only one @Group within each expression, whereas the input data specify an expression with more that one @Group. 

266898002 |Family history: Respiratory disease|

195967001 |Asthma|

24484000 |Severe|

444301002 |Mother of subject|

410589000|All times past|

410515003 |Known present|

161077003 |Father smokes|

77176002 |Smoker|

255604002 | Mild|

444295003 |Father of subject|

15240007 |Current|

410515003 |Known present|

161078008 |Mother smokes|

77176002 |Smoker|

24484000 |Severe|

444301002 |Mother of subject|

15240007 |Current|

410515003 |Known present|

160288009 |Family history: neoplasm of skin| 

372130007 |Malignant neoplasm of skin|

6736007 |Moderate|

113179006 |Skin structure of nose|

444304005 |Sister of subject|

410511007 |Current or past (actual)|

410515003 |Known present|

275937001 |Family history of cancer (situation)|

255604002 |Mild|

88089004 |Skin structure of lip|

	266898002 |Family history: Respiratory disease|:
		{ 246090004 |Associated finding| = (195967001 |Asthma|: { 246112005 |Severity| = 24484000 |Severe| }),
		   408732007 |Subject relationship context| = 444301002 |Mother of subject|,
		   408731000 |Temporal context| = 410511007 |Current or past (actual)|,
		   408729009 |Finding context| = 410515003 |Known present| }

	161077003 |Father smokes| + 161078008 |Mother smokes|:
		{ 246090004 |Associated finding| = (77176002 |Smoker|: { 246112005 |Severity| = 24484000 |Severe| }),
		   408732007 |Subject relationship context| = 444295003 |Father of subject|,
		   408731000 |Temporal context| = 15240007 |Current|,
		   408729009 |Finding context| = 410515003 |Known present|},
		{ 246090004 |Associated finding| = (77176002 |Smoker|: { 246112005 |Severity| = 255604002 |Mild| }),
		   408732007 |Subject relationship context| = 444301002 |Mother of subject|,
		   408731000 |Temporal context| = 15240007 |Current|,
		   408729009 |Finding context| = 410515003 |Known present| }

	160288009 |Family history: neoplasm of skin| + 275937001 |Family history of cancer|:
		{ 246090004 |Associated finding| = (372130007 |Malignant neoplasm of skin|:
				{ 246112005 |Severity| = 6736007 |Moderate|, 363698007 |Finding site| = 113179006 |Skin structure of nose| },
				{ 246112005 |Severity| = 255604002 |Mild|, 363698007 |Finding site| = 88089004 |Skin structure of lip| }), 
		408732007 |Subject relationship context| = 444304005 | Sister of subject|,
		408731000 |Temporal context| = 410511007 |Current or past (actual)|,
		408729009 |Finding context| = 410515003 |Known present| }

	[[+id (<< 71388002 |Procedure|) @Procedure]]:
		

[[@Expression ]] 64572001 |Disease| : [[1..*]] 
[[1..1 @Group]]
			{ [[1..1] 363698007 |Finding site| * @PD_ANVpair]] [[+id (< 405815000 |Procedure device|) @DeviceType]] =  [[+ (<< 272673000<260787004 |BonePhysical structureobject| ) @Site@Device]],
			  [[1..1]] 116676008260686004 |Associated morphologyMethod|  =  [[+ (<< 72704001 |Fracture| ) @Morphology<129264002 |Action (qualifier value)|) @Method]] }

In this case,  the second expression would not be valid … so there would be no need to include the expression column, as each row would signify a separate expression. That is, we could just define the data as: 

...

@Site

...

@Morphology

...

...

...

...

INVALID

Only one @Site is allowed due to cardinality constraints

...

...

...

...

...

...

...

Similarly, if only precoordinated concepts were allowed in the slots, like this:

...

...

387713003 |Surgical procedure|

363699004 |Direct device|

2282003 |Breast prosthesis, device|

257867005 |Insertion - action|

71388002 |Procedure|

363699004 |Direct device|

313025003 |Hearing aid battery|

282089006 |Replacement - action|

363710007 |Indirect device|

6012004 |Hearing aid, device|

	387713003 |Surgical procedure|:
            { 363699004 |Direct device| = 2282003 |Breast prosthesis, device|,
              260686004 |Method| = 257867005 |Insertion - action|}

	384728007 |Replacement of device|:
            { 363699004 |Direct device| = 313025003 |Hearing aid battery|,
              363710007 |Indirect device| = 6012004 |Hearing aid, device|,
              260686004 |Method| = 282089006 |Replacement - action|}

	64572001 |Disease|: 
		[[@Group]] { 363698007 |Finding site|  =  [[+ 

...

(<< 272673000 |Bone structure|

...

) @Site]],

...

					 116676008 |Associated morphology|  =  [[+

...

 (<< 72704001 |Fracture|

...

) @Morphology]] }

then only the following data value would be valid:

...

@Site

...

...

{"Expression Data": [
        { "Group": [
                {  "Site":"312763008 |

...

Bone structure of trunk|",
                    "Morphology":"72704001 |Fracture|" },
                {  "Site": "84667006 |Bone structure of cervical vertebra|",
                    "Morphology": "72704001 |Fracture|" } ] },
        { "Group": [
                {  "Site":"71341001 |Bone structure of femur|",
                    "Morphology": "72704001 |Fracture|" } ] },
        { "Group":[  
                {  "Site":"12611008 | Bone structure of tibia|",
                    "Morphology": "72704001 |Fracture|" } ] } ] }

While it is important that there is no ambiguity as to how each piece of data should be used to create the resulting expressions, there are often opportunities to make the input data much simpler than is represented in the full logical model above. In particular:

• When the maximum cardinality of a relationship group is 1, there is no need to include the relationship group slot in the input data to group the attributes it contains;
• When the maximum cardinality of an attribute name-value pair is 1, there is no need to include the attribute name-value pair slot in the input data to group the corresponding name and value pairs;
• When there is either an attribute name slot with a fixed attribute value, or a fixed attribute name with an attribute value slot, there is no need to include the attribute name-value pair slot in the input data to group the corresponding name and value pairs.
• When the maximum cardinality of the focus concept slot is 1, the
• whenever the maximum cardinality of the focus concept, the relationship groups and attribute

With this in mind, the examples in 8 Expression Template Examples simplify the input data, where appropriate, using these assumptions and an implicit association with the logical model described above.

Summary

In summary, it is recommended to be as explicit as possible when specifying input data for expression templates. However, in situations the input data can be simplified, and then following default can be  assumed by the input data:

• if the expression column is omitted then it is assumed that each row should be processed into separate expressions (i.e. no repeating of rows into the same expression)
• if the grouping is omitted, then it can be assumed that each column should be processed into separate expression parts (i.e. no grouping of rows into the same expression)