Understanding CARC M64 Denials: The Role of ICD-10 “Excludes1” and How to Prevent Rejected Claims

Billing Alerts
1

Understanding CARC M64 Denials: The Role of ICD-10 “Excludes1” and How to Prevent Rejected Claims

A Practical Whitepaper for Healthcare Billing and Coding Teams

Executive Summary

Claims Adjustment Reason Code (CARC) M64 — “Missing/incomplete/invalid other diagnosis” — is a common rejection many practices encounter. These denials often stem from ICD-10 coding conflicts triggered by Excludes1 rules, which designate certain diagnosis codes as mutually exclusive. This paper explores how this issue arises, explains payer logic, and offers actionable solutions to reduce denials and increase first-pass claim acceptance.

What is CARC M64?

CARC M64 signals that a submitted diagnosis code is invalid in the context of another diagnosis present on the same claim. Payers use this code when:

  • Diagnosis codes are mutually exclusive and shouldn’t appear together.

  • A secondary diagnosis contradicts or overlaps with a primary one per ICD-10 rules.

  • Excludes1 conditions are ignored during coding or claim submission.

ICD-10 Excludes1: What It Means

According to the Centers for Medicare & Medicaid Services (CMS), an Excludes1 note means:

“Not coded here! An Excludes1 note indicates that the code excluded should never be used at the same time as the code above the Excludes1 note.”
(CMS Source: ICD-10-CM Coding Guidelines)

This rule exists to prevent conflicting diagnoses on the same claim — for example, a bipolar disorder diagnosis coded with a major depressive disorder, single episode, which are clinically and categorically exclusive.

Case Study: F31.60 + F32.2 Denial

A provider billed a claim with:

  • F31.60 – Bipolar disorder, current episode depressed

  • F32.2 – Major depressive disorder, single episode, severe without psychotic features

Why This Triggered CARC M64:

  • The ICD-10 tabular listing for F31.60 includes an Excludes1 note for all F32 codes.

  • Therefore, reporting F32.2 along with F31.60 contradicts ICD-10 guidelines.

  • Payers (e.g., BlueCross BlueShield of Tennessee and Ambetter) use automated claim edits to enforce this logic — resulting in a denial.

Other Examples of Excludes1 Conflicts That May Trigger M64

Code 1 Code 2 Conflict Type
F31.9 (Bipolar NOS) F33.1 (Recurrent MDD) Mood disorder coding contradiction
I10 (Hypertension) I11.0 (HTN heart disease) I11.0 includes I10; dual coding not allowed
K35.80 (Appendicitis) K36 (Other appendix dz) Diagnostic exclusivity in appendix
E11.9 (Type 2 DM) E10.9 (Type 1 DM) Mutually exclusive diabetes types
Q90.9 (Down syndrome) F70 (Mild intellectual disability) Excludes1: congenital syndromes and general cognitive dx

Best Practice: Avoiding the Denial

:magnifying_glass_tilted_left: Step 1: Review Provider Documentation

Determine the true primary diagnosis of the encounter. Ensure documentation supports a single diagnosis pathway when Excludes1 applies.

:stethoscope: Step 2: Code with Hierarchy in Mind

Use only the most appropriate, non-conflicting ICD-10 code. For behavioral health, identify if the patient has a bipolar spectrum disorder (F31) or a unipolar depression (F32/F33), not both.

:receipt: Step 3: Use the Primary Diagnosis Strategically

Many M64 denials can be avoided by:

  • Assigning the correct diagnosis as Primary (position 1) on the claim.

  • Keeping additional diagnoses in the patient chart, but not on the claim, if they conflict due to Excludes1.

This preserves clinical integrity while complying with billing standards.

What to Do When You Receive an M64 Denial

  1. Pull the claim and review all diagnosis codes.

  2. Use an ICD-10 tabular list or coding tool to check for Excludes1 notes.

  3. Remove the conflicting diagnosis that is less supported by documentation.

  4. Resubmit the claim with the appropriate single diagnosis or corrected hierarchy.

  5. Track repeated M64 denials to educate coders and providers proactively.

Recommendations for Health Centers

  • Train coders and providers on ICD-10 Excludes1 conventions.

  • Include denial code CARC M64 in denial dashboards and root cause reviews.

  • Use pre-bill audits to flag potential mutually exclusive diagnosis pairs.

  • Coordinate with your EHR or billing software vendor to build warnings or soft-edits that catch these combinations before claim submission.

Conclusion

CARC M64 denials are entirely preventable with correct application of ICD-10 Excludes1 guidance. By understanding how these rules work and adjusting workflows to accommodate them, FQHCs and provider organizations can significantly reduce claim rejections, shorten A/R cycles, and ensure clinical coding compliance.