ICD-10 code M35.3: Polymyalgia rheumatica billing guide

Key Takeaways

ICD-10 code M35.3 is the billable diagnosis code for polymyalgia rheumatica (PMR), a systemic inflammatory condition that mainly affects adults over 50.

M35.3 is valid for FY2026, effective October 1, 2025, and sits in the M30-M36 block for systemic connective tissue disorders.

An Excludes1 note means M35.3 can never be billed together with M31.5, the code for confirmed giant cell arteritis with PMR.

Documentation must show a confirmed PMR diagnosis, symptom duration, ESR and CRP findings, and exclusion of other inflammatory conditions.

Practice management software like Pabau links M35.3 directly to encounter notes and lab results, cutting the denials caused by incomplete documentation.

ICD-10 code M35.3 is the billable diagnosis code for polymyalgia rheumatica. PMR is a systemic inflammatory condition that causes bilateral muscle pain and stiffness in adults over 50. The code is also one of the more commonly denied in rheumatology billing. Usually, the chart behind it is missing a lab value or a confirmed diagnosis statement.

A coder assigns the code correctly. The payer then asks for the ESR or CRP result, the confirmed diagnosis note, or the symptom timeline. None of it made it into the encounter. That mismatch between the code and its supporting chart turns a clean claim into a denial.

Defining M35.3 is the easy part. The exclusion rule next to it decides whether the claim survives review, and so does the paperwork behind it.

ICD-10 code M35.3: What it covers and where it sits in the hierarchy

ICD-10 code M35.3 designates polymyalgia rheumatica (PMR), a systemic inflammatory condition causing proximal muscle pain and stiffness. The code is billable and specific, accepted for HIPAA-covered transactions throughout fiscal year 2026. It sits within the M30-M36 block for systemic connective tissue disorders. That block is itself part of the broader M00-M99 musculoskeletal chapter.

Two Excludes1 notes sit on this code. They matter more than almost anything else on this page. An Excludes1 note means the two codes involved can never appear on the same claim. At the M35.3 level, the note excludes polymyalgia rheumatica with giant cell arteritis (M31.5). A chart confirming both conditions together always codes to M31.5 instead.

At the M35 category level, the note excludes reactive perforating collagenosis (L87.1). That’s an unrelated skin condition that occasionally gets miscoded into this block. Treat both exclusions as fixed rules, not judgment calls.

Quick question coders ask here: does M35.3 need a fourth character for extra specificity? No. It’s billable exactly as written, with no further breakdown required.

Verify current code validity using the CDC/NCHS ICD-10-CM web tool. It reflects the official U.S. tabular list by fiscal year. Per the CMS ICD-10 codes page, FY2026 covers all encounters from October 1, 2025 through September 30, 2026.

What polymyalgia rheumatica looks like in a patient

PMR is a systemic inflammatory condition that mainly affects adults over 50, with incidence rising sharply after age 70. It typically presents as bilateral aching and morning stiffness across the shoulder and pelvic girdle. That combination is often severe enough to make dressing or standing up from a chair difficult.

Coders who understand the clinical picture assign M35.3 more accurately. That’s because they can recognize what the physician’s documentation is describing. Key clinical features include:

• Bilateral proximal pain affecting the shoulders, neck, upper arms, hips, or thighs
• Morning stiffness lasting more than 45 minutes
• Symptom duration of at least two weeks
• Elevated inflammatory markers, specifically ESR and CRP
• Rapid and dramatic response to low-dose corticosteroids (typically prednisone), which helps confirm the diagnosis
• Absence of features suggesting alternative diagnoses (rheumatoid arthritis, fibromyalgia, inflammatory myopathy)

Corticosteroids remain the first-line treatment under standard rheumatology guidance. Coders working in functional medicine software see this pattern often. PMR management can span years, and M35.3 shows up repeatedly across the same patient’s record. Each encounter needs its own supporting documentation, not a copy-forward from the last visit.

Synonyms and alternate terms that map to M35.3

Physicians document PMR using several clinical terms. Only some of them actually index to M35.3 in the ICD-10-CM alphabetic index. The terms that map cleanly are:

• Polymyalgia
• Polymyalgia, rheumatica

Watch for terms that sound like PMR but code somewhere else. “Polymyalgia arteritica” points to M31.5, not M35.3. So does any note confirming GCA together with PMR, per the same Excludes1 relationship covered above. When the note says only “polymyalgia” or “polymyalgia, rheumatica” with no GCA mentioned, M35.3 is the correct assignment.

