-->

Field	Value
Short Name	USP Compendial Nomenclature
Family	USP
Source Restriction Level	0
Language	ENG
License Contact	Jeffrey Shick Director Translational Informatics United States Pharmacopeia 12601 Twinbrook Parkway Rockville MD US 20852-1790 1-800-227-8772 HealthcareQuality@usp.org http://www.usp.org/health-quality-safety
Content Contact	Jeffrey Shick Director Translational Informatics United States Pharmacopeia 12601 Twinbrook Parkway Rockville MD US 20852-1790 1-800-227-8772 HealthcareQuality@usp.org http://www.usp.org/health-quality-safety

This section lists specific source data elements and provides information on their representation in RxNorm.

Summary of Changes

There are no changes to the original data format or to RxNorm source processing.

Source Provided Files:

The files will be made available on the USP website later in the year.

The following file is used for RxNorm source processing.

File Name	Description
usp-compendial-nomenclature-yyyy-mm.xlsx.xlsx	Excel File

Source-Provided Files: Details

The following is a list of fields in the USP source file used in RxNorm:

File name: usp-compendial-nomenclature-yyyy-mm.xlsx

Field Name	Description
monograph_identifier	A meaningless alphanumeric string starting with the letter ‘m’ that provides encoding for the monograph.
monograph_name	The title of the monograph.
monograph_type	The monograph type represents a quality standard for either a drug “substance” (e.g. “Warfarin Sodium”) or drug “product” (e.g. “Warfarin Sodium Tablets”).
monograph_status	Values for this field are one of the following: Official Monograph: The monograph is legally enforceable as of the date in the ‘monograph_official_date’ field Pending Official Monograph: The monograph has been finalized and will become official as of the date in the ‘monograph_official_date’ field Nomenclature Finalized: The name of the monograph has been balloted, but a monograph is not yet available
monograph_official_date	The date when the monograph became official or will become official, depending on the value of the ‘monograph_status’ field.

USP Field Representation in RxNorm Files:

Field	RxNorm Representation
monograph_identifier	RXNCONSO.CODE
monograph_name	RXNCONSO.STR
monograph_type	Term Type (TTY) TTY = IN when value is Substance TTY = CD when value is Product
monograph_status	RXNSAT.ATN = MONOGRAPH_STATUS
monograph_official_date	RXNSAT.ATN = MONOGRAPH_OFFICIAL_DATE

This section lists RxNorm data elements and traces them back to the specific USP data that populates them.

Summary of Changes

There are no changes to the original data format or to RxNorm source processing.

Source Provided Files:

The file will be made available on the USP website later in the year.

The following file is used for RxNorm source processing.

File Name	Description
usp-compendial-nomenclature-yyyy-mm.xlsx	Excel File

RxNorm Identifiers:

Identifiers are assigned as follows:

Identifier	Origin
CODE	monograph_identifier
SAUI	Not applicable
SCUI	Not applicable
SDUI	Not applicable

Atoms (RXNCONSO):

Term Type	Origin
IN	monograph_name when monograph_type = Substance
CD	monograph_name when monograph_type = Product

Relationships (RXNREL):

Clinical Drug (TTY = CD):

Atom Type 1	Atom Type 2	Relationship
Clinical Drug (CD)	Semantic Clinical Drug Form (SCDF)	product_monograph_title_of

Semantic Clinical Drug Form (TTY = SCDF):

Atom Type 1	Atom Type 2	Relationship
Semantic Clinical Drug Form (SCDF)	Clinical Drug (CD)	has_product_monograph_title

Attributes (RXNSAT):

ATN	Origin
MONOGRAPH_STATUS	monograph_status
MONOGRAPH_OFFICIAL_DATE	monograph_official_date

This section lists source terminology specific data examples and sample database queries using Structured Query Language (SQL) to obtain the data. For more information about RxNorm data and files, see the RxNorm Technical Documentation.

Names and Codes in RXNCONSO.RRF

Here are sample source terminology code, source string, RxNorm Concept Unique Identifier (RXCUI), RxNorm string, term type (TTY), and suppress values.

SOURCE_CODE	SOURCE_STR	RXCUI	RXNORM_STR	RXNORM_TTY	SUPPRESS
m39860	Ibuprofen	5640	Ibuprofen	IN	N

Here is a sample database query to retrieve the data above:

SELECT distinct rc1.code as source_code, rc1.str as source_str, rc1.rxcui, rc2.str as rxnorm_str, rc2.tty as rxnorm_tty , rc2.suppress
FROM rxnconso rc1, rxnconso rc2
WHERE rc1.code = 'm39860'
     AND rc1.sab = 'USP'
     AND rc1.rxcui = rc2.rxcui
     AND rc2.sab = 'RXNORM';
    

Names and Relationships in RXNCONSO.RRF and RXNREL.RRF

Here are sample source terminology code, source string, RXCUI, relationship name, RxNorm term type (TTY), RxNorm brand name, and suppress values.

SOURCE_CODE	SOURCE_STR	RXCUI	RELA	RXNORM_TTY	RXNORM_BN	SUPPRESS
m39860	Ibuprofen	5640	has_tradename	BN	Motrin PM	N
m39860	Ibuprofen	5640	has_tradename	BN	Samson 8	N
m39860	Ibuprofen	5640	has_tradename	BN	Vicoprofen	N
m39860	Ibuprofen	5640	has_tradename	BN	Neoprofen	N

Here is a sample database query to retrieve the data above:

SELECT distinct rc1.code as source_code, rc1.str as source_str, rc1.rxcui, rr.rela, rc2.tty as rxnorm_tty, rc2.str as rxnorm_bn, rc2.suppress
FROM rxnconso rc1, rxnrel rr, rxnconso rc2
WHERE rc1.code = 'm39860'
     AND rc1.sab = 'USP'
     AND rc1.rxcui = rr.rxcui2
     AND rr.rela = 'has_tradename'
     AND rr.rxcui1 = rc2.rxcui
     AND rc2.sab = 'RXNORM'
     AND rc2.tty = 'BN'
     ORDER BY suppress;