![]() |
|
Unified Medical Language System | |
RxNorm Release Documentation File for 07/01/2008 Full Release |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
RxNorm, a standardized nomenclature for clinical drugs, is produced by the National Library of Medicine. In this context, a clinical drug is a pharmaceutical product given to (or taken by) a patient with a therapeutic or diagnostic intent. In RxNorm, the name of a clinical drug combines its ingredients, strengths, and form. In RxNorm, the form is the physical form in which the drug is administered or is specified to be administered in a prescription or order. The RxNorm clinical drug name does not refer to the size of the package, the form in which the product was manufactured, or its form when it arrived at the dispensary. RxNorm's standard names for clinical drugs are connected to the varying names of drugs present in many different controlled vocabularies within the Unified Medical Language System (UMLS) Metathesaurus, including those in commercially available drug information sources. These connections are intended to facilitate interoperability among the computerized systems that record or process data dealing with clinical drugs. Like other vocabularies in the Metathesaurus, RxNorm is organized by concept or meaning. All concepts in RxNorm are assigned at least one semantic type from the Semantic Network (Section 3.0 of the UMLS documentation). This provides consistent categorization of all concepts in RxNorm at the relatively general level represented in the Semantic Network. RxNorm is both a source and a subset of the Metathesaurus. The scope of RxNorm is determined by the combined scope of its source vocabularies. Many relationships (primarily synonymous), concept attributes, and some concept names are added by the NLM during the creation of RxNorm forms, but essentially all the concepts themselves come from one or more of the source vocabularies. 3.0 Preservation of Content and Meaning from Source Vocabularies RxNorm reflects and preserves the meanings, concept names, and relationships from its source vocabularies in the same way that the Metathesaurus preserves content and meaning. Please refer to the UMLS Metathesaurus documentation for further information on this topic. RxNorm contains source vocabularies produced by different copyright holders. The majority of the content of RxNorm is available for use under the basic and open terms described in sections 1-11 and 13-16 of the Metathesaurus license. Please refer to the UMLS Metathesaurus documentation for further information on this topic. 4.0 Ambiguity in RxNorm Source Data The disparate variety of source providers to the RxNorm dataset, along with their individual schedules for updating and modifying their datasets, has created the possibility of atom strings coming from source providers that look similar, but have different meanings. It is common for these ambiguous strings to be placed in separate concepts within RxNorm in order to maintain the separate level of meaning for each string. In some cases, the ambiguity is a result of the inability to resolve the correct meaning for a given string from a particular source. For example, attributes of an atom string may conflict with the string of the atom. One may refer to an "Oral Tablet", while another may refer to "Extended Release Tablet". This could result in the string in question being placed in a concept separate from similar looking string(s) whose meaning is clearly represented by their source(s). Another case of ambiguity could involve different quantities of a particular drug. In the case of an inhaler, a source may provide a string for a particular brand of inhaler, however, the number of actuations in the container is not specified by the source. Another source may provide this information for a similar drug string, and research at NLM will confirm the different sizes of containers for the particular brand, thus making the first string ambiguous in meaning. As drug source providers have refined and updated their datasets over time, new information has been provided about existing drug strings, making the old information obsolete and ambiguous. RxNorm maintains this old data as RxNorm (SAB=RXNORM) atoms of term type 'OCD'. NLM strives to review these ambiguous strings on a regular basis in both the RxNorm and UMLS data sets. In the UMLS, relationships are created between ambiguous concepts and a unique name is created for each string with multiple meanings. RxNorm normal forms (e.g. SCD, SBD, GPCK, BPCK) only are created when the meaning of the source string is clear at the level of abstraction present. In this sense, SAB=RXNORM atoms are never ambiguous. The RxNorm model of a prescribable drug, which specifies the ingredient, strength, and dose form, adequately represents most prescriptions for medicines. However; there are some important medicines not sufficiently or appropriately characterized by those three components alone. These have been identified as medicines that are dispensed in "Packs". For example, Z-Pak, Medrol Dose Pack, and various oral contraceptive packages. A Pack would contain one or more SCD's or SBD's along with a quantification to represent the number of SCD's or SBD's of a certain type that are contained in the Pack. Packs may be branded or generic packs. A Branded Pack would contain SBD's and/or SCD's and be provided with a Market Name, while a Generic Pack would contain one or more SCD's only. The new Term Types "BPCK" and "GPCK" have been created to represent these strings in the RxNorm vocabulary. The representation of these strings in RxNorm consists of the following syntax: Generic Pack (GPCK): "{'quantity' (SCD1/SBD1) / 'quantity' (SCD2/SBD2) / 'quantity' (SCDn/SBDn) } Pack"Branded Pack (BPCK): "{'quantity' (SCD1/SBD1) / 'quantity' (SCD2/SBD2) / 'quantity' (SCDn/SBDn) } Pack [Market Name]" Examples of BPCK's: {12 (Ethinyl Estradiol 0.035 MG / Norethindrone 0.5 MG Oral Tablet) / 9 (Ethinyl Estradiol 0.035 MG / Norethindrone 1 MG Oral Tablet) / 7 (Inert Ingredients 1 MG Oral Tablet) } Pack [Leena 28 Day]{10 (Chlorpheniramine 8 MG / Methscopolamine 2.5 MG / Phenylephrine 10 MG Oral Tablet) / 10 (Methscopolamine 2.5 MG / Phenylephrine 40 MG Oral Tablet) } Pack [AlleRx PE Dose Pack] Examples of GPCK's: {28 (Norethindrone 0.35 MG Oral Tablet) } Pack{11 (varenicline 0.5 MG Oral Tablet) / 42 (varenicline 1 MG Oral Tablet) } Pack Each BPCK atom has a corresponding GPCK atom. These atom pairs will be represented with relationships in the RXNREL.RRF file in the following way: BPCK -- tradename of -- GPCKGPCK -- has_tradename -- BPCK In addition, relationships are created between the Drug Delivery Device term type atoms (BPCK, GPCK), to their component SCD(s) and/or SBD(s). These relationships are represented in the RXNREL.RRF file in the following way: BPCK -- contains -- SCDBPCK -- contains -- SBD GPCK -- contains -- SCD SCD -- contained_in -- BPCK SCD -- contained_in -- GPCK SBD -- contained_in -- BPCK 6.0 Normalizing NDC codes in RxNorm RxNorm currently distributes NDC data from four different sources. Each of these sources provides NDC codes in a different format. Examples of these include a 14 digit "6-4-2" format, 10 digit "5-3-2", "4-4-2" or "5-4-1" formats, 12 digits with no dashes format, and the 11 digit, no dashes HIPAA format. The NDCs asserted for the atoms of each of these sources are found in RXNSAT.RRF as values of the attribute ATN='NDC'. Since these NDCs are in separate formats, it is difficult to determine when the NDC assignments are inconsistent across sources. A single RxNorm clinical drug concept may properly have several NDCs (each corresponding to a different package size), but a single NDC would be expected to be assigned to only one RxNorm clinical drug concept (RXCUI). The NLM is associating normalized NDC codes to RxNorm clinical drugs of the term types 'SCD', 'SBD', 'BPCK' and 'GPCK' (SAB=RXNORM atoms). The normalized NDCs will follow the 11 digit, no dashes HIPAA format. These normalized NDCs will be associated with an RXCUI where the NLM can determine the "correct" NDCs for that RXCUI. In general, "correctness" of an NDC assignment means there is consistency among the various sources in the association of an RXCUI with a particular NDC. These normalized NLM-asserted NDC associations will be found in RXNSAT.RRF, in additon to all the source-asserted NDC associations that already appear there. The normalized NLM-asserted NDC associations are assigned SAB='RXNORM'. 6.1 Examples of NDC code normalizations
6.2 Examples of RXNSAT.RRF entries for an RXCUI (ATN="NDC") 213684|||2368285|AUI|759|||NDC|MMSL|61646050116|N||213684|||2481750|AUI|100385|||NDC|MTHFDA|061646-*501-16|N|| 213684|||2481751|AUI|108916|||NDC|MTHFDA|058716-*327-16|N|| 213684|||1171481|AUI|213684|||NDC|RXNORM|61646050116|N|| *New data beginning June 2007 213684|||1171481|AUI|213684|||NDC|RXNORM|58716032716|N|| *New data beginning June 2007 7.0 Propagating NDC codes in RxNorm As noted above, a single NDC code should properly be associated with only a single RxCUI, though a single RxCUI can have multiple NDCs. RxNorm takes a slight liberty with this principle, and propagates the NDCs for branded drugs to the corresponding unbranded drugs. In other words, RxNorm associates the NDC for a branded drug with both the branded and unbranded counterparts of an SBD. This is done to make it easy for users to find all the NDCs associated with a particular drug, both the branded and unbranded versions of that drug. This means that the NDC for an SBD would be associated with multiple RxCUIs, i.e. the RxCUI for the SBD as well as the RxCUI for the corresponding SCD. For Drug Delivery Devices, an NDC associated with a multi-component BPCK will propagate and be associated with the corresponding GPCK as well. For single component BPCKs and GPCKs, their NDC codes will propagate to the associated SBDs and SCDs contained within those drug delivery devices atoms. NLM is now associating U.S. Food and Drug Administration (FDA) generated unique ingredient identifiers (UNIIs) to RxNorm (SAB=RXNORM) atoms of term type IN. The association is made by an exact string match to the RxNorm ingredient string (case insensitive) from the official FDA substance list. These UNII codes are found in RXNSAT.RRF as values of the attribute ATN='UNII_CODE'. The UNII is a non-proprietary, free, unique, unambiguous, non semantic, alphanumeric identifier based on a substance’s molecular structure and/or descriptive information. For more information on the FDA UNII codes, please refer to this FDA web page. 9.0 Duplicating Source Asserted Atoms Atoms coming from our sources can contain multiple NDC codes for the same atom. In many cases the NDC codes associated with the atoms are describing a similar product. However, there are cases where NDC codes received from sources for the same atom carry different meanings. For example, a source atom may contain "CAP/TAB" as the dose form portion of the atom and have the NDC codes for both the capsule form of the drug and the tablet form of the drug associated to this one atom. RxNorm is creating duplicates of such source asserted atoms in order to properly associate NDC codes with RxNorm forms. When an atom is duplicated, the original source atom is considered to be a 'Base' atom and it is not assigned an RxNorm form. The duplicate atom's string is created by appending '_#N' to the Base atom string where 'N' is a number from 1 to N number of duplicates for this base atom. The duplicate atoms will carry the same source asserted relationships and attributes as the Base atom except for the NDC code attributes. The NDC code attributes of the base atom will be assigned to the duplicate atoms that represent the different meanings of the base atom. RxNorm forms will be created to reflect the true meaning of the NDC code(s) assigned to each duplicate. An NDC code from a base atom can only be assigned to one duplicate atom at a time, but a duplicate atom can carry more than one similar meaning NDC codes from the base atom. The duplicate atom's term type will be created by prepending 'MTH_RXN_' to the base atom's term type. A Base atom can be identified by the existence of an attribute in RXNSAT.RRF where the ATN='AMBIGUITY_FLAG' and the ATV='Base'. Similarly, the duplicate atoms are identified with ATN='AMBIGUITY_FLAG' and ATV='Duplicate'. This attribute will carry the SAB of the base atom. In addition, a relationship will exist between the base atom and it's duplicate atoms in RXNREL.RRF with "includes" and "included_in" relationship attributes (RELA). This relationship will carry the SAB of the base atom. Examples of RXNCONSO.RRF entries for a base atom and it's duplicates 727359|ENG|P||PF||N|2656259||||GS|BD|28336|Hyalgan 20mg/2ml Solution for Injection||N||727362|ENG|P||PF||N|2719627||||GS|MTH_RXN_BD|28336|Hyalgan 20mg/2ml Solution for Injection_#2||N|| 727308|ENG|P||PF||N|2719626||||GS|MTH_RXN_BD|28336|Hyalgan 20mg/2ml Solution for Injection_#1||N|| Examples of RXNSAT.RRF entries for these atoms (ATN="AMBIGUITY_FLAG") 727362|||2719627|AUI|28336|||AMBIGUITY_FLAG|GS|Duplicate|N||727308|||2719626|AUI|28336|||AMBIGUITY_FLAG|GS|Duplicate|N|| 727359|||2656259|AUI|28336|||AMBIGUITY_FLAG|GS|Base|N|| Examples of RXNREL.RRF entries for these atoms |2656259|AUI|RO||2719626|AUI|included_in|||GS||||N|||2719626|AUI|RO||2656259|AUI|includes|||GS||||N|| |2656259|AUI|RO||2719627|AUI|included_in|||GS||||N|| |2719627|AUI|RO||2656259|AUI|includes|||GS||||N|| 10.0 Drug Dose Forms and the Modified Format for SCD and SBD Normal Forms To accurately represent factors of time, measures or strength for certain dose forms within RxNorm, an additional format for SCD and SBD forms has been utilized along with a more succinct set of dose forms for certain categories of forms. The factor of time, measure or strength can now be represented by a Quantity Factor appended to the beginning of the SCD or SBD name. This quantity factor consists of a number followed by a unit measure. The number might represent a strength, a unit of time, or a quantity of dosages depending upon the dosage form in use at the time. This quantity factor is stored as an attribute to the RxNorm SAB atom as the value of the ATN='RXN_QUANTITY' in RXNSAT.RRF. Some dose forms have been retired and replaced by more generic dose form names, allowing for greater flexibility in representing drug names. Other dose forms have been added. The following dose forms have been replaced by the more generic dose form shown to the right of the name. The Quantity number is variable according to the clinical drug being represented.
Example RxNorm forms before the data transformation: The following dose forms have been added to the RxNorm vocabulary. For these dose forms, a quantity factor is required.
All other dose forms in RxNorm may contain an optional quantity factor.
Example forms are shown below: Examples of RXNSAT.RRF entries for an RXCUI (ATN="RXN_QUANTITY") 104420|||2701594|AUI|104420|||RXN_QUANTITY|RXNORM|24 HR|N||104873|||2701596|AUI|104873|||RXN_QUANTITY|RXNORM|72 HR|N|| 10.1 Deprecating Syrup and Elixir Dose Forms In an effort to reduce the discrepancies related to NDC codes on RxNorm forms, beginning with the March 2008 release, RxNorm will be using the Oral Solution dose form in lieu of the Syrup and Elixir dose forms. Existing RxNorm normal forms (SCD, SBD, SCDF, SBDF) using Syrup and Elixir have been transformed into RxNorm normal forms using the Oral Solution dose form. In some cases, this process resulted in new RxNorm forms being created, in others, an RxNorm form already existed and was reused. The RxNorm normal forms that contained Syrup and Elixir dose forms have been archived. 11.0 Release Types and Explanation This Full release of RxNorm is consistent with the 2008AA UMLS Metathesaurus release.
11.1 The following counts apply for this release of RxNorm:
The content of the RXNSAB.RRF file has been modified to reflect changes required by the UMLS. The number of fields in RXNSAB has not changed, but the format of the following fields have been expanded and include semi-colon separated information. The fields affected are: Source License Contact (SLC), Source Content Contact (SCC), and the Source Citation (SCIT). Please refer to the RXNSAB.RRF detailed documentation within this document for more information. New since the July 2007 release is the RXNCUICHANGES.RRF file. This file contains information about changes to the RxNorm Concept_id (RXCUI) for source asserted atoms and for the RxNorm forms (SAB=RXNORM atoms) that have been archived. More information may be found about this file beginning at this portion of this document. In addition, this release contains database control files and SQL commands for use in the automation of the loading process of these files into a RDBMS. Scripts and controls are provided for the loading the RxNorm files into an Oracle database or a MySQL database. This release contains complete sets of data and the RxNorm forms (RXNORM source) for the following RxNorm drug data source providers:
The most complete, accurate and up-to-date drug information can be obtained from the use of these RxNorm Release files. The character set of RxNorm Release Files is Unicode UTF-8 11.3 RxNorm Release File Format RxNorm uses the Rich Release Format (RRF), introduced in 2004. All Rich Release Format file names have an extension (.RRF). The RxNorm Rich Release Format is described in this documentation (usually abbreviated as RXNRRF). Refer to the UMLS Metathesaurus documentation for a complete description of the RRF. RxNorm follows all previously established standards and practices of the latest version of the UMLS Metathesaurus. Where RxNorm may differ slightly from these practices is documented here. 11.5 Uses of Concept and Atom Identifiers In RxNorm, every RXCUI (concept) is linked to at least one RXAUI (atom), but can be linked to many of these. Every RXAUI (atom) is linked to a single RXCUI (concept). 12.0 Data Files - RxNorm Rich Release Format (RXNRRF) All file names begin with the letters RXN (RxNorm) and are followed by letters that denote the file contents (e.g., RXNREL=relationships, RXNSAB=source abbreviations), and then a file extension .RRF. The data in each RxNorm entry may be represented in different "relations" or files. These files correspond to the four logical groups of data elements described in Sections 2.2 - 2.5 of the Metathesaurus documentation. The exceptions to this rule are the RXNATOMARCHIVE.RRF and the RXNCUICHANGES.RRF files. The RXNATOMARCHIVE.RRF file is a file created by RxNorm for use in tracking the archival of names (atoms) no longer provided by RxNorm drug source providers, or atoms no longer used by the RxNorm system. Only atoms from the source RxNorm (SAB=RXNORM) will be in the archive. The RXNCUICHANGES.RRF file is a new file provided by RxNorm for use in tracking the changes to the RxNorm Concept_id (RXCUI) for source asserted atoms, RxNorm OCD atoms, and for RXCUI changes to RxNorm forms (SAB=RXNORM atoms) that have been archived in the RXNATOMARCHIVE.RRF file. For each release, this tracking is provided for data changed since the last release of RxNorm. The data file is not cumulative. RxNorm provides data in the following types of files: Concepts, Concept Names, and their sources (2.2) = RXNCONSO.RRF Attributes (2.3) = RXNSAT.RRF, RXNSTY.RRF Relationships (2.4) = RXNREL.RRF Data about RxNorm (2.5) = RXNDOC.RRF, RXNSAB.RRF Archive Data = RXNATOMARCHIVE.RRF Concept Changes Tracking Data = RXNCUICHANGES.RRF Each file or named table of data values has by definition a fixed number of columns; the number of rows depends on the content of a particular version of the RxNorm. The RxNorm release files follow the format of the Metathesaurus releases files with a few exceptions which are noted below. 12.2 Descriptions of Each File The descriptions of the files appear in the following order: Each file description lists the columns or data elements that appear in the file and includes sample rows from the file. 12.3 Documentation for Abbreviated Values (File = RXNDOC.RRF) This file follows the format of the Metathesaurus MRDOC.RRF file. At this time, this file contains all of the data contained in the UMLS MRDOC.RRF file. In the furture, the contents of this file may be tailored to the RxNorm subset of data only. There is exactly one row in this table for each allowed value of selected data elements or attributes that have a finite number of abbreviations as allowed values. Examples of such data elements include TTY, ATN, TS, STT, REL, RELA.
Sample Records ATN|DDF|expanded_form|Drug Doseform|
This file follows the general format of the MRCONSO.RRF file of the Metathesaurus. Some of the Metathesaurus fields are not provided by RxNorm and are marked as "(no value provided)". There is exactly one row in this file for each atom (each occurrence of each unique string or concept name within each source vocabulary) in RxNorm, i.e., there is exactly one row for each unique RXAUI in RxNorm. Every string or concept name in RxNorm appears in this file, connected to its language, source vocabularies, and its concept identifier (RXCUI).
Sample Records 91348|ENG|P||PF||Y|707001|707001|91348||RXNORM|SCD|RX10091348|Hydrogen Peroxide 300 MG/ML Topical Solution|||| 12.5 Simple Concept and Atom Attributes (File = RXNSAT.RRF) This file follows the general format of the MRSAT.RRF file of the
Sample Records 178|||4996|AUI|MTHU000146|AT32525185||TYPE|MMSL|bulk compounding chemicals|N|| 12.6 Semantic Types (File = RXNSTY.RRF) This file follows the general format of the MRSAT.RRF file of the
Sample Records 44|T109|A1.4.1.2.1|Organic Chemical||| 12.7 Related Concepts (File = RXNREL.RRF) This file follows the general format of the MRREL.RRF file of the Note that for asymmetrical relationships there is one row for each direction of the relationship. Note also the direction of REL - the relationship which the SECOND concept or atom (with Concept Unique Identifier RXCUI2 and Atom Unique Identifier RXAUI2) HAS TO the FIRST concept or atom (with Concept Unique Identifier RXCUI1 and Atom Unique Identifier RXAUI1).
Sample Records 353653|1553161|AUI|RO|102931|779853|AUI|consists_of|||RXNORM|||||| 12.8 Source Information (File=RXNSAB.RRF) This file follows the general format of the MRSAB.RRF file of the There is one row in this file for every source in RxNorm that is represented in this RxNorm release. The structure of RXNSAB.RRF is as follows:
Sample Record: 12.9 Archive Data (File = RXNATOMARCHIVE.RRF) This file contains data about RxNorm SAB names (atoms) that are no longer a part of the RxNorm database because the drug data source provider is no longer providing this name to RxNorm. This file is not similar to any Metathesaurus RRF files. It is newly created by RxNorm. The structure of RXNATOMARCHIVE.RRF is as follows:
Sample Records: 12.10 Concept Changes (File = RXNCUICHANGES.RRF) This file provides information about changes to the concept_id (RXCUI) for atoms in RxNorm from release to release.
For source asserted atoms and SAB=RxNorm OCD term type atoms, all data fields will be populated. For RXCUI changes to
RxNorm forms that have been archived, only the SAB, OLD_RXCUI, and NEW_RXCUI will be provided. Full information about
RxNorm forms that have been archived can be found in the RXNATOMARCHIVE.RRF file. Information is provided here as a
convenience. The file provides data about changes since the last release of RxNorm, it is not cumulative.
Sample Records: 1253224|688059|RXNORM|OCD|CEPHAPIRIN NA 20GM/VIL INJ|688055|688059|426260|117164003|SNOMEDCT|PT|HLA-DQ2 antigen|27034|461862| ||RXNORM|||670619|702633| 13.0 Database Creation Automation We are providing scripts and control files to help in
the creation and automation of your database loading with the RxNorm Release Files.
The populate_oracle_rxn_db.bat file contains 4 parameters, which should be customized for your particular environment. They are as follows:
Once these parameters are populated, you should remove the '::' (double colon)
characters from the front of each line - this will make the commands active. |
Recommended Software Version - MySQL Server version 5.0
Filenames and brief descriptions follow:Filename | Description | |
Table_scripts_mysql_rxn.sql | Creates the tables | |
Populate_mysql_rxn.bat | Load the RxNorm files from windows into tables | |
populate_mysql_rxn.sh | Load the RxNorm files from Unix/Linux to tables | |
Load_scripts_mysql_rxn_win.sql | Windows loading script (called from populate script) | |
Load_scripts_mysql_rxn_unix.sql | Unix/Linux loading script (called from populate script) | |
Indexes_mysql_rxn.sql | Creates table indexes (optional) |
Prerequisite
The script is written to expect that there is a local MySql Server installed and configured and that you plan to load your RxNorm subset database into a database being managed by this local server. For more information on that, you are encouraged to visit http://www.mysql.comCreating a Database
In order to load your subset into a MySQL database, you will have to either use an existing database or create a new one. To create a new database, use the following command:
CREATE DATABASE IF NOT EXISTS [database name] CHARACTER SET utf8;Windows
Copy the following files to the local drive, where the RRF files are saved:
Edit the Populate_mysql_rxn.bat script and configure the five parameters at the top of the script. These are:
Parameter | Description | |
MYSQL_HOME | The path to your MySQL home directory | |
user | The user name to use to connect to your database schema | |
password | The password to use to connect to your database schema | |
host_name | The host name of your database server | |
db_name | The name of your RxNorm database schema |
MYSQL_HOME should be set to the installation directory of your MySQL server. This is likely to be something like “C:\Program Files\MySQL\MySQL Server 5.0". Remember to enclose the value in quotes if the directory name contains spaces. If your database is configured without a password you can leave the password setting blank. If your database is configured without a hostname you can leave the hostname blank or use localhost. After configuring these four parameters, this section of your script may look something like the following.
Set MYSQL_HOME= “C:\Program Files\MySQL\MySQL Server 5.0"
Set user=myuser
Set password=p4ssword
Set host_name=localhost
Set db_name =RxNorm
You are now ready to run the script. To do so, navigate to your subset directory using the Windows explorer and double-click on the “Populate_mysql_rxn.bat" file you just finished editing.
Here are some things to keep in mind when using this script:
Linux or Solaris
Copy the following files to the local drive, where the RRF files are saved:
Edit the "populate_mysql_rxn.sh" script and configure the four parameters at the top of the script. These are:
Parameter | Description | |
MYSQL_HOME | The path to your MySQL home directory | |
user | The user name to use to connect to your database schema | |
password | The password to use to connect to your database schema | |
db_name | The name of your RxNorm database schema | |
dbserver | The name of your database server |
MYSQL_HOME should be set to the installation directory of your local MYSQL Server. If your database is configured without a password you can leave the password setting blank. After configuring these four parameters, this section of your script may look something like this.
MYSQL_HOME= /usr
user=myuser
password=p4ssw0rd
db_name=RxNorm
dbserver=ServerName
You are now ready to run the script. To do so, navigate to your subset directory and invoke the script from the command line. It may be necessary to change the file permissions to make the script executable before it can be started. For example:
chmod 775 populate_mysql_rxn.sh
And to Execute the script
populate_mysql_rxn.sh
Here are some things to keep in mind when using this script.
Last reviewed: 01 July 2008
Last updated: 01 July 2008
First published: 01 July 2008
Metadata| Permanence level: Permanent: Dynamic Content