M26.35 identifies an anomaly of tooth position in which a fully erupted tooth or multiple fully erupted teeth are axially rotated out of their normal alignment within the dental arch.
Verified May 8, 2026 · 7 sources ↓
- Status
- Billable
- Chapter
- 13
- Related CPT
- 5
- Region
- Other
Documentation tips
What should appear in the chart to support M26.35.
Source · Editorial brief grounded in 7 cited references ↓
- Specify that the affected tooth or teeth are fully erupted — without this, the M26.3x subcategory does not apply and the claim is exposed to query.
- Identify the rotated tooth by universal numbering system (e.g., tooth #7, #11) or arch position in the clinical note to support medical necessity for orthodontic or surgical intervention.
- Distinguish rotation (axial turn on long axis) from horizontal displacement (M26.33) or vertical displacement (M26.34) — the treatment approach and correct code differ.
- If crowding is also documented, add M26.31 as a secondary diagnosis; both codes may be reported together when both conditions are clinically present.
- Include supporting imaging findings (periapical radiograph, panoramic X-ray, CBCT) in the encounter note to substantiate the positional anomaly diagnosis.
Related CPT procedures
Procedure codes commonly billed with M26.35. 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.35 and adjacent codes.
Source · Editorial brief grounded in CDC ICD-10-CM tabular guidance, AAOS coding references, and cited references ↓
- Billing M26.3 (the parent) instead of M26.35 — M26.3 is non-billable and will reject; always use the specific child code.
- Using M26.35 when the tooth is impacted or unerupted — impacted teeth belong under K01, not anywhere in M26.3.
- Defaulting to M26.30 (unspecified) when the provider's note clearly documents rotation — specificity is available and payers expect it.
- Omitting a secondary arch-relationship code (e.g., M26.31 crowding) when both conditions are documented, leaving reimbursement and clinical picture incomplete.
- Confusing tooth rotation with horizontal or vertical displacement — review the clinical description carefully before selecting M26.33, M26.34, or M26.35.
Clinical context
Source · Editorial summary grounded in 7 cited references ↓
M26.35 falls under parent category M26.3 (Anomalies of tooth position of fully erupted tooth or teeth), itself nested within M26 (Dentofacial anomalies including malocclusion). Use this code when the documented finding is rotational displacement — a tooth turned on its long axis — and the tooth or teeth in question have fully erupted. The fully-erupted qualifier is load-bearing: embedded or impacted teeth are excluded from the entire M26.3 subcategory and belong under K01 instead.
This code is commonly applied in orthodontic, oral surgery, and maxillofacial contexts to justify treatment planning for rotated incisors, canines, or premolars. It may appear as a primary diagnosis when rotation is the chief complaint driving treatment, or as a secondary diagnosis alongside arch-relationship codes such as M26.31 (crowding) when both conditions coexist. The Type 2 Excludes note under M26.3 permits coding M26.35 together with K01 if a patient has both rotated erupted teeth and a separate impacted tooth.
Do not stop at the parent code M26.3 — it is non-billable. M26.35 is the billable, claim-ready code. If the anomaly type is not documented specifically enough to distinguish rotation from horizontal displacement (M26.33) or vertical displacement (M26.34), drop to M26.30 (unspecified anomaly of tooth position of fully erupted tooth or teeth) pending clarification.
Sibling codes
Other billable codes under M26.3 (laterality / anatomic variants).
Frequently asked questions
Source · Generated from the editorial pipeline, verified against 7 cited references ↓
01Can M26.35 be used for a tooth that is only partially erupted?
02Can M26.35 and M26.31 (crowding) be coded together on the same claim?
03Is M26.35 valid as a primary diagnosis for orthodontic treatment authorization?
04What is the difference between M26.35 and M26.33 or M26.34?
05Does M26.35 require a 7th-character extension?
06Is M26.35 used in medical billing, dental billing, or both?
Sources & references
Editorial content was developed using the following public sources. Last verified May 8, 2026.
- 01CDC ICD-10-CM Tabular List 2026 — https://www.cdc.gov/nchs/icd/icd-10-cm/files.html
- 02icd10data.comhttps://www.icd10data.com/ICD10CM/Codes/M00-M99/M26-M27/M26-/M26.35
- 03icd10data.comhttps://www.icd10data.com/ICD10CM/Codes/M00-M99/M26-M27/M26-/M26.3
- 04aapc.comhttps://www.aapc.com/codes/icd-10-codes/M26.35
- 05outsourcestrategies.comhttps://www.outsourcestrategies.com/blog/icd-10-codes-report-different-types-malocclusions/
- 06dental.nv.govhttps://dental.nv.gov/uploadedFiles/dentalnvgov/content/Home/Features/ICD-10%20Dental%20Diagnosis%20Codes.pdf
- 07cms.govhttps://www.cms.gov/files/document/fy-2026-icd-10-cm-coding-guidelines.pdf
Mira AI Scribe
Mira's AI scribe captures the eruption status of the affected tooth, its location by arch and universal number, the direction and degree of axial rotation as described or measured by the provider, and any supporting radiographic findings (periapical film, panoramic, CBCT). That documentation locks in M26.35 over the non-specific M26.30 and prevents a K01 mismatch if an impacted tooth is noted separately in the same encounter.
See how Mira captures M26.35 documentation