Evaluating drug-drug interaction information in NDF-RT and DrugBank
© Peters et al.; licensee BioMed Central. 2016
Received: 22 November 2014
Accepted: 30 March 2015
Published: 11 May 2015
There is limited consensus among drug information sources on what constitutes drug-drug interactions (DDIs). We investigate DDI information in two publicly available sources, NDF-RT and DrugBank.
We acquire drug-drug interactions from NDF-RT and DrugBank, and normalize the drugs to RxNorm. We compare interactions between NDF-RT and DrugBank and evaluate both sources against a reference list of 360 critical interactions. We compare the interactions detected with NDF-RT and DrugBank on a large prescription dataset. Finally, we contrast NDF-RT and DrugBank against a commercial source.
DrugBank drug-drug interaction information has limited overlap with NDF-RT (24-30%). The coverage of the reference set by both sources is about 60%. Applied to a prescription dataset of 35.5M pairs of co-prescribed systemic clinical drugs, NDF-RT would have identified 808,285 interactions, while DrugBank would have identified 1,170,693. Of these, 382,833 are common. The commercial source Multum provides a more systematic coverage (91%) of the reference list.
This investigation confirms the limited overlap of DDI information between NDF-RT and DrugBank. Additional research is required to determine which source is better, if any. Usage of any of these sources in clinical decision systems should disclose these limitations.
KeywordsDrug-drug interactions NDF-RT DrugBank
An important component of electronic health record systems is the use of clinical decision support (CDS) to improve medication safety [1,2]. Preventable adverse drug reactions include those resulting from drug-drug interactions (DDIs) [3,4]. Among other things, CDS systems leverage drug-drug interaction information to reduce the possibility of adverse drug events [5,6]. While there are many sources of DDI information, and many commercially available systems which contain this information, there is limited consensus on what constitutes critical and non-critical DDI .
One source of publicly available DDI information is contained in the National Drug File Reference Terminology (NDF-RT) and available through the NDF-RT application programming interface (API). Several applications developed for medication management take advantage of the API for checking interactions in medication lists (e.g., the iOS app “Dosage” for medication information and reminders). However, it was announced before the writing of this article that the DDI information would be soon removed from NDF-RT . Our search for another publicly available source of DDI information led us to evaluate the DrugBank data source as a possible replacement for the NDF-RT DDIs.
In this paper, our objective is to evaluate the DDI information in NDF-RT and DrugBank. More specifically, we contrast NDF-RT and DrugBank interactions against each other, and contrast both against a previously published reference set of critical DDIs . We also contrast NDF-RT and DrugBank in their ability to detect DDIs in a large prescription dataset. Finally, we compare the coverage of the reference set by DrugBank and NDF-RT to that of a commercial source.
Drug information sources
The following sections detail the characteristics of the drug information sources used in this research. We use RxNorm to harmonize drugs between the two sources of DDIs under investigation, NDF-RT and DrugBank.
The National Drug File Reference Terminology (NDF-RT) is a resource developed by the Department of Veterans Affairs (VA) Veterans Health Administration, as an extension of the VA National Drug File . It is updated monthly. NDF-RT covers 7319 active moieties (level = ingredient). In addition to providing information about individual drugs (e.g., mechanism of action, physiologic effect, therapeutic intent), NDF-RT also provides a set of 10,831 drug-drug interactions (DDIs). DDIs are asserted at the ingredient level and accompanied by a mention of severity (significant or critical). For example, NDF-RT asserts a critical interaction between omeprazole and clopidogrel and asserts a significant interaction between diltiazem and lovastatin. The version used in this study is dated July 7, 2014 and was accessed through the NDF-RT API . (Provision of DDI information in NDF-RT was discontinued in November 2014).
Developed with funding from Genome Canada, DrugBank is a knowledge base containing “extensive biochemical and pharmacological information about drugs, their mechanisms and their targets” . DrugBank covers 7683 active moieties. Although not primarily developed for clinical use, DrugBank provides a set of 12,128 drug-drug interactions (DDIs), asserted at the ingredient level, along with a brief textual description of the interaction, and information about the possible molecular basis of the interaction (target-based, enzyme-based, transporter-based). For example, DrugBank asserts an interaction between omeprazole and clopidogrel bisulfate, described as “Omeprazole may decrease serum concentrations of the active metabolite(s) of clopidogrel. Clopidogrel prescribing information recommends avoiding concurrent use with omeprazole, due to the possibility that combined use may result in decreased clopidogrel effectiveness”. The possible molecular basis of the interaction is reported to be enzyme-based or transporter-based. The version used in this study (4.0) was downloaded from the DrugBank website on July 1, 2014.
RxNorm is a standardized nomenclature for medications produced and maintained by the U.S. National Library of Medicine (NLM) . While NDF-RT is one of the drug information sources integrated in RxNorm, DrugBank is not. However, most ingredients from DrugBank are covered by RxNorm and RxNorm can be used to map drugs between DrugBank and NDF-RT. Moreover, RxNorm provides a rich network of relations among various types of drug entities. For example, RxNorm explicitly asserts that clopidogrel bisulfate is the “precise ingredient” of the ingredient clopidogrel, making it possible to normalize the various salts and esters of a drug to their base form. RxNorm also integrates the Anatomical Therapeutic Chemical (ATC) classification, which makes it possible to extract the ATC class for most drugs. For example ATC classifies clopidogrel as a Platelet aggregation inhibitors excl. heparin. The July 2014 version of RxNorm is used in this study and was accessed through the RxNorm API .
Extracting drug-drug interaction (DDI) information from textual resources, such as the biomedical literature or structured product labels is an active field of research [15-18]. Other researchers predict DDIs from a variety of resources .
As mentioned earlier, researchers have shown the benefit of integrating DDI information in CPOEs (e.g., [1,2]). However, not all studies demonstrate improvement on medication safety, especially due to the large number of alerts produced by some systems , which raises questions about the quality of the underlying DDI information.
Given the limited consensus across sources of DDI information , researchers have proposed criteria for assessing high-priority DDIs  and for calibrating CDS systems . An expert panel was convened to identify high-severity, clinically significant DDIs for the Office of the National Coordinator for Health Information Technology (ONC) as part of the Meaningful Use incentive program . Candidate DDIs were assessed by the panel based on a number of factors, including severity levels across medication knowledge bases, consequences of the interaction, predisposing factors, and availability of therapeutic alternatives. The resulting list contains 360 interacting pairs of individual drugs containing 86 unique drugs. This list will be referred to as the reference set of DDIs in the following sections.
The specific contribution of our work is to contrast two publicly available sources of DDI information, NDF-RT and DrugBank, through an assessment of the overlap of their content, and of their coverage of a reference set of DDIs. Moreover, we compare the ability of these two sources to identify DDIs in a large prescription dataset, and contrast them against a commercial source. To the best of our knowledge, this is the first such comparative investigation of NDF-RT and DrugBank DDI information.
Our approach to evaluating drug-drug interaction (DDI) information in NDF-RT and DrugBank can be summarized as follows. We acquire the list of drug-drug interactions in NDF-RT and DrugBank, as well as a reference set of DDIs. We map all drugs from the three sets to RxNorm and further normalize them to ingredient entities. We then compare the lists of pairs of interacting drugs across sources in order to determine the shared coverage between NDF-RT and DrugBank, as well as the coverage of the reference set by both sources. We characterize the differences among DDI sets in terms of drug classes. We also compare the interactions detected with NDF-RT and DrugBank in a large prescription dataset. Finally, we compare the coverage of the reference set by DrugBank and NDF-RT to that of a commercial source.
Acquiring DDI information
We used the NDF-RT API  to first extract the full set of DDIs (DRUG_INTERACTION_KIND concepts), then to extract each associated drug concept (level = ingredient) in the pair.
The DrugBank XML and schema definition files were downloaded from the DrugBank web site. We extracted the interaction data from the XML file and created a table of drug name pairs for the interacting drugs.
The reference set of DDIs was created from the drug names listed in Table two of  by associating each object drug with all corresponding precipitant drug(s) within a given interaction class. One pair involving a multi-ingredient drug (azathioprine and mercaptopurine) was eliminated, because multi-ingredient drugs are generally not consistently represented across sources.
Normalizing drugs in reference to RxNorm
After obtaining the drug name pairs for interacting drugs, we mapped the drugs to RxNorm by retrieving the RxNorm identifiers (RxCUIs). For NDF-RT, the RxCUI is part of the drug’s concept properties, so we used the NDF-RT API to extract the RxCUI from the drug properties. For DrugBank and the reference set, we used the RxNorm API  to find the RxCUI from the drug name. More specifically, we used exact and normalized string matches to map drug names to RxNorm.
We then “normalized” to RxNorm ingredients those drugs which mapped to RxNorm entities. Some of the drugs corresponded to base ingredients (e.g., doxacurium), while others corresponded to salt forms that RxNorm classifies as “precise ingredients” (e.g., doxacurium chloride). In order to establish a consistent drug representation across all three data sets for comparison, we converted precise ingredients to RxNorm ingredients (e.g., doxacurium chloride to doxacurium) using the RxNorm API.
We eliminated from the comparison those pairs for which at least one of the drugs could not be found in RxNorm. For example, the DrugBank drug cerivastatin, which was withdrawn from the U.S. market in 2001, is not present in RxNorm.
Comparing interactions across sources
Having normalized all drugs to RxNorm ingredients, we compared the lists from DDIs of NDF-RT and DrugBank in order to determine the similarities and unique features of each source. In addition, we compared each with the reference set of DDIs to determine how many of the reference DDIs each source covered.
To determine if there was a pattern of missing interactions, we abstracted the pairs of interacting drugs into pairs of classes from the Anatomical Therapeutic Chemical (ATC) Classification System. We mapped the drugs directly to their 4th-level ATC classes using the RxNorm API and identified those pairs of ATC classes for which the proportion of DDIs in common between NDF-RT and DrugBank was low, using the Jaccard score. Of note, some NDF-RT and DrugBank drugs are not represented in ATC. So only DDIs for which both the object and precipitant drugs are present in ATC were analysed.
Comparing coverage of interactions from actual prescription data
In order to assess the difference between NDF-RT and DrugBank interactions based on usage data, we collected drug pairs generated from actual patient prescription lists. Checking medication lists for drug-drug interactions represents a practical use case and is offered as a service by many medication list applications. It also provides some frequency of usage of the co-prescribed drug pairs extracted from the lists. The data was acquired from Symphony Health Solutions (http://symphonyhealth.com/). It included one year of prescription data from the Washington, D.C. area from July 1, 2011 through June 30, 2012. Prescription information included prescriber, de-identified patient information, and specific medication information, including the drug name and strength. The drug information was mapped into RxNorm clinical drugs. From a list of co-prescribed drugs, we generated all possible pairwise combinations within the drug list (ignoring the order of drugs in the pair, since the distinction between object and precipitant drugs is not required for DDI testing). We ignored topical drugs from the prescription list, because DDI information represented at the ingredient level in NDF-RT and DrugBank usually refers to interactions between systemic drugs. For example, we generated the following pair of RxNorm clinical drug, 24 HR Diltiazem Hydrocloride 360 MG Extended Release Oral Capsule (830795) and Lovastatin 20 MG Oral Tablet (197904). We mapped the clinical drugs to their active moieties in RxNorm (Diltiazem Hydrocloride and Lovastatin, respectively) and further normalized those to RxNorm ingredients, as we did with all object and precipitant drugs from the various DDI lists. Here, we normalized Diltiazem Hydrocloride to Diltiazem. In summary, we transformed the pair of RxNorm clinical drugs extracted from the prescription list into the pair of RxNorm ingredients (Diltiazem, Lovastatin) for comparison to the DDIs in NDF-RT and DrugBank.
Publicly available vs. commercial DDI sources
To compare the coverage of the reference set by DrugBank and NDF-RT to that of a commercial source, we investigated the Multum drug knowledge base through the interaction checker of the website Drugs.com (http://www.drugs.com/), against which we tested the 360 DDIs of the reference set.
DDI information in NDF-RT, DrugBank and the reference set
DDI counts in the three datasets
Total from source
Mapped to RxNorm
The reference set contained 360 DDIs; all the drugs mapped to RxNorm and were all classified as ingredients. The 360 DDIs covered 86 RxNorm ingredients.
DrugBank contained 12,128 DDIs defined in the XML file. DDIs involving drugs with no mapping to RxNorm were discarded (418 DDIs involving 46 drugs). Analysis of all the discarded DDIs revealed several reasons why the DDIs were eliminated. Some DDIs involved drugs that were either withdrawn from public use (e.g., cerivastatin, ephedra, heptabarbital) or not approved by the U.S. Food and Drug Adminstration (e.g., cinolazepam, carbetocin) and those drugs could not be mapped to RxNorm. Additionally, 518 DrugBank DDIs were eliminated through the ingredient normalization process. For example, the DDIs containing zuclopenthixol, zuclopenthixol acetate and zuclopenthixol deconoate were normalized to produce a single set with zuclopenthixol as the ingredient, eliminating the redundant pairs containing the salt forms. The resulting 11,552 normalized DDIs covered 1153 RxNorm ingredients.
NDF-RT contained 10,831 DDIs extracted from the data set. DDIs involving drugs with no mapping to RxNorm were discarded (1379 DDIs involving 38 drugs). Analysis of all the discarded DDIs revealed that some DDIs were associated with drugs which referenced obsolete RxNorm concepts, many of these vaccine drugs that were recently removed from RxNorm. Additionally, 60 NDF-RT DDIs were eliminated through the ingredient normalization process. The resulting 9,392 normalized DDIs covered 1079 RxNorm ingredients.
In the remainder of this paper, DDIs refer to pairs of object and precipitant drugs normalized to RxNorm ingredients. However, even after normalization to RxNorm ingredients, the coverage of drugs is not expected to be the same in NDF-RT and DrugBank. For example, vaccines and other biologicals are present in NDF-RT, but out of scope for DrugBank. When analysing DDIs across the two sources, breakdown by pharmacological classes will reflect such differences in drug coverage.
Comparing interactions across sources
Matching DDIs across data sets
Number of matching DDIs
Overlap between DrugBank and NDF-RT
Overall, the 2801 DDIs common to NDF-RT and DrugBank represent a 30% coverage rate of NDF-RT by DrugBank and a 24% coverage rate of DrugBank by NDF-RT. Example of common DDIs include diltiazem/lovastatin and itraconazole/sirolimus. Examples of DDIs in DrugBank only include acebutolol/Insulin Lispro and metronidazole/terfenadine. Examples of DDIs in NDF-RT only include amiodarone/sotalol and meperidine/linezolid.
When we only consider DDIs from the reference set, the overlap between DrugBank and NDF-RT is significantly higher. The 146 reference DDIs common to NDF-RT and DrugBank represent 71% of the 207 reference DDIs covered by NDF-RT and 69% of the 211 reference DDIs covered by DrugBank.
Reference set coverage
Reference Set DDI and coverage in NDF-RT and DrugBank
DDI group description
Amphetamine and derivatives – MAO inhibitors
Dexmethylphenidate, Dextroamphetamine, Methylphenidate, Lisdexamfetamine, Phendimetrazine, Pseudoephedrine, Amphetamine, Benzphetamine, Diethylproprion, Phentermine, Atomoxetine, Methamphetamine
Tranylcypromine, Phenelzine, Isocarboxazid, Procarbazine, Selegiline
Atazanavir – Proton pump inhibitors (PPIs)
Omeprazole, Lansoprazole, Pantoprazole, Rabeprazole, Esmoprazole
Fluoxetine - MOA inhibitors
Fluoxetine, Paroxetine, Citalopram, Escitalopram, Sertraline, Fluvoxamine, Duloxetine, Nefazodone, Desvenlafaxine, Milnacipran, Venlafaxine
Tranylcypromine, Phenelzine, Isocarboxazid, Procarbazine, Selegiline
Irinotecan – Ketoconazole
Ritonavir, Nelfinavir, Atazanavir, Indinavir, Saquinavir, Amprenavir, Darunavir, Lopinavir, Tipranavir, Fosamprenavir, Clarithromycin, Erythromycin, Telithromycin, Amiodarone, Verapamil, Diltiazem, Ketoconazole, Itraconazole, Fluconazole, Voriconazole, Nefazodone, Aprepitant, Cimetidine
Narcotic analgesics – MAO inhibitors
Meperidine, Methadone, Tapentadol, Fentanyl, Tramadol, Dextromethorphan
Tranylcypromine, Phenelzine, Isocarboxazid, Procarbazine, Selegiline
Fluvoxamine, Amiodarone, Ticlopidine, Ciprofloxacin
Rifampin – ritonavir
Bosentan, Rifapentine, Carbamazepine, Rifabutin, Rifampin, St. John’s wort
Ritonavir, Nelfinavir, Atazanavir, Indinavir, Saquinavir, Amprenavir, Darunavir, Lopinavir, Tipranavir, Fosamprenavir
HMG Co-A reductase inhibitors – protease inhibitors
Ritonavir, Nelfinavir, Atazanavir, Indinavir, Saquinavir, Amprenavir, Darunavir, Lopinavir, Tipranavir, Clarithromycin, Erythromycin, Telithromycin, Amiodarone, Verapamil, Diltiazem, Tranylcypromine, Phenelzine, Isocarboxazid, Procarbazine, Selegiline
Telithromycin – ergot alkaloids and derivatives
Ritonavir, Nelfinavir, Atazanavir, Indinavir, Saquinavir, Amprenavir, Darunavir, Lopinavir, Tipranavir, Clarithromycin, Erythromycin, Telithromycin, Ketoconazole, Itraconazole, Voriconazole
Ergotamine, Methylergonovine, Dihydroergotamine, Ergonovine
Tizanidine – ciprofloxacin
Fluvoxamine, Amiodarone, Ticlopidine, Ciprofloxacin, Mexiletine, Propafenone, Zileuton
Tranylcypromine – procarbazine
Triptans – MAO inhibitors
Sumatriptan, Zolmitriptan, Rizatriptan
Tranylcypromine, Phenelzine, Isocarboxazid, Moclobamide, Methylene blue
Of the 86 drugs contained in the reference set, one (moclobamide, involved in 3 DDIs) did not exist in NDF-RT and two (dexmethylphenidate, involved in 5 DDIs and methylene blue, involved in 3 DDIs) did not exist in DrugBank. In addition, there were four other drugs (bosentan, lopinavir, methadone and zileuton) which were present in DrugBank, but not involved in any of the DDIs from the reference set. DrugBank did have DDIs for these four drugs outside of the reference set.
We mapped the DDIs from NDF-RT and DrugBank to 4th-level ATC drug classes to see if there were distinctive class differences between the two sets of DDIs. A small proportion of the drugs, such as avanafil, lopinavir and zileuton (14% in NDF-RT, 11% in DrugBank) were not represented in ATC and the corresponding DDIs were excluded from the analysis.
Top ATC Class Counts in NDF-RT and DrugBank
ATC Class Name
Non-selective monoamine reuptake inhibitors
Protein kinase inhibitors
Selective serotonin reuptake inhibitors
Vitamin K antagonists
Top ATC Class Pairs
ATC Class Pair
Protease inhibitors - Protein kinase inhibitors
Benzodiazepine derivatives - Protease inhibitors
Adrenergic and dopaminergic agents - Non-selective monoamine reuptake inhibitors
Antibiotics - Other quaternary ammonium compounds
Penicillins with extended spectrum - Tetracyclines
Protein kinase inhibitors - Triazole derivatives
Beta blocking agents, non-selective - Sulfonamides, urea derivatives
Macrolides - Protein kinase inhibitors
Comparing coverage of interactions from actual prescription data
Top DDI Pairs found in Prescription Data
Publicly available vs. commercial DDI sources
We were able to match 328 (91%) DDIs of the reference set to Multum DDIs, a significantly higher proportion compared to NDF-RT and DrugBank. The level of severity provided by Multum for these DDIs (on a 3-level scale mild, moderate or major) was consistent with the notion of “high-severity” claimed by the authors of the reference set, since 302 DDIs were rated major and the other 26 were rated moderate.
In this section, we discuss some of the reasons for the limited overlap of DDI information among sources. We also analyse its implications for our interactions API.
Limited overlap between NDF-RT and DrugBank DDIs
One important finding of this investigation is the limited overlap (<30%) between DrugBank and NDF-RT DDIs, although both sources cover roughly the same number of DDIs. We found 6591 DDIs specific to NDF-RT and 8751 specific to DrugBank, while only 2801 DDIs were common to both sources. Differences in scope (e.g., the lack of vaccine DDIs in DrugBank) account for only a small portion of the differences. Differential coverage persisted after abstracting DDIs to the corresponding drug classes from ATC. For example, NDF-RT had many more DDIs than DrugBank for Protease inhibitor drugs, and had much fewer DDIs for Anticholinesterases drugs. Likewise, many ATC class pairs had a small proportion of DDIs in common, evidenced by low Jaccard scores. For example, among the 56 DDIs for the Macrolides - Protein kinase inhibitors class pair, only 15 are common to NDF-RT and DrugBank (Jaccard = 0.27). The low overlap rate also applied to our more frequently prescribed drug pairs in the prescription data set. When we examined the co-prescribed drugs from the prescription data set, we found significant differences in identification of DDIs between the two sources for the most frequently co-prescribed pairs. Of the top 10 most frequently prescribed drug pairs identified as potential DDIs by DrugBank, only 5 were recognized as NDF-RT DDIs (see Table 6 for details).
We wondered if the differential coverage observed between NDF-RT and DrugBank could be due in part to different editorial guidelines for curating less severe DDIs, assuming the most severe DDIs would be covered more consistently by both sources. This did not seem to be the case since the 360 high-severity DDIs from the reference set are only partially covered by NDF-RT and DrugBank. While NDF-RT provides an indication of severity (critical or significant) for its DDIs, DrugBank does not. Nevertheless, we tested if DrugBank would cover a larger proportion of NDF-RT critical DDIs. In fact, DrugBank DDIs accounted for 31% of the total critical DDIs in NDF-RT and for 29% of the total significant DDIs. In other words, there is no difference in the coverage of NDF-RT by DrugBank in terms of DDI severity. (Even when correcting for the absence of vaccine DDIs in DrugBank, the overlapping DDIs accounted for just 40% of the critical DDIs in NDF-RT.)
Differential coverage of DDIs among sources
Our finding of limited overlap between NDF-RT and DrugBank should not be surprising given similar findings in studies comparing drug knowledge bases for critically important DDIs . There is no standardization for what constitutes a drug-drug interaction, and DDI curators have to consider a variety of drug and patient specific factors in their decision to include pairs of drugs in their DDI lists. These factors include the severity of the interaction, the probability of the interaction, patient characteristics (e.g., specific patient groups, such as elderly patients), and evidence supporting the interaction (quantity of evidence, as well as the quality of the evidence). The number of factors to consider makes this a complex and daunting task. Moreover, the maintenance of DDI lists itself is an issue, as additional evidence for or against DDIs becomes available over time. Finally, different strategies for prioritizing the various factors also accounts for some of the differences observed across sources.
Implications for the interactions API
Overall, our investigation of NDF-RT and DrugBank as sources of DDIs for our API provides a mixed picture. Not only do they both provide incomplete coverage of the reference set (about 60% each), but their overlap is also limited (42%). A similar difference could be observed when we simulated interaction detection based on actual usage data. We also confirmed that a commercial source, Multum, provided a more systematic coverage of the reference set.
With the provision of DDI information being discontinued in NDF-RT in November 2014, we decided to use DrugBank as a replacement for our interactions API. This solution is far from ideal, because this investigation did not establish the accuracy of either source, but simply assessed differences among them. On the other hand, DDI determination is not an exact science and both NDF-RT and DrugBank provide valuable information to support medical decision. NDF-RT DDIs are associated with levels of severity, while DrugBank’s come with a short description. In practice, the absence of severity levels in DrugBank is a disadvantage, as severity is an important consideration for determining when to alert physicians to a potential DDI. Severity is also a requirement when checking DDI in the context of the Meaningful Use incentive program.
It is important to keep in mind that no clinical decision system, as good as it is, can be a substitute for medical advice. Our API not only clearly discloses the origin of the information it provides, but also reminds our users to seek advice from health professionals before making decisions about their medications. In the future, we plan to perform a more systematic and qualitative investigation of publicly available and commercial DDI sources in order to better assess the differences among these sources.
This study is the first comparative investigation of DDI information in two publicly available sources, NDF-RT and DrugBank. We compared the two sources not only to themselves, but also to a reference set of DDIs, and assessed their ability to identify DDIs in a large prescription dataset. We also contrasted NDF-RT and DrugBank against the commercial source Multum.
This investigation confirms the limited overlap between DDI information between NDF-RT and DrugBank, even for the reference dataset. Additional research is required to determine which source is better, if any. Usage of any of these sources in clinical decision systems should clearly disclose these limitations.
This work was supported by the Intramural Research Program of the NIH, National Library of Medicine.
- Abramson EL, Malhotra S, Osorio SN, Edwards A, Cheriff A, Cole C, et al. A long-term follow-up evaluation of electronic health record prescribing safety. J Am Med Inform Assoc. 2013;20(e1):e52–8.View ArticleGoogle Scholar
- Kaushal R, Kern LM, Barron Y, Quaresimo J, Abramson EL. Electronic prescribing improves medication safety in community-based office practices. J Gen Intern Med. 2010;25(6):530–6.View ArticleGoogle Scholar
- Agu KA, Oqua D, Adeyanju Z, Isah MA, Adesina A, Ohiaeri SI, et al. The incidence and types of medication errors in patients receiving antiretroviral therapy in resource-constrained settings. PLoS One. 2014;9(1), e87338.View ArticleGoogle Scholar
- McDonnell PJ, Jacobs MR. Hospital admissions resulting from preventable adverse drug reactions. Ann Pharmacother. 2002;36(9):1331–6.View ArticleGoogle Scholar
- Buck MD. Retrospective monitoring of drug-drug interactions using a CPOE alerting knowledgebase. AMIA Annu Symp Proc. 2007;80–4Google Scholar
- Curtain C, Peterson GM. Review of computerized clinical decision support in community pharmacy. J Clin Pharm Ther. 2014;39(4):343–8.View ArticleGoogle Scholar
- Classen DC, Phansalkar S, Bates DW. Critical drug-drug interactions for use in electronic health records systems with computerized physician order entry: review of leading approaches. J Patient Saf. 2011;7(2):61–5.View ArticleGoogle Scholar
- NDF-RT Release Notes, July 2014, http://evs.nci.nih.gov/ftp1/NDF-RT/ReadMe.txt.
- Phansalkar S, Desai AA, Bell D, Yoshida E, Doole J, Czochanski M, et al. High-priority drug-drug interactions for use in electronic health records. J Am Med Inform Assoc. 2012;19(5):735–43.View ArticleGoogle Scholar
- Brown SH, Elkin PL, Rosenbloom ST, Husser C, Bauer BA, Lincoln MJ, et al. VA National Drug File Reference Terminology: a cross-institutional content coverage study. Stud Health Technol Inform. 2004;107(Pt 1):477–81.Google Scholar
- NLM. NDR-RT API, 2011; http://rxnav.nlm.nih.gov/NdfrtAPIs.html
- Law V, Knox C, Djoumbou Y, Jewison T, Guo AC, Liu Y, et al. DrugBank 4.0: shedding new light on drug metabolism. Nucleic Acids Res. 2014;42:D1091–7.View ArticleGoogle Scholar
- Nelson SJ, Zeng K, Kilbourne J, Powell T, Moore R. Normalized names for clinical drugs: RxNorm at 6 years. J Am Med Inform Assoc. 2011;18(4):441–8.View ArticleGoogle Scholar
- NLM. RxNorm API 2011; rxnav.nlm.nih.gov/RxNormAPIs.html
- Segura-Bedmar I, Martinez P, de Pablo-Sanchez C. Using a shallow linguistic kernel for drug-drug interaction extraction. J Biomed Inform. 2011;44(5):789–804.View ArticleGoogle Scholar
- He L, Yang Z, Zhao Z, Lin H, Li Y. Extracting drug-drug interaction from the biomedical literature using a stacked generalization-based approach. PLoS One. 2013;8(6), e65814.View ArticleGoogle Scholar
- Segura-Bedmar I, Martinez P, Herrero-Zazo M. SemEval-2013 Task 9: Extraction of Drug-Drug Interactions from Biomedical Texts (DDIExtraction 2013). In: Proceedings of the 7th International Workshop on Semantic Evaluation (SemEval 2013).Google Scholar
- Segura-Bedmar I, Martinez P, Herrero-Zazo M. Lessons learnt from the DDIExtraction-2013 Shared Task. J Biomed Inform. 2014;51:152–64.View ArticleGoogle Scholar
- Tatonetti NP, Ye PP, Daneshjou R, Altman RB. Data-driven prediction of drug effects and interactions. Sci Transl Med. 2012;4(125):125ra131.Google Scholar
- Smithburger PL, Buckley MS, Bejian S, Burenheide K, Kane-Gill SL. A critical evaluation of clinical decision support for the detection of drug-drug interactions. Expert Opin Drug Saf. 2011;10(6):871–82.View ArticleGoogle Scholar
- Phansalkar S, Desai A, Choksi A, Yoshida E, Doole J, Czochanski M, et al. Criteria for assessing high-priority drug-drug interactions for clinical decision support in electronic health records. BMC Med Inform Decis Mak. 2013;13(1):65.View ArticleGoogle Scholar
- Phansalkar S, van der Sijs H, Tucker AD, Desai AA, Bell DS, Teich JM, et al. Drug-drug interactions that should be non-interruptive in order to reduce alert fatigue in electronic health records. J Am Med Inform Assoc. 2013;20(3):489–93.View ArticleGoogle Scholar
This is an Open Access article distributed under the terms of the Creative Commons Attribution License (http://creativecommons.org/licenses/by/4.0), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly credited. The Creative Commons Public Domain Dedication waiver (http://creativecommons.org/publicdomain/zero/1.0/) applies to the data made available in this article, unless otherwise stated.