M26.25 identifies a dentofacial anomaly in which the vertical or horizontal distance between the maxillary and mandibular dental arches deviates from accepted norms, affecting occlusal relationships and jaw function.
Verified May 8, 2026 · 6 sources ↓
- Status
- Billable
- Chapter
- 13
- Related CPT
- 17
- Region
- Other
Documentation tips
What should appear in the chart to support M26.25.
Source · Editorial brief grounded in 6 cited references ↓
- Record the specific nature of the interarch distance anomaly — state whether the distance is excessive or insufficient, and whether it affects anterior, posterior, or full-arch relationships.
- Include cephalometric or panoramic radiograph findings that quantify the interarch discrepancy (e.g., reduced vertical dimension, increased freeway space) to support medical necessity.
- Document functional impact — chewing difficulty, speech impairment, TMJ symptoms, or prosthetic instability — to justify treatment and defend payer scrutiny.
- If the anomaly is congenital versus acquired (e.g., secondary to tooth loss or prior orthognathic surgery), note etiology explicitly; it affects clinical context even though M26.25 does not split by etiology.
- When multiple arch relationship anomalies coexist (e.g., interarch distance anomaly plus Angle's Class II malocclusion), list all applicable M26.2x codes — do not collapse into M26.29 unless no specific code fits.
Related CPT procedures
Procedure codes commonly billed with M26.25. Linking the right diagnosis to the right procedure is what establishes medical necessity.
Source · CMS LCDs · AAOS specialty guidance · claims-pattern analysis
Common coding pitfalls
The recurring mistakes coders make with M26.25 and adjacent codes.
Source · Editorial brief grounded in CDC ICD-10-CM tabular guidance, AAOS coding references, and cited references ↓
- Confusing M26.25 with M26.36/M26.37: those codes capture interocclusal distance anomalies of fully erupted tooth position, not the broader arch-to-arch relationship; review the clinical distinction before assigning.
- Defaulting to M26.20 (unspecified anomaly of dental arch relationship) or M26.4 (malocclusion, unspecified) when M26.25 is documented — unspecified codes invite downcoding and medical necessity denials.
- Assigning M26.25 for TMJ disorders: temporomandibular joint conditions belong under M26.6x, not M26.2x, even when interarch distance contributes to TMJ loading.
- Omitting secondary codes for coexisting arch anomalies (e.g., open bite M26.220, reverse articulation M26.24) when the patient has multiple documented dental arch relationship problems — each billable condition should be coded.
- Using M26.25 without supporting imaging or clinical measurement documentation, which exposes the claim to medical necessity denial on audit.
Clinical context
Source · Editorial summary grounded in 6 cited references ↓
M26.25 falls under the M26.2 subcategory (Anomalies of dental arch relationship) within the broader M26 category of dentofacial anomalies including malocclusion. Use it when documentation supports an abnormal interarch distance — excessive or insufficient space between the upper and lower arches — that is not better captured by a more specific sibling code. Clinically, this includes conditions like excessive interocclusal clearance or collapsed vertical dimension that affect bite function, TMJ loading, or prosthetic planning.
This code is most commonly assigned in oral and maxillofacial surgery, orthodontic, or prosthodontic contexts. It may appear as a primary diagnosis driving orthognathic surgical planning or as a secondary diagnosis supporting medical necessity for orthodontic treatment, splint therapy, or oral appliance fabrication. If the anomaly is limited to tooth position rather than arch relationship, look first at M26.36 (insufficient interocclusal distance of fully erupted teeth) or M26.37 (excessive interocclusal distance) before defaulting to M26.25.
Do not use M26.25 for TMJ disorders — those belong under M26.6x. If the interarch distance anomaly is part of a broader malocclusion, code all applicable M26.2x conditions; ICD-10-CM does not restrict multiple codes within this subcategory when clinically warranted.
Sibling codes
Other billable codes under M26.2 (laterality / anatomic variants).
Frequently asked questions
Source · Generated from the editorial pipeline, verified against 6 cited references ↓
01What is interarch distance, and why does its anomaly get its own ICD-10 code?
02When should I use M26.25 versus M26.36 or M26.37?
03Can M26.25 be used alongside other M26.2x codes on the same claim?
04Is M26.25 appropriate for a diagnosis of reduced vertical dimension in a denture patient?
05Does M26.25 require a 7th character?
06What CPT procedures are most commonly linked to M26.25?
07Can an orthopedic or oral maxillofacial surgeon assign M26.25, or is it limited to dentists?
Sources & references
Editorial content was developed using the following public sources. Last verified May 8, 2026.
- 01CDC ICD-10-CM Tabular List 2026
- 02icd10data.comhttps://www.icd10data.com/ICD10CM/Codes/M00-M99/M26-M27/M26-/M26.25
- 03cms.govhttps://www.cms.gov/files/document/fy-2026-icd-10-cm-coding-guidelines.pdf
- 04aapc.comhttps://www.aapc.com/codes/icd-10-codes/M26.25
- 05findacode.comhttps://www.findacode.com/icd-10-cm/icd-10-cm-diagnosis-codes-M26-group.html
- 06outsourcestrategies.comhttps://www.outsourcestrategies.com/blog/what-are-the-different-types-of-malocclusions-and-their-icd-10-codes/
Mira AI Scribe
The Mira AI Scribe captures the provider's documented interarch distance finding — including whether it is excessive or insufficient, the affected arch region, any cephalometric or radiographic measurements, functional complaints (chewing, speech, TMJ symptoms), and prior treatment history. This prevents claim submission with unspecified fallback codes (M26.20 or M26.4) that trigger payer downcoding and medical necessity flags.
See how Mira captures M26.25 documentation