ICD-10 Coding for Left Hamstring Strain(M79.605U, S76.311, S76.311A)
Learn about the ICD-10 codes for left hamstring strain, including documentation requirements and coding tips for accurate billing.
Complete code families applicable to Left Hamstring Strain
Compare key differences between these codes to ensure accurate selection
| Code | Description | When to Use | Key Documentation |
|---|---|---|---|
| S76.312A | Strain of muscle, fascia and tendon of left thigh, initial encounter | Use for initial encounter of acute left hamstring strain with confirmed diagnosis. |
|
| S76.312D | Strain of muscle, fascia and tendon of left thigh, subsequent encounter | Use for follow-up visits after the initial treatment of a left hamstring strain. |
|
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 aboutLeft Hamstring Strain
Alternative codes to consider when ruling out similar conditions
Use only when laterality is not specified in documentation.
Use for initial treatment visits only.
Documentation & Coding Risks
Avoid these common issues when documenting Left Hamstring Strain.
Omitting laterality in documentation
Impact
Clinical: Leads to incorrect treatment planning., Regulatory: Increases audit risk due to lack of specificity., Financial: Potential for claim rejections or reduced reimbursement.
Mitigation
Always document the side of the body affected., Use EHR prompts to ensure laterality is captured.
Using unspecified codes when laterality is documented
Impact
Reimbursement: May lead to claim denials or reduced payments., Compliance: Increases risk of audit due to lack of specificity., Data Quality: Decreases accuracy of health records.
Mitigation
Always use specific codes for left or right thigh when documentation allows.
Incorrect encounter type coding
Impact
Using the wrong 7th character for encounter type can lead to audits.
Mitigation
Implement EHR checks to ensure correct encounter type is selected.