Parent topic: 3. SNOMED CT implementationPrevious topic: 3.1.4. Benefits of extensibility and configurabilityNext topic: Clinical recordsReview Guidance Background Material Page reference:
www.snomed.org/tig?t=tig_impl_type

3.2. Implementation Types

SNOMED CT itself is only a part of the solution to addressing the requirements for effective electronic clinical records. A terminology on its own "does" nothing unless it is implemented as part of an application and used. Implementation of SNOMED CT requires software applications that exploit its features to meet the real and perceived needs of users.

The "users" of SNOMED CT include:
  • Those who specify, commission and configure software for use in a particular clinical environment;
  • End-users who enter or retrieve clinical information.
As illustrated by Figure 1, users experience SNOMED CT through application software which delivers services to access and apply SNOMED CT. The ways in which applications apply the features of SNOMED CT to address user requirements determine the extent to which the potential benefits are realized.

The following sections summarize some of the types of implementation that may be needed to meet different requirements. Some types of application do not need to support or use all SNOMED CT features. However, there are some overarching requirements for consistency between implementation used within a given organization, country or region. Even where requirements are limited, care should be taken to ensure that SNOMED CT enabled applications are aligned with good practice and with agreed policies applicable to the situations in which they are used.

Figure 1. Relationship between users application software and SNOMED CT

^ Previous topic: 3.1.4. Benefits of extensibility and configurabilityNext topic: Clinical records