ICD code H46.2 – Nutritional optic neuropathy

Key takeaways

H46.2 is a billable ICD-10-CM code for optic neuropathy caused by a documented nutritional deficiency such as B12 or folate.

H46.2 does not require a laterality modifier, unlike the H46.1x retrobulbar neuritis series. Adding one is a coding error.

Documentation must name the specific nutritional deficiency to justify H46.2 over the unspecified fallback H46.9.

H46 carries Excludes2 notes for H47.01- and G36.0, so those codes may be reported alongside H46.2 when each mechanism is documented.

Pabau’s claims management software checks the fields a payer requires on each claim before it is sent, reducing avoidable rejections.

What is ICD-10 code H46.2?

ICD-10 code H46.2 is the billable ICD-10-CM diagnosis code for nutritional optic neuropathy. Assign it when the record attributes optic nerve damage to a confirmed nutritional deficiency.

The code sits in the H46 Optic neuritis category, inside the H46-H47 block for disorders of optic nerve and visual pathways. That block belongs to chapter H00-H59, diseases of the eye and adnexa. H46.2 reached the 2026 ICD-10-CM release without revision and stays valid for HIPAA-covered electronic transactions.

The quick-reference facts coders check first are summarized in the table below.

H46.2 within the H46 optic neuritis code family

H46 is the parent code for optic neuritis. It is not billable on its own, so coders reach for one of its six specific subcodes. The split that matters most is laterality. The H46.0x and H46.1x series carry laterality extensions, while the etiology-based subcodes from H46.2 onward do not.

H46.3 (toxic optic neuropathy) is the closest structural parallel to H46.2. Both are etiology-specific, both lack laterality extensions, and both need documented causation in the clinical record. Coders who hold that parallel in mind stop defaulting to H46.9 when the cause is already sitting in the note.

Nutritional causes that support H46.2 assignment

Nutritional optic neuropathy results from deficiency of micronutrients essential to optic nerve function. The clinical record must specify the nutritional etiology, not just note optic nerve damage, for H46.2 to be supported. The deficiencies most commonly associated with this diagnosis include the following.

• Vitamin B12 (cobalamin) deficiency: the most frequently documented cause. Associated with strict vegan diets, pernicious anemia, and malabsorption syndromes. Serum B12 levels below the laboratory reference range, combined with optic nerve findings, form the documentation foundation.
• Folate (folic acid) deficiency: less common than B12 but clinically recognized. Documentation should record confirmed folate deficiency alongside the optic neuropathy diagnosis.
• Thiamine (B1) deficiency: associated with alcohol-related malnutrition and Wernicke encephalopathy. When optic neuropathy is part of a broader thiamine-deficiency presentation, H46.2 may apply alongside appropriate nutritional deficiency codes.
• Alcohol-related nutritional depletion: chronic alcohol use can deplete B12, folate, and thiamine simultaneously. The clinical note should name which specific deficiency is driving the optic manifestation.

The B12 and folate associations above come from published clinical literature on nutritional optic neuropathy. Where a specific deficiency type is in question, check the WHO ICD-10 classification notes and current AHA Coding Clinic guidance. If the record does not specify the deficiency, H46.2 is not supportable regardless of clinical suspicion.

Includes and excludes notes for H46.2

The includes and excludes notes at the H46 parent level define the outer boundaries of H46.2. Misreading them is the primary route to a misassigned or denied claim. Per the CDC/NCHS ICD-10-CM tool, the relevant notes at the H46 block level are as follows.

• Includes: retrobulbar neuritis NOS (not otherwise specified) maps into H46 and is directed to the H46.1x series, not to H46.2.
• Excludes2: ischemic optic neuropathy (H47.01-) is classified outside H46. Excludes2 marks a separate condition, so H46.2 and H47.01- may both be reported when each is documented.
• Excludes2: neuromyelitis optica, or Devic disease, is coded to G36.0 and also sits outside H46. The same permission applies, so both codes can appear when the record supports each diagnosis.

Excludes2 is the permissive note, and reading it as Excludes1 is the error that costs practices legitimate revenue. It tells the coder that the excluded condition belongs elsewhere in the classification. It does not say the patient cannot have both. The table below sets out what each note at H46 actually allows.

