NLM logo

Unified Medical Language System (UMLS)

UMLS Vocabularies

UMD (UMDNS) - Metathesaurus Representation


Skip to:
Atoms
Attributes
Definitions
Relationships
Mappings

VSAB:UMD2023

Summary of Changes:

There have been no changes to the UMDNS release format or to UMLS source processing.

Source Provided Files:

The UMLS uses an xml version of UMDNS. Please contact ECRI for source acquisition information.

UMDNS includes concepts and associated descriptions, as well as relationships (associations) between concepts, and a hierarchy. Concepts and terms may have attributes (properties).

Note: Retired UMD concepts are not included in the UMLS Metathesaurus."

Identifiers:

UMDNS includes concepts and associated descriptions

Identifiers are assigned as follows:

  • CODE:
    For termtypes "PT", "SY," "ET," "HT": populated by the value of the concept "code" tag
    For termtype "RT": populated from an external list of values (RTs may be related to more than one PT)
  • SAUI:
    Not Applicable
  • SCUI:
    Not Applicable
  • SDUI:
    Same as CODE

Atoms (MRCONSO):

Term Type Origin
PT CODE, SDUI = value of concept "code" tag
STR = value of concept "name" tag

"PT" atoms are created where the concept "DEVICE_TYPE" is one of:
  • CATEGORY EXPANDED BELOW entry with SEE ALSO references
  • CATEGORY EXPANDED BELOW entry
  • Device has SEE ALSO references
  • Main Device Term
  • NIR entry
HT CODE,SDUI = value of concept "code" tag
STR = value of concept "name" tag

"HT" atoms are created where the concept "DEVICE_TYPE" is:
  • Hierarchical Term
RT CODE, SDUI = populated from an external list of values (RTs may be related to more than one PT)
STR = value of term "name" tag

RT atoms are created for Entry Terms where the "Term Device Type" is:
  • Device is a USE MORE SPECIFIC TERM entry.
SY CODE, SDUI = value of concept "code"
STR = value of the "Synonym" association "to_name"

SYs are created for "Synonym" associations./td>
ET CODE, SDUI = value of concept "code" tag
STR = value of "Entry Term" "to_name"

ET atoms are created for Entry Terms where the "Term Device Type" is:
  • Device is a SEE reference.

Attributes (MRSAT):

Attribute Name Origin of ATV
DEVTYPE The value of the "DEVICE_TYPE" (STYPE = SDUI) or "Term Device Type" property (STYPE = AUI). One of the following:
  • CATEGORY EXPANDED BELOW entry with SEE ALSO references
  • CATEGORY EXPANDED BELOW entry
  • Device has SEE ALSO references
  • Device is a SEE reference
  • Device is a USE MORE SPECIFIC TERM entry
  • Hierarchical Term
  • Main Device Term
  • NIR entry
TERM_CODE The value of the "Term Code in Source" property, if present.

Definitions (MRDEF):

ORIGIN
The value of the "DEFINITION" property, where value of the "Definition _Status" = "Releasable." Definitions with other status values are excluded.

Relationships (MRREL):

Relationship Relationship Label/Inverse Relationship Label ORIGIN
CHD
PAR		 isa/inverse_isa Hierarchy extracted from "defining_concept" values in original xml data
RB/RN
RO
    Relationships are assigned based on termtypes:
  • PT - PT: RO
  • PT - ET: RO
  • PT - RT: RN
(The Preferred term is narrower than Related term)

Mappings (MRMAP):

No mapping data is included for UMDNS