- Joined
- Jan 10, 2008
- Messages
- 3,581
- Reaction score
- 11
- Points
- 4,551
Umm, I'm taking neuroscience right now, and the spine and the optic nerve/optic tractv are really, really far from each other.
Why would blindness be a specific complication of spine surgery? If it's caused by blood loss, then it would be a possible danger of nearly any major surgery. I'm sure there's a connection, but how?
Several responses.
1. Over the past decade I have scrubbed in on hundreds or more likely a thousand or more spine cases. Case of blindness N=0. We frequently do 7 to 10 hour cases.
Your incidence rate for blindness resulting as a complication due to spine surgery is too low. It should be closer to 5%.
My husband lost his sight two weeks after incurring a spinal cord injury that was incomplete (i.e., spinal cord not severed). He is now a paraplegic and blind.
Several responses.
4. I get very frustrated with our anesthesia folks who talk to and terrify our patients just prior to surgery while talking about the rare complication of blindness that the surgeon may cause. Yet those same folks fail to mention the much more likely complication of anesthesia causing chipped teeth, lip lacerations, tongue ulcerations, blepharoplasty via hasty tape removal, or acute renal failure due giving too little IV fluid to avoid the unsightly facial swelling that seems to bother our anesthesia folks soo much. Not to mention the post-op hypotension that accompanies it which requires much higher maintenance fluid and frequent fluid boluses post-op.
The anesthesiologists taking care of your patients probably feel the need to discuss the possibility of perioperative visual complications because it is frequently seen as THEIR complication. It is they who manage the BP, volume, transfusions, and positioning, and it is they who will be opening their checkbook (probably along with the surgeon) when the patient wakes up blind. I'm trying to imagine myself getting "frustrated" watching "my surgical folks" discussing potential surgical complications with the patients.
With regard to the facial swelling, I doubt that it's the appearance that bothers them. More likely it's that when facial edema is present, so too is laryngeal edema, which may require continued intubation/mechanical ventilation postoperatively, one complication of which (ventilator-associated pneumonia) could be detrimental in a patient with new hardware.
"Open up your wallet" is trade lingo, and is certainly not to be confused with the physician being indifferent about a severe complication. When such tragedies happen, physicians take it much harder than some people realize. But complications come with the territory; when one does happen, the best thing the physician can do is learn every possible thing they can from the experience and go forward from there.Why is "open up your wallet" the biggest concern? I mean, I know that attendings become pretty jaded, but would you not still feel a little bit of empathy and guilt if you made someone blind?
Interesting.
I say this because they always mention it in relation to my particular surgeon due to the fact that he is slow. They do not mention it with other surgeons and they say something to the effect of "Due to the extremely long operative times of Dr. ____ there is a greatly increased possibility that you can wake up blind".
I agree with you regarding unprofessionalism. IMHO, one shouldn't discuss their feelings about colleagues with the patient; if you have an issue with a chosen modality or treatment plan, you discuss them with your peers, and not potential laymen who can easily misunderstand or misconstrue what you're saying. It's almost like the imaging tech telling a patient that the EP who ordered the study has a tendency to overimage everyone, or an EP telling a patient that their PCP has been mismanaging them.Wow, that's interesting. On the surface that sounds pretty unprofessional. I wonder if they've been thrown under the bus by this guy in the past... It is true, however, at least based on qualitative analysis of the ASA's registry, that visual loss is associated with longer operative times. Still, no patient deserves to hear "yeah, this guy who's doing you're surgery, well, he's a bit of a hack, so, uh, good luck!" on their way to the OR.
In terms of visual loss, IMHO, at least half of the fault lays with Anesthesia. Certainly operative times should be reduced whenever feasible, but the sedation, ventilation, peri-operative anesthetic and perfusive responsibilities are within the Anesthesiologist's scope. Anesthesiologists are very defensive about their turf in terms of utilizing the appropriate anesthesia modality for the given procedure, and with input from the rest of the team, generally have the final say (and rightfully so because they're the experts). So if they're pushing too much nitroglycerin and the pt suffers hypotensive complications, they're still responsible for the management. A surgeon's duty is to perform within the realm of their best judgment for how to best achieve the desired outcome; if an anesthesiologist is uncomfortable doing such a case, it is their responsibility to pass it along to someone who may be a better provider for it. Just my 2¢. 🙂
This is all well and good, but believe it or not, there is occasionally a lot of pressure (often in the form of whining, foot stomping, and the like) to lower a patient's BP in these cases. I've even heard things like, "I'll have to stop the case if we can't get the BP down so this bleeding stops." Who's to blame, the surgeon for requesting/demanding it, or the anesthesiologist for giving in? Recognize that when you say "pass it along to someone who may be a better provider for it," what that really means in this case is "someone more willing to acquiesce to the surgeon's demand for lower BP and/or take the heat for a bad outcome." It's not like there's some secret technique that some "better provider" is going to come up with to protect the eye in the face of hypoperfusion.
The truth is, no one really knows how low is too low, so saying, "look, I'm not going to go below X" doesn't really get you anywhere. "Why X, and not Y?" It really depends on the patient, their baseline, their position, and, probably more than anything, bad luck. That's not to try to weasel out of the blame, but just to point out that it's more complex than it sounds. The caveat is those cases where it's due to central retinal artery occlusion, it is probably mostly or solely the anesthesiologist's responsibility since they confirm and monitor the patient's position.
Anyway, this really wasn't supposed to be a discussion about who's to blame when it happens, but I'm postcall, so you get a rant.
So, you are frustrated with the anesthesiologists who are trying to inform the patients about a potentially devastating complication like blindness!4. I get very frustrated with our anesthesia folks who talk to and terrify our patients just prior to surgery while talking about the rare complication of blindness that the surgeon may cause. Yet those same folks fail to mention the much more likely complication of anesthesia causing chipped teeth, lip lacerations, tongue ulcerations, blepharoplasty via hasty tape removal, or acute renal failure due giving too little IV fluid to avoid the unsightly facial swelling that seems to bother our anesthesia folks soo much. Not to mention the post-op hypotension that accompanies it which requires much higher maintenance fluid and frequent fluid boluses post-op.
No, I'm not bitter.
Yes, and in the majority of routine and elective cases, accomodating a surgeon unhappy with the BP will most likely not lead to seriously adverse consequences. But for lengthier cases such as trauma and deformity repairs, research is beginning to emerge suggesting that depressing BP to a certain point for a certain length of time is EBM counterindicated in certain conditions, unless certain other steps are taken. The point I was trying to make is that if Anesthesiologists find themselves in positions where the care they are expected to provide exceeds what they are comfortable in doing, they should seek assistance from someone who can provide the necessary care. Given the extremely rare incidence of complications from inducing hypotension, I assume most Anesthesiologists wouldn't have too much of a problem doing this. But the surgeon shouldn't have sole responsibility to be flexibile in how the procedure is done, or to work faster than they are reasonably comfortable; the entire healthcare team goes works together to achieve the maximum desired outcome, and as such, no one member should be expected to shoulder all the blame.
In terms of visual loss, IMHO, at least half of the fault lays with Anesthesia.
The only accepted risk factors for visual loss as far as we know today are:
1- Length of surgery
2- Low hematocrit
3- Blood transfusion
4- Prone position
5- Low BP
Yet those same folks fail to mention the much more likely complication of anesthesia causing chipped teeth, lip lacerations, tongue ulcerations, blepharoplasty via hasty tape removal, or acute renal failure due giving too little IV fluid to avoid the unsightly facial swelling that seems to bother our anesthesia folks soo much. Not to mention the post-op hypotension that accompanies it which requires much higher maintenance fluid and frequent fluid boluses post-op.
FWIW, as an anesthesia resident, I always tell all of my patients "it's possible but very unlikely that you'll have a bruised lip or chipped tooth from the breathing tube" and my consent spiel always, always includes the words "organ damage or death" at some point ... typically with some appropriate qualifier like "there's nothing about you that makes us think you're at significant risk for any of these problems." Or if the patient is stupendously obese, has an EF of 20%, a huge mediastinal mass, etc I'll tell them that whatever condition they have puts them at somewhat higher risk, that we'll be especially attentive to that issue, but that some risk is unavoidable.
Most patients aren't stupid. They know they're not in the hospital for ice cream or the pleasure of a bowel prep; they're in the hospital to get knocked out and cut on. I find they're appreciative of a frank, compassionate discussion about risk. It's possible to tell patients about the risk of catastrophic complications without freaking them out ... all in the delivery. And worth the extra 30 seconds to do properly.
I always mention blindness for cardiac and prone spine cases.
I agree that informed consent is a myth; no lay person can possibly be truly informed. They count on us to use our education, training, and experience to help them weigh the risks and benefits of surgery and anesthesia. Obviously we can't list, explain, and give odds for every single conceivable complication but I do think that especially devastating complications, even if very rare, deserve mentioning.
Blindness certainly qualifies, especially since it's non-intuitive to the lay person. Most CABG patients understand someone's going to cut on their heart and they may worry about the risk of a catastrophic perioperative MI or death; but blindness? Not even on their radar. Patients get angry and sue when they feel lied to or patronized - it's easy for me to see how a devastating complication that literally comes out of nowhere (from their perspective) can tilt them toward anger at the surgeon or anesthesiologist who didn't see fit to mention it.
So, you are frustrated with the anesthesiologists who are trying to inform the patients about a potentially devastating complication like blindness!
Let me ask you this: since you are frustrated, would you promise us that if a patient loses vision you would go straight to them and tell them that the blindness was actually a surgical complication and it's not an anesthetic complication?
Would you have the courage to go tell them that the main reason they became blind was that your surgery was too long or was because you lost too much blood?
I hope that your frustration with us does not prevent you from being straight forward with the patients when a bad outcome happens and I hope that you are not frustrated enough with us that you would lie to the patients and tell them that they became blind because of anesthesia (as I had heard with my own ears once before).
FWIW, as an anesthesia resident, I always tell all of my patients "it's possible but very unlikely that you'll have a bruised lip or chipped tooth from the breathing tube" and my consent spiel always, always includes the words "organ damage or death" at some point ... typically with some appropriate qualifier like "there's nothing about you that makes us think you're at significant risk for any of these problems." Or if the patient is stupendously obese, has an EF of 20%, a huge mediastinal mass, etc I'll tell them that whatever condition they have puts them at somewhat higher risk, that we'll be especially attentive to that issue, but that some risk is unavoidable.
Most patients aren't stupid. They know they're not in the hospital for ice cream or the pleasure of a bowel prep; they're in the hospital to get knocked out and cut on. I find they're appreciative of a frank, compassionate discussion about risk. It's possible to tell patients about the risk of catastrophic complications without freaking them out ... all in the delivery. And worth the extra 30 seconds to do properly.
I always mention blindness for cardiac and prone spine cases.
I agree that informed consent is a myth; no lay person can possibly be truly informed. They count on us to use our education, training, and experience to help them weigh the risks and benefits of surgery and anesthesia. Obviously we can't list, explain, and give odds for every single conceivable complication but I do think that especially devastating complications, even if very rare, deserve mentioning.
Blindness certainly qualifies, especially since it's non-intuitive to the lay person. Most CABG patients understand someone's going to cut on their heart and they may worry about the risk of a catastrophic perioperative MI or death; but blindness? Not even on their radar. Patients get angry and sue when they feel lied to or patronized - it's easy for me to see how a devastating complication that literally comes out of nowhere (from their perspective) can tilt them toward anger at the surgeon or anesthesiologist who didn't see fit to mention it.
It is also very rare to have a patient wake up with any pain at all.
Certainly not; as I mentioned in my earlier posts, I believe that if there is any blame to be had for any potentially avoidable (I use that term loosely) complication, it falls on the entire health care team, and not on any one of the providers. The line you quoted below your post was in reference to POVL caused by parameters controlled by the Anesthesia and not meant to be taken out of context. In a case where POVL occurs as a result of hypotension, the blame shouldn't rest entirely on the surgeon for taking too long.But you believe anesthesia should carry more blame than anyone else?
Plank's risk factors associated with POVL are correct. Count how many are modified by anesthesia. (hint- it's not "more than half")
Certainly not; as I mentioned in my earlier posts, I believe that if there is any blame to be had for any potentially avoidable (I use that term loosely) complication, it falls on the entire health care team, and not on any one of the providers. The line you quoted below your post was in reference to POVL caused by parameters controlled by the Anesthesia and not meant to be taken out of context. In a case where POVL occurs as a result of hypotension, the blame shouldn't rest entirely on the surgeon for taking too long.
I always include these things: Death, infection, continuation of pain, recurrence, non-union (if indicated), injury to recurrent laryngeal .....
So, you tell them that they might die because of the surgery but you think telling them that they might become blind is not needed because it's so rare?
Do you have more patients that die than patients that become blind?
Is it possible that if you included that complication in your discussion with the patient there wouldn't be a reason for you to get so frustrated with us telling them?
Although I understand that this might make it difficult to say it's anesthesia's fault when it really happens 😉 but I am sure you still can find a way to imply that we caused it.
I am not taking it personal, I am just demonstrating the issues with your statement about being frustrated with us talking to patients about a complication that you intentionally ignore which I personally find frustrating and annoying.
I love it when the surgeons take the credit for pain free patients post op. Of course, the uncomfortable patient is the anesthesiologist's fault. 🙁
I'm not sure if I've ever heard of a POVL case where there was no unintended surgical nerve compromise and no perioperative bp suppression. That's not to say it never happened, of course, but I'd imagine such a case would be fairly uncommon in terms of developing EBM guidelines. The ASA are the experts in this phenomenon, and it seems that the causes have been narrowed down to hypoperfusion of the optic nerve and intraocular pressure from pts laying prone for too long. In the former case, the etiology has not been conclusively established, but the educated suspicions include hypotension (which is why many are now suggesting reducing the degree of bp suppression during certain surgeries) and occlusive phenomena (which is also within the scope of Anesthesia). At the same time, the rest of the operative team should also be working to reduce the other potential risk factors, including operative time, blood loss, etc. IMHO, even though there isn't any one cause proven to cause POVL, it's still everyone's duty to adhere to suggestions established based on educated suspicions as far as it would be feasible.In the end, I'm not convinced anyone can reliably look at a case record of POVL and state with confidence it occurred solely because of hypotension. There are instances of POVL where hypotension was not present. So it's nice to say anesthesia should shoulder more than half the blame when hypotension occurs, but it's not always so easy to attribute the POVL to hypotension alone.
I'm not sure if I've ever heard of a POVL case where there was no unintended surgical nerve compromise and no perioperative bp suppression.
MH used to be treated like this when it had gotten more attention and then folks stopped mentioning that complication as much.
I changed my standard "not do anything meaningful afterwards"
If you're dead, or so ill that death will follow after a period of hospitalization, that qualifies.
If you've lost your primary sense (sight), so that you can no longer experience much of anything, that counts.
If you can't even think and aren't even the same person anymore because a stroke killed a key chunk of your brain, that especially counts.
Obviously, even someone with body dismorphic disorder could be treated for a scar. But no treatment can replace lost eyes or brain tissue or lower body control.
But, yes, I've thought about it for about 15 minutes, and it's really hard to put a hard limit on what complications I would consider to be effectively death or as bad as death, such that suicide would be a rational choice. Near complete paralysis, near total blindness AND near total deafness at the same time, a major stroke...the list isn't really all that long. Even if one became blinded, it might be possible to go on living and to eke out enough enjoyment of life that one wanted to continue living.
Gern, I was referring to NS cases in general that involved vision loss.What nerve are you talking about compromising surgically? I thought the discussion was spine surgery and POVL.
The cases you have never heard of exist. Those cases where there is minimal blood loss, no hypotension, short duration, and no pressure on the eyes make it difficult to nail down the ultimate risk factors. It is true that most cases involve one of the major risk factors elucidated above by Plankton, but the outliers exist and Lorri Lee has discussed these cases in her publications on the topic.
Speaking of spine surgery complications, I just read this tonight:
DEATHS AFTER BACK SURGERY OFTEN RELATED TO ANALGESICS:
NEW YORK (Reuters Health) Apr 10 - Roughly one in five deaths after lumbar fusion surgery is related to analgesic use, according to a report in the April 1st issue of Spine.
The results indicate that the risk of such deaths is particularly high in young and middle-aged workers with degenerative disc disease.
To examine complications after lumbar fusion surgery, lead author Dr. Sham Maghout Juratli from the University of Washington, Seattle, and colleagues analyzed workers' compensation claims filed by lumbar fusion patients in Washington State from 1994 to 2001. Washington State vital statistics records were used to assess mortality through 2004.
Data from 2378 patients were included in the analysis. The mortality rate at 90 days was 0.29%, the authors note. Over 3 years, 103 patients died, for a 3-year cumulative mortality rate of 1.93%.
Repeat fusions were found to predict perioperative mortality.
After adjusting for age and gender, 3.1 deaths occurred per 1000 worker-years.
There were 22 analgesic-associated deaths (19 accidental poisonings, 3 suicides). These accounted for 21% of all deaths and for 31.4% of all potential life lost.
Use of cage devices for fusion and the presence of degenerative disc disease were both risk factors for analgesic-related death. In subjects between 45 and 54 years of age, degenerative disc disease increased the odds of analgesic-related death by 7.45-fold (p = 0.01).
"The most important finding of this study was that analgesic-related deaths, both suicidal and accidental, claimed the highest potential life lost (31.4%), more than heart disease (9.2%), cancer (9.1%), and liver disease (5.1%), combined," the investigators conclude.
Spine 2009;34.
Why do you find this surprising?
This study is basically saying that unfortunately we are turning chronic pain patients in to drug abusers and drug addicts and that many abusers and addicts die of overdose (intentionally or by accident).
Gern, I was referring to NS cases in general that involved vision loss.
As I mentioned in my previous post, I'm certain such cases have indeed happened. I admittedly am not too familiar with the literature, but from what I've read, including some of Lorri Lee's recent publications that were available (ASA registry, etc.) even then she seems to be focusing on hypotension and blood loss as the most likely culprits for ION-induced POVL, with obstruction of blood supplies being a rather distant second. The outlier cases are available, but are almost statistically insignificant compared to the more common incidences of POVL, and so at this point, offer little recourse on how to address them.
Hence the last sentence in my post.Another interpretation is that she focused on hypotension and blood loss because those factors are somewhat within our control.