The anticoagulant activity of enoxaparin sodium during on‐line hemodiafiltration and conventional hemodialysis
Bibliographic record
Abstract
To study and compare the anticoagulant activity of enoxaparin sodium during on-line hemodiafiltration (OL-HDF) and conventional hemodialysis (C-HD). Enoxaparin was administered as an anticoagulant to 21 hemodialysis patients at the beginning of a single 4-hour OL-HDF session as an intravenous bolus dose of 80 IU/kg [DOSAGE ERROR CORRECTED] On-line hemodiafiltration was performed using a high-flux polyester polymer alloy dialyzer and a total of 18 L replacement fluid (session A). One week later, the study was repeated in the same patients during a single 4-hour session of C-HD using a low-flux polysulfone dialyzer (session B). Blood samples for the measurement of Hb, blood urea and nitrogen (BUN), activated partial thromboplastin time (APTT), and anti-Xa levels were taken before each study session and 5-minute postdialysis. In 13 more patients, the same study was performed during OL-HDF using a high-flux polysulfone dialyzer (session C). No differences were found between sessions A, B, and C when predialysis values for Hb, BUN, APTT, and anti-Xa were compared. The mean postdialysis APTT and anti-Xa values were 32.5+/-3.8 seconds and 0.19+/-0.11 IU/mL, respectively, in session A, 39.0+/-5.0 seconds and 0.71+/-0.17 IU/mL in session B, and 33.8+/-3.1 seconds and 0.35+/-17 IU/mL in session C (A vs. B, P<0.0001, for both parameters, A vs. C, P<0.003 for anti-XA, and B vs. C, P<0.005, for both parameters). The anticoagulant activity of enoxaparin sodium is decreased significantly during a 4-hour OL-HDF session compared with to a similar session of C-HD. The degree of the reduction seems to depend on the dialyzer's membrane.
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.000 | 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".