MétaCan
Menu
Back to cohort
Record W1997241015 · doi:10.1097/pai.0000000000000069

Standardization of Negative Controls in Diagnostic Immunohistochemistry

2014· article· en· W1997241015 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

VenueApplied immunohistochemistry & molecular morphology · 2014
Typearticle
Languageen
FieldComputer Science
TopicAI in cancer detection
Canadian institutionsLions Gate HospitalUniversity of TorontoUniversity Health Network
FundersNational Cancer Institute
KeywordsStandardizationMedicineTerminologyClinical PracticeImmunohistochemistryPathologyComputer scienceFamily medicine

Abstract

fetched live from OpenAlex

Standardization of controls, both positive and negative controls, is needed for diagnostic immunohistochemistry (dIHC). The use of IHC-negative controls, irrespective of type, although well established, is not standardized. As such, the relevance and applicability of negative controls continues to challenge both pathologists and laboratory budgets. Despite the clear theoretical notion that appropriate controls serve to demonstrate the sensitivity and specificity of the dIHC test, it remains unclear which types of positive and negative controls are applicable and/or useful in day-to-day clinical practice. There is a perceived need to provide "best practice recommendations" for the use of negative controls. This perception is driven not only by logistics and cost issues, but also by increased pressure for accurate IHC testing, especially when IHC is performed for predictive markers, the number of which is rising as personalized medicine continues to develop. Herein, an international ad hoc expert panel reviews classification of negative controls relevant to clinical practice, proposes standard terminology for negative controls, considers the total evidence of IHC specificity that is available to pathologists, and develops a set of recommendations for the use of negative controls in dIHC based on "fit-for-use" principles.

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.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.694
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.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.003
GPT teacher head0.230
Teacher spread0.227 · 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