Does H46.2 require laterality?

No, ICD-10 code H46.2 does not require laterality. That is the most operationally important structural fact about the code, and it is where preventable errors cluster.

The H46.1x series (retrobulbar neuritis) carries four laterality extensions: H46.10 (unspecified eye), H46.11 (right eye), H46.12 (left eye), and H46.13 (bilateral). Coders working across H46.1x and H46.2 in the same session often carry the laterality habit over.

H46.2 has no such extensions in the ICD-10-CM tabular list. Submitting it with an appended laterality character produces an invalid code, and the claim picks up an edit before it reaches the payer.

When nutritional optic neuropathy affects only one eye, H46.2 is still the correct code. The laterality does not change the code assignment. Document the laterality in the clinical record for completeness, but do not append it to the code.

Documentation requirements for H46.2

Supporting ICD-10 code H46.2 takes documentation that ties the optic nerve findings directly to a nutritional deficiency. A clinical impression of “nutritional optic neuropathy” with no lab data or dietary history behind it will not pass payer scrutiny. The CMS ICD-10 coding guidelines require every diagnosis code to be supported by clinical evidence in the medical record.

The essential documentation elements for H46.2 are listed below.

• Confirmed nutritional deficiency: laboratory results showing subnormal serum B12, folate, or relevant micronutrient levels. The specific deficiency must be named, not inferred.
• Optic nerve findings: fundoscopic or imaging evidence of optic nerve involvement (pallor, disc changes, reduced visual acuity consistent with optic neuropathy).
• Causal link documented by the clinician: the treating physician must state in the record that the nutritional deficiency caused the optic neuropathy. A co-occurring low B12 and an unrelated optic finding do not justify H46.2 on their own.
• Assessment of vascular and autoimmune causes: the record should note whether ischemic or demyelinating causes were assessed. Where one of them is also documented, H47.01- or G36.0 is reported in addition to H46.2, not instead of it.

Structured note templates that capture these four elements at the point of care cut the volume of coding queries that come back later. Pabau, our practice management platform, adds software for billing teams that checks each claim for the fields the payer requires before it goes out. Membership and authorization numbers are the usual omissions. Judging whether the documentation supports H46.2 rather than H46.9 stays with the clinician and the coder.

Common coding errors to avoid with H46.2

Three errors account for the majority of H46.2 claim problems. Each is preventable with the right documentation habits and billing workflow.

• Using H46.9 when the nutritional cause is confirmed. Once the clinical record documents a specific deficiency and a causal link to the optic neuropathy, H46.9 (unspecified) is no longer appropriate. Defaulting to the unspecified code when a specific one is supported is a coding accuracy failure, and payers auditing specificity patterns flag it. Tracking the common denial codes your payers return will surface the habit before it becomes a trend.
• Treating H46.2 and H47.01- as interchangeable. Both present with visual loss and optic disc changes, and the separator is mechanism. H46.2 needs a confirmed nutritional deficiency, while H47.01- needs documented vascular compromise. The Excludes2 note at H46 lets both codes stand on one claim when both mechanisms are documented. When the etiology is genuinely unclear, H46.9 is more defensible than guessing.
• Applying laterality extensions to H46.2. As covered above, H46.2 has no laterality subcodes. Appending a right/left character creates an invalid code. This error often originates in EHR templates copied from the H46.1x series.

A fourth, less common error is coding neuromyelitis optica presentations to H46.2. Devic disease belongs to G36.0, and the Excludes2 note at H46 classifies it apart from the optic neuritis category. That note separates the two conditions rather than barring them from the same claim.

H46.2 vs related codes: choosing the right code

The decision between H46.2 and its nearest differentials comes down to documented mechanism. The table below maps each code to its etiology and the documentation required to support it.

A patient can present with optic neuropathy, low B12 levels, and cardiovascular risk factors for ischemia at once. The coder is not forced to choose between H46.2 and H47.01- there. Both may be reported when the clinician documents each mechanism separately. Where only one mechanism is supported, that determination decides the single code.

