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 .
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 116680003 |Is a (attribute)| and subtypes of 410662002 |Concept model attribute (attribute)| .
Note: Field name in the and 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.
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 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 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