FREE TOOL
Search strategy translator
Build concepts with OR terms, combine concepts with AND, then translate the query into common database syntax. Nothing is sent to a server.
Terms in a concept are combined with OR; concept groups with AND.
Translated queries
⚠ "clinical trial" in "Population": truncation applies to a single-word root, not a multi-word phrase - PubMed may not interpret this as intended.
⚠ "clinical trial" in "Population": truncation applies to a single-word root, not a multi-word phrase - Embase may not interpret this as intended.
⚠ "clinical trial" in "Population": truncation applies to a single-word root, not a multi-word phrase - Scopus may not interpret this as intended.
⚠ "clinical trial" in "Population": truncation applies to a single-word root, not a multi-word phrase - Cochrane CENTRAL may not interpret this as intended.
⚠ "clinical trial" in "Population": truncation applies to a single-word root, not a multi-word phrase - Web of Science may not interpret this as intended.
How translation works
Each concept group joins its terms with OR; groups are joined with AND. The translator applies database field tags, quote marks, and trailing truncation according to the syntax implemented in EvidenceFlow.
Search-platform rules can change, and database interfaces may interpret syntax differently. Verify every translated strategy in the target database and document the exact platform and date searched before using it in a review.
FAQ
Frequently asked questions
Which databases are supported?+
PubMed, Embase.com, Scopus, Cochrane CENTRAL, and Web of Science.
Does the translator search the databases?+
No. It formats a Boolean query locally; it does not execute searches or retrieve records.
Can truncation be applied to phrases?+
The tool only adds a trailing wildcard to single-word terms. It displays a warning if truncation is selected for a multiword phrase.
After searching, manage imported records, screening, extraction, and reporting together in EvidenceFlow.
Start free project