One of the most common errors in systematic review search strategies is copying a PubMed search and pasting it directly into Embase or CINAHL. Each database uses different syntax, different field tags, different subject heading systems, and sometimes different truncation or proximity operators. A search that works perfectly in PubMed may retrieve zero results or wildly different results in another database if it is not properly translated.
Subject heading translation is the most important step. Replace every MeSH term with its Emtree equivalent when moving to Embase. Use the Emtree browser to find the corresponding preferred term, it is not always a direct one-to-one match. Some MeSH terms map to multiple Emtree terms, and some Emtree terms have no direct MeSH equivalent. Similarly, when translating to CINAHL, replace MeSH terms with CINAHL Subject Headings.
Field tag translation requires changing the syntax that tells the database where to search. In PubMed, "[MeSH Terms]" searches the MeSH field. In Embase on Ovid, the equivalent is ".sh." or "/exp" on the Embase.com interface. In CINAHL on EBSCO, it is "(MH "term")". These differences seem minor but cause search failures when overlooked.
Truncation and wildcards are generally consistent across databases (the asterisk * is nearly universal), but proximity operators vary significantly. PubMed does not support proximity searching at all. Embase uses NEAR/n and NEXT/n. CINAHL on EBSCO uses Nn and Wn. Web of Science uses NEAR/n. If your PubMed search relies on phrase searching, you may want to use proximity operators in databases that support them to capture variations in word order.
Boolean operator handling is consistent across all major databases, AND, OR, and NOT work the same way, but the order of operations and nesting with parentheses can produce different results if not carefully managed. Always use explicit parentheses to control the logic of your search, and never rely on a database's default operator precedence.
A practical approach is to build and validate your search in PubMed first, then create a translation table that maps every PubMed element to its equivalent in each target database. This systematic translation process ensures nothing is lost in conversion and makes your search documentation complete for PRISMA 2020 reporting.
Our free free search translation tool automates much of this process, converting PubMed syntax into Embase, CINAHL, and Cochrane Library formats with the appropriate field tags and subject headings.
A search strategy should never be executed without validation. Just as a manuscript undergoes peer review before publication, a search strategy should undergo peer review before execution. The PRESS (Peer Review of Electronic Search Strategies) checklist, developed by McGowan et al. (2016), is the gold standard tool for this purpose.
PRESS provides a structured framework for evaluating six domains of search quality:
1. Translation of the research question. Does the search strategy accurately reflect the research question? Are all PICO elements represented? Has any concept been omitted or inadequately represented?
2. Boolean and proximity operators. Are AND, OR, and NOT used correctly? Is the logic sound? Are parentheses used appropriately to group terms within concept blocks?
3. Subject headings. Are the correct MeSH terms, Emtree terms, or other subject headings used? Are explosion (broader searching) and subheadings applied appropriately? Are any relevant subject headings missing?
4. Text word searching (free text). Are sufficient synonyms, spelling variations, abbreviations, and acronyms included? Is truncation applied correctly to capture word variants without introducing irrelevant terms?
5. Spelling, syntax, and line numbers. Are there typographical errors? Are field tags correct for the database being searched? Do line number references in combined searches point to the correct lines?
6. Limits and filters. Are any limits or filters applied? If so, are they justified? Could they introduce bias by excluding relevant studies?
The PRESS process involves having a second researcher, ideally an information specialist or librarian, review your search strategy against these six domains and provide written feedback. Studies have shown that PRESS peer review identifies errors in the majority of search strategies submitted for review, including errors that would have resulted in missed relevant studies (McGowan et al., 2016).
Beyond PRESS, you should validate your search empirically by testing it against a set of known relevant studies. Before finalizing your strategy, identify five to ten studies that you know are relevant to your research question, studies found during scoping searches, cited in previous reviews, or recommended by subject experts. Run your search and verify that it retrieves all of these studies. If any known relevant study is missing, analyze why and adjust your strategy accordingly.
This validation step is the closest thing to a quality assurance test for your search. If your strategy cannot find studies you already know exist, it is almost certainly missing other relevant studies you do not yet know about.
Even experienced researchers make errors in search strategy construction. Understanding the most frequent mistakes helps you avoid them and builds a stronger, more defensible search.
Using only free-text terms without subject headings. Researchers who are unfamiliar with MeSH or Emtree often search only title and abstract fields with their own terminology. This misses studies indexed under different terms and fails to exploit the standardized vocabulary that makes database searching powerful. Always combine subject headings with free-text terms.
Failing to explode subject headings. In PubMed, searching a MeSH term without explosion retrieves only studies indexed under that exact heading. Exploding the term retrieves studies indexed under that heading and all narrower headings in the MeSH hierarchy. For most systematic review searches, explosion is appropriate and significantly increases sensitivity.
Copying searches between databases without translation. As discussed above, each database has unique syntax, field tags, and subject heading systems. Pasting a PubMed search into Embase without replacing MeSH terms with Emtree equivalents and adjusting field tags will produce an incomplete and unreliable search.
Using NOT to narrow results. The NOT operator excludes records containing a specified term, but it can inadvertently remove relevant studies. A study about "diabetes NOT gestational" will exclude any study that mentions gestational diabetes anywhere in its record, even if the study is primarily about type 2 diabetes and only mentions gestational diabetes in passing. The Cochrane Handbook recommends avoiding NOT unless absolutely necessary and carefully evaluating its impact on sensitivity.
Applying unjustified date or language limits. Restricting to English-language publications or to studies published after a certain date introduces bias unless there is a specific methodological justification. Peer reviewers routinely flag unjustified limits as a weakness.
Inadequate documentation. Many researchers record their search terms but not the complete search string with Boolean operators, field tags, and line numbers. PRISMA 2020 requires the full, executable search strategy, not a summary or paraphrase. Without complete documentation, the search cannot be reproduced, and the review's validity is undermined.
Neglecting grey literature. Published studies represent a biased sample of all research conducted, because studies with positive results are more likely to be published. Searching grey literature sources, clinical trial registries (ClinicalTrials.gov, WHO ICTRP), conference proceedings, theses and dissertations, and organizational reports, helps mitigate publication bias. The Cochrane Handbook recommends grey literature searching as a standard component of comprehensive systematic review searches.
Not involving a librarian or information specialist. The Cochrane Handbook explicitly recommends that systematic review teams include or consult an information specialist for search strategy development. Librarians are trained in database syntax, subject heading systems, search validation, and documentation standards. Studies comparing librarian-developed and researcher-developed searches consistently find that librarian searches are more comprehensive and contain fewer errors.
PRISMA 2020 (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) requires transparent reporting of search strategies as a core component of systematic review methodology (Page et al., 2021). Proper documentation serves three purposes: it enables reproducibility, it demonstrates rigor, and it satisfies journal and Cochrane submission requirements.
For each database searched, you must document:
The complete search string, every term, field tag, Boolean operator, and line number, exactly as executed. Do not paraphrase, summarize, or simplify. The reader should be able to copy your search string, paste it into the database, and retrieve the same results (subject to database updates since your search date).
The database name and interface, specify not just "MEDLINE" but "MEDLINE via Ovid" or "PubMed via pubmed.ncbi.nlm.nih.gov." The same database can produce different results depending on the interface used, because interfaces may implement search features differently.
The date the search was executed, record the exact date for each database. If you run updated searches before manuscript submission, document those dates and results separately.
The number of records retrieved, report the raw count before deduplication. This number, combined with the search string, allows readers to assess the scope and sensitivity of your search.
PRISMA 2020 recommends presenting the full search strategy for at least one database in the main manuscript or supplementary materials. Many journals now require full search strategies for all databases. The PRISMA-S extension (Rethlefsen et al., 2021) provides additional guidance specific to search reporting, including recommendations for documenting grey literature searches, hand-searching, and citation searching.
Maintaining a search log throughout the process, recording every iteration, modification, and rationale, makes PRISMA documentation straightforward. Without contemporaneous records, reconstructing your search history months later for manuscript preparation is error-prone and time-consuming.
For additional guidance on extracting and organizing the data your search retrieves, see our data extraction for systematic reviews guide. And for an overview of what to expect when working with a professional team on your review, read our guide on what to expect from a systematic review writing service.
Building a comprehensive, reproducible search strategy is one of the most technically demanding tasks in systematic review methodology. It requires familiarity with controlled vocabularies, Boolean logic, database-specific syntax, and validation frameworks, skills that take years to develop and that most researchers use infrequently enough that each new review requires relearning.
The process follows a clear sequence: define your PICO, generate comprehensive synonym lists, identify subject headings in each database's controlled vocabulary, combine terms with Boolean operators, translate the strategy across all target databases, validate with PRESS peer review and known-study testing, and document everything for PRISMA 2020 compliance.
The investment in a rigorous search strategy pays dividends throughout the review. A comprehensive search reduces the risk of bias in your findings. A well-documented search satisfies peer reviewers and journal requirements. A validated search gives you confidence that your results are based on the best available evidence.
Whether you build your search strategy independently, with the help of a librarian, or with professional support, the principles remain the same: be comprehensive, be systematic, be transparent, and be reproducible. Those four qualities are what distinguish a credible systematic review from a selective literature summary, and they all begin with the search strategy.
A comprehensive search extends beyond indexed databases. Our guide to grey literature sources for systematic reviews covers where and how to find unpublished studies.
After running your search, the screening phase requires dual review. Learn why you need a second reviewer for screening and how to manage disagreements.
To handle large search yields efficiently, consider using AI tools that accelerate screening and extraction.
After building your PubMed strategy, you need to adapt it for other databases. Our guide on translating searches between PubMed, Embase, and Cochrane covers syntax differences.
