A complication of double lumen hemocatheter guide wire entrapment in a hemodialysis patient
Bibliographic record
Abstract
Double lumen hemocatheter is commonly used for temporary hemodialysis patient and various complications have been documented but few reports of guide wire-related complications. We report a complication of double lumen hemocatheter guide wire entrapment in a 43-year-old female of type 1 diabetes mellitus and hemodialysis patient. She was admitted for left arteriovenous shunt dysfunction and right internal jugular vein hemocatheter chamber clotting was found while on hemodialysis, so a new hemocatheter was changed over guide wire. Guide wire was introduced without any resistance and the clotting hemocatheter was removed. During the procedure, the J-tipped guide wire could not be withdrawn and portable chest radiography revealed the J-tip of the guide wire was in the right ventricle near the region of tricuspid valve. Fluoroscopy was arranged and it also confirmed the J-tip was lying in the ventricle near the tricuspid valve where it was stuck. Snare catheter kit was inserted through the 10 Fr sheath and the cardiologist untied the knot by endovascular snare and removed the guide wire smoothly. This report emphasizes the importance of awareness on guide wire entrapment while inserting double lumen hemocatheter. When a guide wire became hard to withdraw, extracting an entrapped guide wire with fluoroscopy guide and snare catheter is a preferable and minimal invasive approach.
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.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.003 | 0.002 |
| 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".