An Annotation Reference Set field containing additional information linked to a SNOMED CT component .

Note: Field name in SNOMED CT Release Format 2.

Related Links

• Annotation Reference Set (Deprecated)

Provide Feedback

Provide Feedback

A datatype that represents either true or false.

Note: In SNOMED CT release files the value 0 (zero) represents "false" and the value 1 (one) represents true.

Provide Feedback

Provide Feedback

The file structure used to distribute alternative Identifiers for SNOMED CT components.

Note: The Identifier file is not currently used in the SNOMED CT International Release as use of the more flexible Simple Map from SNOMED CT Reference Set / Simple Map to SNOMED CT Reference Set structures are preferred for links to/from alternative codes. The only known current use of this file is for internal identification of components during the content development process.

Provide Feedback

A field in the RF2 Identifier file containing a SNOMED CT identifier which identifies the alternate code system.

Note: In practice, the identifier file is not used in the SNOMED CT International Release as the use of Simple Map from SNOMED CT Reference Set or Simple Map to SNOMED CT Reference Set is preferred. The only current use of this file is for internal identification during the development process.

Related Links

• Identifier

Provide Feedback

A datatype that represents a whole number.

Note: In SNOMED CT release file specifications integers are represented as a string of decimal digits. The range of values and support for negative values may be constrained for the specification are specified for each usage of this datatype. However, unless otherwise specified, all release file fields of data type integer are assumed to be 32-bit signed integers.

Related Links

• Release File Data Types

Provide Feedback

Provide Feedback

Provide Feedback

A field in the Word Equivalents Table, which specifies the usual usage of this word, abbreviation or phrase, or the usage in which it has a similar meaning to the text in one or more other rows of the table that share a common WordBlockNumber.

Note: Field name in SNOMED CT toolkit

Provide Feedback

A field that provides the unique identifier of a component ( concept, description or relationship) or reference set member .

Note:

• The data type of the id for a component is SCTID and this identifier is used to refer to the component .

• The data type of the id for a reference set member is UUID. This identifier is only used to support versioning of a rows (member) in a Reference set it does not identify the Reference set itself (see refsetId) nor does it identify to a component refered to by the Reference set (see referencedComponentId).

A datatype representing a sequence of characters.

Note: In SNOMED CT release file specifications strings are represented using Unicode UTF-8 encoding.

A unique integer identifier applied to each SNOMED CT component ( Concept, Description, Relationship).

Note: The value of an SCTID is structured to include an item identifier, a check-digit and a partition identifier. Depending in the value of the partition identifier it may also include a namespace identifier.

A field in a that contains a text string representing criteria for selection of SNOMED CT components to be included in .

Note: A standard syntax for use in these queries is currently under development and is due for publication in late 2014.

A field in the Relationship Release File containing a SNOMED CT identifier that refers to the concept that represents the source of the associated Relationship. The sourceId refers to the concept that is defined by the Relationship .

Note: Field name in SNOMED CT Release Format 2. In RF1 this field was called ConceptId1

A field in the Module Dependency Reference Set which specifies the effectiveTime of the version of the source module with depends on the specified version of the target module. The effectiveTime must match exactly.

Note: Field name in SNOMED CT Release Format 2

A field in a Reference Set which uniquely Identifier which refers to the component to which a row in the Reference Set applies.

Note: This field is present in all types of Reference Sets and its data type is SCTID. It links together all the members of a Reference Set and refers to a concept that names the Reference Set .

A data table relating each word used in SNOMED CT (other than ) to the Descriptions.

Note: File or Table name in SNOMED CT toolkit

A data table in which each row represents a Word Equivalent.

Note: File or Table name in SNOMED CT toolkit

A field in the , which specifies whether this row contains a word, phrase, acronym or abbreviation.

Note: Field name in SNOMED CT toolkit

A previously used distribution file that contained the stated form represented by SNOMED CT relationships.

Notes:

1. The stated form of a Concept is the Description Logic definition that is directly edited by authors or editors. It consists of the stated relationships plus the defining relationships that exist prior to running a classifier on the logic definitions.

2. Prior to July 2019 the stated form of a Concept was represented by a collection of relationships: one or more |Is a|

A field in the Module Dependency Reference Set which specifies the effectiveTime of the version of the target module on which the specified version of the source module depends. The effectiveTime must match exactly.

Note: Field name in SNOMED CT Release Format 2

A field in the Identifier file containing the representation of an Identifier in another code system that is irrevocably linked to a SNOMED CT identifier .

Order ... to be defined.

Note: Field name in SNOMED CT Release Format 2

A field in the Concept Release File containing a SNOMED CT identifier which specifies whether the concept is fully defined or primitive .

Note: Field name in the SNOMED CT Release Format 2 concepts table.

A field in each component release file which represents the development module within which it was created and is maintained.

Note: Field name in SNOMED CT Release Format 2.

A standard method of directly encoding Unicode using two bytes for every character.

Note: SNOMED CT release files do not use UTF-16. However, the UTF-8 representation used in release files can be converted to UTF-16.

Related Links

• Release File Data Types

• Unicode UTF-8 encoding

Provide Feedback

The file structure used to distribute SNOMED CT descriptions.

• Component File name in SNOMED CT Release Format 2

Field in the Relationship File is used to group Relationships together for a concept. For example, where a particular type of prosthesis is inserted a joint, the Defining characteristics describing the prosthesis type would be in one group whereas those describing the location or laterality of the joint would be in another group.

Field in a containing an integer that groups a set of complex map records from which one may be selected as a target code. Where a SNOMED CT concept maps onto 'n' target codes , there will be 'n' groups, each containing one or more complex map records.

A word that in a given language is so frequently used, or has so poor a discriminating power, that it is suggested for exclusion from the indices used to support textual searches of SNOMED CT. Excluded Words are represented as a row in the

Note: Field name in SNOMED CT toolkit

A table in which each row represents a

Note: File or Table name in SNOMED CT toolkit

A standard character set, which represents most of the characters used in the world using a 16-bit encoding.

Note: The Unicode character set can be encoded using either UTF-16 or UTF-8. UTF-16 uses two bytes for every character. UTF-8 is able to store the most commonly used characters in western alphabets using a single byte, but it requires two bytes to encode accented characters and three bytes to encode symbols used in many non-European scripts.

A Boolean field that specifies whether an identified component or is an active from the point in time specified by the effectiveTime .

Note: Field name in SNOMED CT Release Format 2.

Field in a or a that contains the target code(s) to which the SNOMED CT concept represented the referencedComponentId is mapped in the target scheme .

The file structure used to distribute SNOMED CT Reference sets .

A field in the Relationship Release File containing a SNOMED CT identifier that refers to the concept that represents the destination (or attribute-value) of the associated Relationship .

Note: Field name in SNOMED CT Release Format 2. In RF1 this field was called ConceptId2

A field in a that indicates the acceptability of a Description in the language or dialect specified by that Reference Set . Values include "preferred" and "acceptable".

Note: Field name in a

A field in the Component annotation type reference set or a Member annotation type reference set, containing a that indicates the language and/or dialect of the string held in the field.

The format of the languageDialectCode string follows the standard .

Note: Field name in the SNOMED CT Release Format 2 relationships table.

A field in the , which contains a word, phrase, acronym or abbreviation that is considered to be similar in meaning to the text in one or more other rows of the table that share a common .

Note: Field name in SNOMED CT toolkit

Specifies the inclusive date at which the component version's state became the then current valid state of the component.

Note: Field name in SNOMED CT Release Format 2

A field in a Reference Set containing an UUID which refers to the relevant member of another Reference Set in SNOMED CT.

Currently this is used in the

A file containing the transitive closure of the SNOMED CT subtype hierarchy.

The transitive closure file is not currently distributed but can be generated from the snapshot relationship file using a script file. The script file is available for download at http://snomed.org/transclose or via GitHub as part of one of the database loaders ().

• for further details.

A field in the Description file that associates a term with the concept to which it applies .

Note: Field name in the Description file .

Provide Feedback

A reference to a concept that specifies the name and/or usage of an additional attribute in a Refset. If the attributeType is component reference, the values applied to this additional attribute are restricted to subtypes of this concept .

Note: Field name in a SNOMED CT Release Format 2 Reference Set Descriptor.

Provide Feedback

A field holding either an Integer, Decimal, or Text represented as a string. Numbers are prefixed with a # (hash) symbol. Texts are surrounded with " (double quote) with double quotes inside the string escaped using \ (backslash).

Note: The field is used in the following Release Format 2 specifications:

• Concrete Value File Specification

• Component Annotation String Value Reference Set

The file structure used to distribute SNOMED CT concepts.

Note: Component File name in SNOMED CT Release Format 2

A field reference to a concept that specifies the maximum length and format of the term fields for a particular type of Description.

Note: By default the term is a UTF-8 string of up to 255 characters without markup. However, description types can be specified which are longer in length and/or contain format markup (e.g. HTML). For more details of how this is specified see the file structure specification.

A field containing an integer which indicates the maximum length of the term string for a specified type of Description .

Note: By default the term is a UTF-8 string of up to 255 characters without markup. However, description types can be specified which are longer in length and/or contain format markup (e.g. HTML). For more details of how this is specified see the file structure specification.

Provide Feedback

A field in a Reference Set containing an Identifier which refers to the component to which a row in the Reference Set applies.

Note: This field is present in all types of Reference Set and, unless otherwise specified, the field data type is SCTID.

Related Links

• Reference Set Types

• Simple Reference Set

A field in the Description Release File containing a SNOMED CT identifier that indicates whether the text of the term can be modified to by switching characters from upper to lower case (or vice-versa).

Note: Field name in SNOMED CT Release Format 2

An Ordered Reference Set field containing a SNOMED CT identifier which refers to either a sub-group of components or a child concept in the alternative hierarchy represented by the Reference set. The parent of grouping component is represented by the referencedComponentId .

