| Literature DB >> 30271302 |
Wichor M Bramer1, Gerdien B de Jonge2, Melissa L Rethlefsen3, Frans Mast2, Jos Kleijnen4.
Abstract
Creating search strategies for systematic reviews, finding the best balance between sensitivity and specificity, and translating search strategies between databases is challenging. Several methods describe standards for systematic search strategies, but a consistent approach for creating an exhaustive search strategy has not yet been fully described in enough detail to be fully replicable. The authors have established a method that describes step by step the process of developing a systematic search strategy as needed in the systematic review. This method describes how single-line search strategies can be prepared in a text document by typing search syntax (such as field codes, parentheses, and Boolean operators) before copying and pasting search terms (keywords and free-text synonyms) that are found in the thesaurus. To help ensure term completeness, we developed a novel optimization technique that is mainly based on comparing the results retrieved by thesaurus terms with those retrieved by the free-text search words to identify potentially relevant candidate search terms. Macros in Microsoft Word have been developed to convert syntaxes between databases and interfaces almost automatically. This method helps information specialists in developing librarian-mediated searches for systematic reviews as well as medical and health care practitioners who are searching for evidence to answer clinical questions. The described method can be used to create complex and comprehensive search strategies for different databases and interfaces, such as those that are needed when searching for relevant references for systematic reviews, and will assist both information specialists and practitioners when they are searching the biomedical literature.Entities:
Mesh:
Year: 2018 PMID: 30271302 PMCID: PMC6148622 DOI: 10.5195/jmla.2018.283
Source DB: PubMed Journal: J Med Libr Assoc ISSN: 1536-5050
Figure 1Schema for determining the optimal order of elements
Field codes in five most used interfaces for biomedical literature searching
| PubMed | Ovid | EBSCOhost | Embase.com | ProQuest | |
|---|---|---|---|---|---|
| Title/abstract | [tiab] | ().ab,ti. | TI () OR AB () | ():ab,ti | AB,TI() |
| All fields | [All Fields] | .af. | ALL | ||
| Thesaurus term | [mesh:noexp] | …/ | MH “…” | ‘…’/de | MESH(…) |
| Including narrower | [mesh] | exp …/ | MH “…+” | ‘…’/exp | MESH#(…) |
| Combined subheading | exp …/ | MH “…+/ | ‘…’/exp/dm_ | MESH(… LNK ..) | |
| Free subheading | [sh] | .xs. or .fs. | MW | :lnk | |
| Publication type | [pt] | .pt. or exp | PT | :it | RTYPE |
| Proximity | ADJn | Nn | NEAR/n-NEXT/n | N/n | |
| Exact phrase | “double quotes” | No quotes needed | “double quotes” | ‘single quotes’ | “double quotes” |
| Truncated phrase | Use-hyphen* | No quote* | No quote* | ‘single quote*’ | “Double quote*” |
| Truncation | End | End/ mid | End/ mid | End/ mid | End / mid / start |
| Infinite | * | * or $ | * | * | * |
| 0 or 1 character | — | ? | # | — | $1 |
| 1 character | — | # | ? | ? | ? |
| Added to database since | yyyy/mm/dd:yyyy/mm/dd [edat] | limit #N to rd=yyyymmdd-yyyymmdd | EM yyyymmdd-yyyymmdd | [dd-mm-yyyy]/sd | LUPD(yyyymmdd) |
| Publication period (years) | yyyy:yyyy[dp] | limit #N to yr=yyyy-yyyy | PY yyyy-yyyy | [yyyy-yyyy]/py | YR (yyyy-yyyy) |
| Record sets | #1 | 1 | S1 | #1 | S1 |
In PubMed, [tiab] should be placed after each search term.
EBSCOhost does not allow a combination of fields; all search terms for the title field need to be repeated for the abstract field.
EBSCOhost and Embase.com do not use an “all fields” code; a term without a field code is searched in all fields.
Subheadings in Embase.com are only applied to diseases (/dm_), drugs (/dd_), or devices (/dv_).
[sh] and .xs. include narrower terms for subheadings; .fs. and :lnk do not.
In PubMed, proximity searching is not available; search the exact phrase (truncated or between double quotes) or use the Boolean “AND” combination.
[pt] and exp …/ includes narrower publication types; .pt. and :it do not.
The question mark does not work in combination with field codes.
The field [edat] refers to the entry date, when the record was added to PubMed. [mhda] refers to the MeSH date, when the record was last edited.
Adding a date limit can only be applied in a separate record set.
If a number is to be searched in the text, it should be put between double quotes (e.g., “1”).
Figure 2Schematic representation of translation between databases used at Erasmus University Medical Center
Dotted lines represent databases that are used in less than 80% of the searches.