MétaCan
Menu
Back to cohort
Record W2604143891 · doi:10.1093/bmb/ldx009

Expect the unexpected: screening for secondary findings in clinical genomics research

2017· review· en· W2604143891 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

VenueBritish Medical Bulletin · 2017
Typereview
Languageen
FieldBiochemistry, Genetics and Molecular Biology
TopicGenomics and Rare Diseases
Canadian institutionsDalhousie University
Fundersnot available
KeywordsAutonomyProtocol (science)Informed consentGenomicsMedicineClinical researchScale (ratio)Research ethicsData scienceEngineering ethicsAlternative medicineComputer sciencePolitical sciencePathologyBiologyEngineeringPsychiatryGenetics

Abstract

fetched live from OpenAlex

Background: Due to decreasing cost, and increasing speed and precision, genomic sequencing in research is resulting in the generation of vast amounts of genetic data. The question of how to manage that information has been an area of significant debate. In particular, there has been much discussion around the issue of 'secondary findings' (SF)-findings unrelated to the research that have diagnostic significance. Sources of data: The following includes ethical commentaries, guidelines and policies in respect to large-scale clinical genomics studies. Areas of agreement: Research participant autonomy and their informed consent are paramount-policies around SF must be made clear and participants must have the choice as to which results they wish to receive, if any. Areas of controversy: While many agree that clinically 'actionable' findings should be returned, some question whether they should be actively sought within a research protocol. Growing points: SF present challenges to a growing field; diverse policies around their management have the potential to hinder collaboration and future research. Areas timely for developing research: The impact of returning SF and accurate estimates of their clinical utility are needed to inform future protocol design.

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.004
metaresearch head score (Gemma)0.006
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.854
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.006
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0000.000
Science and technology studies0.0000.001
Scholarly communication0.0000.000
Open science0.0020.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0000.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.199
GPT teacher head0.474
Teacher spread0.275 · 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