Page History

The template population processing requirements include:

 Requirement P.1: Processability of Processable input data

Expression templates Input data must be able to be processed against a specified input data (set of slot values). 

Input data should explicitly specify when multiple (or empty) slot values should be instantiated as multiple (or zero) attributes, multiple (or zero) groups, or multiple (or zero) full expressions. 

...

available, which can be automatically processed with the template to populate the slots with values. Input data must be clear (either explicitly or implicitly) as to which slot it is intended to populate, and whether multiple values are intended to be used within the same relationship group, the same expression (but different relationship groups), or different expressions.

Requirement P.2:  Cardinality and value constraints validity after processingPost-processing validity of constraints

After template processing, the resulting language instance (e.g. expression) must be valid against the cardinality, slot type and value constraints that were defined Processing of expression templates should validate any cardinality or value constraint expressed in the template.  

Requirement P.3: Syntactical validity after processingPost-processing syntactic validity

After template processing, the resulting language instance (e.g. expression) must Processing of an expression templates should result in a syntactically valid SNOMED CT expression, and hence conform to the ABNF rules syntax of that the associated base language . For expression templates, the language to validate against is the SNOMED CT Compositional Grammar(e.g. SNOMED CT compositional grammar).

Requirement P.4: Substrate validity after processing 

If the expression template is being used as the definition of a precoordinated concept, the resulting expression must conform with the rules for representing content in RF2. For example, nested attribute values would not be allowed.

Post-processing concept model validity

After template processing, the resulting language instance (e.g. expression) should be valid according to the concept model rules defined by the relevant MRCM. 

Requirement P.5: Concept model validity after processing

In some circumstances, it may be required for the resulting expression to be valid according to the concept model rules.

...

Post-processing use case validity

After template processing, the resulting language instance (e.g. expression) should conform to all additional rules that are imposed by the relevant use case. For example, if an expression template is being used to author precoordinated concepts, then the resulting expression must not use nested values (to enable representation in RF2).