Page History

...

When a SNOMED CT extension is required, the extension may serve a range of purposes. Successful extension producers must clearly understand the requirements and purpose of their extension,  before before deciding which types of SNOMED CT artifacts should be included.

Table 3-1   below shows some typical purposes for a SNOMED CT extensions. For each purpose, the table includes some common use case examples and a list of SNOMED CT artifacts that should be included. For more information about each of these purposes, please click on the corresponding diagram.

Table 3-1: Purposes and use cases for extensions

Purpose	Use Case Examples	Included Artifacts
Translate SNOMED CTImage Removed Image Added	Adding terms used in a local language or dialect Adding terms used by a specific user group, such as patient friendly terms	Descriptions Language reference sets Concepts (metadata only) Relationships (metadata only)
Manage content gapsImage Removed Image Added	Adding components that are missing in the International Edition Adding concepts that are only relevant to a local context	Concepts Descriptions Relationships Language reference sets
Maps between SNOMED CT and other code systems Image RemovedImage Added	Maps between local codes and SNOMED CT Maps between statistical classification systems and SNOMED CT	Map reference sets Concepts (metadata only) Descriptions (metadata only) Relationships (metadata only)
Configuration of the terminology for specific use cases	Specifying groups of components for reporting and analytics Linking components to clinical knowledge resources	Reference sets Concepts (metadata only) Descriptions (metadata only) Relationships (metadata only)

...