 |
NetWellness provides the highest quality health information and education services created and evaluated by faculty of our partner universities.
Monday, February 6, 2012
|
|
|
NetWellness provides the highest quality health information and education services created and evaluated by faculty of our partner universities.
Monday, February 6, 2012
|
| Home | HealthTopics | Health Centers | Reference Library | Research |
 Join us on Facebook
|
Share on Facebook | Tweet |
|
Colorectal Diseases |
Prevention of Sepsis Following Colon Surgery06/07/2010 |
Three days following a laparoscopic colon resection due to deterioration, a staple let loose causing fever, delirium, weakness, and sharp pain in the upper RT quadrant. Diagnostic test were done. Five hours later heavy antibiotics were administered, and 20 hours later a 2nd surgery was done to repair the rupture. Respiratory distress and other manifestations of sepsis followed. The patient, my mother who was a lively 82 year old, eventually succumbed 3 weeks later. In your opinion, can you tell me:1. Would a more timely 2nd surgery have made a difference in decreasing the severity of the sepsis. 2. What would experts say would be a safe/prudent window of time for a follow up surgery give this situation? 3. Is there an association or GI expert I might ask these questions of to receive a helpful answer, if not here?
Thank you for your response.
The problems you describe could be due to a number of things, and not being familiar with the details of your case, it would not be appropriate for me to comment.
|
NetWellness Staff NetWellness.org |
|
|
Please note: only your personal physician or other health professional you consult can best advise you on matters of your health based on your medical history, your family medical history, your medication history, and how information from any of these databases may apply to you. Neither University of Cincinnati (NetWellness) nor any party involved in creating, producing or delivering this web site shall be liable for any damages arising out of access to or use of this web site, or any errors or omissions in the content thereof. (More) 
|