3.1. Requirements

To decide if a reference set is needed, successful implementers of SNOMED CT must clearly understand their requirements.

The table below shows some typical requirements that may be met using SNOMED CT reference sets. The examples in this table are not exhaustive, but instead illustrate common use cases in which the category of requirement is needed. T he table also shows the type (or types) of reference set that best meets each requirement . For more information on each requirement category, please click on the diagram to visit the relevant section.

REQUIREMENTS	EXAMPLE USE CASES	REFERENCE SET
3.1.1. A Subset of Components 3.1.1. A Subset of Components	3.2.6.1. Constrain Value Sets 3.2.3.2. Specifying Queries for Retrieval and Analysis 3.2.5.2. Interface Terminology	5.1. Simple Reference Set
3.1.2. An Ordered List of Components 3.1.2. An Ordered List of Components	3.2.1.4. Order Items for Search and Data Entry 3.2.1.5. Alternative Hierarchical View	Ordered Reference Set
3.1.3. A Set of Associations between Components 3.1.3. A Set of Associations between Components	3.2.6.3.2. Representing Historical Associations 3.2.1.6. Use Case Specific Associations	5.4. Association Reference Set
3.1.4. A Set of Components Annotated with Additional Information 3.1.4. A Set of Components Annotated with Additional Information	3.2.2.1. Linking Concepts to Web Resources Link components to a textual advice	5.6. Annotation Reference Set
3.1.5. A Set of Maps between SNOMED CT and Another Code System 3.1.5. A Set of Maps between SNOMED CT and Another Code System	3.2.3.1. Maps to Statistical Classifications Link concepts to legacy codes and data, to support migration	5.2.9 Simple Map Reference Set 5.2.10 Complex and Extended Map Reference Sets
3.1.6. A Set of Sets of Components 3.1.6. A Set of Sets of Components	3.2.6.2. Managing Value Sets 3.2.6.2. Managing Value Sets	5.1. Simple Reference Set 5.2. Query Specification Reference Set

Page tree

3.1. Requirements