Skip Navigation Bar

Unified Medical Language System® (UMLS®)

ICD-10-CM Source Information

This page lists UMLS Metathesaurus data elements and traces them back to the specific source data that populates them.

Skip to: Atoms, Attributes, Definitions, Relationships, Mappings

VSAB: ICD10CM_2017_2016_10_19

Summary of Changes

Note: ICD10CM_2017_2016_10_19 is a minor update to correct an omission in processing ICD10CM_2017. A small number of atoms, relationships and the "NOTE" attribute were missing in 2017AA. The changes listed here are in comparison to ICD10CM_2016.
  • The reimbursement mappings have been discontinued
  • Previously, the UMLS received and processed files submitted in TREF (Terminology Representation and Exchange Format). Starting with 2017AA, a publicly available xml file was processed for tabular data.
  • Deprecated ATN. The following data is not included in the tabular xml data:
    • ALT_SORT_CODE

Source Provided Files:

The following files are downloaded and processed from http://www.cdc.gov/nchs/icd/icd10cm.htm:

Documentation:
  • icd10OrderFiles-508.pdf
  • icd10cm_tabular_2017-508.pdf
  • GemsTechDoc_2017.pdf

Data:
  • 2017_I10gem.txt
  • 2017_I9gem.txt
  • icd10cm_order_2017.txt
  • icd10cm_tabular_2017.xml
The tabluar xml file aligns with the order file, and redundant data is not processed.

Identifiers:

Identifiers are assigned as follows:
  • CODE:
    • Diagnoses, chapters: value of "<name>" tag
    • Diagnoses, 7 character codes: value of "<name>" tag" concatenated with "<SevenChrDef> <extension>" tag
    • Sections: value of "id" attribute of "<section>" tag
  • SAUI: Not Applicable
  • SCUI: Not Applicable
  • SDUI: same as CODE

Atoms (MRCONSO):

(return to top)
Term Type Description Origin
AB Abbreviation (Short description) CODE = icd10cm_order_<YYYY>.txt (character positions 7-13)
STR = icd10cm_order_<YYYY>.txt (character positions 17-76)
SDUI = same as CODE
SUPPRESS = "Y"
ET Entry Term CODE: value of "<name>" tag in icd10cm_tabular_<YYYY>.xml
STR: value of "<includes>" or "<inclusionTerm>" tag in icd10cm_tabular_<YYYY>.xml
SDUI: same as CODE
SUPPRESS = "Y"
HT Hierarchical Term CODE:
  • For diagnoses or chapters: value of "<name>" tag
  • For sections: value of "id" attribute of "<section>" tag
STR: value of "<desc>" tag in icd10cm_tabular_<YYYY>.xml
SDUI: same as CODE
SUPPRESS = "N"

Note: Chapters, Sections, and all "non-leaf" nodes are assigned TTY = "HT." In icd10cm_order_<YYYY>.txt, a value of "0" in character position 15 indicates that the code is not valid for submission on a UB04.
PT Preferred Term CODE: Value of "<name>" tag
For 7th character extensions: the "<sevenChrDef extension>" char is appended to the subcategory name value
STR: value of "<desc>" tag in icd10cm_tabular_<YYYY>.xml
For 7th character extensions: The "<sevenChrDef>" value is appended to the desc value
SDUI: same as CODE
SUPPRESS = "N"

Note: All "leaf" nodes are assigned TTY = "PT." In icd10cm_order_<YYYY>.txt, a value of "1" in character position 15 indicates that the code is valid for submission on a UB04.
XM Cross Mapping Set This data is added during Metathesaurus source processing.

Attributes (MRSAT):

(return to top)

Most attributes are extracted from "<note>" tags in icd10cm_tabular_<YYYY>.xml.

Mapping attributes are added during Metathesaurus source processing.

