Platelet count recovery and seroreversion in immune HIT despite continuation of heparin: further observations and literature review
Bibliographic record
Abstract
One of the standard distinctions between type 1 (non-immune) and type 2 (immune-mediated) heparin-induced thrombocytopenia (HIT) is the transience of thrombocytopenia: type 1 HIT is viewed as early-onset and transient thrombocytopenia, with platelet count recovery despite continuing heparin administration. In contrast, type 2 HIT is viewed as later-onset (i. e., 5 days or later) thrombocytopenia in which it is generally believed that platelet count recovery will not occur unless heparin is discontinued. However, older reports of type 2 HIT sometimes did include the unexpected observation that platelet counts could recover despite continued heparin administration, although without information provided regarding changes in HIT antibody levels in association with platelet count recovery. In recent years, some reports of type 2 HIT have confirmed the observation that platelet count recovery can occur despite continuing heparin administration, with serological evidence of waning levels of HIT antibodies ("seroreversion"). We now report two additional patient cases of type 2 HIT with platelet count recovery despite ongoing therapeutic-dose (1 case) or prophylactic-dose (1 case) heparin administration, in which we demonstrate concomitant waning of HIT antibody levels. We further review the literature describing this phenomenon of HIT antibody seroreversion and platelet count recovery despite continuing heparin administration. Our observations add to the concept that HIT represents a remarkably transient immune response, including sometimes even when heparin is continued.
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.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.006 | 0.007 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.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.
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".