Codes / ICD10CM / O07.32

O07.32 Renal failure following failed attempted termination of pregnancy

ICD10CM code

ICD10CM

Chat with GenHealth to automate any coding or chart task.

Name of the Condition

  • Renal Failure Following Failed Attempted Termination of Pregnancy

Summary

This condition describes acute or chronic kidney failure that occurs after an unsuccessful attempt to terminate a pregnancy. The renal failure may result from complications such as hemorrhage, sepsis, or other systemic issues related to the failed procedure, requiring prompt medical intervention to address both the kidney dysfunction and underlying causes.

Causes

Renal failure in this context typically arises from severe complications of the failed termination, including significant blood loss (hemorrhage), infection (sepsis), or other systemic insults that impair kidney function. These complications can stem from procedural errors, incomplete abortion, or inadequate post-procedure care, leading to reduced blood flow or direct damage to the kidneys.

Risk Factors

  • Severe hemorrhage or hypovolemia during or after the procedure.
  • Sepsis or systemic infection.
  • Prolonged hypotension or shock.
  • Pre-existing kidney disease or risk factors for acute kidney injury (e.g., dehydration, certain medications).
  • Delayed or inadequate medical response to complications.

Symptoms

  • Decreased urine output or oliguria.
  • Swelling (edema) in the legs, ankles, or face.
  • Fatigue, nausea, or confusion.
  • Elevated blood pressure or fluid retention.
  • Signs of underlying complications (e.g., fever, severe pain, or bleeding).

Diagnosis

Diagnosis involves assessing kidney function through laboratory tests (e.g., serum creatinine, blood urea nitrogen) and evaluating for underlying causes such as hemorrhage or infection. Imaging (e.g., ultrasound) may be used to check for retained tissue or other complications, and clinical history of the failed termination is critical for correlation.

Treatment Options

Treatment focuses on addressing the underlying cause (e.g., managing hemorrhage, treating infection) and supporting kidney function. Interventions may include fluid resuscitation, medications to stabilize blood pressure, dialysis in severe cases, and monitoring for further complications. Supportive care and close observation are essential.

Prognosis and Follow-Up

Prognosis depends on the severity of kidney damage and how quickly treatment is initiated. Early intervention improves outcomes, but some cases may progress to chronic kidney disease. Follow-up includes regular monitoring of kidney function, managing underlying conditions, and addressing any long-term effects of the failed termination.

Complications

  • Progression to chronic kidney disease or end-stage renal failure.
  • Electrolyte imbalances (e.g., hyperkalemia).
  • Fluid overload or pulmonary edema.
  • Increased risk of future kidney-related issues.
  • Persistent effects from the original complications (e.g., infection, hemorrhage).

Lifestyle & Prevention

  • Maintain adequate hydration and avoid nephrotoxic substances (e.g., certain medications).
  • Follow up with healthcare providers to monitor kidney function after the event.
  • Address any underlying health conditions that may affect kidney health.
  • Ensure proper medical care during and after termination procedures to minimize complications.

When to Seek Professional Help

Seek immediate medical attention if experiencing symptoms of kidney failure (e.g., reduced urination, swelling, confusion) or signs of severe complications (e.g., heavy bleeding, fever, severe pain) after a failed termination attempt.

Tips for Medical Coders

Document the failed termination attempt and the onset of renal failure clearly, including clinical findings, lab results, and treatment provided. Ensure the code O07.32 is used only when renal failure is directly linked to the failed procedure, with supporting documentation of the causal relationship.

Book a walkthrough

O07.32 policy automation walkthrough

Walk through the policies, prior authorization requirements, and workflow automation opportunities connected to this code.