RxNorm for drug name normalization: a case study of prescription opioids in the FDA adverse events reporting system

Abstract

Numerous studies have been conducted on the US Food and Drug Administration (FDA) Adverse Events Reporting System (FAERS) database to assess post-marketing reporting rates for drug safety review and risk assessment. However, the drug names in the adverse event (AE) reports from FAERS were heterogeneous due to a lack of uniformity of information submitted mandatorily by pharmaceutical companies and voluntarily by patients, healthcare professionals, and the public. Studies using FAERS and other spontaneous reporting AEs database without drug name normalization may encounter incomplete collection of AE reports from non-standard drug names and the accuracies of the results might be impacted. In this study, we demonstrated applicability of RxNorm, developed by the National Library of Medicine, for drug name normalization in FAERS. Using prescription opioids as a case study, we used RxNorm application program interface (API) to map all FDA-approved prescription opioids described in FAERS AE reports to their equivalent RxNorm Concept Unique Identifiers (RxCUIs) and RxNorm names. The different names of the opioids were then extracted, and their usage frequencies were calculated in collection of more than 14.9 million AE reports for 13 FDA-approved prescription opioid classes, reported over 17 years. The results showed that a significant number of different names were consistently used for opioids in FAERS reports, with 2,086 different names (out of 7,892) used at least three times and 842 different names used at least ten times for each of the 92 RxNorm names of FDA-approved opioids. Our method of using RxNorm API mapping was confirmed to be efficient and accurate and capable of reducing the heterogeneity of prescription opioid names significantly in the AE reports in FAERS; meanwhile, it is expected to have a broad application to different sets of drug names from any database where drug names are diverse and unnormalized. It is expected to be able to automatically standardize and link different representations of the same drugs to build an intact and high-quality database for diverse research, particularly postmarketing data analysis in pharmacovigilance initiatives.

1 Introduction

Spontaneous AE reporting systems are essential components in post-marketing drug surveillance to assess human drug safety. They are an important source of information for the detection of previously unidentified or unknown AEs in clinical trials, and are important for real-world safety assessments in various populations and clinical practice (Noguchi et al., 2021). FAERS is a database for post-marketing drug safety monitoring and was constructed for the pharmaceutical industry, healthcare providers and consumers to easily report human adverse events to the FDA. Since 1969 into the present, FAERS has been the largest repository of spontaneously reported AEs maintained by any single country, with over 16 million AE reports (Administration, USFDA, 2021). Therefore, numerous studies have used this publicly available database to assess post-marketing drug safety and risks (Winnenburg et al., 2015; Botsis et al., 2017; Fukazawa et al., 2018; Ly et al., 2018; Schotland et al., 2018) to support the FDA’s post-marketing safety surveillance program for currently marketed US drugs and therapeutic biologics products (Rodriguez et al., 2001; Trontell, 2001; Wysowski and Swartz, 2005).

