ICD-10 Coding for Full Thickness Rotator Cuff Tear(M75.1, M75.111U, M75.121)

Learn about the ICD-10 coding for full thickness rotator cuff tears, including documentation requirements and coding pitfalls.

Also known as:
Complete Rotator Cuff TearFull Thickness Tear of Supraspinatus
Related ICD-10 Code Ranges

Complete code families applicable to Full Thickness Rotator Cuff Tear

Code Comparison: When to Use Each Code

Compare key differences between these codes to ensure accurate selection

CodeDescription
M75.121Complete rotator cuff tear/rupture of right shoulder, not specified as traumatic
S46.011ATraumatic rupture of right rotator cuff, 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 aboutFull Thickness Rotator Cuff Tear

Differential Codes

Alternative codes to consider when ruling out similar conditions

Incomplete rotator cuff tear/rupture of right shoulder, not specified as traumaticM75.111

Use when the tear is partial rather than full thickness.

Complete rotator cuff tear/rupture of right shoulder, not specified as traumaticM75.121

Use when the tear is non-traumatic.

Documentation & Coding Risks

Avoid these common issues when documenting Full Thickness Rotator Cuff Tear.

Not specifying laterality

Impact

Clinical: Ambiguity in treatment planning., Regulatory: Non-compliance with coding standards., Financial: Potential claim denials.

Mitigation

Always document whether the tear is on the right or left shoulder.

Using M75.121 for a traumatic tear

Impact

Reimbursement: Incorrect coding can lead to denied claims., Compliance: Non-compliance with coding guidelines., Data Quality: Inaccurate clinical data representation.

Mitigation

Verify trauma history and use S46.011A if trauma is present.

Trauma Documentation

Impact

Failure to document trauma can lead to incorrect coding.

Mitigation

Ensure trauma history is clearly documented when applicable.

Frequently Asked Questions