Challenges in Detecting Clinically Relevant Heparin-Induced Thrombocytopenia Antibodies
Bibliographic record
Abstract
Heparin-induced thrombocytopenia (HIT) is an antibody-mediated hypercoagulable state featuring high thrombosis risk and distinct pathogenesis involving immunoglobulin G-mediated platelet activation. The target of the immune response is a cationic "self" protein, platelet factor 4 (PF4), rendered antigenic by heparin. A key problem is that only a minority of anti-PF4/polyanion antibodies induced by heparin are pathogenic, i.e., capable of causing platelet activation and thereby clinical HIT. Since thrombocytopenia occurs frequently in hospitalized, heparin-treated patients, testing for "HIT antibodies" is common; thus, the problem of distinguishing between pathogenic and nonpathogenic antibodies is important. The central concept is that those antibodies that have platelet-activating properties demonstrable in vitro correlate well with pathogenicity, as shown by platelet activation tests such as the serotonin-release assay (SRA) and heparin-induced platelet activation assay. However, in most circumstances, immunoassays are used for first-line testing, and so it is important for clinicians to appreciate which immunoassay result profiles-in the appropriate clinical context-predict the presence of platelet-activating antibodies (Bayesian analysis). Clinicians with access to rapid, on-demand HIT immunoassays (e.g., particle gel immunoassay, latex immunoturbidimetric assay, chemiluminescent immunoassay) can look beyond simple dichotomous result interpretation ("negative"/"positive") and incorporate semiquantitative interpretation, where, for example, a strong-positive immunoassay result (or even combination of two immunoassays) points to a greater probability of detecting platelet-activating antibodies, and hence supporting a diagnosis of HIT. Recent recognition of "SRA-negative HIT" has increased the importance of semiquantitative interpretation of immunoassays, given that strong immunoassay reactivity is a potential clue indicating possible HIT despite a (false) negative platelet activation assay.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.038 | 0.085 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.003 | 0.001 |
| Bibliometrics | 0.004 | 0.002 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.006 | 0.004 |
| Open science | 0.005 | 0.002 |
| Research integrity | 0.004 | 0.008 |
| Insufficient payload (model declined to judge) | 0.003 | 0.004 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".