ICD-10 Coding for Sprained Ankle(S93.4, S93.409A, S93.409S)

Comprehensive guide on ICD-10 coding for sprained ankles, including specific ligament codes, documentation requirements, and common pitfalls.

Also known as:
Ankle SprainTwisted Ankle
Related ICD-10 Code Ranges

Complete code families applicable to Sprained Ankle

Code Comparison: When to Use Each Code

Compare key differences between these codes to ensure accurate selection

CodeDescription
S93.409ASprain of unspecified ligament of unspecified ankle, initial encounter
S93.491ASprain of anterior talofibular ligament of right ankle, initial encounter

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 aboutSprained Ankle

Differential Codes

Alternative codes to consider when ruling out similar conditions

Sprain of anterior talofibular ligament of right ankle, initial encounterS93.491A

Use when the anterior talofibular ligament is specifically identified as injured.

Sprain of unspecified ligament of unspecified ankle, initial encounterS93.409A

Use when the specific ligament is not identified.

Documentation & Coding Risks

Avoid these common issues when documenting Sprained Ankle.

Failure to document laterality

Impact

Clinical: May lead to incorrect treatment., Regulatory: Non-compliance with coding guidelines., Financial: Potential for denied claims.

Mitigation

Always include laterality in documentation., Use templates that prompt for laterality.

Using unspecified codes when specific ligament is identified

Impact

Reimbursement: May result in lower reimbursement rates., Compliance: Non-compliance with specificity requirements., Data Quality: Decreases accuracy of clinical data.

Mitigation

Update documentation and code to reflect specific ligament involvement.

Use of unspecified codes

Impact

High risk of audit if unspecified codes are used when specific ligament involvement is documented.

Mitigation

Regularly review documentation to ensure specificity.

Frequently Asked Questions