Browse › Natural Language Processing › PICO › EBM PICO
EBM PICO Benchmark (PICO)
The proliferation of healthcare data has contributed to the widespread usage of the PICO paradigm for creating specific clinical questions from RCT.
PICO is a mnemonic that stands for:
Population/Problem: Addresses the characteristics of populations involved and the specific characteristics of the disease or disorder. Intervention: Addresses the primary intervention (including treatments, procedures, or diagnostic tests) along with any risk factors. Comparison: Compares the efficacy of any new interventions with the primary intervention. Outcome: Measures the results of the intervention, including improvements or side effects. PICO is an essential tool that aids evidence-based practitioners in creating precise clinical questions and searchable keywords to address those issues. It calls for a high level of technical competence and medical domain knowledge, but it’s also frequently very time-consuming.
Automatically identifying PICO elements from this large sea of data can be made easier with the aid of machine learning (ML) and natural language processing (NLP). This facilitates the development of precise research questions by evidence-based practitioners more quickly and precisely.
Empirical studies have shown that the use of PICO frames improves the specificity and conceptual clarity of clinical problems, elicits more information during pre-search reference interviews, leads to more complex search strategies, and yields more precise search results.
The archive carries no text for this table; the description above is the archive's text for the task PICO. archive 2025-07-28
Over time archive 2025-07-28
The chart needs JavaScript; the table below carries every value.
Direction inferred from the metric name, not from the archive: Macro F1 word level (higher is better). Points are placed at the row's paper date; 3 of 3 rows carry one.
Results archive 2025-07-28
Archive rows end at the archive snapshot, 2025-07-28: no result published after that date is in this table. Rank is the archive's row order at that snapshot; not re-ranked here. Metric values are the archive's strings. Column headers sort the table in your browser; each row keeps its archive rank.
| Paper | Code | Ran Syntology | Report | |||||
|---|---|---|---|---|---|---|---|---|
| 1 | BioLinkBERT (large) | 74.19 | – | Paper | Code | 2022 | 0 of 14 ran · 14 unverified | report |
| 2 | BioLinkBERT (base) | 73.97 | – | Paper | Code | 2022 | 0 of 14 ran · 14 unverified | report |
| 3 | PubMedBERT uncased | 73.38 | – | Paper | Code | 2020 | linked, not harvested | report |
All 3 rows shown. 3 link to a paper page on this site; 0 are marked as using additional training data in the archive. No GitHub stars are tracked; "Code" is the first repository the archive lists for the row. The archive carries no row tags, review links or community-submitted rows for this table; none are shown. archive 2025-07-28
Syntology Ran reads "N of M ran · U unverified": of the M code samples Syntology harvested from repositories linked to that row's paper (joined by arXiv id), N executed on a synthesized input and the other U = M−N are unverified (harvested, no recorded run). It counts code from repositories linked to that row's paper, not this result: the row's number was not reproduced and nothing here is a correctness claim. The other cell texts mean no graph line for the row: "linked, not harvested" (the archive links code, Syntology has not harvested it), "no code linked" (no code link in the archive), "not matched" (the row's paper URL matched no paper on this site). 2 rows have a graph line, from 1 distinct papers; 0 rows (0 papers) have at least one sample that ran. Counting each paper once: Syntology ran 0 of 14 samples; 14 unverified. Separately, 0 of those 14 are pointer-only (licence): the site points at that code rather than redistributing it, a licence property recorded for ran and unverified samples alike; each cell's tooltip carries the row's own pointer-only count. Read from the graph 2026-09-24. Per-sample status is on the paper page.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections