Parent topic: 4.5. Requirements summaryPrevious topic: 4.5.2.7. Terminology structure: relationshipsNext topic: Terminology maintenance and distributionCurrent Guidance Page reference:
www.snomed.org/eg?t=overview_requirements_sum_content

4.5.3. Content

4.5.3.1. Content scope

The scope covered by SNOMED CT must be adequate to meet the requirements of various countries, organizations, disciplines and specialties. The extent to which the content requirements of different realms are covered is likely to develop over time. However, the initial release should cover:
  • The scope of the existing clinical terminologies that it is intended to replace:
    • All versions of the Read Codes and NHS Clinical Terms.
    • All versions of SNOMED including SNOMED RT.
  • Other scope requirements to be identified by the Editorial Board.

4.5.3.2. Content updates

The content of SNOMED CT must be regularly updated.

4.5.3.3. Content levels of granularity

SNOMED CT must allow coded meanings to be expressed at different levels of granularity.

4.5.3.4. Content not elsewhere classified

Codes from legacy terminologies with the "not elsewhere classified" label must be retired and no new ones may be added.

4.5.3.5. Extensions

To allow scope requirements not met by the main body of SNOMED CT , the terminology structure must be designed to accommodate extensions to the main body of work. Extensions should be distinguishable from components issued as part of the main body of SNOMED CT and should be traceable to a responsible organization. It must be possible to distinguish and trace the source of a code or identifier used in a patient record.

^ Previous topic: 4.5.2.7. Terminology structure: relationshipsNext topic: Terminology maintenance and distribution

July 2012 International Release

Copyright 2002-2012 International Health Terminology Standards Development Organisation (www.ihtsdo.org)