SNOMED Documentation Search
...
Scg expression | ||||
---|---|---|---|---|
| ||||
[[1..*]] [[+id (<< 64572001 |Disease|) @Disease]]: [[1..* @Group]] { [[1..* @CausedBy]] 246075003 |Causative agent| = [[+id (< 410607006 |Organism|) @Organism]], [[0..1 @After]] 255234002 |After| = [[+id (< 404684003 |Clinical finding|) @Finding]] } |
Expression Data | Disease | Group | CausedBy | Organism | After | Finding | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 |
| 1 | 1 |
| 1 |
| ||||||||||||
| 2 |
| ||||||||||||||||
2 | 1 |
| 1 |
The input data above includes 2 focus concepts, 2 relationship groups, and 2 CausedBy attribute-name value pairs in the first relationship group. To support this input data, the expression template must duplicate the focus concept, relationship group, and the attribute name-value pair (in the first relationship group).
...
In particular, this step involves moving removing any extra brackets (i.e. "( ... )"), braces (i.e. "{ ... }"), colons (i.e. ":"), equals (i.e. "="), attribute names or connectors (i.e. "+" or ",") that would cause the resulting expression to be syntactically invalid. Extraneous characters are most likely to occur when optional parts of an expression template have no corresponding value in the populated expression. When this occurs, clean up may be required to remove these characters.
...