MétaCan
Menu
Back to cohort
Record W3162795083 · doi:10.1055/a-1484-7235

Versorgungsnahe Daten zur Evaluation von Interventionseffekten: Teil 2 des Manuals

2021· article· de· W3162795083 on OpenAlex

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

VenueDas Gesundheitswesen · 2021
Typearticle
Languagede
FieldEconomics, Econometrics and Finance
TopicHealth Systems, Economic Evaluations, Quality of Life
Canadian institutionsCochrane
Fundersnot available
KeywordsGynecologyPolitical scienceHumanitiesMedicinePhilosophy

Abstract

fetched live from OpenAlex

The evaluation of intervention effects is an important domain of health services research. The ad hoc commission for the use of routine practice data of the German Network for Health Services Research (DNVF) therefore provides this second part of its manual focusing on the use of routine practice data for the evaluation of intervention effects. First, we discuss definition issues and the importance of contextual factors. Subsequently, general requirements for planning, data collection and analysis as well as concrete examples for the evaluation of intervention effects for the 3 fields of application regarding pharmacotherapy, nonpharmaceutical interventions as well as complex interventions are elaborated. We consider scenarios in which no information from randomized controlled trials (RCTs) comparing the two groups directly is yet available or in which RCTs are already available but an extension of the research question is required. In all examples either with or without randomization, the first and foremost question is always whether the data source is suitable for the specific research question. Most of the examples chosen are from oncology trials, because the necessary data are already available for Germany, at least in some form. Finally, the manual discusses possible challenges for future use of these data.

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.038
metaresearch head score (Gemma)0.015
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Meta-epidemiology (narrow), Insufficient payload (model declined to judge)
Consensus categoriesMetaresearch, Insufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.314
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0380.015
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0020.001
Bibliometrics0.0010.001
Science and technology studies0.0010.000
Scholarly communication0.0010.002
Open science0.0010.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0100.031

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.437
GPT teacher head0.495
Teacher spread0.058 · 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