Search

Our review provides a summary of clinical evidence published in surgical, radiology, and nephrology literature highlighting the pros and cons of different types of lower extremity permanent dialysis access” Parekh et al (2016).

Abstract:

Hemodialysis remains the most commonly used RRT option around the world. Technological advances, superior access to care, and better quality of care have led to overall improvement in survival of patients on long-term hemodialysis. Maintaining a functioning upper extremity vascular access for a prolonged duration continues to remain a challenge for dialysis providers.

[ctt tweet=”ReTweet if useful… Lower extremity permanent dialysis vascular access devices http://ctt.ec/QRqch+ @ivteam #ivteam” coverup=”QRqch”]

Frequently encountered difficulties in clinical practice include (1) a high incidence of central venous catheter-related central vein stenosis and (2) limited options for creating a functioning upper extremity permanent arteriovenous access. Lack of surgical skills, fear of complications, and limited involvement of the treating nephrologists in the decision-making process are some of the reasons why lower extremity permanent dialysis access remains an infrequently used option. Similar to upper extremity vascular access options, lower extremity arteriovenous fistula remains a preferred access over arteriovenous synthetic graft. The use of femoral tunneled catheter as a long-term access should be avoided as far as possible, especially with the availability of newer graft-catheter hybrid devices. Our review provides a summary of clinical evidence published in surgical, radiology, and nephrology literature highlighting the pros and cons of different types of lower extremity permanent dialysis access.

Reference:

Parekh, V.B., Niyyar, V.D. and Vachharajani, T.J. (2016) Lower Extremity Permanent Dialysis Vascular Access. Clinical Journal of the American Society of Nephrology. May 27th. Epub ahead of print].

Thank you to our partners for supporting IVTEAM
[slideshow_deploy id=’23788’]