Custom Search

Wednesday, June 9, 2010

Lasix and Hypoproteinemia - low protein

This is from a patient's perspective.

I am an educated allied health science disabled patient... let me explain why I have to take lasix due to my low protein:

The protein I'm low in is Albumin.  This is a plasma protein that helps hold water/fluid inside blood cells and other cells.  Without the Albumin holding water 'in',  the water runs out into the interstitial tissues... This is what they call third-spacing.

Doctors describe this process in terms of "osmotic pressure".  That is the osmotic pressure is upset, and fluid is allowed to run across semipermeable cell membranes, causing edema (fluid accumulation in body tissues).

This is where Lasix comes in.  The Generic name is furosemide.  This medication pulls fluid into the bloodstream and is allowed to be eliminated upon urination.  Exactly how this works is not clear to me.  All I know is, it's supposed to make you pee.

Now, the reason I'm losing my protein is yet unclear.  The results of the protein loss in me is generalized edema and (I believe) this edema also builds up in my intestines.

I believe this because on many occasions, medications taken by mouth including  lasix seem to lose effectiveness.  When this happens, I accumulate exessive fluid - upwards of 40 pounds.. that's almost like pouring 5 gallons of water inside my skin.

Before it gets to this point, I call my doctor who has me admitted into the VA hospital where I am treated.  I explain the treatment in previous blog entries.

The treatment involves IV meds including Albumin as well as Lasix which then doesn't have to be absorbed across the intestinal walls... it works then let me tell you.

I get 60 to 80mg of lasix either 2 or 3 times per day, causing me to urinate up to 2 liters or more for each dose.

I've noticed my first urinations are typical yellow in color, but the second liter is very clear and the color of tap water.

hypoproteinemia - hypoalbuminemia - low protein - treatment - medications - patient - case history - case study

No comments: