RXCUIs in SAB=RXNORM are never reused and in exceptional cases, some are remapped, split, or archived. In contrast, RXCUIs for normalized drug names in SAB=RXNORM and the meanings of those concepts generally persist from one RxNorm release to the next. For example, RXCUIs for drug names considered out-of-scope are transient and history information is limited. Out-of-scope content does not receive RxNorm normalized names and are excluded from SAB=RXNORM along with their RXCUIs.Īlso, the RXCUIs that identify out-of-scope content are treated differently than the RXCUIs for in-scope content.
#Another word for content library full#
RXCUIs) become the NLM created RXNORM data source (SAB=RXNORM) within the full RxNorm data set. As mentioned above in step 2, drug names considered in-scope receive RxNorm normalized names. However, all RXCUIs are not created equal.
#Another word for content library code#
An RXCUI is a machine-readable code or identifier that points to the common meaning shared by the various source names grouped and assigned to a particular concept. RXCUIĮvery name and code provided to NLM by a source vocabulary receives an RXCUI. Assign an RxNorm concept unique identifier (RXCUI) to each concept and an RxNorm atom unique identifier (RXAUI) to each atom. The branded version of this drug uses the same format but includes the brand name in brackets at the end (e.g., 'Naproxen 250 MG Oral Tablet ').ģ. In our example, the RxNorm normalized name is 'Naproxen 250 MG Oral Tablet'. The normalized name consists of the ingredient, strength, and dose form (in that order) for fully-specified generic drugs. The Naproxen concept above is in-scope for RxNorm, so it is assigned an RxNorm normalized name. The most common types of names that are not assigned RxNorm normalized names are medical devices, foods, and enzymes. The other 40% of source vocabulary drug names do not receive RxNorm normalized names because they are either out-of-scope or their names are too ambiguous. For more information about SAB=RXNORM, click on 'What does the RxNorm model look like?' below. SAB=RXNORM is both a source and a subset of the full RxNorm data set. RxNorm normalized names and codes are available in SAB=RXNORM which is one of the source vocabularies within the full RxNorm data set. Create an RxNorm normalized name for each concept (if the concept is in-scope and unambiguous).Ībout 60% of the drug names from RxNorm source vocabularies receive RxNorm normalized names. RxNorm groups these as synonyms into one concept.Ģ. Although the drug names in this Naproxen example appear different, they all have the same meaning at a certain level of abstraction. Sources format their drug names in many different ways. Naproxen 250 MILLIGRAM In 1 TABLET ORAL TABLET.Group source data into collections of synonyms (called concepts).
There are many steps involved in RxNorm production, but these five basic steps give a general idea of how RxNorm is produced:ġ. NLM receives drug names from many data sources, analyzes and processes the data, and outputs the data into RxNorm files in a standard format. Medical devices include but are not limited to bandages and crutches. Non-therapeutic radiopharmaceuticals, bulk powders, contrast media, food, dietary supplements, and medical devices are all out-of-scope for RxNorm.
The National Library of Medicine (NLM) produces RxNorm. RxNorm is two things: a normalized naming system for generic and branded drugs and a tool for supporting semantic interoperation between drug terminologies and pharmacy knowledge base systems.