Unified Medical Language System® (UMLS®)
2012AA UMD Source Information
Atoms, Attributes, Definitions, Relationships, Mappings
VSAB:UMD2012
Summary of Changes:
No changes have been made to the original data files or to
representation of UMDNS.
Source Provided Files:
The UMLS uses an xml version of UMDNS which is created with the TDE tool from Apelon, Inc. The file used for 2012AA is "2011NLM_v5.xml" (the defined view). (http://apelon.com/dtd/tde/ontylog.dtd)
Identifiers:
UMDNS includes both “concepts,” i.e. collections of synonymous atoms, and “descriptors,” i.e. collections of concepts that are considered to be closely related (but not necessarily synonymous). Therefore, atoms with TTY = "SY" are assigned the same Source-asserted Concept Identifer (SCUI), and Source-asserted Descriptor Identifier (SDUI) as their PT. However, atoms with TTY = "ET" are considered to be in a different concept from their "PT" (different SCUI) but members of the same descriptor (same SDUI). Identifiers are assigned as follows:
- CODE:
For termtypes "PT", "ET", "RT", "HT": populated by the "CODE_IN_SOURCE" property.
For termtype "SY": populated by the "CODE_IN_SOURCE" value of the "PT" - SAUI:
Not Applicable - SCUI:
Same as "CODE" - SDUI:
For termtypes "PT", "SY", "ET": CODE of "PT"
For termtype "HT": CODE of "HT"
For termtype "RT": CODE of "RT" (An "RT" may have multiple "PT"s, so we can't use code of "PT")
Atoms (MRCONSO):
| Term Type | Origin |
|---|---|
| PT | CODE = value of <CODE_IN_SOURCE> property STR = value of <conceptDef><name> SCUI = value of <CODE_IN_SOURCE> property SDUI = value of <CODE_IN_SOURCE> property Termtypes are assigned based on the value of the "DEVICE_TYPE" property. "PT"s are created where the "DEVICE_TYPE" is one of:
|
| HT | CODE = value of <CODE_IN_SOURCE> property STR = value of <conceptDef><name> SCUI = value of <CODE_IN_SOURCE> property SDUI = value of <CODE_IN_SOURCE> property Termtypes are assigned based on the value of the "DEVICE_TYPE" property. "HT"s are created where the "DEVICE_TYPE" is:
|
| RT | CODE = value of <CODE_IN_SOURCE> property STR = value of <conceptDef><name> SCUI = value of <CODE_IN_SOURCE> property SDUI = value of <CODE_IN_SOURCE> property Termtypes are assigned based on the value of the "DEVICE_TYPE" property. "RT"s are created where the "DEVICE_TYPE" is:
|
| SY | CODE = value of <CODE_IN_SOURCE> property of
associated
"PT" STR = value of the "SYNONYM" property SCUI = value of <CODE_IN_SOURCE> property of associated "PT" SDUI = value of <CODE_IN_SOURCE> property of associated "PT" SYs are created when a "SYNONYM" property exists |
| ET | CODE = value of <CODE_IN_SOURCE> property STR = value of <conceptDef><name> SCUI = value of <CODE_IN_SOURCE> property SDUI = value of <CODE_IN_SOURCE> property of associated "PT" Termtypes are assigned based on the value of the "DEVICE_TYPE" property. ETs are created where the "DEVICE_TYPE" is:
|
Attributes (MRSAT):
| Attribute Name | Origin of ATV |
|---|---|
| DEVTYPE | The value of the "DEVICE_TYPE" property. One of the
following:
For consistency, in the Metathesaurus, all SY atoms are defaulted to "Device is a SEE reference." DEVTYPE is attached to AUI for SY atoms; for all other atoms, it is attached to CODE. |
| SYCODE | The value of the "Synonym_Code" qualifier, if present. Attached to AUI. |
Definitions (MRDEF):
| ORIGIN |
|---|
| The value of the "DEFINITION " property, where value of the "Definition _Status" qualifier = "Releasable." Definitions with other qualifier values are excluded. |
Relationships (MRREL):
| Relationship | Relationship Label/Inverse Relationship Label | ORIGIN |
|---|---|---|
| CHD PAR SIB |
isa/inverse_isa | Hierarchy extracted from "<definingConcept><concept>" values in original xml data |
| RB/RN RO |
Relationships are assigned based on termtypes:
It has been acknowledged that this default may result in a small number of semantically incorrect relationships but this is considered the best default |
Mappings (MRMAP):
No mapping data is included for UMDNS
