Removal of vancomycin administered during dialysis by a high‐flux dialyzer
Bibliographic record
Abstract
Abstract Introduction: Hemodialysis patients frequently receive vancomycin for treatment of gram‐positive bacterial infections. This drug is most conveniently administered in outpatient dialysis units during the hemodialysis treatment. However, there is a paucity of data on the removal of vancomycin by high‐flux polyamide dialyzers. Methods: This is a prospective crossover study in which seven uninfected chronic hemodialysis patients at three dialysis units received vancomycin 1 gram intravenously over one hour immediately after the dialysis treatment (Phase 1), and vancomycin 1.5 grams during the last hour of dialysis treatment using a polyarylethersulfone, polyvinylpyrrolidone, polyamide high‐flux (Polyflux 24R) dialyzer (Phase 2). There was a three‐week washout period between phases. Serial serum vancomycin concentrations were used to determine the removal of vancomycin when administered during dialysis. Findings: Dialysis removed 35 ± 15% (range 18‐56%) of the vancomycin dose when administered during the last hour of dialysis. The calculated area under the curve (AUC) of vancomycin levels for 0‐44.5 hours from the start of infusion were similar between the two phases (AUCPhase 1 884 ± 124 mg‐hr/L, mean ± SD; AUCPhase 2 856 ± 208 mg‐hr/L; P=0.72). Serum vancomycin concentrations immediately prior to the next dialysis treatment following vancomycin administration were also similar between the two phases (13.1 ± 2.7 mg/L in Phase 1 and 12.3 ± 3.3 mg/L in Phase 2; P=0.55). Discussion: When using a polyarylethersulfone, polyvinylpyrrolidone, and polyamide high‐flux HD membrane with a 24R Polyflux dialyzer, vancomycin can be administered during the last hour of dialysis if the dose that is prescribed for intra‐dialysis dosing is empirically increased to account for intra‐dialytic drug removal.
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.001 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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".