Note: Field name in SNOMED CT Release Format 2.

A release file that follows the pattern and contains expressions that represent general statements about the SNOMED CT ontology and axioms that define SNOMED CT concepts.

• The OWL expression reference set contains two reference sets, the OWL ontology reference set and the OWL axiom reference set.

Field in a Complex and Extended Map from SNOMED CT Reference Sets that specifies the order in which complex map records should be checked. Only the first map record meeting the run - time selection criteria will be taken as the target code within each mapGroup .

Provide Feedback

A standard method of encoding Unicode characters in a way optimized for the ASCII character set. UTF-8 is described in Unicode UTF-8 encoding.

Note: This encoding is used for release file fields of data type "String".

Related Links

• Release File Data Types

• Unicode UTF-8 encoding

An integer representing the position of an additional attribute in a Refset. The value 0 (zero) refers to the referencedComponentId. All other values refer to the position of an additional attribute relative to the referencedComponentId.

Note: Field name in a SNOMED CT Release Format 2 Reference Set Descriptor.

Field in a containing a machine-readable rule, (evaluating to either 'true' or 'false' at run-time) that indicates whether this map record should be selected within its mapGroup .

A field in the Complex Map Reference Set containing a SNOMED CT identifier which represents the correlation between the SNOMED CT concept and the target code .

Note: Field name in SNOMED CT Release Format 2

Field in a that contains the source code that is mapped to the SNOMED CT concept represented by the referencedComponentId.

A data table in which each row represents an .

Note: File or Table name in SNOMED CT toolkit

A field in the relationship file that indicates the description logic modifier that applies to that defining Relationship (e.g. "some" or "all").

Usage: Field name in SNOMED CT Release Format 2.

A field in the , which links together several rows which have an identical or similar meaning.

Note: Field name in SNOMED CT toolkit

The file structure used to distribute SNOMED CT relationships.

An Association Reference Set field containing a SNOMED CT identifier which specifies the target of the association from the source component (e.g. a concept or Description) referred to by the referencedComponentId .

Note: Field name in SNOMED CT Release Format 2.

A reference to a concept that specifies the nature of a Relationship . Values include "defining", "qualifying" etc.

Note: Field name in the SNOMED CT Release Format 2 relationships table.

A reference to a concept that specifies the data type of an additional attribute in a Refset .

Note: Field name in a SNOMED CT Release Format 2 Reference Set Descriptor.

A key used to facilitate textual searches of SNOMED CT that consists of the first three letters of a pair of words in a Description. All possible pairs of words in each Description may be paired irrespective of their relative position in the Description. Dualkeys are represented as a row in the Dualkeys Table.

Note: Field name in SNOMED CT toolkit

A datatype representing a Universally Unique Identifier encoded as a 128-bit integer.

Note: In SNOMED CT release files UUIDs are represented as a string following the standard canonical form. In this string form a UUID is represented by 32 hexadecimal digits, displayed in five groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 digits and four hyphens).

Example: ac527bed-9c70-4aad-8fc9-015828b148d9

A field containing a potential search text in one of the or a word excluded for key generation in the .

Note: Field name in SNOMED CT toolkit

Field in a containing human-readable advice, that may be employed by the software vendor to give an end-user advice on selection of the appropriate target code from the alternatives presented to him within the group.

ValueId ... to be defined.

Note: Field name in SNOMED CT Release Format 2

A datatype representing a date or time.

Note: In SNOMED CT release file specifications date and times are represented as strings using the ISO 8601 basic format.

• The date format used is YYYYMMDD.

• Where time is included the format is YYYYMMDDThhmmssZ. The time is separated from the date by the letter "T" and followed by the letter "Z" indicating that the timezone is UTC.

Examples:

July 31st 2012: 20120731 .

13:15 UTC on August 2nd 2012: 20120802T131500Z

A field in the Description and Relationship Release Files which contains a SNOMED CT identifier that represents the type of Description or Relationship represented.

• Description.typeId represents the type of Description. Description types include subtypes of 900000000000446008 |Description type (core metadata concept)| . These include 900000000000013009 |Synonym (core metadata concept)| and 900000000000003001 |Fully specified name (core metadata concept)|. There is no typeId value for " Preferred term " as the preferred term is the synonym marked as "Preferred" in the appropriate Language Reference Sets.

• Relationship.typeId represents the type of Relationship between the concept identified by sourceId and the concept identified by destinatonId. Relationship types are and subtypes of .

Note: Field name in the and in the .

A text string that represents the concept referenced by the conceptId field in the Description file.

Note:

By default the term is a UTF-8 string of up to 255 characters. However, description types can be specified which are longer in length and/or contain format markup (e.g. HTML).

Field name in the .

Field in a that identifies the SNOMED CT concept in the metadata hierarchy which represents the MapCategory for the associated map member.

Note: The categories vary for different target code systems, each set of categories is represented by a subtype of . For example in the case of ICD-10 the individual category values are subtypes of:

.