Managing pregnancy-associated clinical emergencies in systemic lupus erythematosus: a case-based approach
Bibliographic record
Abstract
Introduction: Systemic lupus erythematosus (SLE)-related thrombocytopenia during pregnancy and the postpartum period have been associated with adverse pregnancy outcomes and perinatal complications. In this case report, we present two SLE patients with thrombocytopenia emergencies secondary to HELLP (hemolysis, elevated liver enzymes, and low platelets) syndrome and thrombotic thrombocytopenic purpura (TTP).Areas covered: The first case involved a 26-year-old woman, G1P0 at 26 weeks gestation (GA), with high-titer antiphospholipid antibodies (aPL) (positive lupus anticoagulant, anti-beta 2 glycoprotein-1 (aβ2GP1), anti-cardiolipin) and non-criteria aPL to phosphatidylserine/prothrombin complex and anti-domain 1 β2GP1. This case highlights the risks associated with aPL in pregnancy, considers management issues relating to anticoagulation during pregnancy and highlights the importance of maintaining a high index of suspicion for diagnosis of HELLP in SLE patients. The second case was a 36-year-old female, G3P2 at 32 weeks GA, with class III lupus nephritis (LN) who developed severe pre-eclampsia, which included mild thrombocytopenia. This case illustrates the challenges in identifying and differentiating between three pregnancy emergencies that can be seen in SLE patients (pre-eclampsia, LN, and TTP) and presents the management of TTP in peripartum SLE.Expert opinion: These two cases remind us of the importance of timely diagnosis and management of thrombocytopenia in this population.
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.006 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.003 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.003 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.003 | 0.003 |
| Insufficient payload (model declined to judge) | 0.004 | 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".