ICD-10 Code M35.2: Behçet’s disease diagnosis and billing reference

Key takeaways

ICD-10 code M35.2 is the billable ICD-10-CM code for Behçet’s disease, valid for FY2026 claims from October 1, 2025.

Behçet’s disease is a rare systemic vasculitis, and it sits under the non-billable parent category M35 in chapter M00-M99.

One code carries the diagnosis, so document active manifestations such as oral ulcers, uveitis, and skin lesions as additional diagnoses.

The International Criteria for Behçet’s Disease, or ICBD 2014, is the current diagnostic standard, and a score of 4 meets the threshold.

Practice management software like Pabau keeps rheumatology and multi-specialty notes in one record, so M35.2 documentation holds up under payer review.

ICD-10 code M35.2 is the billable ICD-10-CM diagnosis code for Behçet’s disease, a rare systemic vasculitis. It codes the condition itself rather than its individual manifestations. One code therefore carries the diagnosis across every organ system involved.

In practice, active findings such as uveitis, oral ulcers, or a deep vein thrombosis are coded alongside M35.2 as additional diagnoses. They never replace it once the provider has documented the disease as established.

Under CMS ICD-10-CM coding guidelines, every HIPAA-covered electronic transaction in the US carries ICD-10-CM diagnosis codes. Specifically, for Behçet’s disease that means M35.2, with concurrent codes added where the record supports them.

M35.2 code details and billable status

M35.2 is a specific, billable ICD-10-CM diagnosis code. Specifically, it is valid for claims in the FY2026 code year, effective October 1, 2025. In practice, use it for any encounter where Behçet’s disease is active, under evaluation, or being managed.

The parent code M35 is a non-billable header, so never submit it alone on a claim. By contrast, M35.2 is the child code that carries the clinical detail payers expect. In practice, you can confirm its current billable status in the CDC/NCHS ICD-10-CM web tool, which mirrors the official Tabular List.

Practice management software like Pabau keeps the coded diagnosis attached to the encounter record, so a coder can see what the note supports. That check happens before billing, which is where a non-billable header code would otherwise slip through.

What is Behçet’s disease?

Behçet’s disease is a rare, chronic systemic vasculitis, meaning inflammation of blood vessels throughout the body. Specifically, it is autoimmune-mediated, with both genetic susceptibility and environmental triggers involved. In particular, the strongest known genetic association is with HLA-B51.

Prevalence is highest along the ancient Silk Road trade route, from East Asia through the Middle East to the Mediterranean. In fact, that history is why some literature still calls it Silk Road disease. US prevalence is low, so it qualifies as a rare disease.

Rheumatologists and ophthalmologists in tertiary care still see it regularly. For example, other systemic vasculitides carry their own codes, and hypersensitivity angiitis is reported with M31.0.

Clinicians use “disease” and “syndrome” for the same condition, and both map to M35.2. In practice, the ICD-10-CM Alphabetic Index is what makes that equivalence explicit.

Multi-specialty practices that see autoimmune patients need one client record for all of it. In turn, that record holds rheumatology notes, ophthalmology findings, and whatever a dermatology practice adds. When every clinician writes into the same file, the coder is not chasing three systems for one encounter.

Diagnostic criteria for Behçet’s disease

Two criteria sets are in clinical use. First, the 1990 International Study Group, or ISG, criteria required recurrent oral ulceration at least three times in 12 months. In addition, two of the following features had to be present:

• Recurrent genital ulceration
• Eye lesions, including uveitis or retinal vasculitis
• Skin lesions such as erythema nodosum, pseudofolliculitis, or acneiform lesions
• A positive pathergy test

Second, the International Criteria for Behçet’s Disease (ICBD 2014) has since replaced ISG in most clinical and research settings. It scores findings by points instead of running a checklist. In turn, that change recognizes that vascular and neurological disease carry diagnostic weight on their own.

A total of 4 points or more meets the ICBD threshold. In practice, documentation should record which criteria were met, and at which encounter. Where the workup includes a pathergy test or HLA-B51 typing, filing those lab results against the record keeps the score verifiable.

