What is rxcui

RxMix offers users the ability to test and run programs instantaneously or in batch mode, with resulting files automatically emailed to the user. The schematic below shows an example data manager query of the sort that a user might run using the RxMix tool. Next, the user selects the source of drug-class relationships to use 2. Depending on the drug-class source selected, the user may then need to choose the TYPE of drug-class relationship for which to query 3. As the CMS information is not a true source vocabulary, but simply ad hoc information, it is not released as a source vocabulary.

Rather, the normalized names are created de novo by the editors based on the information provided by CMS. We have observed a steady and fast growth in the use of RxNorm over the past few years, manifested by the increasing number of RxNorm downloads and the vibrant user community activities. Monthly RxNorm downloads averaged about in There are currently 89 subscribers to the RxNorm listserv begun in January In addition, we frequently receive inquires, comments, and suggestions from RxNorm users.

Typical uses of RxNorm include using RxNorm standard names and codes to capture drug product information in EHR, cross mapping among disparate drug vocabularies, and facilitating medication-related clinical decision support. This medication was started on February 4, 4. This medication was prescribed February 4, by Dr John Jose 8. Number of refills is 5 9 and quantity dispensed is 90 Note that the branded medication and the corresponding generic drug are represented by RxNorm names and codes.

An example medication section in the Continuity of Care Document body with prescription history. Vendors have developed products that support their customers for drug terminology interoperability as well. Some products exploit mappings available in RxNorm as well as those not included in RxNorm.

Standard drug names and codes, and cross-mapping among various drug terminologies can be considered as a necessary first step toward medication-related decision support. That is, correct identification of medications is essential. Based on this, more advanced decision support can be achieved via relationships and attributes in RxNorm. For example, relationships linking the clinical drug and branded drug can be used to discover the unintended duplicate therapy of a branded drug and its generic equivalent.

NDCs associated with a drug can be used for dispensing and for inventory checking. With the drug classification information, medications can be organized into categories and thus what may be duplicate drug therapies within the same class can be identified.

The organization and presentation of patient medication data into drug classes and diseases can facilitate decision support as well as cognitive support. Users should be aware that while medication related decision support can render many benefits, it can also have significant limitations. For example, drug—drug interaction checking or drug—allergy checking can improve patient safety and lower medication-related cost when combined with computerized provider order entry CPOE , but it may result in excessive alerting and disrupt clinical workflow.

It serves as a supplemental tool to help users browse through RxNorm in a visually friendly and interactive manner. Today, RxNav serves as both a browser and an application programming interface for RxNorm. It reorganizes RxNorm names and codes into a two dimensional representation tailored for prescription writing; it eliminates certain drug names that are less likely to be needed in a prescribing environment as well. Rather than linking drug descriptions at different levels via named relationships, such association is achieved by organizing a SCD or SBD and its related information into rows of records within a single table of named columns.

MyMedicationList MML is an application that helps patients create, update, and save their medication lists. Certain functionalities implemented in MML and MyRxPad can be desirable for other systems, including CPOE with standard RxNorm names and codes, medication or prescription information in the standard CCD format, and some medication-related decision support capabilities.

A patient uses MML to maintain and update his medication list and shares his medication list brought in on a USB drive or emailed beforehand with prescribers. Prescribers use MyRxPad to open the patient medication list, write new or refill prescriptions, and make necessary changes on the patient medication record. Accordingly, the patient obtains an updated medication list that might include refilled medications and other medication adjustments. As the patient carries along the medication list to various prescribers, the evolving and updated list serves as the integrated medication data across disparate providers.

As aggregating medication histories from multiple sources may often be difficult, 20—22 this patient-centric, participatory approach can address this challenge.

MML and MyRxPad provide an alternative approach to medication reconciliation across points of care as illustrated in figure 3. MyMedicationList and MyRxPad: an alternative approach for medication reconciliation across points of care.

Source content is integrated into RxNorm through an inversion, insertion, editing, and production life cycle. Second, converted source vocabularies are inserted into RxNorm using various matching algorithms. Third, human editors review all the content that was inserted, creating normalized names where needed. Finally, after the quality assurance process, RxNorm content is released. During this RxNorm data life cycle, semantically equivalent names and codes are grouped, RxNorm unique identifiers, normalized names, relationships, and attributes are generated and assigned, and source content is preserved.

