ICD code M95.0 – Acquired deformity of nose

Key takeaways

M95.0 is a billable ICD-10-CM code for acquired, non-congenital nasal deformity, valid for 2026 submissions.

J34.2 (deviated nasal septum) is an Excludes2 note on M95.0, so both codes can be reported together when documented.

M95.0 supports rhinoplasty CPT codes 30400-30450, but medical necessity still needs documented functional impairment.

Pabau’s claims management software embeds ICD-10 code lookup and Claim.MD clearinghouse integration to reduce M95.0 denials.

ICD-10 Code M95.0: full code definition and descriptor

ICD-10 Code M95.0 is the specific, billable subcode for acquired deformity of the nose. It sits within the M95 category, Other acquired deformities of the musculoskeletal system and connective tissue. The parent code M95 is non-billable, so M95.0 is the code to submit on a claim. Per the CDC/NCHS ICD-10-CM tool, M95.0 carries no non-billable notation and needs no 7th character extension.

The code belongs to Chapter 13, Diseases of the musculoskeletal system and connective tissue (M00-M99). Within that chapter it sits in the block M95-M95, Other disorders of the musculoskeletal system and connective tissue. Chapter placement matters because coders sometimes search Chapter 10 for nasal conditions. That lands them on respiratory J-codes, which do not describe structural deformities of acquired origin.

Clinical presentations captured by M95.0 include:

• Post-traumatic nasal deformity following a resolved fracture
• Saddle nose deformity from prior septal surgery or infection
• Boxer’s nose
• Any other acquired structural change to the external or internal nasal architecture

Congenital nasal deformities are excluded and coded instead under Q30-Q30.9. Confirming the acquired-versus-congenital distinction is the first documentation step before M95.0 is assigned.

Excludes notes that affect M95.0 claims

The official ICD-10-CM tabular for M95.0 carries instructional notes that affect claim validity. The one coders misread most often is the Excludes2 note covering J34.2.

Excludes2 note

Excludes2 means the listed condition is not part of M95.0, though a patient can have both at once. Per the CMS ICD-10-CM guidelines, an Excludes2 note allows the two codes on the same claim where the record documents each one. The Excludes2 note at M95.0 covers:

• J34.2 (Deviated nasal septum): M95.0 and J34.2 may both be reported when the chart documents a deviated septum alongside a broader acquired deformity. Where septal deviation is the only finding, J34.2 stands alone. Where the deformity is broader, such as saddle nose or a post-traumatic external change, M95.0 applies.

Congenital exclusion

Congenital nasal deformities (Q30.8 and related Q30 codes) are not included under M95.0. The differentiator is onset. Present at birth means a congenital Q-code, while a deformity that developed after birth through trauma, surgery, or infection means M95.0. Payers routinely flag the mix-up during automated claim edits.

Adjacent codes coders confuse with M95.0

Four codes are regularly confused with M95.0. The table below shows each code, its descriptor, and the single most important differentiator. Refer to the AAPC ICD-10-CM lookup to verify current descriptor alignment before finalizing any claim.

The M95.1 confusion turns up often in ENT and facial plastic billing. Coders search “acquired deformity” in the M95 category, then select M95.0 when the chart actually describes an auricular hematoma. Always confirm the anatomical site before submitting.

Which code, or which pair of codes, belongs on the claim follows from what the note documents. The panel below routes the five scenarios this article covers.

When to use M95.0: clinical scenarios and sequela coding

Three clinical scenarios account for most M95.0 submissions. Each follows a specific coding logic that the medical record must support.

Scenario 1: Post-traumatic nasal deformity after a resolved fracture

When a nasal fracture has healed but left a residual deformity, the fracture is in its sequela phase. Per the ICD-10-CM Official Guidelines (Section I.C.19.a), sequela coding lists the sequela condition first, then the causative injury code with the 7th character “S”. For a resolved nasal fracture, assign M95.0 as the principal diagnosis and add S02.2xxS as a secondary code. Do not use the active fracture code S02.2xxA once the fracture has healed.

Scenario 2: Saddle nose deformity from prior septal surgery or infection

Saddle nose is a collapse of the nasal bridge following septal surgery, cocaine use, or granulomatous infection. The ICD-10-CM Alphabetic Index routes it to M95.0 under “Deformity, nose, acquired”. The chart must document the causative event, because payers treat saddle nose without an etiology as an unsubstantiated diagnosis. Record that etiology as a secondary code where one applies.

Scenario 3: Acquired deformity supporting functional rhinoplasty

When M95.0 supports a rhinoplasty procedure, the record must also document functional impairment. M95.0 alone rarely satisfies medical necessity for surgical payers. The note should capture airway obstruction, breathing difficulty, or epistaxis linked to the structural deformity. A secondary code such as J34.89 for functional compromise strengthens the claim where the deformity has a measurable airway impact.

M95.0 as a supporting diagnosis for rhinoplasty procedures

M95.0 is the standard diagnosis pairing for functional and reconstructive rhinoplasty. It supports the CPT codes surgeons bill when correcting acquired nasal deformities, including CPT code 30420 for a primary rhinoplasty with major septal repair.

The cosmetic-versus-reconstructive distinction drives payer coverage decisions, not CPT code selection alone. M95.0 supports the reconstructive argument where the documentation establishes an acquired etiology and a functional consequence. Without both, most payers reclassify the procedure as cosmetic and deny the claim. Confirm CPT descriptors for the current year in the AMA CPT manual, since they are updated annually.

Documentation requirements for M95.0 claims