Common manifestations and symptoms

Coders working Behçet’s encounters need the full symptom spectrum. Not every symptom earns its own code, but documenting each one strengthens the M35.2 assignment and informs concurrent coding.

• Oral aphthous ulcers: Recurrent, painful ulcers of the oral mucosa, and the most consistent feature across patient populations
• Genital ulcers: Painful lesions on the scrotum, vulva, or vaginal mucosa. They often scar as they heal, which separates them from herpes lesions
• Uveitis: Anterior, posterior, or pan-uveitis. Posterior uveitis and retinal vasculitis carry the greatest risk of vision loss
• Skin lesions: Erythema nodosum, pseudofolliculitis, acneiform lesions, and superficial thrombophlebitis
• Vascular involvement: Deep vein thrombosis, arterial aneurysms, and Budd-Chiari syndrome in severe cases
• CNS manifestations: Parenchymal disease, or neuro-Behçet, presenting as headache, meningoencephalitis, or pyramidal signs
• Arthritis: Non-erosive, asymmetric oligoarthritis, usually in large joints
• Gastrointestinal involvement: Ulceration, most commonly in the ileocecal region

Each active manifestation in the record may warrant a concurrent code alongside M35.2. The next section lists the ones reported most often. Practices using digital intake forms for rheumatology visits can pre-populate organ-system review fields, so active symptoms are captured before the provider writes the note.

Inclusions, exclusions, and parent code hierarchy

Three things around M35.2 cause most classification errors. In particular, the index entry, the parent code, and the single exclusion note are each worth a moment.

Index entry for Behçet’s syndrome

The ICD-10-CM Alphabetic Index lists Behçet’s syndrome and points it to M35.2. However, the Tabular List carries no separate Includes note for the term. So it is an index entry rather than a tabular inclusion, and either way the two terms produce one code.

Parent code and code block

M35.2 sits in the M35 category, Other systemic involvement of connective tissue. M35 in turn sits in the M30-M36 block, Systemic connective tissue disorders. Neither is billable, so M35.2 is the four-character code that carries billable status.

The same block structure appears in the WHO ICD-10 classification, which ICD-10-CM builds on with additional character detail.

Exclusions at the M35 level

M35 carries one Excludes1 note, for reactive perforating collagenosis, coded L87.1. In other words, an Excludes1 note means the two conditions are never reported together on the same encounter. Accordingly, check the AAPC ICD-10-CM code range for the sibling codes under this category.

For practices handling complex autoimmune documentation, an EHR integration that surfaces exclusion notes during the encounter keeps excluded pairings off the bill.

Codes reported alongside M35.2

M35.2 codes the primary diagnosis, and active manifestations are coded concurrently. In short, the table below lists the codes reported most often in Behçet’s encounters.

Code M35.2 first, then the manifestation codes as additional diagnoses. Do not swap M35.2 for a symptom code once the disease is established and documented. For example, Behçet’s arthropathy indexes to M14.8-, and M35.2 is sequenced ahead of it.

Degenerative joint disease is a separate diagnosis, not a substitute. Where a patient also carries knee osteoarthritis coded M17.5 or thumb-base disease coded M18.4, those codes stand on their own.

Documentation that supports the code

Correct code assignment is half the work. Still, the documentation behind it has to survive a payer audit.

Confirm the diagnosis before coding

Assign M35.2 when the provider documents Behçet’s disease as established. Instead, do not assign it from signs and symptoms alone. During the workup, code the presenting manifestations individually until the diagnosis is confirmed in the record.

Principal versus additional diagnosis sequencing

For outpatient visits focused on Behçet’s management, M35.2 is usually the principal diagnosis. If the patient presents for an urgent uveitis flare, the uveitis code may sequence first. M35.2 then becomes an additional diagnosis. In short, sequencing follows what drove the encounter, per CMS coding guidelines.

Laterality and specificity for ocular codes