What documentation M35.3 actually requires

Insufficient documentation is the leading cause of M35.3 denials. Per HIPAA-compliant documentation standards, the medical record must support every diagnosis code submitted on a claim. For M35.3, the supporting record should include all of the following:

• Confirmed PMR diagnosis by the treating or consulting physician, stated explicitly in the encounter note
• Symptom onset and duration, establishing the bilateral proximal pattern lasting at least two weeks
• ESR and CRP values from the relevant encounter or a recent lab result referenced in the note
• Exclusion of alternative diagnoses, such as rheumatoid arthritis, malignancy, or fibromyalgia, documented in the assessment
• Treatment response notation, particularly the corticosteroid trial outcome, which reinforces the clinical diagnosis
• Prescribing or attesting physician signature on the encounter note

Digital intake forms capture this structured data at the point of care. That cuts down on the missing documentation that leads to downstream coding errors. Practices using patient care management workflows benefit from templates that prompt for each required clinical element. The note needs that prompt before it gets signed.

The documentation errors that get M35.3 claims denied

Several patterns show up again and again on denied M35.3 claims:

• Coding without confirmed diagnosis: “Rule out PMR” or “possible polymyalgia rheumatica” does not support M35.3. Only a confirmed, attested diagnosis warrants the code.
• Confusing PMR with fibromyalgia: These are distinct diagnoses with separate codes (M79.7 for fibromyalgia). Document which condition is confirmed.
• Omitting lab values: ESR and CRP are integral to a PMR diagnosis. A note that references the diagnosis but contains no lab data creates audit risk.
• Missing GCA documentation: when giant cell arteritis is confirmed alongside PMR, the correct code is M31.5, not M35.3 plus a separate GCA code. Coding both conditions under M35.3 alone, or splitting a confirmed combined diagnosis into two codes, is incorrect.
• Vague symptom language: “Muscle aches” or “joint pain” without specifying girdle distribution and bilateral pattern does not map cleanly to M35.3.

Compliance management tools can flag incomplete encounter notes before they reach billing. That gives coders and clinicians a chance to fix the note without delaying the claim.

Before you submit an M35.3 claim

Run the chart against these six points before the claim goes out:

• Confirmed PMR diagnosis stated explicitly in the encounter note, not “rule out” or “possible”
• ESR or CRP value on file from the visit, or a recent, referenced lab result
• Symptom duration of at least two weeks, with a bilateral, girdle-pattern description
• Alternative diagnoses excluded in the assessment, especially fibromyalgia and rheumatoid arthritis
• GCA status addressed directly: confirmed together (code M31.5 instead), confirmed separately (code both), or not present
• Physician signature on the note carrying the diagnosis

M35.3 and giant cell arteritis: How the coding actually works

Giant cell arteritis (GCA) and polymyalgia rheumatica share the same underlying inflammation. The two conditions frequently overlap. A meaningful share of PMR patients develop GCA during their disease course. GCA cases, in turn, often present with PMR symptoms.

When a physician confirms both conditions together, a single combined code applies. M35.3 should never appear alongside a separate GCA code on that same claim, per the Excludes1 note above.

The GCA codes relevant to PMR co-coding are:

When the physician documents GCA with PMR as one combined diagnosis, M31.5 replaces M35.3 as the code. It doesn’t get added alongside it. A separate, concurrent GCA without combined PMR features works differently. M31.6 covers the GCA, M35.3 stays as the PMR code, and sequencing follows whichever condition drove the encounter.

Worked example: a 68-year-old patient presents with new jaw claudication. A temporal artery biopsy confirms GCA on top of an existing PMR diagnosis already managed with prednisone. The note ties both conditions to one confirmed clinical picture, so the claim goes out as M31.5 alone.

Now picture the biopsy coming back negative instead, with the physician documenting an ongoing, unconfirmed GCA workup. In that case, M35.3 stays as the primary code for the PMR visit.

One code that does not belong in this exclusion pair is M31.7. It codes microscopic polyangiitis, a distinct vasculitis with its own diagnostic workup. It carries no Excludes1 relationship with M35.3.

Don’t fold it into the GCA sequencing question above.

The related ICD-10 codes coders reach for around M35.3

Coders working with PMR encounters regularly need adjacent codes for comorbidities, exclusions, and related systemic conditions. The table below covers the most clinically relevant codes in the M30-M36 block.