ATN Note Type Description
CODE_ALSO codeAlso Instructs that 2 codes may be required to fully describe a condition but the sequencing of the two codes is discretionary, depending on the severity of the conditions and the reason for the encounter.
CODE_FIRST codeFirst Certain conditions have both an underlying etiology and multiple body system manifestations due to the underlying etiology. ICD-10-CM has a coding convention that requires the underlying condition be sequenced first followed by the manifestation. Wherever such a combination exists there is a "code first" note at the manifestation code. These instructional notes indicate the proper sequencing order of the codes, etiology followed by manifestation. In most cases the manifestation codes will have in the code title, "in diseases classified elsewhere." Codes with this title are a component of the etiology/manifestation convention. The code title indicates that it is a manifestation code.
EXCLUDES1 excludes1 A pure excludes. It means "NOT CODED HERE!" Indicates that the code excluded should never be used at the same time as the code above the Excludes1 note. Used for when two conditions cannot occur together, such as a congenital form versus an acquired form of the same condition.
EXCLUDES2 excludes2 Represents "Not included here". Indicates that the condition excluded is not part of the condition it is excluded from but a patient may have both conditions at the same time. When an Excludes2 note appears under a code it is acceptable to use both the code and the excluded code together.
ORDER_NO N/A Order number (icd10cm_order_<YYYY>.txt characters 1-5)
SOS N/A This data is added during Metathesaurus source processing
USE_ADDITIONAL useAdditionalCode Certain conditions have both an underlying etiology and multiple body system manifestations due to the underlying etiology. ICD-10-CM has a coding convention that requires the underlying condition be sequenced first followed by the manifestation. Wherever such a combination exists there is a "use additional code" note at the etiology code. These instructional notes indicate the proper sequencing order of the codes, etiology followed by manifestation. In most cases the manifestation codes will have in the code title, "in diseases classified elsewhere." Codes with this title are a component of the etiology/ manifestation convention. The code title indicates that it is a manifestation code. "In diseases classified elsewhere" codes are never permitted to be used as first listed or principle diagnosis codes. They must be used in conjunction with an underlying condition code and they must be listed following the underlying condition.
FROMRSAB N/A This data is added during Metathesaurus source processing
FROMVSAB N/A This data is added during Metathesaurus source processing
MAPSETRSAB N/A This data is added during Metathesaurus source processing
MAPSETVERSION N/A This data is added during Metathesaurus source processing
MAPSETVSAB N/A This data is added during Metathesaurus source processing
MAPSETXRTARGETID N/A This data is added during Metathesaurus source processing
MTH_MAPFROMCOMPLEXITY N/A This data is added during Metathesaurus source processing
MTH_MAPFROMEXHAUSTIVE N/A This data is added during Metathesaurus source processing
MTH_MAPSETCOMPLEXITY N/A This data is added during Metathesaurus source processing
MTH_MAPTOCOMPLEXITY N/A This data is added during Metathesaurus source processing
MTH_MAPTOEXHAUSTIVE N/A This data is added during Metathesaurus source processing
TORSAB N/A This data is added during Metathesaurus source processing
TOVSAB N/A This data is added during Metathesaurus source processing



Definitions (MRDEF):

(return to top)

There are no DEFINITIONs for ICD10CM.


Relationships (MRREL):

(return to top)
REL RELA
Inverse RELA
Origin
CHD
PAR
(no rela) Hierarchy created from icd10cm_tabular_<YYYY>.xml
RQ (no rela) Connect Entry Terms (TTY = "ET") to their preferred form (TTY = "PT" or TTY = "HT")
SY expanded_form_of
has_expanded_form
Connect short forms (TTY = "AB") to their preferred form (TTY = PT")

Mappings (MRMAP):

(return to top)

Two mapsets ("XM" atoms, along with associated attributes and mappings), are included for ICD-10-CM. These are extracted from the General Equivalence Mappings (GEMs) and reimbursement mappings.

Note: The original mapping files do not include decimal points for the ICD-9-CM and ICD-10-CM codes. For clarity, decimals are added appropriately to the MRMAP.RRF representation, e.g. "A021" is converted to "A02.1" for use as a FROMID or TOID.


Field Origin (GEMs) Origin(Reiumbursement mappings)
MAPSUBSETID Compound value of "Scenario:Choice"
Note: Anything with the same FROMEXPR and MAPSUBSETID values should be "OR'd" together.
Not populated
REL RO where approximate flag = "1"
SY where approxmiate flag = "0"
XR where target value = "NoDx"
RQ
RELA approximately_mapped_to where approximate flag = "1"
mapped_to where approxmiate flag = "0"
null (empty) where target value = "NoDX"
mapped_to
TOTYPE SDUI SDUI