VibeRoundsThis course is built in the spirit of VibeRounds — Socratic learning (AI that questions rather than answers) and Guided Discovery, part of the wider Clinical Cognition Operating System.
Evidence-Based Medicine · Course for Techies
Lesson 4: Systematic Reviews & Meta-Analyses
Part 4 — one trial is a data point. A systematic review is what happens when you stop trusting any single data point.
In Lesson 3 you appraised a single RCT. But no single trial is ever the final word — it has its own sample, its own setting, its own quirks. A systematic review tries to find every relevant trial on a question, appraise them with the same rigor you learned in Lesson 3, and combine them into one answer. When that combination is done statistically, it's called a meta-analysis.
Why this matters for techies: think of individual trials as noisy sensor readings. One reading might be biased by a faulty sensor (a flawed trial) or just random noise (small sample size). A systematic review is signal averaging — but only if you've first thrown out the broken sensors, which is why appraisal still comes before pooling.
Systematic Review vs. Ordinary Literature Review
Not everything called a "review" is a systematic review. The difference is method, not just topic:
Ordinary (narrative) review
Systematic review
Author picks papers they know or find convenient
Pre-registered, explicit search strategy across multiple databases
No fixed inclusion/exclusion criteria
Defined PICO-based inclusion/exclusion criteria, set in advance
Selection and conclusions can reflect the author's prior views
Reproducible methodology; two reviewers screen independently
Rarely appraises quality of included studies systematically
Every included study is formally appraised for risk of bias
A systematic review doesn't have to include a meta-analysis — sometimes the included studies are too different to combine numerically, and the review just summarizes them narratively (this is sometimes done, and is still valuable, but weaker than a pooled estimate).
Reading a Forest Plot
A forest plot is the standard way to visualize a meta-analysis: each row is one trial, and the diamond at the bottom is the pooled result across all of them.
Illustrative Forest Plot — Effect of Drug X on Stroke Risk
Study
Relative Risk (95% CI)
Weight
Trial A (2018)
18%
Trial B (2019)
27%
Trial C (2020)
12%
Trial D (2021)
31%
Trial E (2022)
12%
Pooled
100%
← favors Drug XRR = 1.0 (no effect)favors control →
How to read it:
The vertical center line represents "no difference" (relative risk = 1.0). If a trial's confidence interval crosses this line, that trial alone didn't reach statistical significance.
Each dot is a trial's point estimate; the line through it is its 95% confidence interval. A wider line means a smaller, less precise trial.
Box/dot size roughly reflects weight — bigger trials with more events usually get more influence over the pooled result.
The diamond at the bottom is the pooled estimate; its width is the pooled confidence interval. Because it combines all the data, it's almost always narrower (more precise) than any single trial.
In the plot above, every individual trial's confidence interval touches or crosses the line of no effect — none was significant alone. But the pooled diamond sits clearly to the left of it. This is the whole point of meta-analysis: several underpowered trials pointing the same direction can add up to a confident answer.
For non-medical readers: think of each trial as one A/B test run on a different, smaller sample. None alone gave statistical confidence, but averaging results (weighted by sample size) is like merging several underpowered experiments into one well-powered one — the "diamond" is essentially a weighted mean with its own recalculated confidence interval.
Heterogeneity: When Is It Fair to Pool?
Averaging only makes sense if the trials are answering roughly the same question. Heterogeneity is the term for how much trials disagree beyond what you'd expect from chance alone.
Clinical heterogeneity — different populations, doses, follow-up durations, or outcome definitions across trials.
Statistical heterogeneity — measured by the I² statistic, which estimates the percentage of variation across trials due to real differences rather than random chance.
I² value
Rough interpretation
0–40%
Might not be important; trials are reasonably consistent
30–60%
May represent moderate heterogeneity
50–90%
May represent substantial heterogeneity
75–100%
Considerable heterogeneity — pooling may not be meaningful
High heterogeneity doesn't automatically mean "don't pool" — but it does mean you should ask why trials disagree (different doses? different patient ages?) before trusting the single pooled number, and a random-effects model (which assumes true effects vary across settings) is usually more honest than a fixed-effect model (which assumes one true effect everywhere) when I² is high.
Funnel Plots and Publication Bias
Studies with exciting, positive results are more likely to get published than "boring" null results — which can bias a meta-analysis toward overstating an effect. A funnel plot checks for this: plot each trial's effect size against its precision (or sample size). With no publication bias, trials should scatter symmetrically around the pooled estimate, forming a rough funnel/triangle shape — small trials scattered widely at the bottom, large trials tightly clustered near the top.
If small studies are missing from one side of the funnel — typically the side showing a null or negative result — that gap is a red flag for publication bias: small "boring" trials may have been left unpublished, skewing the pooled result.
Appraising a Systematic Review Itself
The three-question framework from Lesson 3 still applies — just aimed at the review, not a single trial:
Are the results valid? Was the search comprehensive (multiple databases, no language restriction)? Was study selection and quality appraisal done by at least two independent reviewers? Were the included studies actually similar enough to combine?
What are the results? What's the pooled effect size and confidence interval? How much heterogeneity was there, and was it explored (subgroup or sensitivity analysis)?
Will this help my patient? Do the included trials' populations resemble your patient? Were all patient-important outcomes covered, not just the ones easiest to pool?
AMSTAR-2 and PRISMA are the two most widely used formal checklists here: AMSTAR-2 rates the methodological quality of a review, while PRISMA is a reporting checklist authors are expected to follow when writing one up. Reviewers use AMSTAR-2; authors (and readers checking completeness) use PRISMA.
Homework for Lesson 4
Find a systematic review or meta-analysis relevant to the clinical question you've been building since Lesson 2 (search PubMed with a "systematic review" or "meta-analysis" publication-type filter).
Locate its forest plot. Identify: how many trials were pooled, whether any individual trial's CI crossed the line of no effect, and what the pooled diamond shows.
Find the reported I² value. Based on the table above, how much heterogeneity was there, and does the review explain why (if at all)?
One paragraph: would you trust this pooled result enough to change how you'd treat your patient from Lesson 1?