Page History

...

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

A subset of components

Simple reference set

An ordered list of components

Link components to web-resources Annotation reference setA set of maps or links other code systemsLink concepts to a statistical classification to enable statistical analysis (specification) Set (specification)

A set of sets of components

Simple reference set

Query specification reference set

REQUIREMENTS	EXAMPLE USE CASES	REFERENCE SET
Image Modified	Specify a value set within a specific clinical domain Specify groups of concepts for analytics purposes Specify descriptions used for data entry	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
Image Modified	Prioritize data entry items or search results Specify alternative hierarchies for navigation	Ordered reference set
Image Removed A set of associations between components	Associate inactive components with their replacements Associate components of different types to support consistent and efficient documentation	Association reference set
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	5.3. Ordered Reference Set
Image Added 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
Image Added 3.1.4. A Set of Components Annotated with Additional Information	3.2.2.1. Linking Concepts to Web Resources	Image Removed A set of components annotated with additional information	Link components to a textual advice	5.5. Annotation Reference Set
Image Modified	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	4.2.8. Simple Map Reference Set	4.2.9.	Complex and Extended Map Reference	Sets
Image Modified	Specify a set of subsets for a particular organisational unit Specify a set of intensionally defined subsets	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

Search

Page tree

Versions Compared

Old Version 3

New Version 4

Key