Unified Medical Language System® (UMLS®)
2015AB UMLS RXNORM Source Information
This page lists UMLS Metathesaurus data elements and traces them back to the specific source data that populates them.
RxNorm, a standardized nomenclature for clinical drugs, is produced by the National Library of Medicine. Data files are released monthly and available by download. Within each Metathesaurus cycle, RxNorm is updated multiple times. This document reflects the latest cumulative update. The scope of RxNorm is determined by the combined scope of its source vocabularies which include the following:
|ATC_2015_15_09_08||Anatomical Therapeutic Chemical Classification System|
|GS_2015_08_07||Gold Standard Drug Database|
|MDDB_2015_07_29||Master Drug Data Base|
|MMSL_2015_08_01||Multum MediSource Lexicon|
|MMX_2015_08_03||Micromedex RED BOOK|
|MTHCMSFRE_2014||Metathesaurus CMS Formulary Reference File|
|MTHSPL_2015_08_28||Metathesaurus FDA Structured Product Labels|
|NDFRT_2015_09_07||National Drug File|
|NDFRT_FDASPL_2015_09_07||National Drug File - FDASPL|
|NDFRT_FMTSME_2015_09_07||National Drug File - FMTSME|
|VANDF_2015_07_16||Veterans Health Administration National Drug File|
Note: Selected portions of MSH and SNOMEDCT are included in the RxNorm release files, however, they are not processed as part of RxNorm for the Metathesaurus except in assigning RXCUI and RXAUI attributes. All MSH or SNOMEDCT data in the Metathesaurus comes directly from that source's data files. This document describes how the RxNorm release files (RXN*RRF) are processed for representation in the UMLS Metathesaurus. It does not cover processing of individual source vocabularies for inclusion in RxNorm.
MTHCMSFRE is included in each Metathesaurus release as part of RxNorm, however, it was not updated in this version. MTHCMSFRE was last updated in 2014.
Summary of Changes
No changes were made to the RXNORM format itself or to Metathesaurus source processing for 2015AB. Data changes include the following:Attributes:
New dose form added: Jet Injector (part of the Injectable Product group).
The subsource MTHFDA (FDA National Drug Code Directory) and the OCD files have been deleted from the RXNORM files.
Source Provided Files:
RXNORM data files are released monthly and available by download.
|RXNCONSO.RRF||Concept and source information.|
|RXNREL.RRF||Relationship and merge information.|
|RXNSTY.RRF||Semantic type information.|
|RXNATOMARCHIVE.RRF||Archive data. Not used.|
|RXNCUICHANGES.RRF||CUI changes. Not used.|
- CODE: RXNCONSO.CODE
- SAUI: RXNCONSO.RXAUI for RXNORM atoms; RXNCONSO.SAUI for other sources. (Currently SAUI is blank for other sources).
- SCUI: RXNCONSO.RXCUI for RXNORM atoms; RXNCONSO.SCUI for other sources. (Currently SCUI is blank for other sources except NDFRT).
- SDUI: RXNCONSO.SDUI (Currently always blank).
Term types are extracted from field 13 of RXNCONSO.RRF.
For many RxNorm and subsource termtypes, the suppressibility value can be either "O" or "N". For all others, the value is "N". Suppressibility values are extracted from field 17 of RXNCONSO.RRF.
In addition, source NDC attributes may have SUPPRESS="O".
All attribute names and their values are extracted from field 9 and 11 of RXNSAT.RRF except for RXCUI and RXAUI which are created using RXNCONSO.RRF.
There are no DEFINITIONS with SAB = "RXNORM". NDFRT does contribute a small number of DEFINITIONS to MRDEF.RRF.
All relationships are extracted from field 4 (REL) and field 8 (RELA) of RXNREL.RRF
Note: In the table below, where reasonable we have
supplied term types involved in the listed
relationships. For sources that do not have "semantic
term types" (e.g. NDFRT uses "HT" and "PT," which are based on
the structure of the source, rather than types like "IN" which
is derived from the meaning of the concept), these term types
may not apply.
Inverse Relationship Label
|(no rela)||CREATED from the "PAR" relationships in
Currently, NDFRT is the only RXNORM source with a hierarchy.
|Connects the "SBD", "SCD" with its drug delivery device.|
|Connects the "PIN" with its "IN".|
|Creates relationships using the "SBD" or "SCD".|
|Connects the branded name with the generic or clinical name.|
|Connects the "PT" with its clinical drug name and connects the "SCD" & "SBD" to its drug form.|
|Connects the "BN" with its "PIN".|
|Connects the "SCDC" with its "PIN".|
|Connects the "SCD", "SBD" with its drug component.|
|Connects "GN" atoms with other "GN" atoms.|
|Connects the "SCDG" and "SBDG" with the dose form group.|
|Connects the "SCD", "SCDF", "SBD", and "SBDF" with the dose form.|
|Connects the drug name with its Metathesaurus created name.|
|Connects the "SCDF", "SCDC" to its ingredients; connects the "SBD", "SBDC", "SBDF" to its fully-specified drug brand name.|
|Connects "SCD" with "MIN"|
|Connects a concept of "DRUG_KIND" with a concept of "DISEASE_KIND"|
|Connects a concept of "MECHANISM_OF_ACTION_KIND" with a concept of "DRUG_KIND"|
|Connects a concept of "PHARMACOKINETICS_KIND" with a concept of "DRUG_KIND"|
|Connects "IN" or "PIN" with "MIN"|
|Connects "PIN" with "SCDC"|
|Creates relationships using "BN".|
|RXNORM||SY||(no rela)||Connects RXNORM atoms to other sources|
There are no mappings present in RxNorm.