MétaCan
Menu
Back to cohort
Record W2106705776 · doi:10.1111/hir.12004

Utilisation of search filters in systematic reviews of prognosis questions

2012· article· en· W2106705776 on OpenAlex
Trish Chatterley, Liz Dennett

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueHealth Information & Libraries Journal · 2012
Typearticle
Languageen
FieldDecision Sciences
TopicMeta-analysis and systematic reviews
Canadian institutionsInstitute of Health EconomicsUniversity of Alberta
Fundersnot available
KeywordsLimitingMEDLINEMedicineFilter (signal processing)Information retrievalComputer scienceMedical physics

Abstract

fetched live from OpenAlex

BACKGROUND: Search filters are designed to increase efficiency of information retrieval and can be particularly useful in limiting the large numbers of articles retrieved for systematic reviews (SRs). Existing published prognosis search filters (or hedges) have lower sensitivity and precision values than their therapy counterparts. OBJECTIVES: Taking into account the relatively poor performance of prognosis filters, this study seeks to identify which methods of limiting search results to prognostic studies are most often used by SR teams. METHODS: One hundred and three SRs of prognostic studies published in 2009 and indexed in MEDLINE were retrieved. Each review's search strategy was reviewed and prognosis-related search terms were extracted. RESULTS: Forty-seven of 103 studies used prognosis-related terms to limit the search. Six SRs of 103 did not specify their search terms, and the remaining 50 SRs used content terms only (no terms related to methodology or prognosis). Of the 47 strategies using prognosis-related terms, only six used a published filter. Many SRs used few or poorly selected prognosis-related search terms which are unlikely to provide the sensitivity generally sought for SRs. CONCLUSIONS: Published prognosis search filters are used in only a small minority of prognosis SRs.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.160
metaresearch head score (Gemma)0.032
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Insufficient payload (model declined to judge)
Consensus categoriesMetaresearch
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.624
Threshold uncertainty score0.998

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.1600.032
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0030.001
Bibliometrics0.0010.002
Science and technology studies0.0000.000
Scholarly communication0.0000.006
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.769
GPT teacher head0.532
Teacher spread0.236 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it