Strata Academy
Systematic Review Search Strategy: MEDLINE, Embase & CENTRAL
Building sensitive search strings, database selection, MeSH and Emtree, peer review, and documenting searches for PRISMA
Quick answer
A systematic review search prioritises sensitivity over precision: combine controlled vocabulary (MeSH in MEDLINE, Emtree in Embase) with free-text synonyms across MEDLINE, Embase, and Cochrane CENTRAL at minimum. Document the full strategy, dates searched, and filters in the protocol and final report (PRISMA Item 7). Peer review the string with a librarian before screening begins.
1. Sensitivity, reproducibility, and why search matters
The search strategy is the foundation of a systematic review. If relevant studies are missed, subsequent screening, risk-of-bias assessment, and meta-analysis cannot recover them — the review inherits selection bias from the outset.
Cochrane methods distinguish sensitivity (finding all relevant records) from precision (minimising irrelevant hits). For systematic reviews, sensitivity wins. A search returning 8,000 references after deduplication is normal; screening applies eligibility criteria later.
Every search must be reproducible: another team should be able to run the same strategy and obtain comparable results. That requires documented databases, full strings, date limits, language filters, and search dates.
Before you open a database, stabilise your review question. Draft your PICO using the free PICO builder at /tools/pico-builder — population, intervention, comparator, and outcomes should map directly to search blocks. A vague question produces a vague string and ambiguous screening.
2. Core databases: MEDLINE, Embase, and CENTRAL
MEDLINE (via Ovid, EBSCO, or PubMed with documented syntax) indexes biomedical journal literature with MeSH headings. It remains the primary source for most clinical reviews but does not comprehensively cover European journals, many conference abstracts, or drug trade names.
Embase adds Emtree thesaurus terms, broader European coverage, and conference proceedings. For pharmacological interventions, device trials, or reviews where Embase is accessible through your institution, searching both MEDLINE and Embase is standard.
Cochrane CENTRAL (Cochrane Central Register of Controlled Trials) aggregates trial reports from multiple sources including handsearching. It is essential for intervention reviews and often surfaces trials not indexed elsewhere.
Beyond the core trio, add databases matched to your question: CINAHL for nursing and allied health, PsycINFO for mental health, AMED for complementary medicine, trial registries (ClinicalTrials.gov, ISRCTN, WHO ICTRP), and grey literature sources where pre-specified in the protocol.
3. Building the search string
Organise the strategy into concept blocks aligned with PICO elements. Population and intervention blocks usually carry the most synonyms; comparator is often omitted from the search (screening handles it). Outcome terms are included when they improve sensitivity without exploding the yield unmanageably.
Within each block, combine synonyms with OR. Combine blocks with AND. Use truncation ($ or * depending on platform) and adjacency operators where supported. Document which operator syntax applies — Ovid MEDLINE differs from PubMed.
For MeSH, explode broader headings where appropriate and include specific subheadings (e.g. /drug therapy). Pair each MeSH term with a free-text search in title/abstract to capture records not yet indexed. Repeat the pattern with Emtree in Embase — MeSH and Emtree are not identical.
Add a study design filter only if pre-specified and validated for your topic. Cochrane highly sensitive RCT filters exist but may miss quasi-randomised trials; document any filter and run sensitivity analyses without it if yield is low.
- Block 1 — population (diagnosis, condition, setting)
- Block 2 — intervention or exposure (generic and trade names)
- Block 3 — optional outcome terms if they improve sensitivity
- Block 4 — study design filter (if validated and pre-specified)
- Document line numbers for each database export
4. Peer review and librarian involvement
The PRESS (Peer Review of Electronic Search Strategies) checklist recommends independent review of search strategies before execution. University librarians trained in systematic review methods can identify missing synonyms, incorrect MeSH explosions, and syntax errors that students miss.
Provide your librarian with the registered protocol, PICO, and any preliminary strings. Request feedback on concept blocks, not just spelling. If your institution offers a systematic review service, use it early — rework after screening is far costlier.
For coursework, a documented email exchange or meeting notes with a librarian satisfies reproducibility expectations better than an undocumented solo search.
5. Supplementary search methods
Database searching alone rarely achieves 100% sensitivity. Cochrane recommends citation searching (forward and backward from included studies), handsearching key journals or conference proceedings, and contacting experts where appropriate.
Reference lists of included studies and relevant systematic reviews should be screened. Forward citation tracking (e.g. via Web of Science or OpenAlex) finds newer papers citing your included set.
Trial registry searches identify ongoing or unpublished studies. Grey literature — theses, regulatory documents, conference abstracts — is covered in our dedicated grey literature guide and should be pre-specified, not added post hoc.
- Backward citation — reference lists of included studies
- Forward citation — who cited your included studies
- Handsearching — target journals missed by indexing
- Expert contact — document who was contacted and responses
- Grey literature — see grey-literature guide for thesis and report searching
6. Documenting and reporting the search (PRISMA)
PRISMA 2020 Item 7 requires reporting of all information sources, search dates, and full search strategies for at least one major database. PRISMA-S extends this with structured tables for each database, platform, and supplementary method.
Export results from each database with counts before and after deduplication. Record the reference manager or review software used (Covidence, Rayyan, EndNote). Note any limits applied — date, language, publication type — and justify them in the protocol.
If the review process exceeds 12 months, re-run searches before final submission and document the update search in an appendix. Report how many new records entered screening and whether any changed conclusions.
Structured search documentation is a core competency tested in the Strata Academy certificate course at /academy/course — Part A covers protocol design and Part B walks through screening and synthesis with supervisor-ready outputs.
7. Common student errors
Copying a search string from a published review without adapting concepts to your PICO. Published strings reflect someone else's question, date limits, and database access.
Over-restricting with outcome terms in the search when outcomes were not consistently indexed in primary studies — this drops relevant trials that report unexpected secondary endpoints.
Failing to deduplicate across databases before screening, inflating PRISMA counts and wasting reviewer time.
Reporting 'PubMed search' without the actual string. Examiners and journal reviewers expect appendices with full reproducible strategies.
Interactive version (quizzes, walkthroughs) loads when JavaScript is enabled.