Coders managing overlapping connective tissue diagnoses also cross paths with M34.2 fairly often. Keep it on your radar alongside this table. For a comprehensive lookup, the AAPC ICD-10-CM code search provides detailed descriptions and crosswalk tools.

Also consult the CMS ICD Code Lists when verifying code inclusion or exclusion. This matters for specific Medicare or Medicaid claim submissions.

How M35.3 maps to an MS-DRG on inpatient claims

When M35.3 serves as the principal diagnosis in an inpatient encounter, the CMS MS-DRG grouper takes over. It assigns the claim to one of the connective tissue disorder DRGs. Assignment depends on the patient’s complications.

That could be a major complication or comorbidity (MCC), a complication or comorbidity (CC), or neither. Verify current DRG numbers against the CMS IPPS Final Rule tables, as MS-DRG assignments are updated annually.

Accurate CC/MCC documentation significantly affects reimbursement for inpatient stays. Coders should review all secondary diagnoses for valid comorbidities. GCA under M31.5 or M31.6 is one example that can qualify as CC or MCC. Confirm that before finalizing the DRG assignment.

How M35.3 has changed since ICD-10-CM launched

M35.3 has remained stable across ICD-10-CM editions since the system’s U.S. adoption in 2015. No description changes or code revisions have affected M35.3 during this period. That makes it a reliable, consistent code for chronic PMR documentation.

Check the ICD List code reference for the latest edition notes and annual update summaries. For institutional coding teams, the CMS publishes annual update tables that list all new, revised, and deleted codes.

Where M35.3 breaks down inside a practice management system

This is also where rheumatology and integrative practices lose the most money. The code can be correct. The chart behind it, sitting inside the EHR or practice management system, might not back it up at all.

A clean M35.3 claim moves through four steps inside the system:

1. The physician confirms PMR in the encounter note, with symptom duration and distribution spelled out.
2. The coder assigns M35.3 and links it to that same note, plus the ESR or CRP result from the visit or a recent lab.
3. Billing checks that a GCA status is documented one way or another, confirmed together, confirmed separately, or ruled out, before the claim goes out.
4. The claim submits with all three pieces attached, so a payer request for supporting documentation gets answered in minutes, not days.

When any one of those links breaks, a payer audit or pre-payment review can step in. It can reject the claim even though the code itself is correct. The EHR integration workflow connects diagnostic codes to encounter documentation. That’s what separates claims that pay on first submission from those that cycle through denials.

How Pabau keeps the code and the chart together

Pabau’s claims management software lets coders attach M35.3 directly to the encounter note and lab results. That happens inside the same electronic client records workflow. A PMR patient returns for a follow-up steroid taper review. The diagnosis code and its supporting documents carry forward automatically. That cuts the rework burden on the billing team.

That matters just as much in physical therapy EMR settings. The same patient often shows up there for joint mobility work alongside PMR management. Structured clinical forms built around the PMR documentation checklist help here. They make sure the required elements land in the note before it’s signed.

For practices managing PMR patients long-term, a missed ESR value or an unsigned corticosteroid note creates risk. That risk shows up on a follow-up visit just as much as on the initial encounter. Keeping the code linked to its documentation across the whole care episode keeps the audit risk down.

Conclusion

ICD-10 code M35.3 is a stable, billable code for polymyalgia rheumatica, valid for FY2026 with no recent revisions. Getting it right consistently comes down to documentation discipline. That means a confirmed diagnosis, symptom duration, ESR and CRP values, and correct GCA handling.

Practices that link M35.3 to complete encounter documentation at the point of care avoid the denial cycle. That cycle costs rheumatology and integrative medicine teams revenue every year. See how Pabau keeps that documentation attached automatically, and book a demo with the team.

See how Pabau connects ICD-10 codes to clinical documentation

Pabau links diagnosis codes like M35.3 directly to encounter notes, lab results, and prescriptions, so your claims go out complete and your audits stay clean.

Book a demo

Continue your research

Need the Kawasaki disease code? ICD-10 code M30.3 covers documentation and sequencing for pediatric Kawasaki disease claims in the same connective tissue block.

Coding microscopic polyangiitis? ICD-10 code M31.7 walks through the distinct vasculitis workup and why it doesn’t share an Excludes1 note with M35.3.

Billing a postfusion complication? ICD-10 code M96.0 covers pseudarthrosis after fusion or arthrodesis and its documentation requirements.

Frequently asked questions