HELLP Syndrome, Thrombotic Thrombocytopenic Purpura or Both: Appraising the Complex Association and Proposing a Stepwise Practical Plan for Differential Diagnosis
Bibliographic record
Abstract
Both thrombocytopenia and microangiopathic hemolytic anemia (TMA) are seen in thrombotic thrombocytopenic purpura (TTP) and HELLP syndrome among other disorders during pregnancy. Although both share backgrounds of endothelial injury and microvascular thrombi and some clinical features, yet, they have different etiologies and courses. In late pregnancy, differentiating between these two pathologies can be extremely difficult due to the immense overlap in clinical and laboratory manifestations and this becomes only possible with the use of specific markers as ADAMTS-13, when available. Hereby, we describe three cases that may exemplify the complex association between PE/HELLP syndrome and TTP. The first case presented with PE/HELLP syndrome and deteriorated postpartum to improve on plasmapheresis. The second case was a known TTP patient who developed superimposed PE/HELLP at 27 weeks gestation which necessitated emergent delivery. The third was a case of preeclampsia that progressed to HELLP syndrome on day 2 postpartum but 3 days later was complicated by TTP. HELLP syndrome and TTP can co-exist, but can also complicate one another. In the absence of instantaneous results of ADAMTS-13 and when diagnosis with clinical judgement alone cannot be done with certainty, a short trial-plasmapheresis could be attempted with close observation of the immediate response. This stepwise approach might prove to be a valuable tool when integrated in the usual workup of clinical and laboratory evaluation both before and after delivery.
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.002 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.004 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.005 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.003 | 0.003 |
| 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".