When to use H46.9 instead of H46.2

H46.9 is the unspecified fallback within the H46 family. Use it when the clinical record carries no confirmed etiology for the optic neuritis.

H46.9 is the defensible choice while laboratory results are pending or the workup is incomplete. It also fits where the clinician has listed optic neuropathy with no cause attached. Once the deficiency is confirmed and documented, correct the claim or code the next encounter to H46.2.

Billing and submitting ICD-10 code H46.2

H46.2 is a valid code for HIPAA-covered electronic transactions, including CMS-1500 and 837P claim submissions. Practices submitting ophthalmology or neurology claims with H46.2 should still check payer-specific coverage policies. Some commercial payers want a nutritional deficiency code from the E40-E64 range as a secondary diagnosis, to corroborate the etiology.

Submitting through a clearinghouse puts a checking layer between your practice management system and the payer. Pabau integrates with Claim.MD, a US clearinghouse that reaches thousands of payers and handles 837P claim submission. The integration also carries real-time eligibility checks and electronic remittance advice, so posting and follow-up run off the payer’s own response.

Our guide to the Claim.MD clearinghouse walks through that submission path end to end. Reading it before you switch H46.2 billing over saves a round of rejected test claims.

Billing teams should also confirm that the claim form carries every required data element. H46.2 is valid for submission, but a missing subscriber or authorization field will stop the claim whatever the diagnosis code says.

Is H46.2 valid for 2026?

Yes, ICD-10 code H46.2 is valid for fiscal year 2026. The code appears in the 2026 ICD-10-CM tabular list without revision. Its descriptor, billable status, and position within the H46 family are unchanged from prior years. No new Excludes notes or inclusion terms were added for FY 2026 that affect H46.2 specifically.

Coders can verify current-year validity directly through the AAPC ICD-10-CM code lookup or the official CMS release files. Annual code set updates take effect October 1 each year. H46.2 was not flagged for deletion or revision in the draft FY 2026 update tables. Practices that set calendar reminders to re-verify code validity each October avoid submitting claims under retired codes.

How Pabau keeps H46.2 claims clean before they leave the practice

Most ophthalmology and neurology teams find a bad H46.2 claim only after the payer returns it. The note goes back to the clinician, the coder re-reads it, and the claim is resubmitted weeks later. The deficiency was documented the whole time.

Pabau, our practice management software, holds the note, the code and the claim in one patient record. Charting templates can prompt for the serum B12 or folate value and for the clinician’s causal statement at the point of care. The coder then works from a note that already carries what H46.2 needs.

Before submission, Pabau checks each claim for the fields the payer requires and routes it electronically through Claim.MD. Remittance advice returns into the same record, so your team can see which H46.2 claims paid without exporting a separate report.

Send H46.2 claims with the fields payers require

Pabau checks every required field on a claim before it reaches the clearinghouse. Your ophthalmology and neurology claims stop coming back for missing data.

Book a demo

Conclusion

Two rules prevent most of the trouble with H46.2. Confirm the nutritional etiology in writing before you assign the code, and never append a laterality character to it. Everything else on this code follows from documentation that was either done at the visit or was not.

The Excludes2 notes at H46 are worth re-reading if your team has been treating them as prohibitions. Where ischemia or Devic disease is documented alongside the nutritional mechanism, H47.01- or G36.0 belongs on the claim next to H46.2. Coding one and dropping the other understates the encounter and the revenue attached to it.

For teams submitting H46.2 at volume, the fix sits upstream of billing, in the note rather than the claim scrubber. Book a demo to see how Pabau links the deficiency lab, the clinical note and the H46.2 claim in one record.

Continue your research

Need to understand how clearinghouse validation works for ICD-10 claims? Medical claims clearinghouse guide explains how real-time code validation reduces optic nerve and other specialty claim denials.

Want a systematic approach to reducing coding denials across your practice? Denial management in healthcare shows billing teams how to read denial reasons and spot a trend before it compounds.

Looking for billing compliance guidance for your clinic software? Medical billing compliance outlines the documentation and submission standards that support accurate ICD-10 code assignment.

Frequently asked questions