Documentation is what separates a clean M95.0 claim from a denial. CMS guidance and commercial payer local coverage determinations (LCDs) for nasal reconstruction agree on what the record needs. These elements should be present before M95.0 is assigned.

• Documented etiology: The provider’s note must state the cause of the deformity. “Post-traumatic nasal deformity” without the injury event, meaning an approximate date and mechanism, is insufficient for most payers. “Saddle nose deformity following septal surgery performed 2026” is the standard format.
• Physical examination findings: Describe the deformity objectively, using anatomical landmarks. Most surgical payers require photographic documentation, and the operative note should reference it.
• Functional impairment notation: Where M95.0 supports a rhinoplasty claim, the note must state the functional consequence. Airway obstruction, a nasal obstruction score, or difficulty breathing all qualify. Structural deformity alone rarely satisfies medical necessity criteria.
• Prior conservative treatment: Payers increasingly want evidence that non-surgical options were tried or considered before surgical correction. Document this where it applies.
• Acquired versus congenital confirmation: The note should make clear the condition was not present at birth. This heads off automated edits that flag M95.0 on younger patients.

Structured note templates prompt for etiology, functional findings, and prior treatment at the point of care. Practices that build those prompts into the documentation workflow catch problems before claims go out, rather than during a denial audit.

Common claim denial reasons for M95.0 and how to avoid them

M95.0 denials follow predictable patterns. Five reasons account for most of them, and each arrives on the remittance as one of the standard denial codes.

• An unsupported pairing with J34.2: J34.2 sits on M95.0 as an Excludes2 note, so the two codes together are not a coding conflict. Denials arise where only one of the two conditions appears in the chart. Report both codes only when the record documents both, and drop J34.2 where the note describes a broader deformity alone.
• Missing etiology in the record: Coders assign M95.0 on a diagnosis of “nasal deformity” without a documented cause. Payers pull the medical record and find no etiology. Ask the provider to amend the note before resubmitting, not after.
• Cosmetic-versus-reconstructive dispute: The payer classifies the rhinoplasty as cosmetic based on the diagnostic coding alone. Appeal language should quote the physical examination findings showing functional impairment and cite the applicable LCD by number.
• Procedure-to-diagnosis linkage failure: The claim form does not link M95.0 to the rhinoplasty CPT code. Confirm the diagnosis pointer on Box 24E of the CMS-1500 is correctly mapped.
• Congenital versus acquired mismatch: Payer edits flag M95.0 when other codes on the claim suggest a congenital condition. Review the full claim for consistency before submission.

Billing teams that track M95.0 denial reasons by payer can spot patterns specific to individual plans and prepare appeal templates in advance. Using claims management software that validates ICD-10 codes at submission lowers first-pass denial rates without a separate review step.

How Pabau keeps M95.0 claims clean before submission

Most practices find an M95.0 problem only after the remittance arrives. The coder assigns the code, the claim goes out, and a missing etiology or an unsupported J34.2 pairing surfaces as a denial weeks later. By then the chart is closed and the provider has moved on.

Practice management software like Pabau moves that check to the point of documentation. The ICD-10 lookup sits inside the note, so your coder picks M95.0 against its official descriptor rather than from memory. The Claim.MD integration then routes the claim through a clearinghouse serving 4,000-plus US payers. Pre-submission edits run there, before the payer’s adjudication queue sees the claim.

For a rhinoplasty practice, the diagnosis pointer, the etiology note, and the supporting codes are all in place while the chart is still open. Fewer claims come back, and the ones that do come back with a reason the billing team can act on.

Stop M95.0 denials before they start

Pabau’s ICD-10 lookup puts the official M95.0 descriptor and its Excludes2 note in front of your coder. The Claim.MD connection then runs pre-submission edits on every rhinoplasty claim.

Book a demo

2026 ICD-10-CM M95.0 validity and annual update status

M95.0 is valid for FY 2026 with no descriptor change, no new instructional notes, and no effective-date revision from the prior year. The CMS ICD-10-CM 2026 tabular release confirms the code remains active. Check the current-year tabular each October 1, because the M95 category occasionally picks up instructional note revisions even when its subcodes are unchanged.

The ICD-10-CM Alphabetic Index continues to route “Deformity, nose, acquired” to M95.0, and “Saddle nose” to M95.0 as well. Check the index entry for post-traumatic nasal deformity too. Its sequela routing through S02.2xxS occasionally changes between fiscal years.

Conclusion

M95.0 is a straightforward billable code when the documentation does its job. That means a confirmed acquired etiology, physical examination findings, and functional impairment notation on surgical claims. Whether J34.2 belongs on the claim turns on what the chart records, since the Excludes2 note permits the pair. That question and a missing etiology account for most denials on this code.

Build the etiology prompt into the note template first, because that single change removes the most common reason these claims come back. Book a demo to see how Pabau surfaces ICD-10 validation and clearinghouse edits at the point of claim creation.

Continue your research

Need guidance on denial code patterns across claim types? Denial codes in medical billing covers the CARC and RARC codes that appear on M95.0 and rhinoplasty claim remittances.

Want to understand how clearinghouse validation reduces first-pass denials? How the Claim.MD clearinghouse works explains the pre-submission edit process and payer enrollment workflow.

Looking for end-to-end revenue cycle context? What is revenue cycle management covers the full billing workflow from patient encounter to payment posting.

Not sure what a payer counts as a clean claim? Clean claim requirements sets out the fields and attachments that get a claim paid on first submission.

New to the workflow behind these codes? What is medical billing walks through each step a claim takes, from coding to remittance.

Frequently asked questions