MétaCan
Menu
Back to cohort
Record W4404641227 · doi:10.1080/20565623.2024.2432233

DNA sequencing in oncology: a focus group study on a duty to recontact

2024· article· en· W4404641227 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

VenueFuture Science OA · 2024
Typearticle
Languageen
FieldBiochemistry, Genetics and Molecular Biology
TopicGenomics and Rare Diseases
Canadian institutionsInstitute of Cancer Research
FundersZonMw
KeywordsBiologyDNA sequencingGeneticsComputational biologyDNAOncologyMedicineInternal medicineBioinformatics

Abstract

fetched live from OpenAlex

Introduction Particularly in genetics, former results can gain new meaning in the course of time. This raises questions about when professionals should recontact patients with new information. The aim of this focus group study is to clarify how different stakeholders in oncology think about the extent and limits of a duty to recontact.Materials and methods One focus group with oncology patients (n = 12) and two groups with healthcare professionals (total n = 13) were conducted. In general, there was support for recontacting patients. The scope and extent of this duty was, however, perceived differently. Differences and similarities on the following six contextual factors are discussed: information features, costs and efforts, personal preferences, who is contacted, clinic or research setting, and time.Discussion Oncology patients were clear in their wish to receive updates while the professionals were more hesitant to consider recontact as a standard of care. This is not surprising as recontacting patients with new information would mean a shift from a patient-initiated approach toward an information-initiated approach. This entails a different way of offering healthcare. Furthermore, the question is not only what professionals’ responsibilities are, but how to design a system that complies with patients’ wishes to receive updates.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.800
Threshold uncertainty score0.350

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
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.013
GPT teacher head0.300
Teacher spread0.287 · 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