Toward a comprehensive drug ontology: extraction of drug-indication relations from diverse information sources
© The Author(s). 2017
Received: 14 July 2015
Accepted: 16 December 2016
Published: 10 January 2017
Drug ontologies could help pharmaceutical researchers overcome information overload and speed the pace of drug discovery, thus benefiting the industry and patients alike. Drug-disease relations, specifically drug-indication relations, are a prime candidate for representation in ontologies. There is a wealth of available drug-indication information, but structuring and integrating it is challenging.
We created a drug-indication database (DID) of data from 12 openly available, commercially available, and proprietary information sources, integrated by terminological normalization to UMLS and other authorities. Across sources, there are 29,964 unique raw drug/chemical names, 10,938 unique raw indication ”target” terms, and 192,008 unique raw drug-indication pairs. Drug/chemical name normalization to CAS numbers or UMLS concepts reduced the unique name count to 91 or 85% of the raw count, respectively, 84% if combined. Indication ”target” normalization to UMLS ”phenotypic-type” concepts reduced the unique term count to 57% of the raw count. The 12 sources of raw data varied widely in coverage (numbers of unique drug/chemical and indication concepts and relations) generally consistent with the idiosyncrasies of each source, but had strikingly little overlap, suggesting that we successfully achieved source/raw data diversity.
The DID is a database of structured drug-indication relations intended to facilitate building practical, comprehensive, integrated drug ontologies. The DID itself is not an ontology, but could be converted to one more easily than the contributing raw data. Our methodology could be adapted to the creation of other structured drug-disease databases such as for contraindications, precautions, warnings, and side effects.
KeywordsDrug indications Drug-disease relations Drug ontologies Drug information integration UMLS WHO-ATC
Biomedical information overload and the potential of formal ontologies to help overcome it are well recognized [1–3]. Information overload is but one threat to the viability of the traditional pharmaceutical industry. Others include the rising costs of laboratory research, clinical trials, litigation over anomalous harmful side effects, and increasing times to market . The success of the Gene Ontology (GO) as an in silico molecular biology research tool  suggests that drug ontologies could have a similar impact on drug research. The advance of practical ontologies into the pharmaceutical domain has been much anticipated [6–8], and is becoming evident [9, 10].
Pioneering reports on ontology-based, in silico drug discovery have emerged [11–13]. The basic goal is ontology-assisted inference of surprising and/or more-likely-to-succeed new drug candidate compounds for known uses, thus cutting costs and time to market. Drug ontology-assisted inference could also be applied to finding new uses for known compounds (drug repurposing) , or “personalized” genome-dependent safety/efficacy profiling (pharmacogenomics) [15–18]. These ontologies include drug relations to chemically similar compounds, diseases (therapeutic classifications, indications, side effects), and biological pathways (mechanisms of action, molecular target proteins or their genes, secondary disease-gene and protein-protein interactions). In principle, such ontologies could be expanded to encompass many more dimensions of drug information [19, 20]; that is, they can be made more comprehensive.
For further progress in building comprehensive drug ontologies, rich and well-structured knowledge (content) about biological pathways and chemically similar compounds is readily available from resources such as GO, GenBank , DrugBank , PubChem , and ChemIDplus . Rich drug-disease knowledge also is readily available, but usually as unstructured (“free”) text; e.g., DailyMed . Thus the well-structured but relatively shallow WHO-ATC drug classification  has been utilized as a source for drug-disease knowledge [12, 13].
It is important to distinguish between diseases, indications, contraindications, side effects, and other such dimensions of drug information. A drug indication can be a disease1 that the drug is “used for” (i.e., to treat, prevent, manage, diagnose, etc.). An important subset are approved indications which have been through a formal, country-specific regulatory vetting process. But drugs can also be indicated for medical conditions which may not be considered diseases, such as pregnancy. Drugs can also be indicated for procedures, such as contrast media for radiology. In ontological terms, medical conditions (of which diseases are a subclass) and medical procedures constitute the range of drug indications. They also constitute the range of very different, even orthogonal, drug relations such as contraindications, precautions, and warnings. The range for side effects, on the other hand, is arguably limited to diseases. Thus it is important to specify which of these relations is being addressed. This paper addresses indications, but much of it is extensible to other drug-disease relations.
We created a drug-indication database (DID) using content from openly available, commercially available, and Merck proprietary information resources. To integrate the data, we attempted to identify distinct “triples” of a drug, indication, and indication subtype (treat, prevent, manage, diagnose, etc.), and then normalize each component to a standard terminology or code. The raw data varied widely in format, from well-structured, vocabulary-controlled triples to hierarchical classifications to free text. While the DID itself is not an ontology, it could be converted to one more easily than the contributing raw data.
Raw data on drug/chemical-indication relations were collected from the following resources.
DailyMed  is a free drug information resource provided by the U.S. National Library of Medicine (NLM) that consists of digitized versions of drug labels (also called “package inserts”) as submitted to the U.S. Food and Drug Administration (FDA). The information format of the labels is mostly free text but with standard section headings, including “Indications & Usage.” DailyMed was of special interest because of its comprehensive coverage, open availability, and the package inserts’ combination of format consistency, rich detail, and provenance (manufacturer-written, scientifically vetted, and FDA-approved).
DrugBank  “is a unique bioinformatics and cheminformatics resource that combines detailed drug (i.e. chemical, pharmacological and pharmaceutical) data with comprehensive drug target (i.e. sequence, structure, and pathway) information” provided by the University of Alberta. Many records include an explicit Indication field populated with free text values, and leveraging these was of special interest due to DrugBank’s rich coverage of molecular target information.
MeSH (Medical Subject Headings)  is NLM’s controlled vocabulary used to index Medline/Pubmed  articles by scientific topics including drugs, chemicals, diseases, and other biomedical conditions, processes, and procedures. MeSH has ontology-like hierarchical and other relationships between concepts, but it does not consistently link drugs to diseases/conditions/processes explicitly (e.g., “Aspirin” to “Fever”). It does, however, have a special Pharmacological Action (PA) relationship which links drugs and other chemicals to therapeutic classes (e.g., “Aspirin” to “Antipyretics”) which could be mapped to diseases/conditions/processes (e.g., “Antipyretics” to “Fever”).
NDFRT (National Drug File Reference Terminology)  is produced by the U.S. Veterans Health Administration and is openly available from several resources including NLM’s UMLS (Unified Medical Language System) . Like MeSH PA, NDFRT consists of controlled vocabulary terms connected by specific relationship names, five of which could be considered pointers to indications or PA’s: may_treat, may_prevent, may_diagnose, has_mechanism_of_action, has_physiological_effect.
PDR (Physicians’ Desk Reference) is “a commercially published compilation of manufacturers’ prescribing information (package insert) on prescription drugs, updated annually.”  Its long history (65 editions) and ubiquitous hardcopy availability give PDR a certain provenance. “Section 3 - Product Category Index” classifies drugs (trade names) by disease (e.g., “ALCOHOL DEPENDENCE”) and/or PA (e.g., “ANALGESICS”).
ChEBI (Chemical Entities of Biological Interest)  consists of a database and ontology supplied by the European Bioinformatics Institute. The has_role relationship of the ontology connects drugs and chemicals to functions, including PAs (e.g., “antibacterial drug”; “anti-ulcer drug”; “proton pump inhibitor”).
CTD (Comparative Toxicogenomics Database) [33, 34] is supplied by North Carolina State University and Mount Desert Island Biological Laboratory, Salisbury Cove, Maine. The Chemical-Disease Associations file consists of pairs of MeSH terms connected by the relationships therapeutic and/or marker/mechanism and annotated by evidence type; we used the “direct evidence” subset.
WHO-ATC (World Health Organization Anatomic-Therapeutic-Chemical) is a five-level drug classification hierarchy specifying (typically, from top to bottom) the anatomical system acted upon, therapeutic action, and chemical nature of the drug. The hierarchy can convey multiple indications/PAs for a given drug. WHO-ATC is widely accepted as a standard for drug classification, including in the Merck eVOC system. We obtained WHO-ATC data from two WHO datasets purchased by Merck and additional mappings in eVOC; these are referred to as WHO_ATC , WHO_DD , evoc_ATC, and evoc_eProj in the rest of this document. (All evoc_eProj and some evoc_ATC data represent Merck proprietary information and therefore have been removed from the attached DID subset, Additional file 1.)
Parsing and filtering
Source contributions of drug-indication data
source name or description
subset if any
number of drug-indication pairs
Chemicals of Biological Interest Ontology
104/June 1, 2013
Comparative Toxicogenomics Database
Chemicals-Diseases Associations,“direct evidence” subset
May 2, 2014
NLM’s database of FDA package inserts
single component title (product name) & Indications sections with tractable text length (<540)
March 20, 2011
U. Alberta open access DB of drug target and other info
title (drug name) & Indications sections
Medical Subject Headings Pharmacologic Action relations
2013/Dec. 3, 2012
National Drug Formulary Reference Terminology
may_treat & may_prevent relations
Physicians’ Desk Reference
Section 3 - Product Category Index
United States Adopted Names Therapeutic Claims
March 31, 2014 (eVOC)
World Health Organization Anatomic-Therapeutic-Chemical, Defined Daily Dose index
World Health Organization Drug Dictionary
single generic compounds with ATC codes (minus 2005 WHO-ATC overlap and herbals BNA = “9…”)
WHO-ATC codes in Merck’s eVOC generic names dictionary
single generic compounds with ATC codes (minus WHO-ATC & WHO-DD overlap)
May 6, 2014
Filtering is not qualitatively different from initial subsetting (Table 1, column 3). For example, ChEBI’s, CTD’s, and MeSH PA’s relatively large initial contributions can be attributed to their higher coverage of non-drug chemicals and non-therapeutic quasi-indications (e.g., “Carcinogens”; “Mutagens”). These could be considered irrelevant to pharmacy/prescription applications of the DID, but were left in for drug discovery applications. ChEBI’s contribution was reduced 48% by filtering out irrelevant (non-indication) has_role objects (e.g., “metabolite”; “prodrug”; “epitope”), but CTD’s “marker/mechanism” subset (63%) was not removed due to its potential use in future analysis. DailyMed’s filtering reduction was even larger but aimed at very different targets: combination products (20%), intractably long (>539 characters) “Indication & Usage” texts (37%), and redundant “Indication & Usage” values paired with the same drug generic name differing only by dosage, formulation, trade name, or supplier (33%). NDFRT’s (90%) and PDR’s (62%) filtering reductions were also due primarily to conflating various forms (trade names, in PDR’s case) of the same generic name.2
Initial counts from the WHO-ATC resources are based on viewing each level of the WHO-ATC hierarchy as a separate indication, rather than combining them into a single raw term. Filtering resulted in reductions of 52% (WHO_ATC), 47% (WHO_DD), and 75% (evoc_ATC) reflecting removal of combination and ill-formed drug names, and non-indication and redundant classification terms (e.g., “Antithrombotic Agents” at nested hierarchical levels [B01 and B01A]).
It must be emphasized that the parsing, filtering, and normalizing (see below) done in this work employed a wide variety of ad hoc methods and manual curation commensurate with the raw data/source diversity.
Normalizing drug names
Various types of drug identifiers are exemplified in Fig. 1, including a generic name (in this case a USAN, “aftobetin hydrochloride”), chemical names, a structural formula, sponsor code designations, and a CAS (Chemical Abstracts Service) Registry Number. Other types not shown in Fig. 1 include trade names (e.g., “Tylenol” corresponding to the generic name “acetaminophen”), FDA’s UNII (Unique Ingredient Identifier; e.g., “A1FCZ940WA” for “aftobetin hydrochloride”), and InChI (International Chemical Identifier) Key (e.g., “GMWHTUNMFTUKHH-NDUABGMUSA-N” for “aftobetin hydrochloride”) . The equivalence of such terms for the exact same chemical entity can sometimes be debated due to details such as isomerism, salt forms, hydration, formulation, and dosage, but they are commonly considered synonyms, with the generic name as the preferred term (PT).
Thus, to parse out the drug identifier in each raw drug-indication record, we looked for source database fields or elements containing these types of terms, and attempted to normalize them to generic names using the sources’ own and/or other synonym dictionaries. These dictionaries included those available from ChemIDplus, ChEBI, CTD, DrugBank, UMLS, and Merck’s eVOC. In addition, to resolve conflicts among these dictionaries, we attempted to derive a “preferred PT” via CAS number mapping and ranking the dictionaries in the order ChemIDplus > ChEBI > DrugBank > eVOC > CTD. For example, in ChemIDplus the PT for CAS number 103-90-2 is “acetaminophen” but in ChEBI it is “paracetamol.” Thus the DID enables ChEBI drug-indication data for “paracetamol” to be grouped with other sources’ drug-indication data for “acetaminophen.” UMLS is not a rich source of CAS numbers, but supplies an equally language-neutral “CUI” (Concept Unique Identifier).
Raw entire value/string (column AQ): the raw source’s term/text, including entire DailyMed “Indications & Usage” sections converted to single-line sentences.
Raw target/substring (column AR): a term/phrase within or based on the entire value/string, denoting a distinct indication concept. If the target/substring is the same as the entire value/string, it is flagged with “Y” in column AS.
UMLS entry term (column AU) that best matches the target/substring and conforms to our semantic type preference for phenotypes (diseases and other biological conditions, processes, and functions; see below). UMLS mapping was done using ad hoc perl scripts designed to work with UMLS flat files (2013AA version), MetaMap , and/or NLM’s online UMLS browser . Each UMLS entry term is tagged for whether it is preferred (“P”) or a non-preferred synonym (“S”) (column AX). For readability in the DID, all “P” terms were converted to proper case and all “S” terms were converted to lower case using Excel string functions.
UMLS preferred term (column AV) and corresponding CUI (column AW) were computed from UMLS 2013AA flat files to unify all encoding at this level, even if raw values consisted of UMLS terms or CUIs (MeSH PA and NDFRT), except for mappings only available in more recent UMLS versions via NLM’s online browser.
Indication semantic types
For UMLS encoding of indication concepts, we had a preference for UMLS concept terms classified under UMLS semantic types signifying phenotypes (diseases and other biological conditions, processes, and functions). The goal of this was to reduce encoding scatter. For example, the raw term “antibacterial agent” exactly matches a UMLS synonym under “Anti-Bacterial Agents” (CUI C0279516) classified under semantic type “Antibiotic” (A126.96.36.199.1.1). But calling a drug an “antibacterial agent” is equivalent to saying that its indication is “Bacterial Infections” (C0004623, classified under “Disease or Syndrome” B188.8.131.52.1). By mapping “Anti-Bacterial Agents”/C0279516 to “Bacterial Infections”/C0004623, raw data that encode to either are unified. This is tantamount to trading lexical match precision for increased terminological reduction (explained below).
In the DID and Additional file 1, initial indication mappings to non-phenotypic semantic type UMLS terms are encoded in columns BD-BL with their remapping to phenotypic type CUIs in AT-BC. If the initial non-phenotypic type mapping could not be mapped to a phenotypic type CUI, it is encoded in AT-BC. For example, “Cephalosporins” (a WHO-ATC category, among other instances) maps to C2266959/Antibiotic/A184.108.40.206.1.1, but is “stuck” there because UMLS had no phenotypic type term such as “cephalosporin activity”; “cephalosporin effect”; or “cephalosporin-sensitive infection.”
In prior work [19, 20] we observed that drug indications are often classified or annotated by subtypes such as approved vs. non-approved, or treatment vs. prevention. The current work’s expanded raw data scope brought to light additional types with lexical cues such as therapeutic/pharmacologic class prefixes (“Antidiabetic”), suffixes (“Anxiolytic”), and head nouns (“beta-adrenergic agonist”; “Lipoprotein Lipase Activators”; “smoking cessation adjunct”). Some of these distinctions are likely to be even more substantial than treatment vs. prevention; e.g., “Antineoplastics” and “Carcinogens” both map to “cancer” but in opposite ways, one inhibitory or negative, the other causative or positive. This suggests an indication subtype hierarchy representing a gradient of granularity with raw terms like “treatment” and “prevention” at the bottom/leaf level and “negative” and “positive” at the top. In between would be lexical root forms such as “treat” representing “treats”; “treating”; “treatment”; etc. If so encoded in the DID, users could select the most appropriate indication subtypes and level of granularity for their use case. We identified indication subtypes based on Excel string searches (“treat”; “anti”; “inhibit”; etc.) in the raw entire value/string (column AQ).
The inherent value of terminological normalization is the core principle of controlled vocabularies that have been used to organize, search, and represent information for over a century . To measure the success of our terminological normalization efforts, we defined terminological reduction (TR) as TR = (N + X)/U, where N = number of unique normalized names, X = number of unique raw names which remain unnormalized, and U = number of unique original raw names.
The Merck in-house version of the DID (January 2015 release) contains 198,415 rows of data representing unique quadruplets of source, raw drug/chemical name, raw indication “target” term, and indication UMLS CUI. Across sources, there are 29,964 unique raw drug/chemical names, 10,938 raw indication target terms, and 192,008 unique raw drug/indication pairs. Additional file 1 is a copy of this spreadsheet minus 5,557 rows (3%) containing Merck proprietary information. Therefore reproducing these counts and the following analyses on Additional file 1 would yield slightly different quantitative results, but not substantially alter our qualitative conclusions. Additional file 1’s “schema” worksheet shows the DID schema and two example records.
Drug name normalization
Drug name mapping to CAS numbers is encoded in DID columns E-H. CAS numbers were assigned to 87% of the DID rows and 71% of the unique raw drug names, providing TR of the unique names to 91%. The preferred authority ChemIDplus alone covered 84% of the rows and 68% of the unique raw drug names. Almost all (98%) of these CAS number mappings are based on exact (case-insensitive) matches to the ChemIDplus’ or other standard’s PT for that CAS number, or to a source-specified synonym (“<syn per source>”). The synonym matches were manually curated and obvious broader term (BT) and narrower term (NT) matches were reclassified as such. For BT and NT matches the directionality is raw-to-standard; e.g., raw “arformoterol fumarate” is a NT (a salt, derivative, analog, or formulation of) the closest ChemIDplus term which has a CAS number, “Arformoterol”. Also distinguished are quasi-synonym matches such as “cidofovir anhydrous”: “Cidofovir”. The intent is to offer users multiple match quality levels as options for filtering. The individual drug name mappings to ChEBI, ChemIDplus, and CTD are encoded in DID columns I-AC.
Drug name mapping to UMLS is encoded in DID columns AD-AM. UMLS CUI mapping, compared to CAS number mapping, produced superior coverage of DID rows (96% vs. 87%) and unique raw DB drug names (89% vs. 71%), and superior TR (85% vs 91%). The difference is at least partly due to the higher numbers of synonym and narrower UMLS matches, which may be an artefact of unequal curation effort or UMLS’ coverage of broad classes (e.g.,“antiseptics”) which by nature do not have CAS numbers.
Ninety-nine percent of DID rows represent unique triplets of raw data source (column B), drug name (column D), and indication target/substring (column AR), the other 1% representing compound matches where more than one UMLS term was needed to cover the indication concept completely. There are 10,938 unique values of the target/substring, of which 28 (0.3%) could not be mapped to UMLS. The rest mapped to 7,522 UMLS entry terms and thence to 6,227 UMLS PT/CUIs of the preferred semantic type (columns AT-BC), yielding a TR of 57%.
Indication semantic type normalization
Unlike the drug name normalization mappings, the indication UMLS mappings have a sizable prevalence of quasi-synonym match types (column AT; 46% of rows, 30% of unique target/substrings). This is attributable to our preference for indication normalization to phenotypic-type UMLS terms, operationalized in the semantic type normalization step. Non-phenotypic-type terms were thus reduced from 29% of DID rows among initial UMLS mappings (columns BD-BL) to 3% among final (AT-BC), primarily terms of type “Pharmacologic Substance”/A220.127.116.11.1 (25% initial, 1% final). The prevalence rank of “Pharmacologic Substance”/A18.104.22.168.1 changed from first to 13th, reflecting the large contributions from ChEBI, CTD, MeSH, PDR, USAN, and WHO-ATC consisting or raw therapeutic/pharmacologic class terms (e.g., “Analgesics”; “Antineoplastics”; “Carcinogens”).
Indication subtype data are contained in DID columns AN-AP. These data are very preliminary and incomplete. Supplementing and refining it is one of our ongoing extensions of this work.
Comparison of sources
Comparison of sources’ coverage of unique drug names, indication terms, and drug-indication relations after normalization
Comparison of sources’ overlapping coverage of unique drug names, indication terms, and drug-indication relations before and after normalization
Each source’s average numbers of indications per drug name and drug names per indication, before and after normalization, measure what might be called the “richness” of their drug-indication information. CTD had by far the highest (10) average raw indication targets per drug/chemical name, consistent with its low overlap and high coverage. Following CTD was a cluster in the range of 3.5–4 indication targets/drug that included DailyMed, MeSH_PA, DrugBank, and NDFRT, then a cluster in the 2.7–3.3 range that included WHO_DD, WHO_ATC, evoc_eProj, PDR, and evoc_ATC, and finally ChEBI (1.8) and USAN_TC (1.2). These numbers were little changed by normalization. The biggest changes were actually negative (0.4 more raw than normalized indications/drug for MeSH_PA and evoc_eProj).
The highest average numbers of drug names per raw indication target were provided by WHO_DD (69), evoc_ATC (56), and MeSH_PA (55). This same cluster also showed the biggest effect of normalization. At the low end, DailyMed and DrugBank data showed the most dramatic effect of processing, their average indications/drug increasing from approximately 1 (raw entire values) to 2 (raw targets) to 3 (normalized indications).
Our DID is intended to facilitate building practical, comprehensive, integrated drug ontologies. As for comprehensiveness, we achieved high source/data diversity as evidenced by a low overall degree of coverage overlap consistent with the idiosyncrasies of each source (non-drug chemicals, free text, hierarchical terms, etc.). Diversity is not equivalent to comprehensiveness, but is indicative of it. As for integration, indication normalization to phenotypic-type UMLS concepts provided substantial TR (57%). However, drug/chemical name normalization (TR 84%) was poor by comparison; therefore there was almost no effect of overall normalization on the average number of indications per drug.
WHO_DD’s, WHO_ATC’s, evoc_eProj’s, PDR’s, and evoc_ATC’s “richness” may be somewhat artificial in that it may be mainly due to WHO-ATC’s and PDR’s very general higher hierarchical categories. However, this feature may facilitate clustering of drug-indication relations and so explain WHO-ATC’s wide acceptance as a standard for drug classification and discovery research.
Because its true richness was not captured, DailyMed raises major issues for further development of the DID. These include the cost of dealing with the current (different) downloading, subsetting, and sectional parsing options, and developing better, less manual, free text-to-UMLS mapping methods. On the benefit side, methods applicable to DailyMed’s “Indications & Usage” sections are expected to be adaptable/re-usable for contraindications, side effects, and other dimensions of drug information. Relevance to clinical use cases is recognized  but DailyMed’s fit to early-stage drug discovery has been questioned . NDFRT presents the opposite conundrum. In a spot check of two drugs, we  found major discrepancies between NDFRT’s may_prevent and may_treat relations and the approved clinical indications. Therefore these relations may be a poor fit to clinical drug ontology use cases. However, as a representation of possible drug indications conveyed by co-occurrence of MeSH terms in Medline, they may be ideal for early-stage drug discovery. Also, NDFRT’s may_diagnose, has_mechanism_of_action, and has_physiological_effect relations will be examined for future inclusion in the DID.
Finally, CTD’s high-coverage, low-overlap outlier status raises suspicion that its “marker/mechanism” subset (63%) may not be relevant to drug indications and therefore should be examined and possibly excluded from future DID releases.
The DID is a database of structured drug-indication relations created using openly available, commercially available, and Merck proprietary information resources and terminological normalization tools. It is intended to facilitate building practical, comprehensive, integrated drug ontologies. The DID has good source/raw data diversity as measured by low coverage overlap, and significant integration/normalization as measured by terminological reduction. Numerous opportunities exist for data cleaning, addition, and other improvements. Our methodology could be adapted to the creation of other structured drug-disease databases such as for contraindications, precautions, warnings, and side effects.
Following UMLS, we take “diseases” to be synonymous with “disorders.” We also mean “diseases” to convey the larger sense of pathological or aversive states that might otherwise be distinguished as signs, symptoms, abnormalities, deficiencies, injuries, etc.
Although different forms of the same generic name can in principle be specific to different indications, our conflation of NDFRT is not “lossy” because NDFRT appears to cross-generalize them regardless. For example, finasteride is marketed as a 1 mg tablet indicated to treat male-pattern baldness and a 5 mg tablet indicated to treat benign prostatic hyperplasia. But NDFRT has may_treat relations to both “Alopecia” and “Prostatic Hyperplasia” (the corresponding MeSH PTs) for all three: “Finasteride 1 mg Tab”; “Finasteride 5 mg Tab”; and “Finasteride.” In another example, “Bismuth” and all of its salt variants have relations to “Escherichia Coli Infections”; “Virus Diseases”; “Helicobacter Infections”; and “Dysentery, Bacillary” presumably related to bismuth subsalicylate’s gastrointestinal effects but definitely inappropriate for “Bismuth Hydroxide” which is a hazardous industrial chemical. In another example, radioactive and hazardous “Iodine, I-125” inappropriately shares the “Iodine” relations to “Burns”; “Leg Ulcer”; “Radiation Injuries”; “Staphylococcal Infections”; and “Surgical Wound Infection.”
American Medical Association
British Approved Name
- CAS number or CAS#:
Chemical Abstracts Service Registry Number
Chemical Entities of Biological Interest
Comparative Toxicogenomics Database
Concept Unique Identifier [UMLS]
electronic VOCabularies [Merck internal system]
U.S. Food and Drug Administration
generic [drug] name
International Chemical Identifier
Medical Dictionary for Reporting Activities
- MeSH PA:
Medical Subject Headings Pharmacological Action [relations]
Medical Subject Headings
U.S. National Drug Formulary Reference Terminology
U.S. National Library of Medicine
natural language processing
Open Biological & Biomedical Ontologies
Physicians’ Desk Reference
Systematized NOmenclature of MEDicine Clinical Terminology
Unified Medical Language System
UNique Ingredient Identifier
- USAN TC:
United States Adopted Names Therapeutic Claim
United States Adopted Names
United States Pharmacopeia
UMLS Terminology Services
World Health Organization Anatomic-Therapeutic-Chemical [classification]
World Health Organization Drug Dictionary
I would like to thank my Merck colleagues, especially Jyoti Shah, Karen Marakoff, and Carol Rohl, for their contributions to this work. Also I would like to thank Olivier Bodenreider at NLM, Nicholas Belkin at Rutgers University, and the Merck Educational Assistance Program for their contributions to my Ph.D. thesis , of which this work is an extension.
Availability of data and materials
The non-proprietary subset of the DID is included with this paper (Additional file 1).
The author holds a M.A. in Biochemistry and a Ph.D. in Information Science. He has been involved in biomedical vocabularies, ontologies, and information systems at NIH, NLM, and Merck since 1988.
The author has been employed by Merck & Co., Inc., since 1994.
Open AccessThis article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. 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.
- Smith B, Ashburner M, Rosse C, Bard J, Bug W, Ceusters W, Goldberg LJ, Eilbeck K, Ireland A, Mungall CJ, Consortium OBI, Leontis N, Rocca-Serra P, Ruttenberg A, Sansone SA, Scheuermann RH, Shah N, Whetzel PL, Lewis S. The OBO foundry: coordinated evolution of ontologies to support biomedical data integration. Nat Biotechnol. 2007;25:1251–5.View ArticleGoogle Scholar
- Rubin DL, Shah NH, Noy NF. Biomedical ontologies: a functional perspective. Brief Bioinform. 2008;9:75–90.View ArticleGoogle Scholar
- Hoehndorf R, Dumontier M, Gkoutos GV. Evaluation of research in biomedical ontologies. Brief Bioinform. 2013;14:696–712.View ArticleGoogle Scholar
- Khanna I. Drug discovery in pharmaceutical industry: productivity challenges and trends. Drug Discov Today. 2012;17:1088–102.View ArticleGoogle Scholar
- The Gene Ontology Consortium. Gene ontology consortium: going forward. Nucleic Acids Res. 2015;43:D1049–56.View ArticleGoogle Scholar
- Meyer HF. Streamlining the research and development pipeline by coupling of information technology and biology. Drug Inf J. 2002;36:169–78.View ArticleGoogle Scholar
- Gardner SP. Ontologies and semantic data integration. Drug Discov Today. 2005;10:1001–7.View ArticleGoogle Scholar
- Bawden D, Robinson L. Pharmaceutical information: a thirty year perspective on the literature. Annu Rev Inf Sci Technol. 2010;45:63–119.View ArticleGoogle Scholar
- Hanna J, Joseph E, Brochhausen M, Hogan WR. Building a drug ontology based on RxNorm and other sources. J Biomed Semantics. 2013;4:44.View ArticleGoogle Scholar
- Tao C, He Y, Arabandi S. A 2013 workshop: vaccine and drug ontology studies (VDOS 2013). J Biomed Semantics. 2014;5:16.View ArticleGoogle Scholar
- Quan D. Improving life sciences information retrieval using semantic web technology. Brief Bioinform. 2007;8:172–82.View ArticleGoogle Scholar
- Yildirim MA, Goh KI, Cusick ME, Barabási AL, Vidal M. Drug-target network. Nat Biotechnol. 2007;25:1119–26.View ArticleGoogle Scholar
- Campillos M, Kuhn M, Gavin AC, Jensen LJ, Bork P. Drug target identification using side-effect similarity. Science. 2008;321:263–6.View ArticleGoogle Scholar
- Boguski MS, Mandl KD, Sukhatme VP. Repurposing with a difference. Science. 2009;324:1394–5.View ArticleGoogle Scholar
- Hug H, Dannecker R, Schindler R, Bagatto D, Stephan A, Wess RA, Gut J. Ontology-based knowledge management of troglitazone-induced hepatotoxicity. Drug Discov Today. 2004;9:948–54.View ArticleGoogle Scholar
- Aronson JK, Ferner RE. Clarification of terminology in drug safety. Drug Saf. 2005;28:851–70.View ArticleGoogle Scholar
- Mendrick DL. Translational medicine: the discovery of bridging biomarkers using pharmacogenomics. Pharmacogenomics. 2006;7:943–7.View ArticleGoogle Scholar
- Iyengar R, Altman RB, Troyanska O, FitzGerald GA. Personalization in practice. Science. 2015;350:282–3.View ArticleGoogle Scholar
- Sharp M, Bodenreider O, Wacholder N. A framework for characterizing drug information sources. Proc AMIA Annu Fall Symp. 2008;6:662–6.Google Scholar
- Sharp ME. Dimensions of drug information. PhD thesis. New Brunswick: Rutgers University, School of Communication and Information; 2011.
- GenBank Home. http://www.ncbi.nlm.nih.gov/genbank/.
- DrugBank. http://www.drugbank.ca/.
- The PubChem Project. http://pubchem.ncbi.nlm.nih.gov/.
- ChemIDplus Advanced. http://chem.sis.nlm.nih.gov/chemidplus/.
- DailyMed. http://dailymed.nlm.nih.gov/.
- WHOCC – ATC/DDD Index. http://www.whocc.no/atc_ddd_index/.
- Medical Subject Headings. https://www.nlm.nih.gov/mesh/.
- PubMed. http://www.ncbi.nlm.nih.gov/pubmed.
- National Drug File Reference Terminology. https://www.nlm.nih.gov/research/umls/sourcereleasedocs/current/NDFRT/.
- UMLS. https://www.nlm.nih.gov/research/umls/.
- Physicians’ Desk Reference. https://en.wikipedia.org/wiki/Physicians’_Desk_Reference.
- ChEBI The database and ontology of Chemical Entities of Biological Interest. http://www.ebi.ac.uk/chebi/.
- Davis AP, Murphy CG, Johnson R, Lay JM, Lennon-Hopkins K, Saraceni-Richards C, Sciaky D, King BL, Rosenstein MC, Wiegers TC, Mattingly CJ. The comparative toxicogenomics database: update 2013. Nucleic Acids Res. 2013;41:D1104–14.View ArticleGoogle Scholar
- Comparative Toxicogenomics Database. http://ctdbase.org/.
- About Us | USAN Council. https://www.ama-assn.org/about-us/usan-council?
- USP Dictionary. http://www.usp.org/store/products-services/usp-dictionary.
- Adopted Names. https://www.ama-assn.org/about-us/adopted-names.
- WHO-ATC-DDD (Defined Daily Dose) Index, 2005 release; Updates available at https://www.whocc.no/atc_ddd_index_and_guidelines/order/.
- WHO Drug Dictionary, Sept. 1, 2013 release; Updates available at http://www.umc-products.com/DynPage.aspx?id=73588&mn1=1107&mn2=1139.
- ChemIDplus, Substance Name: Aftobetin Hydrochloride [USAN]. http://chem.sis.nlm.nih.gov/chemidplus/name/contains/aftobetin%20hydrochloride.
- MetaMap - A Tool for Recognizing UMLS Concepts in Text. https://metamap.nlm.nih.gov/.
- UMLS Terminology Services - Metathesaurus Browser. https://uts.nlm.nih.gov//metathesaurus.html. [requires UTS login].
- Library of Congress, Thesauri and Controlled Vocabularies. http://www.loc.gov/library/libarch-thesauri.html.
- Zipf GK. The Psychobiology of Language. Houghton-Mifflin, 1935.
- Li Q, et al. Mining FDA drug labels for medical conditions. BMC Med Inform Decis Mak. 2013;13:53.View ArticleGoogle Scholar
- Boyce R, Harkema H, Conway M. Leveraging the semantic web and natural language processing to enhance drug-mechanism knowledge in drug product labels. In: Proceedings of the first ACM international health informatics symposium: november 11–12, 2010. Arlington, VA, USA. 2010. p. 492–6.Google Scholar