PurposeThe Concept |
---|
ShowParts | term |
---|
t | 705109006 Code to expression type reference set |
---|
| is designed to enable associations between code 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. |
Field | Data type | Purpose | | Part of Primary Key |
id | | A 128 bit unsigned Specref |
---|
RefType | (data type) |
---|
t | Integer |
---|
| , uniquely identifying this .Different versions of a reference set member share the same but have different Specref |
---|
RefType | (field) |
---|
t | effectiveTime |
---|
| . This allows a reference set member to be modified or made (i.e. removed from the active set) at a specified time. | NO | YES (Full/Snapshot) |
Specref |
---|
RefType | (field) |
---|
t | effectiveTime |
---|
|
| | The inclusive date or time at which this version of the identified Gloss |
---|
Space | true |
---|
t | reference set member |
---|
| became the current version.The current version of this Gloss |
---|
Space | true |
---|
t | reference set member |
---|
| at time T is the version with the most recent Specref |
---|
RefType | (field) |
---|
t | effectiveTime |
---|
| prior to or equal to time T . | YES | YES (Full) Optional (Snapshot) |
| Specref |
---|
RefType | (data type) |
---|
t | Boolean |
---|
|
| The state of the identified Gloss |
---|
Space | true |
---|
t | reference set member |
---|
| as at the specified Specref |
---|
RefType | (field) |
---|
t | effectiveTime |
---|
| .If = 1 (true) the Gloss |
---|
Space | true |
---|
t | reference set member |
---|
| is part of the current version of the set, if = 0 (false) the Gloss |
---|
Space | true |
---|
t | reference set member |
---|
| is not part of the current version of the set. | YES | NO |
| | Identifies the Gloss |
---|
Space | true |
---|
t | SNOMED CT module |
---|
| that contains this Gloss |
---|
Space | true |
---|
t | reference set member |
---|
| as at the specified Specref |
---|
RefType | (field) |
---|
t | effectiveTime |
---|
| .The value must be a of Concept |
---|
t | 900000000000443000|Module (core metadata concept)| |
---|
ShowFormat | inline |
---|
| within the metadata . | YES | NO |
| | Identifies the to which this Gloss |
---|
Space | true |
---|
t | reference set member |
---|
| belongs.In this case, set to as subtype descendant of: Concept |
---|
ShowParts | term |
---|
t | 705109006 Code to expression type reference set |
---|
|
| NO | NO |
Specref |
---|
RefType | (field) |
---|
t | referencedComponentId |
---|
|
| | A reference to the Gloss |
---|
Space | true |
---|
t | SNOMED CT component |
---|
| to be included in the . | NO | NO |
| | The to/from which the concept is mapped. | NO | NO |
| | A that represents the SNOMED CT definition of the . This expression may be a Gloss |
---|
t | stated |
---|
GlosTerm | stated view |
---|
| or of the definition provided that documentation of each identified reference set specifies the view provided.The expression must conform to the syntax defined in the SNOMED CT Compositional Grammar - Specification and Guide (http://snomed.org/scg). | YES | NO |
| Indicates whether or not the expression contains a sufficient definition of the
in the mapTarget field.
Possible values are the following subtypes of Concept |
---|
t | 900000000000444006 Definition status |
---|
|
: Scg expression |
---|
900000000000074008 |Necessary but not sufficient concept definition status|
900000000000073002 |Sufficiently defined concept definition status| |
Refset spec table |
---|
Size | fs7 |
---|
RefsetType | Code to Expression Reference Set |
---|
|
|
refs
YES | NO | | | The correlation between the SNOMED CT expression and the . Possible values are the following subtypes of Concept |
---|
t | 447247004 SNOMED CT source code to target map code correlation value |
---|
| : Scg expression |
---|
447559001 |Broad to narrow map from SNOMED CT source code to target code|
447557004 |Exact match map from SNOMED CT source code to target code|
447558009 |Narrow to broad map from SNOMED CT source code to target code|
447560006 |Partial overlap between SNOMED CT source code and target code| |
When these values are applied to this reference set type, the phrase "SNOMED source code" is interpreted as meaning "SNOMED expression" and "target code" refers to the Gloss |
---|
t | other-code. |
---|
t: | other-codes |
---|
| . | YES | NO |
| | Indication of whether the concept was initially in one of the terminologies (SNOMED CT or Gloss |
---|
t | other-codes |
---|
t: | other-codes |
---|
| ) and added to the other as part of mapping or was in both terminologies at the outset. Values are subtypes of Concept |
---|
t | 705116007 Original code system source for linked content value |
---|
| . | YES | NO