Getting liver failure coding right takes a lot more than picking a code off a list. It calls for a real understanding of how the liver functions, how the disease progresses, what clinical clues to look for, and how documentation shapes the final code. If you’ve ever second-guessed whether a case is acute, chronic, or something in between, you’re not alone — this is one of the trickier areas in hepatic coding.
This guide walks through the core concepts behind liver failure coding, based on insights shared ahead of an upcoming ACDIS & JustCoding virtual seminar led by James F. Salter IV, CCS, a coding and regulatory education specialist for HCPro.
Why Liver Failure Coding Is So Complex
The liver quietly handles hundreds of jobs every single day — producing clotting factors, making albumin and bile, filtering out toxins, processing nutrients, storing vitamins, and keeping digestion running smoothly. When that function starts to break down, all of those jobs get disrupted at once. That ripple effect is exactly why liver failure coding requires such a careful eye: the clinical picture gets messy fast, and the documentation supporting it has to keep pace.
Understanding Acuity in Liver Failure Coding
If there’s one concept coders need to master for liver failure coding, it’s acuity. Specifically, the timing of hepatic encephalopathy relative to when the illness started determines whether a case is labeled acute, subacute, chronic, or acute-on-chronic. This isn’t just a clinical detail — it has a direct, measurable impact on which ICD-10-CM code gets assigned.
To code accurately, coders need to recognize terms like “fulminant liver failure,” know when a physician query is warranted, and correctly identify the right code category based on the timeline.
Acute and Subacute Liver Failure
Acute (fulminant) liver failure is diagnosed when encephalopathy shows up within roughly eight weeks of jaundice onset, there’s no prior history of liver disease, and the overall illness runs less than 26 weeks. These cases fall under ICD-10-CM subcategory K72.0- (acute and subacute hepatic failure).
Subacute (subfulminant) liver failure follows a similar path but develops later — anywhere up to six months after disease onset. These cases are also coded under K72.0-.
Chronic Liver Failure
Chronic liver failure is a different story. It’s diagnosed when encephalopathy develops more than six months after disease onset, and it’s typically the end stage of cirrhosis. These cases are coded from subcategory K72.1- (chronic hepatic failure).
Acute-on-Chronic Liver Failure
Acute-on-chronic liver failure is where things get genuinely tricky for coders. This happens when a new, acute insult hits a liver that already has established chronic disease — but there’s no dedicated ICD-10-CM code for that exact scenario. Instead, coders have to lean on provider documentation, and often a query, to pin down the supported acuity level and whether coma is present.
One useful rule of thumb: if a provider documents “fulminant” liver failure, treat it as acute liver failure for coding purposes — even if the word “acute” never actually appears in the chart.
Key Documentation That Supports Liver Failure Coding
Solid documentation is what makes accurate liver failure coding possible in the first place. Coders should be watching for three key clinical findings:
- Jaundice — shown through elevated bilirubin levels along with yellowing of the skin or sclera
- Coagulopathy — reflected by a prolonged INR, since a failing liver can’t produce enough clotting factors
- Encephalopathy — altered mental status caused by a buildup of toxins the liver can no longer clear
When two of these three findings show up in the chart but liver failure itself hasn’t been explicitly documented, that’s a strong signal for a provider query. A well-written query can help make sure the medical record actually reflects what’s happening with the patient.
Why Query Opportunities Matter in Liver Failure Coding
At the end of the day, liver failure coding isn’t just about spotting a diagnosis on a chart. It requires a working knowledge of liver physiology, the ability to correctly read disease progression and acuity, an eye for distinguishing between similar hepatic conditions, and the judgment to know when documentation truly supports a given code. If the record shows a clear loss of liver function but the term “liver failure” was never used, that gap is often exactly where a query adds the most value.
Learn More: Deepen Your Liver Failure Coding Skills
This overview only scratches the surface. In the full ACDIS & JustCoding seminar, James F. Salter IV will go further into the clinical and coding differences between liver failure and related hepatic conditions, walk through how to assign ICD-10-CM codes correctly based on acuity and coma status, cover common documentation pitfalls, highlight query opportunities coders often miss, and review real-world coding scenarios.
If sharpening your liver failure coding accuracy — and your documentation instincts — is on your radar, this session is worth carving out time for. Register today to save your spot.
