# Summary of SNOMED CT Requirements

A summary of the SNOMED CT requirements is as follows. Additional information may be found throughout this guide, as well as in other documents on the [SNOMED International website](https://www.snomed.org/).

## Terminology Structure Requirements

<table><thead><tr><th width="209.37109375">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Coded meaning</td><td><ul><li>The central component is coded meanings.</li></ul><ul><li>Each code must have a single clear and unambiguous meaning</li></ul></td></tr><tr><td>Identifier</td><td><ul><li>Components must have unique identifiers.</li></ul><ul><li>The internal structure of these identifiers must not imply the meaning or relationships of a code</li></ul></td></tr><tr><td>Description</td><td><ul><li>Represents the association between terms (text strings) and the meanings that they describe (may be language or dialect dependent)</li></ul></td></tr><tr><td>Preferred Term</td><td><ul><li>Represents the special association between each code and a preferred term (used to display the meaning, unless there is an alternative preference)</li><li>The preferred term association is language or dialect dependent</li></ul></td></tr><tr><td>Fully Specified Name</td><td><ul><li>Provides each code with a structured fully specified name that unambiguously describes its meaning</li></ul><ul><li>The fully specified name is defined in a reference language (the language of first use)</li><li>Translations of the fully specified name may also be required</li></ul></td></tr><tr><td>Hierarchy</td><td><ul><li>Represents hierarchical relationships between coded meanings</li><li>The form of representation allows a coded meaning to have multiple hierarchical parents (supertypes)</li><li>It guarantees that any alternative hierarchical view of a coded meaning is consistent</li></ul></td></tr><tr><td>Relationship</td><td><ul><li>Represents non-hierarchical relationships between coded meanings</li></ul></td></tr></tbody></table>

## Content Requirements

<table><thead><tr><th width="211.62890625">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Scope</td><td><ul><li>The scope is adequate to meet the requirements of various countries, organizations, disciplines, and specialties</li><li>The extent to which the content requirements are covered develops over time</li></ul></td></tr><tr><td>Updates</td><td><ul><li>The content is regularly updated</li></ul></td></tr><tr><td>Granularity</td><td><ul><li>Allows coded meanings to be expressed at different levels of granularity</li></ul></td></tr><tr><td>Not Elsewhere Classified (NEC); Not Otherwise Specified (NOS)</td><td><ul><li>Codes with not elsewhere classified or not otherwise specified must be inactivated and no new ones may be added</li></ul></td></tr><tr><td>Extension</td><td><ul><li>Allows extensions to the main body of work</li><li>Extensions are distinguishable from components of the main body; should be traceable to a responsible organization</li><li>Allows for distinguishing and tracing the code source or identifier used in patient records</li></ul></td></tr></tbody></table>

## Maintenance and Distribution Requirements

<table><thead><tr><th width="208.375">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Distribution</td><td><ul><li>Distributed in a format that is readily usable by application developers</li><li>This format is fully specified and is not changed from release to release</li><li>May be distributed for use with associated software, such as a browser</li></ul></td></tr><tr><td>Persistence</td><td><ul><li>The meaning of a code is persistent; It is not changed or deleted by updates</li><li>A code may be marked as inactivated when its meaning is found to be ambiguous, redundant or otherwise incorrect</li><li>Changes to the association between a concept and a code do not change or delete the description.</li><li>The description is marked as inactivated, and a new corrected description is created</li></ul></td></tr><tr><td>History</td><td><ul><li>All changes to components are tracked and saved in history files (includes details about new components and changes to the status of components)</li><li>When a component is made inactive, relationships or references indicate the replacement or equivalent component</li></ul></td></tr></tbody></table>

## Subset Requirements

<table><thead><tr><th width="204.90234375">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Concepts</td><td><ul><li><p>Includes a mechanism for representing subsets of concepts appropriate for a language, dialect, or specialty. It should allow:</p><ul><li>Specification of the synonyms, preferred terms, and translated fully specified names in each language or dialect</li><li>Rational combination of languages and modification of language subsets to meet the needs of organizations or specialties</li></ul></li></ul></td></tr><tr><td>Codes</td><td><ul><li><p>Includes mechanisms for representing subsets of codes for a country, organization, discipline, or specialty. The form of representation should allow:</p><ul><li>An indication of the priority, or frequency of use</li><li>Rational combinations of subsets to meet the needs of users or groups of users</li></ul></li></ul></td></tr><tr><td>Specified Contexts</td><td><ul><li>Includes mechanisms for representing subsets of codes and concepts for particular contexts in a record, decision support protocol, or data entry field</li></ul></td></tr><tr><td>Combinations</td><td><ul><li>Include consistent rules for combining subsets to meet the requirements of users</li></ul></td></tr><tr><td>Distribution and Installation</td><td><ul><li><p>Subsets are distributed in a format that is readily usable by system developers. The format is fully specified and does not vary from release to release. The distribution format allows:</p><ul><li>Subsets to be installed separately</li><li>Related or interdependent subsets to be selected and installed as groups</li><li>Subsets to be updated with each new release</li></ul></li></ul></td></tr><tr><td>Configuration</td><td><ul><li>It is possible to configure an application to use a particular subset or combination of subsets; changing configurations does not require reinstallation</li></ul></td></tr></tbody></table>

## Relationships Requirements

<table><thead><tr><th width="204.96875">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Navigating Relationships</td><td><ul><li>Includes relationships that allow hierarchical navigation from a chosen code to a code that represents either a subtype or part of the chosen code</li><li>Supports navigation from a specific code to more general codes that represent a supertype of that code</li><li>Navigational concepts are not supported by SNOMED International</li></ul></td></tr><tr><td>Aggregation of Related Codes</td><td><ul><li>Includes relationships that allow aggregation of related codes to enable comprehensive and accurate retrieval from patient records</li><li>These relationships, together with appropriate history and cross-reference tables, enable the aggregation to include inactivated codes with similar or equivalent meanings</li></ul></td></tr><tr><td>Defining Characteristics</td><td><ul><li>Includes formal definitions of codes represented by relationships with defining characteristics (e.g. the anatomical site of the code named appendicitis is the vermiform appendix )</li></ul></td></tr><tr><td>Qualifying Characteristics</td><td><ul><li>Enables a code recorded in a patient record to be qualified by adding relevant qualifying characteristics</li><li>Each qualifying characteristic is itself a code with a specified relationship to a qualified code</li><li>Specifies possible qualifying characteristics for each code or for a group of related codes (e.g. an anatomical site could be added to the code named osteoarthrosis )</li></ul></td></tr><tr><td>Kind-of-Value</td><td><ul><li>Enables codes to be qualified by the addition of relevant values</li><li>Specifies the types of values that can be added to particular codes (e.g. a substance concentration value can be added to the code named hemoglobin concentration )</li></ul></td></tr><tr><td>Additional Characteristics</td><td><ul><li>Is able to assert other characteristics of a code that may be time- or context-dependent (e.g. new medical information may require updates to some codes)</li></ul></td></tr></tbody></table>

## Retrieval Requirements

<table><thead><tr><th width="205.25">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Analysis</td><td><ul><li><p>Enables the consistent and reproducible storage of information, which is subsequently retrieved for analysis; this requires retrieval that allows the inclusion of subtypes and equivalent codes to be included. Equivalent codes may include:</p><ul><li>Codes represented in another (legacy) coding scheme</li><li>Redundant codes that were inactivated</li><li>Combinations of general codes and qualifying characteristics</li></ul></li><li>Analysis usually requires retrieval of selected records from a population of patient records; usually performed in batch</li></ul></td></tr><tr><td>Patient Review</td><td><ul><li>Enables the consistent and reproducible storage of information, which is subsequently retrieved for patient recall for preventive procedures or review; requirements similar to those for analysis</li></ul></td></tr><tr><td>Decision Support</td><td><ul><li>Enables the consistent and reproducible storage of information, which is subsequently retrieved for decision support</li><li><p>Requirements are broadly similar to those for analysis</p><ul><li>Decision support requires retrieval of selected records from an individual patient record</li><li>Requires real-time processing to determine code meaning equivalence</li></ul></li></ul></td></tr><tr><td>Presentation</td><td><ul><li>Enables the consistent and reproducible storage of information, which is subsequently retrieved for presentation</li><li><p>Requirements are similar to those for decision support</p><ul><li>Must be real-time, but usually involves filtering by broad categories of code; less precise than for decision support</li></ul></li></ul></td></tr></tbody></table>

## Searches and Text Parsing Requirements

<table><thead><tr><th width="206.7421875">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Searches and Text Parsing</td><td><ul><li><p>SNOMED CT facilitates searches for descriptions A simple keyword index may be generated from the descriptions and used for more effective searching although this may not be optimal due to:</p><ul><li>Use of abbreviations</li><li>Word form variants</li><li>Word order variants</li><li>Word equivalences and combinations</li><li>Locally added mnemonics for frequently used descriptions</li><li><p>Composite coded meanings that can only be represented by:</p><ul><li>Combinations of a code with one or more qualifying characteristics</li><li>Multiple codes related together by the patient record structure components</li></ul></li><li><p>Searches with multiple redundant hits for a single code</p><ul><li>When several synonyms of the same code match the search key</li><li>When techniques for word equivalences and combination are applied and return alternative descriptions related to the same code for two or more word equivalences</li></ul></li><li>Searches with multiple redundant hits for a large number of closely related coded meanings</li><li>Search keys matching descriptions associated with a code with a more general meaning and many of its more specific hierarchical descendants</li></ul></li></ul><p>A further complication is the application of searches within subsets. This restricts the range of available concepts or codes; efficiency may depend on the relationships of keyword indices and subsets</p></td></tr><tr><td>Parsing or Encoding Free Text</td><td><ul><li>The use of natural language parsing to encode free-text derived from typing, scanning, or voice recognition is increasing; the text of descriptions and associated search indices may assist with this process</li></ul></td></tr></tbody></table>

## Implementation Requirements

<table><thead><tr><th width="199.78125">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Terminology Services</td><td><ul><li>Terminology services should be implemented independent of application data; by individual applications or by terminology servers accessible by many applications</li></ul></td></tr><tr><td>Advice</td><td><ul><li>Application data cannot be specified to the same level of detail as terminology services. It us dependent on the general functionality of the application and its record structure</li><li>Providing advice early in the SNOMED CT implementation process is required. This helps with some issues that may not be immediately apparent to developers</li></ul></td></tr><tr><td>Limited Applications</td><td><ul><li>The advice provided should not place onerous requirements on applications with limited needs for the SNOMED CT terminology</li><li>It is inappropriate to have all-or-nothing requirements for SNOMED CT enabled applications</li></ul></td></tr></tbody></table>

## Legacy Data and Migration Requirements

<table><thead><tr><th width="201.7734375">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Code Recognition</td><td><ul><li>It should be possible to distinguish a code from an earlier coding schemes (SNOMED, Read Codes, or NHS Clinical Terms) from the identifiers used in SNOMED CT</li></ul></td></tr><tr><td>Equivalence</td><td><ul><li>It must be possible to relate each code in early coding schemes (SNOMED, Read Codes, or NHS Clinical Terms) to a code in SNOMED CT</li></ul></td></tr><tr><td>Query/Protocol Conversion</td><td><ul><li>There must be support to convert queries and protocols, based early coding schemes (SNOMED, Read Codes, or NHS Clinical Terms), to SNOMED CT compatible forms</li></ul></td></tr><tr><td>Record Conversion</td><td><ul><li>It should be possible to convert legacy data, based on early coding schemes (SNOMED, Read Codes, or NHS Clinical Terms), to SNOMED CT compatible forms. This is subject to medico-legal constraints</li></ul></td></tr><tr><td>Migration of Terminology-Dependent Products</td><td><ul><li>Projects in the UK NHS, that currently make use of Read Codes or NHS Clinical Terms, must plan migration to allow future use of SNOMED CT</li></ul></td></tr></tbody></table>

## Data Structure Requirements

<table><thead><tr><th width="196.25390625">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Patient Record Architectures</td><td><ul><li><p>SNOMED CT is intended to represent clinical meanings in patient records</p><ul><li>A patient record consists of a series of related statements that are organized under headings</li><li>The statements and headings may contain clinical codes derived from SNOMED CT</li><li>Headings, and other contextual elements, may modify the meaning of related statements</li></ul></li><li><p>The relationship between a terminology, such as SNOMED CT, and a record architecture can be summarized as follows:</p><ul><li><p>SNOMED CT codes and terms may populate different elements in the record structure</p><ul><li>Different SNOMED CT codes may be applicable to different elements in the record</li><li>Some codes may not be appropriate for inclusion in the record</li></ul></li><li>The meaning of a SNOMED CT code may be modified by its context within the record structure</li></ul></li><li><p>SNOMED CT should be evaluated within the context of evolving standards for patient record architectures. Recommendations based on the evaluations may include:</p><ul><li>Possible changes to record architectures in order to realize benefits from SNOMED CT</li><li>Changes to SNOMED CT to better fit into record structures</li><li>Selecting SNOMED CT codes for use in specific record structure contexts</li></ul></li></ul></td></tr><tr><td>Expression Coordination and Equivalence</td><td><p>Some codes may be entered in a precoordinated or a post-coordinated manner.<br>For example, "excision of ovary" might be entered by:</p><ul><li>selecting the precoordinated code 83152002 |Oophorectomy (procedure)|, OR</li><li><p>alternatively by selecting the codes for</p><ul><li>71388002 |Procedure (procedure)| and adding the qualifying characteristics:<br>260686004 |Method (attribute)| = 129304002 |Excision - action (qualifier value)|<br>405813007 |Procedure site - Direct (attribute)| = 15497006 |Ovarian structure (body structure)|</li></ul></li><li>The coded meanings are stored in the forms entered. This may be using a single precoordinated code, a single post-coordinated expression, or a set of separate codes that together represent the clinical meaning.</li><li>A retrieval query must therefore search for the precoordinated and all possible post-coordinated ways of expressing equivalent meanings. This can be done using the Expression Constraint Language (<a href="http://snomed.org/ecl">http://snomed.org/ecl</a>) and a terminology service that can compute subsumption between expressions.</li><li>These methods for retrieving records based on their clinical meaning rely on the formal definitions of SNOMED CT concepts being as complete as possible. Missing defining characteristics may result in problems with equivalence testing and therefore data retrieval.</li></ul></td></tr></tbody></table>

## Communication Requirements

<table><thead><tr><th width="205.265625">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Clinical Information</td><td><ul><li>The ability to communicate clinical information (represented by SNOMED CT) between applications must be supported</li><li>Message specifications and other communication structures must accommodate SNOMED CT identifiers, and combinations of identifiers, in order to express postcoordinated coded meaning</li></ul></td></tr><tr><td>Message Specifications</td><td><ul><li>Current message specifications (e.g EDIFACT, HL7, and XML) use plain text files; SNOMED CT identifiers must use plain text so that they are appropriate for these messages</li></ul></td></tr><tr><td>Postcoordinated Expressions</td><td><ul><li>Communication of postcoordinated expressions may be possible using specific qualifier fields in messages. This can also be accomplished by using syntactic representation of identifier combinations; these must be consistent with message syntax and field size limitations</li></ul></td></tr></tbody></table>

## Mapping Requirements

<table><thead><tr><th width="205.6015625">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Classification</td><td><ul><li>Based on recorded codes, mapping tables are used to generate statistical and administrative data</li><li>Automation of the process depends on the nature of the classification, the richness of the mapping table, and the functionality of the mapping software</li></ul></td></tr><tr><td>Grouping</td><td><ul><li>Mapping tables are used to generate groupings for funding, administration, etc.</li><li>Mapping to a classification, then using the classification codes to generate groupings, is an alternative method</li></ul></td></tr><tr><td>Communication Specifications</td><td><ul><li>Codes are mapped to specific values, in an enumerated list, associated with a message or communication specification</li><li>Recognizing these mappings may prevent double data entry, when sending or receiving such messages</li></ul></td></tr><tr><td>Reference Works</td><td><ul><li>Codes are used to establish links with decisions-support protocols or other references</li><li>Mapping between these codes and reference sources may help to facilitate their use</li></ul></td></tr></tbody></table>

## Availability Requirements

<table><thead><tr><th width="205.2890625">Requirement</th><th>Description</th></tr></thead><tbody><tr><td>Limited Applications</td><td><ul><li>Applications vary in their ability to use terminological components.</li><li>Special consideration may be necessary for applications that require only limited use of SNOMED CT</li></ul></td></tr><tr><td>Concepts in Different Languages</td><td><ul><li>Translating SNOMED CT into other languages is required</li><li>Multiple translations may support communication of clinical information across language barriers</li></ul></td></tr><tr><td>Patients</td><td><ul><li>Patients may be users of SNOMED CT if they record information in their own medical records</li><li>This may require limited licensing of SNOMED CT for populations, in general</li></ul></td></tr></tbody></table>

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Summary%20of%20SNOMED%20CT%20Requirements" class="button primary">Provide Feedback</a>