However, when mining adverse event reports from FAERS, it was noticed that although adverse events were coded as Preferred Terms (PTs) in MedDRA (Medical Dictionary for Regulatory Activities. Available at: http://www.meddra.org/), drug names in FAERS reports might appear different for various reasons including that both brand names and generic names of drugs are used; data are collected from various sources worldwide; discrepancies occur between the reported name and the correct name due to errors or misspellings when entering drug names to the system; drug names can change over time due to factors such as rebranding, patent expiration, or regulatory decisions; use of slang terms for drugs. Therefore, different formats of drug names for the same drug entity are present in the FAERS database for numerous drugs. Currently, there are no available tools to automatically group all the different drug name formats into a single drug entity without proper data pre-processing. Consequently, to ensure accurate analysis and interpretation of FAERS data, it is essential to consider all potential variations of drug names and reconcile them appropriately. Otherwise, it may result in incomplete data collection of adverse event reports from FAERS consequently leading to inaccurate results and interpretation. This phenomenon not only exists in FAERS, but also occurs in any other spontaneous reporting databases where drug names were diverse and unnormalized due to the unstructured entry (e.g., Yellow Card Scheme (Report a problem with a medicine or medical device. Available at: https://www.gov.uk/report-problem-medicine-medical-device)).

To the best of our knowledge, only a few studies have been conducted on the issue of drug name variations in FAERS reports. Some studies used the RxNorm for drug name mapping to try to build a standardized dataset of FAERS adverse events (Poluzzi et al., 2012; Banda et al., 2016; Khaleel et al., 2022), but detailed information on how the RxNorm mapping facilitated drug normalization was not provided. RxNorm is freely available and public-accessible, and has been developed by the National Library of Medicine and provides a standardized nomenclature for clinical drugs as well as the relationships of different names based on different external source vocabularies (Liu et al., 2005; Nelson et al., 2011). Evaluations of RxNorm for representative ambulatory electronic prescriptions (e-prescriptions) have shown that the coverage rate of RxNorm for representing clinical drugs is very high, up to 99.995%, in different random samples of thousands of e-prescriptions (O'Neill and Bell, 2010; Dhavle et al., 2016). In addition to searching the RxNorm concepts (i.e., standardized drug names) by exact match or normalized string search, RxNorm allows approximate matching to determine the most closely-related searching string-matched RxNorm concepts by fixing spelling errors as well as informal abbreviations and acronyms. Consequently, it might be effective to use RxNorm to automatically map heterogeneous drug names to a standard drug name to build up a clean and accurate dataset on FAERS-related studies.

In this study, a novel method was developed to use RxNorm for drug normalization in spontaneous reporting databases through the RxNorm API (https://rxnav.nlm.nih.gov/RxNormAPIs.html), which is a web interface for inputting and accessing information from the RxNorm data set. We have described each step of this process in detail through a case study involving retrieving FDA-approved opioid-associated adverse event reports. The effectiveness of our method using RxNorm application was demonstrated as capable of reducing the heterogeneity of opioid names entered by the public in the FAERS database, and therefore was able to build up a more complete dataset of opioid-related adverse event reports. This RxNorm method is not only applicable to FAERS but can also be useful with other spontaneous reporting databases where there is no fixed rule for drug name entries. The application of this method for drug normalization is expected to not only reduce the heterogeneities of drug name entries to overcome drug name discrepancies and inconsistencies; but also standardize the representation of drug-related adverse events or other data in a consistent and comparable manner. In addition, this RxNorm-driven method could facilitate the integration of data from multiple databases, technologies, or modalities to enhance the comprehensive analysis of drug-related data, leading to more robust insights and discoveries in drug safety and pharmacovigilance.

2 Materials and methods

As shown in Figure 1, the entire list of FDA-approved drugs was downloaded in February 2021 (Drug Approvals and Databases. Available at: https://www.fda.gov/drugs/development-approval-process-drugs/drug-approvals-and-databases). Opioid names were manually identified from this list. The RxNorm API was then applied to map all FDA-approved opioids to their equivalent RxCUIs and RxNorm names. Each opioid name was associated with one RxCUI (an integer number), and one RxNorm name (a standardized drug name). RxCUI is the key component of RxNorm and is used as a unique, explicit identifier for an individual drug entity in RxNorm.

FIGURE 1

The adverse event reports (AERs) collected from FAERS between 2004 Quarter 1 and 2020 Quarter 3 were retrieved and downloaded in “xml” format (Administration, USFDA, 2021). Although drug names appear heterogeneous, they were located in “xml” tag pairs as <medicinalproduct></medicinalproduct> in AERs. The drug names were then automatically extracted from the reports and their usage frequencies were counted, respectively. The RxNorm API was applied to the extracted drug names in the same way to map all drug names to their respective RxCUIs and RxNorm names. The drug names were then clarified by matching their RxCUIs with the RxCUI list of the FDA-approved opioids in the database.

When using RxNorm API to find the matching RxCUI of a drug, a list of RxCUIs, instead of only one RxCUI, might be shown in the results. Therefore, their respective ranking scores represented how close the RxNorm concepts matched with the search strings. Under these circumstances, only the RxCUIs with the highest-ranking scores were accepted. To ensure the accuracy and avoid possible errors made by the algorithm in RxNorm API, manual checking was also applied to remove easily recognized mistakes in the RxCUI list of the FDA-approved opioids.

3 Results and discussion

3.1 Construction of a reference database for FDA-approved prescription opioids

The entire list of FDA-approved drugs as of February 2021 contained 7,436 drug names. After manual identification and RxNorm API application, a preliminary database was constructed that contained the information for 92 FDA-approved prescription opioids, their corresponding RxCUIs and RxNorm names, which we designated as the reference database for drug name normalization of FDA-approved prescription drugs in this study. Therefore, RxCUI/RxNorm should be an appropriate identifier or index for drug annotation and normalization. In addition, the application of RxCUI/RxNorm to the database makes it possible and available to relate all things associated with a specific drug.

3.2 A case study using prescription opioids in FAERS

To demonstrate the application and function of the reference database for drug normalization, we have used the prescription opioid entries in FAERS as a case study. After normalizations, we obtained 20,178,515 drug-AE pairs from 2004 Quarter 1 through 2020 Quarter 3. In total, there were 737,169 unique drug names in these reports. After mapping to their equivalent RxCUIs (or RxNorm names), 69,889 unique numbers of RxCUIs (or RxNorm names) were obtained (Figure 2) which was less than 10% of the total drug names in those reports. These unique RxCUIs were matched with those in the reference RxCUI database of FDA-approved opioids and 92 RxCUIs (or RxNorm names) were identified. When we compared this with the dataset of originally retrieved adverse event reports from 2004 Quarter 1 to 2020 Quarter 3, the 92 RxCUIs corresponded with 7,892 different opioid names before RxNorm API mapping. With the application of the reference database, we could easily retrieve the FDA-approved opioid-associated RxCUIs from a big dataset and avoided missing or duplicating information from different formats of drug names. In addition, the fact that 69,889 unique RXCUIs represented the original 737,169 drug names after mapping with RxNorm API revealed that the RxNorm API mapping could greatly (737,169/69,889 = 10.5 times) reduce the usage heterogeneities of drug names by assigning the different drug name with the same active components into the same group (RXCUIs). This was also confirmed by the correspondence of 92 opioids with 7,892 opioid names in the original dataset (7,892/92 = 85.8 times, Figure 2).

FIGURE 2

To further understand the usage status of different drug names, the usage frequencies were calculated for different drug names that were used at least one time (k>=1), three times (k > = 3), five times (k > = 5) and ten times (k > = 10, Table 1; Figure 3). The number of RxNorm names for the FDA-approved opioids (92) and their total usage frequency (936,716) did not change with k, while the total number of different drug names and their total usage frequencies decreased when k increased. For example, when k > = 1, there were 7,892 opioid names responding to 92 RxCUIs (RxNorm names) of opioids that were used 1,417,126 times total in this dataset; when k > = 10, the total number of different drug names reduced to 842 (∼89.3%), while their total usage frequency was only reduced 12,734 out of 1,417,126 (∼0.9%). These results reveal the large heterogeneities in the usage of opioid names due to the different variations on drug names used by the public. Among the 842 different formats of the drug names that were used at least ten times, the 92 standard RxNorm names contributed around 66.1% (936,716/1,417,126) of the total usage frequencies, the other 750 (842–92) formats of the drug names contributed around 33.0%. If AERs are extracted using the 92 RxNorm names only (i.e., standard names) from FAERS or other adverse events databases, a large amount of information would be missing in the dataset, which may lead to inaccuracy and misinterpretation of the data and its analysis results. The drug name normalization by an appropriate approach is therefore very important. The results of this study demonstrated that using RxNorm mapping could reduce the heterogeneity of opioid names and is necessary to build an intact dataset for analysis by collecting any reports with different drug names which would otherwise be missing.

FIGURE 3

To further describe the results in detail, we collected the opioid RxNorm names which had at least two different names and where each name was used at least three times (to exclude the possibility of spelling errors) in the opioid-AE dataset from FAERS and calculated the usage frequencies of each individual name. The data mining results are listed in Table 2. Sixty seven out of 92 RxNorm names of FDA-approved opioids were filtered out and categorized into 13 opioid groups, including buprenorphine, codeine, dihydrocodeine, fentanyl, hydrocodone, hydromorphone, meperidine, methadone, morphine, oxycodone, oxymorphone, tapentadol, and tramadol. Each group has a few opioids with their corresponding RxCUI numbers and RxNorm names identified (Table 2). Each RxNorm drug was reported with several different names, and the numbers of names as well as the usage frequencies were reported. It was observed that more than 37.3% (25 out of 67) of RxNorm names had the percentages of their usage frequencies above 90%, possibly due to the drug commonalities and ease of remembering (e.g., “codeine” or “opana”). Conversely, 14 RxNorm names had a percentage of usage frequency less than 0.1%. It was noticed that these RxNorm names were mostly combined opioids (i.e., opioids with other ingredients such as aspirin or acetaminophen) and in the format of long strings with special characters “/”, for example, “aspirin/oxycodone” or “acetaminophen/caffeine/dihydrocodeine”. Hence, it might be difficult for patients to remember accurately the standard names of these combined opioids leading to entry of different names when reporting their AEs in FAERS. In addition, more than half of these 67 FDA-approved opioids had more than 10 various names other than their RxNorm names, with three of them having even more than 200 various names. They are “acetaminophen/codeine”, “acetaminophen/hydrocodone” and “tramadol hydrochloride”, which have been popularly used for years but potentially could not be remembered and typed correctly due to their long names. For example, in the class of hydrocodone, there were 286 various names under the same RxCUI number 214182 but the standard name (RxNorm name) acetaminophen/hydrocodone was only used 73 times in the dataset, and the rest of the 285 various names were used 77,666 (77,739–73) times, within which three different names “hydrocodone bitartrate and acetaminophen”, “hydrocodone bitartrate/acetaminophen”, and “hydrocodone/acetaminophen” were used more than 10,000 times, respectively (data not shown here). A search using only the RxNorm standard name to retrieve the reports from FAERS would not include more than 99% of the AERs in the dataset, which might result in biased and inaccurate analysis results.

To describe the method in more detail, we randomly selected two RxCUI numbers and listed all the various names and their usage frequencies in our retrieved dataset. Table 3 shows the example of the opioid with the RxCUI number of 214256. This opioid had 12 different names shown in the FAERS adverse reports including its standard RxNorm name of “aspirin/oxycodone” (highlighted in red). The different names in Table 3 were sorted by usage frequency from high to low, and the most popularly used name was “oxycodone and aspirin” which was used in 55 FAERS reports in our dataset. The RxNorm standard name “aspirin/oxycodone” was used only four times in addition to ten usages of its inverted word format “oxycodone/aspirin”. The same situation was shown in Table 4 where the opioid with the RXCUI number of 218337 was listed as another example. The RxNorm of RxCUI 218337 is “methadone hydrochloride” (highlighted in red) and was used 1,261 times; while the very similar name “methadone hydrochloride.” was shown in 2,117 FAERS reports in the data set. The most used name for this opioid was “methadone hcl” which was reported 11,040 times, far more than the others. In both randomly selected examples, the standard RxNorm names exhibited in less than 10% of the adverse events reports, with “aspirin/oxycodone” as low as 3%. In fact, most of the adverse event reports had various formats of names instead of the standard RxNorm name since FAERS is a spontaneous reporting system. These two randomly selected examples confirmed the existence of the drug name variations and the potentially severe consequences in FAERS and other spontaneous reporting systems.

4 Conclusion

It is extremely important to recognize and identify variations in drug names when using spontaneous reporting databases for data analysis. In responding to this challenge, it is necessary to explore appropriate methods and algorithms that aim to automatically standardize and link different representations of the same drugs to build an intact and high-quality database for all kind of research, especially during postmarketing data analysis in pharmacovigilance. In addition, drug name normalization is also a crucial step in computerization and machine learning analysis of drug-related data. As a conclusion, in this study, we have developed a workflow to provide a standardized nomenclature for clinical drugs and for drug name normalization by using the RxNorm API system. The case study of prescription opioids analysis of FAERS data confirmed the importance of drug name normalization and the effectiveness and accuracy of the proposed method. The reference opioid/RxNorm/RxCUI database, as a derivative product of the method in the case study, will provide a simple and direct way for drug reviewers and analysts to conduct pharmacovigilance and safety analysis, where AEs and drug interactions are monitored. In addition, the drug names normalized by this method provide consistent and standardized inputs as a foundation for machine learning algorithms and predictive modeling for future prediction and analysis tasks.

References

• 1

  ADMINISTRATION, USFDA (2021). Questions and answers on FDA's adverse event reporting system (FAERS). Available: https://www.fda.gov/drugs/surveillance/questions-and-answers-fdas-adverse-event-reporting-system-faers (Accessed).

  • Google Scholar

• 2

  BandaJ. M.EvansL.VanguriR. S.TatonettiN. P.RyanP. B.ShahN. H. (2016). A curated and standardized adverse drug event resource to accelerate drug safety research. Sci. Data3, 160026. 10.1038/sdata.2016.26

  • CrossRef
  • Google Scholar

• 3

  BotsisT.FosterM.AryaN.KreimeyerK.PandeyA.AryaD. (2017). Application of natural language processing and network analysis techniques to post-market reports for the evaluation of dose-related anti-thymocyte globulin safety patterns. Appl. Clin. Inf.8, 396–411. 10.4338/aci-2016-10-ra-0169

  • CrossRef
  • Google Scholar

• 4

  DhavleA. A.Ward-CharlerieS.RuppM. T.KilbourneJ.AminV. P.RuizJ. (2016). Evaluating the implementation of RxNorm in ambulatory electronic prescriptions. J. Am. Med. Inf. Assoc.23, e99–e107. 10.1093/jamia/ocv131

  • CrossRef
  • Google Scholar

• 5

  FukazawaC.HinomuraY.KanekoM.NarukawaM. (2018). Significance of data mining in routine signal detection: analysis based on the safety signals identified by the FDA. Pharmacoepidemiol Drug Saf.27, 1402–1408. 10.1002/pds.4672

  • CrossRef
  • Google Scholar

• 6

  KhaleelM. A.KhanA. H.GhadziS. M. S.AdnanA. S.AbdallahQ. M. (2022). A standardized dataset of a spontaneous adverse event reporting system. Healthc. (Basel)10, 420. 10.3390/healthcare10030420

  • CrossRef
  • Google Scholar

• 7

  LiuS.MaW.MooreR.GanesanV.NelsonS. (2005). RxNorm: prescription for electronic drug information exchange, 7. IEEE Computer Society, 17–23.

  • Google Scholar

• 8

  LyT.PamerC.DangO.BrajovicS.HaiderS.BotsisT.et al (2018). Evaluation of Natural Language Processing (NLP) systems to annotate drug product labeling with MedDRA terminology. J. Biomed. Inf.83, 73–86. 10.1016/j.jbi.2018.05.019

  • CrossRef
  • Google Scholar

• 9

  NelsonS. J.ZengK.KilbourneJ.PowellT.MooreR. (2011). Normalized names for clinical drugs: RxNorm at 6 years. J. Am. Med. Inf. Assoc.18, 441–448. 10.1136/amiajnl-2011-000116

  • CrossRef
  • Google Scholar

• 10

  NoguchiY.TachiT.TeramachiH. (2021). Detection algorithms and attentive points of safety signal using spontaneous reporting systems as a clinical data source. Brief. Bioinform22, bbab347. 10.1093/bib/bbab347

  • CrossRef
  • Google Scholar

• 11

  O'NeillS. M.BellD. S. (2010). Evaluation of RxNorm for representing ambulatory prescriptions. AMIA Annu. Symp. Proc.2010, 562–566.

  • Google Scholar

• 12

  PoluzziE.PiccinniC.RaschiE.De PontiF. (2012). Data mining techniques in pharmacovigilance: analysis of the publicly accessible FDA adverse event reporting system (AERS). IntechOpen, data mining applications in engineering and medicine.

  • Google Scholar

• 13

  RodriguezE. M.StaffaJ. A.GrahamD. J. (2001). The role of databases in drug postmarketing surveillance. Pharmacoepidemiol Drug Saf.10, 407–410. 10.1002/pds.615

  • CrossRef
  • Google Scholar

• 14

  SchotlandP.RaczR.JacksonD.LevinR.StraussD. G.BurkhartK. (2018). Target-adverse event profiles to augment pharmacovigilance: a pilot study with six new molecular entities. CPT Pharmacometrics Syst. Pharmacol.7, 809–817. 10.1002/psp4.12356

  • CrossRef
  • Google Scholar

• 15

  TrontellA. E. (2001). How the US Food and Drug Administration defines and detects adverse drug events. Curr. Ther. Res.62, 641–649. 10.1016/s0011-393x(01)80070-9

  • CrossRef
  • Google Scholar

• 16

  WinnenburgR.SorbelloA.RippleA.HarpazR.TonningJ.SzarfmanA.et al (2015). Leveraging MEDLINE indexing for pharmacovigilance - inherent limitations and mitigation strategies. J. Biomed. Inf.57, 425–435. 10.1016/j.jbi.2015.08.022

  • CrossRef
  • Google Scholar

• 17

  WysowskiD. K.SwartzL. (2005). Adverse drug event surveillance and drug withdrawals in the United States, 1969-2002: the importance of reporting suspected reactions. Arch. Intern Med.165, 1363–1369. 10.1001/archinte.165.12.1363

  • CrossRef
  • Google Scholar