| Literature DB >> 35143713 |
Theodoros G Soldatos1, Sarah Kim2, Stephan Schmidt2, Lawrence J Lesko2, David B Jackson1.
Abstract
Promising drug development efforts may frequently fail due to unintended adverse reactions. Several methods have been developed to analyze such data, aiming to improve pharmacovigilance and drug safety. In this work, we provide a brief review of key directions to quantitatively analyzing adverse events and explore the potential of augmenting these methods using additional molecular data descriptors. We argue that molecular expansion of adverse event data may provide a path to improving the insights gained through more traditional pharmacovigilance approaches. Examples include the ability to assess statistical relevance with respect to underlying biomolecular mechanisms, the ability to generate plausible causative hypotheses and/or confirmation where possible, the ability to computationally study potential clinical trial designs and/or results, as well as the further provision of advanced features incorporated in innovative methods, such as machine learning. In summary, molecular data expansion provides an elegant way to extend mechanistic modeling, systems pharmacology, and patient-centered approaches for the assessment of drug safety. We anticipate that such advances in real-world data informatics and outcome analytics will help to better inform public health, via the improved ability to prospectively understand and predict various types of drug-induced molecular perturbations and adverse events.Entities:
Mesh:
Year: 2022 PMID: 35143713 PMCID: PMC9124355 DOI: 10.1002/psp4.12765
Source DB: PubMed Journal: CPT Pharmacometrics Syst Pharmacol ISSN: 2163-8306
FIGURE 1Innovative postmarket data mining and novel methods to analyze and detect toxicities are key to (pre‐)clinical modeling. (a) The standard drug development process is aligned to characterization steps spanning (animal) model screening, target identification and validation, product formulation and development, preclinical model optimization, preclinical and clinical testing, approval and postmarket monitoring. (b) Advanced pharmacovigilance studies may benefit from data augmentation opportunities that consider multiple layers of information. ADME, absorption, distribution, metabolism, and excretion; IND, investigational new drug; NDA, new drug application; PoC, proof of concept
Sample challenges and limitations hindering the analysis and management of adverse event data
| AE content | Knowledge engineering | Data mining |
|---|---|---|
| Lack of specific severity grading for described conditions (indications, reactions). | Scalability (and increasing data sizes) | Multi‐pharmacy (co‐medications) |
| Disambiguation of symptoms (e.g., disease vs. reactions) | Lack of universal benchmark data | Comorbidities |
| Polypharmacy and drug interference | Visualization | Statistical normalization / control background |
| Detail regarding patient/event history (+) | Management of dictionaries and ontologies | Semantics and hierarchies |
| Missing, incorrect, or vague information | Data standardization | Pattern identification / synergistic effects |
| Handling of duplicates and/or multiple reports per case (e.g., follow‐ups) | Data safety, ownership and transparency | Signal does not provide proof of causation |
| Reporting bias (over‐/under‐reporting) | Disambiguation and synchronization of reports between systems | Unbalanced data sets |
| Data entry and coding | Different and changing reporting requirements between systems | Definition of (risk) populations / cohorts |
| Difficulty in verifying AE occurrence | Inconsistent database structure | Observation of signals over time |
| Not all AEs are reported | Biomedical plausibility | Biomedical plausibility |
(+)Detailed patient/event history may include treatment duration, cycles, timing, dosage or previous therapies and co‐morbidities, de‐/re‐challenge information, demographics, disease stage, laboratory, and clinical parameters.
Abbreviation: AE, adverse event.
FIGURE 2Safety reports contain clinical outcomes data for millions of real‐world patient treatments with details about drug‐induced phenotypes (i.e., side effects) that can be linked to chemical and molecular information about drugs and their targets. Similar to model‐based approaches, perturbation studies are key to identifying the molecular underpinnings of human disease, via the process of comparing individuals and/or cohort‐populations for differences at the molecular‐level. Therefore, linking the molecular functions targeted by therapeutics to resultant side‐effect phenotypes—and this for millions of patients—should enable the computational dissection of the molecular mechanisms underlying these effects. This approach for the molecular analysis of side effects (MASE) enables production of datasets valuable to the molecular characterization of human disease, directly from real‐world treatment outcomes/safety data. This strategy provides a standardized approach in a variety of contexts; prototype results can be accessed via Molecular Health’s Effect platform. Figure adapted from Soldatos et al
Selected studies that demonstrate examples or discuss ways to gain potentially new insights from the interrogation of AEs at additional data layers
| Description of case study (+) (Summary of example with respect to key AE extension perspectives) | |
|---|---|
| Title citation; year |
|
| Focus category |
|
| Study’s domain | Oncology |
| Purpose/emphasis | To examine the potential clinical impact of model (e.g., experimental, laboratory) findings. |
| Method/approach | Retrospective computational mining; Statistical analysis Bayesian inference |
| Molecular data | Indirect; use of ATC classification hierarchy to automatically identify beta‐blockers/AEs. |
| Hypothesis/goal | Molecular hypothesis validation using outcome data from human AE observations. |
| Implications |
|
| Title citation; year | Association Between Serotonin Syndrome and Second‐Generation Antipsychotics via Pharmacological Target‐Adverse Event Analysis |
| Focus category |
|
| Study’s domain | Serotonin syndrome (SS) |
| Purpose/emphasis | Insight into the molecular mechanisms of SS |
| Method/approach | Systems pharmacology; Data mining Disproportionality (PRR) |
| Molecular data | Drug interactors (T), Pathways (P) |
| Hypothesis/goal | Molecular characterization of AEs can help determine relationship between SS and SGAs. |
| Implications |
|
| Title citation; year | Adverse Event Circumstances and the Case of Drug Interactions |
| Focus category |
|
| Study’s domain | Circumstances of AEs |
| Purpose/emphasis | Preventable AEs, DDIs, personalized therapeutic optimization |
| Method/approach | Systems level analysis; Graph representation Network co−occurrence |
| Molecular data | Drug interactors (T), Pathways (P), DDIs (D) |
| Hypothesis/goal | Molecular level interrogation of therapeutic setting can help optimize use of co‐medications. |
| Implications |
|
| Title citation; year | Target Adverse Event Profiles for Predictive Safety in the Postmarket Setting |
| Focus category |
|
| Study’s domain | Prediction of unlabeled adverse effects at the time of drug approval |
| Purpose/emphasis | Prediction of post‐market label changes using molecular features |
| Method/approach | Ensemble of classification methods; Data mining Disproportionality (PRR) |
| Molecular data | Drug interactors (T) |
| Hypothesis/goal | Parameters from the molecular layer may provide important information to predictive safety. |
| Implications |
|
(+)Case studies sorted by year of publication (ascending order); all studies utilized the US Food and Drug Adverse Event Reporting System (FAERS) data, organized based on the Molecular Analysis of Side Effects (MASE) extension principle. (T) Information about drug interactors refers to targets, metabolizing enzymes, carriers, and transporters (and may include potential pharmacokinetic and pharmacodynamics aspects). (P) Should a drug interact with components that belong to a certain (functional and molecular) pathway network, then that pathway may be transitively annotated via its (drug, or drug interacting) members. (TAE) Indicates type of target adverse event (TAE) analysis implementation. (D) Between medication products reported for the same patient case.
Abbreviations: AE, adverse event; ATC, anatomic therapeutic chemical; DDI, drug‐drug interaction; MoA, mode of action; PRR, Proportional Reporting Ratio; SGA, second generation antipsychotic; SS, serotonin syndrome; SSRI, selective serotonin reuptake inhibitor.
Selected features for assessing and comparing AE data analysis software and platforms
| Category | Feature | Description (value, parameters, examples) |
|---|---|---|
| Audience | Availability | Is the technology a commercial product or an academic/open‐source solution? What is the licensing status? |
| Target groups | May refer to (a combination) of regulatory, interdisciplinary health/life‐experts, medical, clinical, “pharma” or other industry stakeholders, including clinical pharmacologists, medicinal chemists, pharmacovigilance professionals, preclinical toxicologists, translational researchers, epidemiologists, health policy makers, or even the public. | |
| Core capabilities | Analytical power |
May refer to signal detection capabilities, such as:
The mathematical methods to define the degree of statistical association between entities (e.g., drug and side effect), including disproportionality/frequentist or Bayesian methods, identification of confounders, and so on. Or, the use of sophisticated analytical technologies such as knowledge graphs, ML(+), and BD(+). |
| Content diversity |
Key integration parameters include:
Data breadth: does it integrate drug/chemistry (e.g. structure, synonyms, descriptions) or molecular (e.g., targets, metabolizing enzymes, transporters, signaling/metabolic pathway models, DDIs(+)) knowledge, preclinical toxicity, label information, evidence from literature, etc. Datasets (e.g., public or proprietary data, RWD(+), AEs(+), CTs(+), and so on) Data depth (e.g., dictionaries, ontologies, hierarchies, resolution in GUI(+)) | |
| Key functionalities |
Types of analyses may address multiple use cases, such as:
Drug safety signal detection and prediction Comparative/competitive safety analysis (In‐)validation / assessment of emergent signals Design of rational drug combinations Molecular analysis of emergent safety signals Genotype to phenotype analysis Biological plausibility analysis Drug repositioning Prediction of (target) AE(+) profiles and DDIs(+)
Rational design of combination therapies | |
| Systems pharmacology | Systems level molecular analysis of real‐world drug safety data |
Main abilities include:
Integrates AEs(+)/RWD(+) with molecular knowledge Analyzes clinical effects of drug targets (e.g., safety profile) Analyzes potential clinical effects of novel drug targets (e.g., using neighborhood analysis) Analyzes the clinical effects of biological pathways Examines patient level drug‐mode of action models Analyzes DDIs(+) at the level of biological systems Compares clinical safety profiles for independent drug targets or pathways Constructs and compares independent cohorts of patients based on user‐defined clinical and molecular parameters |
| Technology | Easy to understand and user‐friendliness | May include aspects such as intuitiveness of GUI(+), search/browse utilities, speed and responsiveness, graphical data visualization functionalities. |
| Information access |
May refer to aspects regarding:
Web accessibility, report generation and/or data download capabilities Format (e.g., DB(+), cloud‐native, BD(+), SaaS(+)) Can it be integrated or customized and in what scope (scalable or consultancy/project‐based approach)? | |
| Analytical features | May refer to safety signal management, provision of advanced search capabilities, access to patient level case reports, cohort building functionalities, depth of (GUI(+)) exploration/data resolution (e.g., seriousness, demographics, outcomes, hierarchies, synonyms, etc.), number of statistic/metric scores, embedded analytical scenarios, advanced/customizable graphical visualization options (charts, dashboards, etc.), molecular mechanism/drug‐MoA(+) insights. | |
| Quality | May refer to quality management and control procedures, such as proprietary data integration and transformation processes, benchmarking, or compliance with industry certified quality assurance standards. | |
| Validation |
Main points of endorsement include:
Use by regulators Industry acceptance (customer projects and market usage and advocacy) Patent protection Peer reviewed studies and recognition |
Abbreviations: AE, adverse event; BD, big data; CT, clinical trial; DB, database; DDI, drug‐drug interaction; GUI, graphical user interface; ML, machine learning; MoA, mode of action; RWD, real‐world data; SaaS, software‐as‐a‐service.
Aspects that may reflect on the structure of the discussed web‐based services or GUIs(+) with respect to the organized exploration of complicated AE information
| GUI(+) or service parameter | Aspect description (examples / discussion) |
|---|---|
| Search forms | Identifying sets of AEs with specific characteristics is one main GUI or service functionality. Some of these options may be simpler or more complicated. Commonly, searches rely on text queries matching drug or symptom names. Often, advanced search forms are used to include more structured queries utilizing logical operators and complex hierarchies. Finally, some allow for customizable result views and/or cohort definition options, using different content characteristics as filters. |
| Data dissemination | Main dimensions when exploring AE content (in turn, display pages, or views) include information regarding reported outcomes, seriousness, timelines, demographics (e.g., age, sex, or geographical/regional origin), and/or symptoms (indications or reactions) the resolution and detail with which such condition layers are described and/or presented is variable among the different tools. |
| Content resolution | In some cases, aggregation of results may rely on pre‐calculated views rather than on on‐demand computations. Access to individual AE case‐level descriptions may be available too. |
| Data irregularities | May refer to unprocessed data or irregular representation structures, including free‐text descriptions (e.g., generic vs. product drug names, medicinal products vs. active substances). |
| Data delivery | Generated data may be shared via views organized in web‐reports, and sometimes may be exportable into a commonly downloadable form (such as ASCII, Excel, JSON, CSV, or otherwise formatted files). |
| Analytic resources (mining and storage) | Addressing availability of resources (or rather, the lack thereof) is key—whether it is about handling (limited) computational capacity or (large) computational requirements. Lead ways to handle the topic may include: (a) narrowed breadth: some web services (or GUIs) apply techniques to reduce the analytical load (e.g., force the user to specify the exact multi‐parameterized combination of records to be analyzed each time, or restrict the computation to a limited number of top only records); (b) resort to benefits that rely on third party solutions (e.g., OpenVigil FDA |
| Visualization provision | Above factors (including data and resource management) may directly affect visualization decisions, and on the degree that data delivery is organized in a dynamic fashion (e.g., in terms of charts, tables, or graphs and whether these are configurable by the user). In comparison, ezFAERS |
Abbreviations: AE, adverse event; FAERS, US Food and Drug Adverse Event Reporting System; FDA, US Food and Drug Administration; GUI, graphical user interface.