ICD-10 Coding for Steatosis(E88.81E, E88.81U, K70.10)

Learn about ICD-10 coding for steatosis, including primary codes, documentation requirements, and common pitfalls.

Also known as:
Fatty LiverHepatic SteatosisNonalcoholic Fatty Liver Disease (NAFLD)
Related ICD-10 Code Ranges

Complete code families applicable to Steatosis

Code Comparison: When to Use Each Code

Compare key differences between these codes to ensure accurate selection

CodeDescription
K76.0Fatty (change of) liver, not elsewhere classified
K75.8Other specified inflammatory liver diseases
K70.10Alcoholic hepatitis without ascites

Clinical Decision Support

Always review the patient's clinical documentation thoroughly. When in doubt, choose the more specific code and ensure documentation supports it.

Key Information

Essential facts and insights aboutSteatosis

Differential Codes

Alternative codes to consider when ruling out similar conditions

Other specified inflammatory liver diseasesK75.8

Use when biopsy confirms steatohepatitis with inflammation.

Fatty (change of) liver, not elsewhere classifiedK76.0

Documentation & Coding Risks

Avoid these common issues when documenting Steatosis.

Vague documentation of liver disease

Impact

Clinical: Inaccurate diagnosis and treatment planning., Regulatory: Non-compliance with coding standards., Financial: Potential for denied claims or reduced reimbursement.

Mitigation

Use specific terms and document etiology clearly.

Miscoding drug-induced steatosis as K76.0

Impact

Reimbursement: Incorrect coding may lead to denied claims., Compliance: Non-compliance with coding guidelines., Data Quality: Inaccurate data on liver disease etiology.

Mitigation

Use K71.- for drug-induced liver disease.

Using unspecified codes like K75.9

Impact

Reimbursement: Potential for reduced reimbursement., Compliance: Failure to meet specificity requirements., Data Quality: Loss of specificity in clinical data.

Mitigation

Use specific codes like K70.10 if alcohol-related.

Use of unspecified codes

Impact

High risk of audit if unspecified codes are used without supporting documentation.

Mitigation

Ensure documentation supports the specificity of the code used.

Frequently Asked Questions