MétaCan
Menu
Back to cohort
Record W4401729323 · doi:10.1002/cyto.b.22202

Flow cytometry assay modifications: Recommendations for method validation based on <scp>CLSI H62</scp> guidelines

2024· review· en· W4401729323 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

VenueCytometry Part B Clinical Cytometry · 2024
Typereview
Languageen
FieldBiochemistry, Genetics and Molecular Biology
TopicSingle-cell and spatial transcriptomics
Canadian institutionsBC Children's HospitalUniversity of British Columbia
Fundersnot available
KeywordsStandardizationWorkflowComputer scienceMedical physicsGuidelineMedicineData sciencePathologyDatabase

Abstract

fetched live from OpenAlex

The Clinical and Laboratory Standards Institute (CLSI) H62-Validation of Assays Performed by Flow Cytometry guideline, released in 2021, provides recommendations for platform workflow and quality system essentials, instrument setup and standardization, assay development and optimization and fit-for-purpose analytical method validation. In addition, CLSI H62 includes some recommendations for the validation strategies after a validated flow cytometric method has been modified. This manuscript builds on those recommendations and discusses the impact of different types of assay modifications on assay performance. Recommendations regarding which validation parameters to evaluate depending on the type of modification are provided. The impact of assay modification on the assay's intended use is discussed. When recommending minor deviations from the CLSI H62 process for a laboratory-initiated assay revision (e.g., specimen numbers for sensitivity, specificity, or precision studies), a rationale based on expert opinion is provided with the understanding that not every laboratory, assay type, and circumstance can be comprehensively addressed in this paper. These recommendations are meant as a practical recommendation and are not intended to be restrictive, prescriptive, or understood as necessarily sufficient to meet every specific requirement from regulatory bodies (e.g., FDA or New York State Department of Health).

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.008
metaresearch head score (Gemma)0.020
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Meta-epidemiology (narrow), Research integrity
Consensus categoriesMeta-epidemiology (narrow)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.695
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0080.020
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0030.004
Bibliometrics0.0020.004
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0020.000
Research integrity0.0030.002
Insufficient payload (model declined to judge)0.0000.001

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.300
GPT teacher head0.501
Teacher spread0.200 · 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