PurposeThe Concept |
---|
ShowParts | term |
---|
t | 705109006 Code to expression type reference set |
---|
| is designed to enable associations between codes in another code system Gloss |
---|
t | (other-codes) |
---|
t: | other-codes |
---|
| and , where the following constraints apply:- Some of the
Gloss |
---|
t | other-codes |
---|
t: | other-codes |
---|
| cannot be mapped to an individual SNOMED CT . - Licensing conditions (or other considerations) prevent addition of new SNOMED CT concepts to represent the same meaning as the
Gloss |
---|
t | other-codes |
---|
t: | other-codes |
---|
| . - The
Gloss |
---|
t | other-codes |
---|
t: | other-codes |
---|
| can be logically defined using the to represent the same meaning or a similar though less specific meaning . - Other requirements similar for those applicable to mapping may also apply including:
- An indication of the degree of correlation between the and the SNOMED CT expression.
- An indication of whether the was created before any single concept representation of that meaning in SNOMED CT or whether the single concept representation in SNOMED CT predated the creation of the association.
Data StructureThe general approach to the above requirements is to associate each of the Gloss |
---|
t | other-codes |
---|
t: | other-codes |
---|
| with a representation of the same logic based definition as would have been applied to a SNOMED CT concept with that meaning. However, since the are not identified by an , the logical definition cannot be represented using . There are two potential approaches to this, one would be to use a general purpose description logic language (e.g. ) and the other is to use a to represent each definition. The Concept |
---|
ShowParts | term |
---|
t | 705109006 Code to expression type reference set |
---|
| is designed to support the expression-based approach.
Refset spec table |
---|
Size | fs7 |
---|
RefsetType | Code to Expression Reference Set |
---|
| |
refs
|