Using Tunneled Femoral Vein Catheters for “Urgent Start” Dialysis Patients: A Preliminary Report
Bibliographic record
Abstract
BACKGROUND: Multiple benefits of arteriovenous fistulas (AVF) and arteriovenous grafts (AVGs) exist over catheters. As part of a strategy to preserve thoracic venous sites and reduce internal jugular (IJ) vein catheter use, we inserted tunneled femoral vein catheters in incident "urgent start" dialysis patients while facilitating a more appropriate definitive dialysis access. METHODS: "Urgent start" dialysis patients between January 15, 2013 and January 15, 2014 who required chronic dialysis, and did not have prior modality and vascular access plans, had tunneled femoral vein catheters inserted. We determined the femoral vein catheter associated infections rates, thrombosis, and subsequent dialysis access. Eligible patients were surveyed on their femoral vein catheter experience. RESULTS: Twenty-two femoral vein catheters were inserted without complications. Subsequently, one catheter required intraluminal thrombolytic locking, while all other catheters maintained blood flow greater than 300 ml/min. There were no catheter-related infections (exit site infection or bacteremia). Six patients continued to use their tunneled catheter at report end, one transitioned to peritoneal dialysis, thirteen to an arteriovenous graft, and two to a fistula. One patient received a tunneled IJ vein catheter. Of the patients who completed the vascular access survey, all indicated satisfaction with their access and that they had minimal complaints of bruising, bleeding, or swelling at their access sites. Pain/discomfort at the exit site was the primary complaint, but they did not find it interfered with activities of daily living. CONCLUSIONS: Femoral vein tunneled catheters appear to be a safe, well tolerated, and effective temporary access in urgent start dialysis patients while they await more appropriate long-term access.
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.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".