Refer to http://snomed.org/-sts
Reconfirm decisions made in London include:
- Slot names will be used (@name), slot references are out of scope for v1 (no $reference)
- Slot names must be unique within a template OR Allow slot names to be repeated within a template and interpret this as meaning that the value is the same
- For next week: Discuss an example in which repeated slot names may be required (e.g. finding and observable)
- Default cardinality of all slots is [1..*]
- Exclusive slot ranges will be represented by adding a '>' before the minimum and/or a '<' before the maximum - e.g. [[+int (>#20..<#30)]]
- No minimum or maximum will be represented by omitting the respective value in the range - e.g. [[+int (#20..)]]
Examples of non-unique slots:
Scg expression |
---|
404684003 | finding |: {
363698007 | finding site | = [[ + @site ]],
363714003 | interprets | = ( 363787002 | observable |: 704319004 |inheres in| = [[ + @site ]]) } |
Scg expression |
---|
| specimen |: {
|specimen source topography| = [[ + @site ]],
|specimen procedure| = ( |procedure| : {|procedure site - Indirect| = [[ + @site ]] } ) } |
Examples of unique slots:
Scg expression |
---|
404684003 | finding |: {
363698007 | finding site | = [[ + @siteA ]],
363714003 | interprets | = ( 363787002 | observable |: 704319004 |inheres in| = [[ + (<< @siteA) @siteB ]] ) } |
Scg expression |
---|
| specimen |: {
|specimen source topography| = [[ + @siteA ]],
|specimen procedure| = ( |procedure| : {|procedure site - Indirect| = [[ + (<< @siteA) @siteB ]] } ) } |