The Reporting Odds Ratio (ROR) is a frequentist disproportionality measure representing the odds of a specific adverse event being reported with a particular drug compared to the odds of that event being reported with all other drugs. It is calculated from a 2x2 contingency table of case counts, where a value greater than 1 indicates a higher reporting frequency than expected, flagging a potential safety signal for further clinical review.
Glossary
Reporting Odds Ratio (ROR)

What is Reporting Odds Ratio (ROR)?
A foundational frequentist statistic used in pharmacovigilance data mining to quantify the strength of a statistical association between a specific drug and a specific adverse event within a spontaneous reporting database.
Unlike Bayesian methods such as the Empirical Bayes Geometric Mean (EBGM), the ROR does not apply statistical shrinkage to adjust for low-count drug-event combinations, making it more sensitive but also more prone to generating false-positive signals from sparse data. It is commonly applied alongside the Proportional Reporting Ratio (PRR) in exploratory analyses of databases like FAERS and EudraVigilance.
Key Statistical Properties of ROR
The Reporting Odds Ratio (ROR) is a foundational disproportionality statistic in pharmacovigilance. Understanding its statistical properties—including its calculation, confidence intervals, and susceptibility to bias—is essential for interpreting signal detection results from spontaneous reporting databases like FAERS and VigiBase.
The 2x2 Contingency Table
ROR is calculated from a 2x2 contingency table that cross-classifies reports by drug and event presence:
- a: Reports with the target drug AND target adverse event
- b: Reports with the target drug WITHOUT the target event
- c: Reports WITHOUT the target drug WITH the target event
- d: Reports WITHOUT the target drug AND WITHOUT the target event
The formula is: ROR = (a / b) / (c / d) = (a × d) / (b × c). This represents the odds of the event occurring with the drug relative to the odds of it occurring without the drug.
Confidence Interval Estimation
The precision of an ROR estimate is quantified using a 95% confidence interval (CI). The standard error of the natural logarithm of ROR is:
SE(ln ROR) = √(1/a + 1/b + 1/c + 1/d)
The 95% CI is then: exp(ln ROR ± 1.96 × SE)
A signal of disproportionate reporting (SDR) is typically defined when the lower bound of the 95% CI exceeds 1.0, indicating a statistically significant elevation above the null value.
Susceptibility to Small-Cell Bias
ROR is highly sensitive to sparse data. When any cell in the 2x2 table contains a very low count (especially zero), the ROR can become unstable or undefined:
- A single report in cell a with zero reports in cell c produces an infinite ROR
- Small fluctuations in low-count cells cause dramatic swings in the point estimate
- This volatility generates false-positive signals that waste reviewer resources
For this reason, many pharmacovigilance systems apply a minimum cell count threshold (e.g., n ≥ 3) before calculating ROR.
Comparison with Bayesian Methods
Unlike Bayesian approaches such as the Empirical Bayes Geometric Mean (EBGM), ROR does not apply shrinkage to adjust for sampling variability:
- ROR: Unshrunk, frequentist estimate; high sensitivity but low specificity with sparse data
- EBGM: Shrinks estimates toward the null based on the prior distribution of all drug-event pairs
- PRR: Similar to ROR but uses proportions instead of odds; shares the same small-cell instability
ROR is often used as a screening tool alongside Bayesian methods, with EBGM providing a more conservative, confirmatory estimate.
Confounding and Masking Effects
ROR calculations can be distorted by confounding by indication and masking:
- Confounding by indication: The underlying disease, not the drug, causes the event. For example, a high ROR for insulin and hypoglycemia reflects the diabetic condition, not a safety signal.
- Masking: A drug with an extremely strong, known association (e.g., warfarin and hemorrhage) inflates the background rate, obscuring signals for other drugs.
Stratification by age, sex, and concomitant medications can partially mitigate these biases.
Subgroup Disproportionality Analysis
ROR can be calculated within stratified subgroups to identify effect modification:
- Age-stratified ROR: Detects signals specific to pediatric or geriatric populations
- Sex-stratified ROR: Identifies differential risk profiles between males and females
- Reporter-stratified ROR: Compares signals from healthcare professionals versus consumer reports
Subgroup analysis increases the granularity of signal detection but reduces cell counts, exacerbating small-cell bias. Interaction terms in logistic regression models offer an alternative approach.
ROR vs. Proportional Reporting Ratio (PRR)
A technical comparison of the two foundational frequentist disproportionality statistics used in spontaneous reporting database mining for pharmacovigilance signal detection.
| Feature | Reporting Odds Ratio (ROR) | Proportional Reporting Ratio (PRR) | Key Distinction |
|---|---|---|---|
Core Formula | ROR = (a/c) / (b/d) | PRR = [a/(a+b)] / [c/(c+d)] | ROR uses odds; PRR uses rates |
Contingency Table Basis | Odds ratio framework | Rate ratio framework | Mathematical structure differs |
Null Value (No Signal) | 1.0 | 1.0 | Identical null hypothesis |
Signal Threshold (Common) | Lower 95% CI > 1 and a ≥ 3 | PRR ≥ 2, Chi-square ≥ 4, and a ≥ 3 | ROR adds confidence interval criterion |
Sensitivity to Low Counts | Higher variance with sparse cells | Higher variance with sparse cells | Both unstable with n < 5 |
Handling of Zero Cells | Requires continuity correction (0.5) | Requires continuity correction (0.5) | Identical correction method |
Confidence Interval | Calculated via ln(ROR) ± 1.96 × SE | Not typically reported | ROR provides precision estimate |
Regulatory Adoption | Used by EMA EudraVigilance | Used by UK MHRA and historically by WHO | Jurisdictional preference varies |
Interpretability | Odds of event with drug vs. without | Rate of event with drug vs. without | PRR more intuitive to non-statisticians |
Bias Susceptibility | Susceptible to confounding by indication | Susceptible to confounding by indication | Neither corrects for confounding |
Frequently Asked Questions
Clear, technically precise answers to the most common questions about the Reporting Odds Ratio (ROR) and its application in pharmacovigilance signal detection.
The Reporting Odds Ratio (ROR) is a frequentist disproportionality statistic representing the odds of a specific adverse event being reported with a particular drug compared to the odds of that event being reported with all other drugs in a spontaneous reporting database. It is calculated from a 2x2 contingency table where a is the number of reports for the drug-event combination of interest, b is reports for the drug with all other events, c is reports for the event with all other drugs, and d is reports for all other drug-event combinations. The formula is ROR = (a/c) / (b/d), which simplifies to (a*d) / (b*c). A ROR greater than 1.0 suggests a higher reporting frequency than expected, potentially indicating a safety signal. The 95% confidence interval is calculated using the natural logarithm of the ROR and its standard error: SE(ln ROR) = sqrt(1/a + 1/b + 1/c + 1/d).
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Core statistical measures and data sources used alongside the Reporting Odds Ratio for comprehensive disproportionality analysis in drug safety signal detection.
Bayesian Shrinkage
A statistical technique that shrinks observed disproportionality scores toward a null value to reduce the risk of flagging false-positive signals from drug-event combinations with very low report counts. This directly addresses a key limitation of the ROR.
- Mechanism: Applies a prior distribution that pulls extreme estimates toward the mean
- Benefit: Stabilizes ROR estimates when cell counts are < 5
- Implementation: Used in EBGM and Information Component (IC) calculations
- Trade-off: May mask true signals with very sparse data
Confounding by Indication
A critical bias in pharmacovigilance where the underlying disease being treated, rather than the drug itself, is the true cause of an observed adverse event. This confound can inflate ROR values and generate spurious safety signals.
- Example: Higher rates of myocardial infarction with diabetes drugs may reflect the disease, not the medication
- Mitigation: Stratified analysis, restriction to specific indications, or active comparator designs
- Impact on ROR: Can produce elevated disproportionality scores that fail causality assessment

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us