Comparison of the injection of low‐molecular weight heparin in the arterial vs. venous blood line for preventing extracorporeal circuit clotting during hemodialysis
Bibliographic record
Abstract
Low-molecular weight heparins (LMWH) are widely used for preventing clotting during hemodialysis (HD). Although injection in the venous blood line is recommended to avoid initial loss of LMWH through the dialyzer, LMWH is still frequently administered in the arterial blood line at the start of dialysis. This study aimed to compare the safety and efficacy of the same enoxaparin dose administered through the venous blood line or arterial blood line. We also evaluated antifactor Xa (aXa) activity according to the injection route and dialysis modalities: high-flux (HF) HD, medium cut-off (MCO) HD, and online hemodiafiltration (OL-HDF). Forty-three patients were studied over 18 consecutive dialysis sessions using a fixed enoxaparin dose (20 or 40 mg), first administered through the arterial blood line bolus and then through the venous blood line for another 18 sessions. Compared to arterial blood line administration, venous blood line bolus resulted in a significant increase in median post-dialysis aXa activity: 0.16 (0.1-0.6) IU/ml versus 0.31 (0.1-1.3) IU/ml, respectively, p = 0.006. After arterial blood line bolus of 40 mg enoxaparin, median post-dialysis aXa activity was significantly lower with OL-HDF compared to HF-HD: 0.14 (0.1-0.35) versus 0.32 (0.15-0.49), p = 0.02. A trend for lower clotting within lines and bubble trap using venous blood line bolus was observed. In conclusion, venous blood line enoxaparin injection is safe in OL-HDF patients. However, in HF-HD and MCO-HD, venous blood line injection of 40 mg enoxaparin may increase overdosing risk. Thus, aXa activity should be monitored in HF-HD and MCO-HD patients at risk of bleeding and/or on vitamin K antagonists and careful surveillance is required when administering a 40 mg enoxaparin dose through the venous blood line route.
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.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
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".