Quality assurance is a major concern in the production of the RxNorm releases. While minimizing requirements for keyboard entry during RxNorm data production keeps typographical errors to a minimum, review of consistency of relationships and other internal checks help assure the quality of the release.

One step in the assurance cycle is reviewing where two sources with the same NDC code are linked to different RxNorm names. Reviewing and reconciling these errors provides an important check on consistent creation of RxNorm names and the RxNorm model.

RxNorm is released in full on the working day coinciding with or following the first Monday of each month. Each release follows the rich release format of the UMLS Metathesaurus, and, where references to concepts in the Metathesaurus occur, they refer to the current extant version of the Metathesaurus.

Twice a year the releases of the Metathesaurus and RxNorm are scheduled to occur simultaneously, in which case the references in RxNorm are to that release of the Metathesaurus.

Weekly releases of RxNorm were begun to keep up with new medications and new formulations when they appear on the market. The weekly release consists of only new material, linked by codes to older material if necessary.

Changes in concept structure, such as moving a source atom from one RxNorm concept to another, take place only in the monthly releases, which are full releases. The downloadable zip file contains several RxNorm content files which are bar-delimited text files, as well as load scripts that can be used to import the content files into MySQL or Oracle databases. At the same web site, users can find related information, including the RxNorm overview and technical documentation.

To obtain the RxNorm file, users need to complete a UMLS license agreement, which permits uses of public domain content in perpetuity. Certain content of RxNorm is freely available, including RxNorm names and codes. Other content contains copyrighted proprietary information. For use of that proprietary content, users need to contact the source vocabulary contributor for specific terms of use or licenses.

To be informed about the upcoming RxNorm changes, users can subscribe to the RxNorm announcement at rxnorm-announces-l list. Inquires, comments, or suggestions can be directed to rxnorminfo nlm. Over the past few years, RxNorm has evolved to be an emerging standard for clinical information exchange.

RxNorm names and codes have gained wide recognition. RxNorm is a terminology built on and derived from other terminologies. RxNorm reflects and preserves the meanings, drug names, attributes, and relationships from its sources.

Click on a Source Abbreviation SAB link in the table below for details about a source, including how a source is represented in RxNorm. RxNorm receives drug names from these source terminologies:. If a drug name isn't included in the RxNorm data files, then RxNorm didn't receive this information from any of its data sources. In addition to the data sources listed above, the derived RxNorm normalized drug names become a terminology.

RxNorm is composed of the normalized names based upon the information received from the sources listed above. Strengths use the "milli" metric system equivalents e. Liquids are expressed per milliliter. When a powder can be reconstituted to a range of liquid concentrations, the highest concentration in the range is used for the normalized form. For instance, drugs containing multiple active ingredients will have all active ingredients listed.

Another example is drugs using specific dose forms that require a quantity factor even though they are not RxNorm drug packs, such as the volume of drug in a prefilled syringe, number of actuations in a metered dose inhaler, or duration of action of an extended release capsule. See Appendix 1 for a full list of relationships. Fully-specified drugs have other attributes, including NDCs. Here are some attribute examples:. The full monthly RxNorm release includes 9 data files, which are simple text files with pipe ' ' delimiters between each field value.

RxNorm data files are meant to be loaded as separate tables into a database management system. However, the files are not fully normalized as would be the case in a formal database; there are duplications across and within files by design. Essentially, the row is the atom.

These six rows of data represent synonymous drug names from the same concept. The RXAUIs for each of these atoms are different as shown in the column of numbers that starts with ''.

In the sample data, you can see one direction of relationships above the dividing line and relationships going in the opposite direction below the line. Every concept receives at least one semantic type.

A concept is retired when it:. This file is not cumulative. RXNSAB contains contact information for source providers, available term types and attributes, and other information related to each RxNorm source. RRF in the Metathesaurus. The APCD portal offers a convenient set of tools for users to compare and download All-Payer Claims reporting specifications from single state and multiple states, as well as the APCD council core specification. The Children's EHR Format the Format is a set of child-specific requirements and other requirements of special importance for children that an EHR should meet to perform optimally for the particular health care needs of children.

RXCUI ingredient. Drugs whose names map to the same RXCUI are taken to be the same drug, identical as to ingredients, strengths, and dose forms. Conversely, drugs that differ in any of these particulars are conceptually distinct and will have different RXCUIs.