What is OpenVigil?
OpenVigil 1 and 2 are software packages
to analyse pharmacovigilance data. There are several national and
international databases of so called spontaneous adverse event
reports, e.g., the U.S. american FDA Adverse Event Reporting
System (AERS, mostly domestic data) or the WHO Uppsala Monitoring Centre (international).
Currently, analyses of FDA AERS (LAERS & FAERS)
pharmacovigilance data are available. In addition to U.S. american data, we are currently importing German data. Data mining features include highly configurable search criteria filters and output filters. Analyses include
disproportionality analyses for signal detection like Proportional Reporting Ratio (PRR) calculations. Results can be viewed,
sorted and filtered in the webbrowser or saved for further
analyses in statistical software packages. Both projects aim at
integrating these and other pharmacolovigilance sources to
pharmacoepidemiological data like prescription data.
Where can I access OpenVigil?
OpenVigilFDA is a fron-end to the openFDA-interface which is being developed by the FDA since 2014. It allows you to extract the latest reports.
Due to technical limitations, the beta-version status and the ongoing changes to the API of openFDA, OpenVigil 2 is more stable and superior for analyses of disproportionality.
There are live installations with U.S. american FDA pharmacovigilance data of both versions of OpenVigil with FDA AERS data and OpenVigilFDA freely
available at Christian Albrecht University (CAU) of Kiel, Germany:
Where can I download OpenVigil?
OpenVigil 2.1-MedDRA (data 2004Q1-2014Q2): http://www.is.informatik.uni-kiel.de/pvt/OpenVigilMedDRA/search/
OpenVigil 2.1 (data 2004Q1-2014Q2): http://www.is.informatik.uni-kiel.de/pvt/OpenVigil2.1/search/
OpenVigil 2.0 (data 2004Q1-2012Q2): http://www.is.informatik.uni-kiel.de/pvt/OpenVigil/search/
OpenVigil FDA: http://openvigil.pharmacology.uni-kiel.de/openvigilfda.php
OpenVigil 1: http://openvigil.pharmacology.uni-kiel.de/openvigil.php
(development version at: http://openvigil.pharmacology.uni-kiel.de/openvigil-current.php)
OpenVigil 2 and OpenVigilFDA are the successors of OpenVigil 1 and use cleansed FDA
AERS data. For scientific research on U.S. american data, do not use OpenVigil 1 but
only version 2 or OpenVigilFDA!
There is also a development version of OpenVigil 1 with German pharmacovigilance data available for preview:
OpenVigil 1 German: http://openvigil.pharmacology.uni-kiel.de/openvigil-current-bfarm.php)
We are also working on a development version of OpenVigil 1 with Canadian pharmacovigilance data (database is currently sill empty):
OpenVigil 1 Canadian: http://openvigil.pharmacology.uni-kiel.de/openvigil-current-hc.php)
The German and Canadian pharmacovigilance data are of sufficient quality and do not need further drugname-mapping prior to mining or analysing them.
You can download the PHP-sources/executables of OpenVigil 1 and OpenVigilFDA and a WAR-file of OpenVigil 2.1 at
Who can be contacted about this project?
Source code of OpenVigil 2 will be made available soon, too, after some more improvement on code readability and documentation has been done.
The project is maintained by Dr. Ruwen Böhm, specialist for clinical pharmacology, Institute of
Experimental and Clinical Pharmacology, UKSH Kiel, <email@example.com>
and Prof. Dr. Hans-Joachim Klein, computer scientist, Institut für Informatik, Christian Albrechts
University, Kiel, <firstname.lastname@example.org>
The OpenVigil project follows the HONcode and was certified in november 2015. The annual re-certification was made possible by private funding and the kind help of the HON foundation for projects without dedicated budget.
This site complies with the HONcode standard for trustworthy health information:
All software uses browser cookies. Cookies are used for the captchas and to store previous queries as convenience for the user (OpenVigilFDA only). Users are not tracked.
Emails sent to the projects members are treated confidentially and are neither systematically saved nor used for statistics.
Cf. the installation overview pages for date of last changes to programs or databases and version numbers and the cave-at documents for general pitfalls.
All software uses brand names which are not specifically identified (e.g., by using ®). Cf. the documentation to understand the difference between drug name and brand name and to learn which output does contain brand names.
The authors declare no conflicts of interested as they have no financial or other relation to any of the producers.
Responsible for this website (Impressum / Betreiber der Website): Dr. med. Ruwen Böhm, Institut für Experimentelle und Klinisch Pharmakologie, UKSH Kiel, Hospitalstr. 4, 24105 Kiel, Germany. Tel. +49 431 500 30414, <email@example.com>.
The project is funded by public funding via the Christian Albrechts University (CAU) of Kiel, Germany. There is no funding via advertisements.
The OpenVigil project does not produce or gather any of the pharmacovigilance data itself but is dependent on external data sources.
Our software is being developed for physicians, pharmacists and scientists. Due to the origin and nature of the data and the ongoing work on our programs, all results should be considered unvalidated.
Especially, any findings must not uncritically be used for therapy changes or legal proceedings. However, these data are well usable for hypothesis generation.
This page was last changed on 2017-10-18.
What is pharmacovigilance?
Pharmacovigilance is defined as the science and activities relating to the detection, assessment, understanding and prevention of adverse effects or any other drug-related problem.
Why do we have pharmacovigilance?
Triggered by the thalidomide (Contergan®) tragedy 1957-1961, various countries have introduced the systematic collection
of spontaneous filed reports of adverse events occuring during or after pharmacotherapy. This ongoing monitoring of (newly approved) drugs ensures detection
of rarely occuring adverse event and other types of issues with the pharmaceutical product or the patient adhearance to it. So, while clinical trials can
contribute to drug safety, pharmacovigilance can improve drug therapy safety!
What type of data is gathered?
Reports can be filed by physicians, pharmacists, pharmaceutical companies and patients. Depending on the domestic laws, it is mandatory for most of these parties
to report any observed adverse event. Recent EU directives recommend to gather reports from patients. The quality of the data is thus diverse: Some are unusable due to missing data.
One the other hand, reports made by pharmaceutical contain a lot of information due to enforced laws concerning patient security.
Most pharmacovigilance databases traditionally contain some basic data on the patient (e.g., gender and age),
the adverse event(s) and a list of drugs. Depending on primary data sources (e.g., outpatient or hospital patient), quality of the report
and policy of the agency that is taking care of the database, other data, e.g., indications or laboratory values, can be added.
How does analysis of pharmacovigilance data contribute to healt care?
By the nature of this 'spontaneous collection' these data have to be treated with caution and are generally not suited for hypothesis confirmation
but only for hypothesis generation.
Pharmacovigilance data-mining for signals, i.e., disproportionally stronger associations between drugs and adverse events, is routinely done by
the regulatory authorities. However, pharmacovigilance data is not only useful for monitoring new drugs but also for detecting more complex signals, e.g., drug-drug
interactions or syndromes (so called multi-item data mining) or to further analyse known signals and find a especially vulnerable population or mode of application.
Where can I extract or analyse pharmacovigilance data?
Open access to pharmacovigilance data is limited. The freedom of information act (US) and similar laws in other jurisdictions have led to the availability of raw data
(e.g., FDA AERS datafiles) and new portals to access data (e.g., EMA http://www.adrreports.eu/). A list of possible access and analysis options is provied in our resource library page.
How are statistical signals in pharmacovigilance data detected?
However, the open availability combined with the advanced and cleaning, filtering, extraction and analysis capabilities of OpenVigil 2 are unique:
All pharmacovigilance research using OpenVigil software is completely transparent and reproducible, thus allowing other scientists to confirm any findings and expand the analyses.
Statistical detection of signals whether a drug-event combination is a
putative dverse drug reactions or just a random association can be
done using either (i) frequency based methods comparing estimated
counts to observed counts for a drug-event-combination like Relative
Reporting Ratio (RRR), Proportional Reporting Ratio (PRR) or Reporting
Odds Ratio (ROR) or Likelihood Ratio Test (LRT), (ii) Bayesian
probabilities like Bayesian conidence propagation neural network
(BCPNN) or Poisson-Dirichlet process (DP) or (iii) the (Multi-item) Gamma
Poisson Shrinker (GPS/MGPS).
What are the usual pitfalls when analysing pharmacovigilance data?
All OpenVigil software provides RRR, PRR and ROR which are similar in
magnitude and explanatory power. These measurements of
disproportionality are calculated as RRR=DE*N/(D*E), PRR=(DE/D)/(dE/d) and ROR=DE*de/(De*dE).
A value of 1 is considered normal background noise. The confidence interval can be
estimated using Chi-squared with Yates' correction chisq > 4 or lower
bound of the 95% confidence interval (CI) of RRR, PRR or ROR, e.g. for
s = sqr( 1/DE + 1/De + 1/dE + 1/de ) for ROR with CI = e ^ ( ln ROR ±
OpenVigil 2.2 will offer MGPS calculations. This signal detection
algorithm is especially suited for small numbers of drug-event
Signal detection can be used to find a subgroup of vulnerable
patients. By stratifying the reports by age, gender, mode of
administration, dosage, indication or other categories, it is possible
to identify any confounders and/or vulnerable patients.
By the very nature of this data collection, it represents only a certain part of the general population in health care (the so-called "open world" problem). Issues like under/over-reporting
and counting issues due to multiplicates are summarized in the OpenVigil 1 & 2 cave-at document.
Which clinical or scientific questions can be addressed by analysing pharmacovigilance data?
The quality of reports and the verbatim text items, e.g., DRUG.DRUGNAME in the FDA AERS data, require preprocessing of the records and a careful validation
of any analysis results. OpenVigil 2 provides cleaning of imported data by using external databases like drugbank.ca and user input.
An analysis of pharmacovigilance data can usually not confirm a hypothesis. E.g., you cannot use it proof a certain association. In some situations it might support a hypothesis.
Instead, pharmacovigilance data is routinely used to generate a new hypothesis that requires testing in more in silico, preclinical or clinical research, as well as to give therapy guidiance in direct health care.
Obviously, detecting new adverse drug reactions are the primary reason why pharmacovigilance has been implement and thus they are the most important analysis goal. Other usages include detection of especially vulnerable subpopulations, of harmful excipients/brands, of toxic chemical moieties, of syndromes, of drug-drug-interactions and comparing drugs within drug class.
How about other usage (e.g., marketing or legal proceedings)?
Because of the limitations of pharmacovigilance data analysis due to the origin and nature of the data, any findings of disproportionality do generally not allow to proof an assumption or to suport a hypothesis. Occassionally, it might be usefull to show that a certain signal was present or not present at a certain date in the past for these purposes.
Interpretation of queries requires sound knowledge of statistics, pharmacy, pharmacology and clinical significance of any findings. To fully understand the results,
a team combining expertise in these areas is recommended.
Technical documents: Installation, Data cleaning, Caveat, Citing
Due to the nature of the method of collecting pharmacovigilance data and the nature of the data itself, several precautions need to be taken for high-quality analyses
of drugs and their putative adverse drug reactions. This is especially important if you chose to install OpenVigil yourself.
Other general data analysis tools, pharmacovigilance
database sources and similar analysis tools
- Cave at documents: Methodological mistakes when crafting
or interpreting queries
- Software validation reports/bug lists
- Before using an installation of OpenVigil, be sure to know
your data, e.g., check which files were successfully
- Basic methodologies for validation and interpretation
- How to install you own OpenVigil instance
(For citation of an installation, give a summary/overview of
imported files and software version, see above!)
- Interface to RxNorm to map verbatim drugnames to USAN: http://openvigil.pharmacology.uni-kiel.de/rxn.php
- Suggested software packages for further analysis of the
- Pharmacovigilance datasources (with download link if
- Publicly available search engines
- Search engines based on US FDA pharmacovigilance data
- Search engines of official drug-regulating agencies
- Testing data and various tools for analysing observational study data
Tutorial and standard operating procedures
Common analysis scenarios are depicted here. Please note that our installations of OpenVigil do not use weekly updated data so that monitoring
newly approved drugs is usually not readily possible.
Tutorials: How to perform certain tasks with OpenVigil
Selected analysis scenarios
Our OpenVigil publications
Peer-reviewed publications referring to OpenVigil or data
extracted by OpenVigil
- Herdegen T, Böhm R: Dtsch Apoth Ztg 2009; 149(4): 315.
[Neuro-psychiatric ADR of montelukast] Neuropsychiatrische UAW von Montelukast.
- Böhm R., Herdegen Th. Dtsch Apoth Ztg 2009, 149(32), S. 3623. [Risk of infection and liver damage by orlistat] Infektionsrisiko und Leberschädigung unter Orlistat
- Böhm, R., Cascorbi, I. & Herdegen, T. [Hypoglycemic risk of insulinotropic drugs] Hypoglykämie bei insulinotropen Substanzen. Med. Monatsschr. Pharm. 32,
453–458 (2009). PMID 20088347
- Schulz-Du Bois, C. & Böhm, R. Haloperidol
intravenous – a preliminary risk assessment.
Pharmacopsychiatry 44, A104 (2011). https://www.thieme-connect.com/products/ejournals/abstract/10.1055/s-0031-1292545
- Böhm R, Höcker J, Cascorbi I, Herdegen T.
OpenVigil--free eyeballs on AERS pharmacovigilance data.
Nat Biotechnol. 2012 Feb 8;30(2):137-8. doi:
- Böhm R, Reinecke K, Haen E, Cascorbi I, Herdegen Th.
[Clinical pharmacy – Understand, teach and avoid
Drug-Drug-Interactions ] KLINISCHE PHARMAZIE -
Arzneimittelinteraktionen verstehen, vermitteln und
vermeiden. Deutsche Apotheker-Zeitung Vol. 152, No. 36
(2012), p. 64-75
- Böhm R, Meybohm P. [Pediatric emergencies - part 1: fever] Kindernotfälle - Teil 1: Fieber. Notfallmedizin up2date 2012(7):2-4
- Eggeling Ch. and Zieger S. [Project report
pharmacovigilance analysis] Projektbericht
- Eggeling Ch. [Data quality in pharmacovigilance data]
Datenqualität in Pharmakovigilanzdaten. Master
- Zieger S. [Statistical methods of pharmacovigilance data
mining] Statistische Methoden des Data Mining in der
Master Thesis 2013
- Böhm R, Meybohm, P. [Intoxications and antidotes - part 1] Intoxikationen und Antidote - Teil 1. Notfallmedizin up2date, 2013(2):82-85.
- Böhm R, Meybohm, P, Kunz T. [Ketamine - established anaethetic with new indications] Ketamin–bewährtes Narkotikum mit neuen Indikationen. Notfallmedizin up2date, 2014(9):292-293.
- von Hehn L, Zieger S, Freitag-Wolf S, Böhm R, Klein
H.-J., Herdegen T. Clinical applications of the
OpenVigil 2 pharmacovigilance analysis tool: Reverse
disproportionality analyses and detection of
Naunyn-Schmiedeberg´s Arch Pharmacol (2015) 388
(Suppl 1):S57. DGPT Congress 2015, Poster
- Böhm R, Liebetrau A, Weiler N, Hedderich J, Tag H,
Goeder R, Höcker J, Herdegen T, Hohagen F, Adlenhoff J,
Schulz-Du Bois C, Schulz-Du Bois A. Cardiotoxicity of
intravenous haloperidol - an update. Naunyn-Schmiedeberg´s
Arch Pharmacol (2015) 388 (Suppl 1):S32.
DGPT Congress 2015,Poster #129
- Böhm R, Eggeling Ch, Polomski T, Heidebrecht D, von Hehn
L, Herdegen T, Klein HJ. Data Quality and Methodological
Transparency in Pharmacovigilance.Naunyn-Schmiedeberg´s
Arch Pharmacol (2015) 388 (Suppl 1):S58.
DGPT Congress 2015. Short
- Böhm R, Herdegen T. Pharmacovigilance applied to clinical neurology and psychiatry. Poster at 2nd Kiel Neuroscience Day 2015
- Böhm R, Herdegen T. Using the OpenVigil 2 pharmacovigilance tool for guidance for clinical decisions involving newly occurring adverse events. GPTS Congress 2016 Poster #408
- Böhm R, von Hehn L, Herdegen T, Klein HJ, Bruhn O, Petri H, Höcker J. OpenVigil FDA - Inspection of U.S. American Adverse Drug Events Pharmacovigilance Data and Novel Clinical Applications. PLoS One. 2016 Jun 21;11(6):e0157753.
PMID: 27326858 http://dx.plos.org/10.1371/journal.pone.0157753
- Böhm R, Herdegen T. Using the OpenVigil FDA pharmacovigilance tool to screen for new drug-drug-interactions among neuro- and psychotropic drugs. Poster at Kiel Neuroscience Day 2016
- Böhm R, Cascorbi I. Pharmacogenetics and Predictive Testing of Drug Hypersensitivity Reactions. Frontiers in Pharmacology 2016; 7: 396
- Thingholm LB, Rühlemann MC, Koch M, Laucke G, Böhm R, Bang C, Heinsen FA, Frost F, Lerch MM, Homuth G, Kacprowski T, Lieb W, Laudes M, Huttenhower C, Franke A. Gut microbiome associations with diet and
medication usage in type 2 diabetes. Poster presentation Cambridge 2017
- Schulz M, Gradl G, Laufs U, Herdegen T, Werning J, Kieble M, Bruckmüller H, Klein HJ, Böhm R. Temporal synchrony between drug dispensings and adverse drug events? The example of
statins & rhabdomyolysis and metamizole or clozapine & agranulocytosis. Poster at ESCP 2017 Presentation at ESCP 2017
Other Articles and Books referring to OpenVigil
- Diethelm Tschöpe, Peter Bramlage, Christiane Binz,
Michael Krekler, Tanja Plate,Evelin Deeg and Anselm K
Gitt. Antidiabetic pharmacotherapy and anamnestic
hypoglycemia in a large cohort of type 2 diabetic patients
- an analysis of the DiaRegis registry. Cardiovasc
Diabetol. 2011 Jul 14;10:66. doi: 10.1186/1475-2840-10-66.
- Li N, Deng Y, Wang D, Qiao Y, Li F. Determination of glibenclamide and puerarin in rat plasma by UPLC–MS/MS: Application to their pharmacokinetic interaction study. Talanta 2013; 104, 109-115. PMID: 23597896
- Sakaeda T, Tamon A, Kadoyama K, Okuno Y. Data mining of
the public version of the FDA Adverse Event Reporting
System. Int J Med Sci. 2013 Apr 25;10(7):796-803. doi:
- Yum, S. K., Kim, T., & Hwang, M. Y. (2014). Polycystic ovaries is a disproportionate signal in pharmacovigilance data mining of second generation antipsychotics. Schizophrenia research, 158(1), 275-276. PMID: 25048421
- Grigoriev I, zu Castell W, Tsvetkov P, Antonov AV. AERS
spider: an online interactive tool to mine statistical
associations in Adverse Event Reporting System.
Pharmacoepidemiol Drug Saf. 2014 Aug;23(8):795-801. doi:
10.1002/pds.3561. Epub 2014 Feb 12. http://onlinelibrary.wiley.com/doi/10.1002/pds.3561/pdf
- Etminan M. Risk of intracranial hypertension with intrauterine levonorgestrel: reply. Ther Adv Drug Saf. 2016 Feb; 7(1): 25–26.
- Guo M, Luo H, Samii A, Etminan M. Risk Of Glioblastoma With Tnf Inhibitors. Pharmacotherapy: The Journal of Human Pharmacology and Drug Therapy (2016).
- Mammo Z, Guo M, Maberley D, Matsubara J, Etminan M. Oral Bisphosphonates and Risk of Wet Age-Related Macular Degeneration. American Journal of Ophthalmology (2016).
- Poluzzi, E., Raschi, E., Piccinni, C., & De Ponti,
F. (2012). Data mining techniques in pharmacovigilance:
analysis of the publicly accessible FDA adverse event
reporting system (AERS). Data mining applications in
engineering and medicine. Croatia: InTech, 267-301. http://cdn.intechopen.com/pdfs/38579/InTech-Data_mining_techniques_in_pharmacovigilance_analysis_of_the_publicly_accessible_fda_adverse_event_reporting_system_aers_.pdf
- Susan Alexander, Karen Frith. Applied Clinical
Informatics for Nurses. NEA-BC 2014. http://books.google.de/books?isbn=1284027015
- Sharma S, Lele C. The Future of Safety Signal Detection
and Risk Management. Pharmaceutical Executive 2014. http://images2.advanstar.com/PixelMags/pharma-exec-global/pdf/2014-08.pdf
- Klose S, Schwaninger M, Verheyen F, Linder R.
Lassen sich GKV-Routinedaten für die Pharmakovigilanz nutzen?
- Tharwat 2016. http://www.johnsnowlabs.com/dataops-blog/toolset-handle-big-datasets/
News & History
- 2017-10-18: MedDRA has been incorporated into OpenVigil 2.1 and is now available
- 2016-10-10: The contingency table calculator has been expanded and announced in Frontiers in Pharmacology
- 2016-06-21: OpenVigilFDA 1.0.2 is released and announced in PLOS ONE
- 2015-11-24: openvigil.sf.net is certified to comply with the Health On the Net code (HONConduct959695)
- 2015-10-19: OpenVigilFDA 1.0 released.
- 2015-10-18: OpenVigil 2.0 and 2.1 are now available for public usage without prior registration.
- 2015-09-29: Successful validation of data extraction (OpenVigil FDA 1.0rc4) and calculations of measurements of disproportionality analyses (all software)
New online-tool to calculate arbitrary 2x2 contingency tables and measurements of disproprotionality, e.g., relative odds ratio
- 2015-08-27: OpenVigil 1 is being tested with German pharmacovigilance data
- 2015-08-26: OpenVigilFDA is available for beta-testing
- 2015-07-31: An interface to the openFDA API (OpenVigilFDA) is being developed
- 2015-07-23 The German Institute for Drug Use Evaluation (Deutsches Arzneiprüfungsinstitut e. V. (DAPI), http://www.dapi.de), Berlin, and the creators of OpenVigil (Institute of Experimental and Clinical Pharmacology and Department of Computer Science, University of Kiel) have joined their expertise and commenced to assess how pharmacoepidemiologic and pharmacovigilance data can improve signal detection for certain drug/adverse event-combinations.
The correlation of data on drug usage and adverse events might also improve estimations of the incidence of a certain drug/adverse event-association.
- 2015-07-03: New webpage with more general information on pharmacovigilance
- 2015-06-30 (Updated 2015-10-03) The ability of OpenVigil to help with clinical decisions (project title "From the Adverse Event to the most likely Culprit")
is now being evaluated at wards at the UKSH Kiel and at the hospital pharmacy at Werner Wicker Klinik, Bad Wildungen.
The goal is to find the most likely pharmacological cause of a newly occurring adverse event during pharmacotherapy.
Medical doctors and pharmacists are being trained how to systematically estimate the most likely cause of a new adverse event by using
both "eminence-based approaches" (i.e., internal SOPs which specialist or guideline to consult) and evidence-based medicine (EBM) like SIDER ( http://sideeffects.embl.de/ ),
OpenVigilFDA ("List the most likely drugs in a list of medications causing a specified adverse event and compare likelihoods") and OpenVigil 2 (reverse DPA "Frequentist methods").
During this project, the utility of this analysis method shall be evaluated (e.g., decrease of costs, adverse events or length of stay in hospital) and
a new user interface to address this clinical problem and offering easily readable output will be created (in parts done in OpenVigilFDA, pending for OpenVigil 2).
- 2015-03-11: Oral and poster presentations of OpenVigil 2 and potential uses at the annual congress of the DGPT
- 2014-09-12: OpenVigil 1.2.6b is released
Changes: Major bugfixes to importer, SQL clean-ups with speed improvements
- 2013-06-21: First public release of OpenVigil 2.0-testing
- 2012-05-08: Development of OpenVigil 2 is started
- 2012-01-13: OpenVigil 1.2.3 released and announced in Nature Biotechnology
- 2011-05-03: Project registered at SourceForge
- 2009: First pharmacovigilance-based analyses (cf. publication list) creating a need for a tool to easily access and analyse pharmacovigilance data