Concurrent uveitis and other ocular codes require laterality in ICD-10-CM: right eye, left eye, or bilateral. Unspecified laterality codes exist, but they raise denial risk. As a result, the record should name the involved eye at every ocular encounter.

Structured encounter forms can make laterality a required field at the point of care. In turn, that is one of the medical form design choices that keeps a record audit-ready. Consistent records also support HIPAA-compliant record-keeping for a condition tracked over years.

MS-DRG mapping for inpatient encounters

On an inpatient claim with M35.2 as the principal diagnosis, the code groups into a connective tissue disease MS-DRG. However, MS-DRG assignments change with each fiscal year revision. Verify the FY2026 grouping against the current CMS grouper files before the claim goes out.

Alternate names you will see in records

Records and referral letters use several terms for this condition. Still, all of them map to M35.2.

• Behçet’s syndrome
• Behcet’s disease (alternate spelling, without diacritic)
• Behcet disease
• Silk Road disease
• Adamantiades-Behçet disease (historical, used in older European literature)
• Ocular Behçet disease (descriptive term emphasizing ophthalmologic manifestations)
• Triple symptom complex (older clinical term, rarely used now)

A term alone is not enough to assign the code. Instead, verify the clinical context supports the systemic diagnosis first. “Silk Road disease” in particular deserves a chart check, since the phrase also gets used loosely.

Sibling codes within the M35 category

M35 holds several sibling codes that come up in a Behçet’s differential or in related connective tissue diagnoses. Two of them are headers rather than codes you can bill.

For example, M35.81 covers multisystem inflammatory syndrome and M35.89 covers other specified involvement. Reaching for M35.0 or M35.8 on a claim is the same error as reaching for M35, since none of the three are valid codes.

Never report M35.9 when a specific child code is documented and available. Consequently, unspecified codes invite medical necessity review. Standardized workflows that default to the most specific documented code keep that from happening, which matters most in practices handling complex patient care.

How Pabau supports multi-specialty Behçet’s documentation

Right now, a Behçet’s patient’s history is usually spread across systems. For example, the rheumatology note lives in one place, the ophthalmology letter in another, and the ICBD score in a paper chart. When a payer asks what supported M35.2 in March, someone spends an afternoon assembling the answer.

Pabau holds all of it in one client record. In turn, custom forms capture the organ-system review and the ICBD criteria as structured fields, so the score is never buried in free text. Meanwhile, photos, lab results, and letters attach to the same timeline.

Similarly, practices that run infusion appointments for refractory disease can keep those infusion notes in the same record. Compliance tools show who accessed the file and when, which is what an audit request asks for.

The outcome is a record that answers a documentation request without a hunt. In fact, thin notes are the most common reason a rare disease claim gets questioned, and the fix belongs at the point of care.

Keep every M35.2 encounter audit-ready

Pabau brings client records, digital forms, and billing into one system. Practices coding complex diagnoses like M35.2 can capture every active finding as a structured field. The documentation behind the code is then there when someone asks for it.

Book a demo

Conclusion

Rare disease coding asks more of the record than routine billing does. Specifically, M35.2 gives you one billable assignment for Behçet’s disease. In turn, holding on to it means the note shows active findings, the ICBD criteria met, and laterality for anything ocular.

Specificity costs a few minutes at the encounter and saves hours at review. In short, that is the trade-off worth remembering. As a result, a practice that captures the organ-system review as a structured field never reconstructs it later.

Pabau’s client records and configurable forms build that habit into the workflow, so nothing falls between the clinical note and the bill. Book a demo to see how Pabau handles rheumatology and multi-specialty documentation.

Continue your research

Coding another systemic vasculitis? ICD-10 code M30.0 walks through polyarteritis nodosa documentation and the codes reported with it.

Need the giant cell arteritis pairing? ICD-10 code M31.5 covers the combined arteritis and polymyalgia rheumatica assignment.

Documenting a necrotizing vasculopathy? ICD-10 code M31.8 explains when the other specified code is the right choice.

Wondering how long these records have to stay? Medical record retention rules sets out what each state requires.

Frequently asked questions