There are a number of use cases for value sets, including constraining the permitted values for elements in a communication specification, specifying the values in a pick list on a user interface and defining the required values to use for reporting. Value sets may range from a simple flat list of codes from a single code system, to an unbounded hierarchical set of post-coordinated expressions drawn from multiple code systems. Value sets containing only SNOMED CT components may be represented as SNOMED CT reference sets.

For example, a message or reporting specification might define a single value set for a problem list, which includes: 

• SNOMED CT

  Concept
  t 64572001 | Disorder | ShowFormat inline

  concepts

• SNOMED CT expressions that are subtypes of 

  Concept
  t 64572001 | Disorder |

• ICD-10 classification codes representing diseases

Value Set Example

The diagram below illustrates an example of an Observation model, which may be used to support diagnosis, monitor progress, determine patterns in clinical data, etc. Each data element in the information model is linked to a value set, which represents the value values for that element. As shown below, the value sets used in this information model may be selected from different code systems. In some cases, a single value set may also include concepts from different code systems.

Value sets used in an information model