Purpose

The 

1. Some of the 

   Gloss
   t other-codes t: other-codes

    cannot be mapped to an individual SNOMED CT 

   Gloss
   t concept

   .
2. 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

   .
3. The 

   Gloss
   t other-codes t: other-codes

    can be logically defined using the 

   Gloss
   t SNOMED concept model

    to represent the same meaning 

   Gloss
   t (sufficiently defined)

    or a similar though less specific meaning 

   Gloss
   t (primitive)

   .
4. Other requirements similar for those applicable to mapping may also apply including:
   1. An indication of the degree of correlation between the  

      Gloss
      t other-code t: other-codes

       and the SNOMED CT expression.
   2. An indication of whether the 

      Gloss
      t other-code t: other-codes

       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 Structure

The general approach to the above requirements is to associate each of the 

Code to 

Expression 

Reference 

Set - Data 

structure

Metadata

The following metadata

Code to Expression Reference Set in the Metadata Hierarchy

  900000000000454005 |Foundation metadata concept|
		900000000000455006 |Reference set|
				705109006 |Code to expression type reference set (foundation metadata concept)|

Descriptor template and examples

The tables below show the descriptors that define examples of

Refset Descriptor rows for a Code to Expression Reference Set

Code to Expression type Refset Examples

Sample Content from a Code to Expression Reference Set

Related Links

• For further information see Using LOINC with SNOMED CT: 4.2.2 LOINC Term to Expression Reference Set.

...