ICD code R50.9 – Fever, unspecified

Key takeaways

R50.9 (Fever, unspecified) is a valid, billable ICD-10-CM code for fever without a confirmed etiology at the time of service.

Use R50.9 only when no definitive diagnosis explains the fever; once a cause is confirmed, code the confirmed diagnosis instead.

Sibling codes R50.2 (drug-induced fever) and R50.81 (fever presenting with conditions classified elsewhere) need documentation that R50.9 does not.

Pabau, the practice management platform we build, keeps temperature readings, evaluation notes and the physician’s assessment in one patient record.

ICD-10 code R50.9: Official description and code details

ICD-10 code R50.9 is the billable ICD-10-CM diagnosis code for fever, unspecified: a raised temperature with no cause confirmed at the encounter.

It is listed as a billable, complete code in CMS’s FY 2027 ICD-10-CM files, with no further characters to add. Once the physician confirms a cause, that diagnosis replaces it.

The code is classified under CMS ICD-10-CM Chapter 18, which covers symptoms, signs, and abnormal findings not elsewhere classified. That chapter designation tells coders and payers that R50.9 is a symptom code, not a confirmed disease entity. Browse the neighboring Chapter 18 codes in our code library for coders. Sound medical billing fundamentals help you apply a symptom code correctly.

What does R50.9 cover? Clinical scope and inclusions

R50.9 covers fever of unspecified type when no underlying cause has been identified at the time of the clinical encounter. Its inclusion terms in the tabular list include:

• Pyrexia NOS — elevated body temperature documented without further qualifier
• Fever NOS — the most common documentation phrase, accepted when no etiology is stated
• Hyperpyrexia NOS — extremely high temperature (typically above 41°C / 105.8°F) without a known cause
• Fever of unknown origin (FUO) — also indexed here as pyrexia of unknown origin
• Persistent fever — ongoing fever with no etiology documented
• Fever with chills or rigors — fever accompanied by chills or rigors, with no cause established

The code fits when a patient presents with a measured temperature elevation and the physician evaluates for potential causes. No definitive diagnosis is reached during that encounter. It is not a placeholder. Assigning R50.9 is a clinical statement that the etiology was investigated and remained unconfirmed at the time of service.

Common clinical scenarios that appropriately map to R50.9:

• A pediatric urgent-care visit with acute fever, pending lab results
• An adult with low-grade fever of recent onset in primary care, where the work-up has started but is not yet conclusive
• An ED evaluation where fever is the chief complaint and no infection source is identified during the visit

What R50.9 does not cover: Exclusions and excluded codes

R50.9 sits under the official Excludes1 notes at category R50, which coders must check before assigning the code. An Excludes1 note means the excluded condition is never coded together with R50.9.

One common documentation trap involves the phrase “fever of unknown origin.” FUO is indexed to R50.9 as an inclusion term, but true FUO as a clinical syndrome needs careful chart review before assignment. The classic syndrome is fever lasting more than three weeks with no cause found after a week of investigation. Do not assign R50.9 for fever of unknown origin in a newborn; P81.9 applies instead.

R50.9 vs. similar fever codes: How to choose the right code

The R50 category contains several codes, including R50.2, R50.81 and R50.9. Choosing among them depends on what the physician documents, never on the coder’s own clinical interpretation.

The pivot between R50.9 and R50.81 is a frequent selection error. R50.81 is used when a known condition is driving the fever, such as sickle cell disease in a febrile patient. R50.9 is used when no such condition has been confirmed, and the physician’s note decides it. The ladder below puts every R50 option in the order a coder should test it.

When to use R50.9 as the primary vs. secondary diagnosis

Whether R50.9 belongs in the first diagnosis position depends on the setting and what the physician documented. The ICD-10-CM Official Guidelines set different rules for outpatient and inpatient encounters.

Outpatient encounters

Under Section IV of the Official Guidelines, symptom codes are not coded when a confirmed definitive diagnosis accounts for the symptom. If the physician documents “acute pharyngitis with fever,” code the pharyngitis (J02.9 or more specific), not R50.9. A diagnosed periodic fever syndrome works the same way and moves to M04.1. R50.9 is first-listed only when the physician’s assessment does not establish a definitive diagnosis at that encounter. A raised white count on the same visit follows that logic, coding to leukocytosis code D72.829 alongside R50.9 only while no cause is confirmed.

A practical three-question gate for outpatient coding:

1. Did the physician document a confirmed diagnosis? If yes, code that diagnosis, not R50.9.
2. Is fever the chief reason for the encounter, with no etiology established? If yes, R50.9 may be first-listed.
3. Does another confirmed condition explain the fever? If yes, code that condition. R50.9 may appear as secondary only if it adds clinical value the primary code does not capture.

Inpatient encounters

Inpatient guidelines (Section II) allow coding uncertain diagnoses as if confirmed when the physician documents them as “probable,” “likely,” or “suspected.” A patient admitted for evaluation of fever, with discharge documentation of “probable bacterial infection pending culture,” would have that probable diagnosis coded rather than R50.9. Use R50.9 as the principal inpatient diagnosis only when discharge documentation offers no etiology, confirmed or probable.

Documentation that supports R50.9 on a claim

Payers reviewing a claim with R50.9 look for specific documentation signals to confirm medical necessity. Missing any one of these is the most direct path to a denial.

• Measured temperature: A numerical temperature reading in the chart (oral, tympanic, rectal, or temporal), documented by a clinical staff member or the treating physician
• Duration: Onset date or approximate duration of fever, to establish clinical context
• Clinical evaluation performed: Evidence that the physician reviewed potential causes, such as history, physical findings and any ordered diagnostics
• Absence of confirmed etiology: An explicit physician statement that no cause was identified, or an assessment and plan that names no definitive diagnosis
• Physician attestation: The treating physician’s signature or electronic attestation on the note, since unsigned or incomplete notes are a frequent audit flag

Pabau’s patient records hold the temperature reading, the visit note and the physician’s assessment together, so a reviewer sees the evaluation behind the code. Linking that record to a claims management workflow keeps the supporting documentation attached to the encounter the claim bills.

Drug-induced fever: When to use R50.2 instead of R50.9

R50.2 is the code for drug-induced fever, and it cannot be assigned on clinical suspicion alone. The physician must document that a specific drug causes the fever. The tabular list also requires an additional adverse-effect T-code for that drug (“Use additional code for adverse effect, if applicable”).

Three documentation signals that support R50.2 over R50.9:

• The physician explicitly names the causative drug in the assessment or plan
• The note documents that fever resolved after the drug was discontinued or dose-adjusted
• No infectious or other etiology was identified despite workup

When those elements are absent and the physician documents only “fever” with a list of active medications, the correct code is R50.9, not R50.2. Assigning R50.2 without physician documentation of causation creates a claim integrity problem and may trigger a payer audit. If documentation is ambiguous, a physician query is the appropriate next step.

Common claim denial reasons for R50.9 and how to avoid them

R50.9 generates a predictable set of denial patterns. Each one has a documentation or coding correction that prevents it.

Effective denial management starts before the claim goes out. A clean claim for a fever encounter requires the coder to verify three things at submission:

• The diagnosis code matches what the physician documented
• Documentation of medical necessity is complete
• No more-specific sibling code applies

Payer-specific requirements and Medicare coverage for R50.9

Medicare does not issue a National Coverage Determination (NCD) specific to R50.9. Local coverage determinations from individual Medicare Administrative Contractors (MACs) govern whether a claim with R50.9 as the principal diagnosis is accepted. Coders and billers should check the applicable MAC’s LCDs in the Medicare Coverage Database before submitting fever-only claims for Medicare patients.

Three practical rules for payer acceptance:

• R50.9 alone is a review trigger. A claim carrying only R50.9 and an E/M code commonly triggers medical necessity review with commercial and government payers. The exception is a note that documents diagnostics or explains why no workup was done.
• Secondary codes strengthen the claim. If the patient has coexisting conditions (diabetes, immunosuppression, recent surgery), coding those alongside R50.9 gives payers the clinical context they use to assess appropriateness.
• Medicaid policies vary by state. State Medicaid programs set their own LCD-equivalent policies, so a fever-only claim accepted in one state may be denied in another. Verify before submission when billing across state lines.

ICD-10 R50.9 to ICD-9-CM crosswalk

The official General Equivalence Mapping (GEM) from CMS maps R50.9 to ICD-9-CM code 780.60 (Fever, unspecified). The mapping is a forward-approximate match. CMS GEMs provide the closest ICD-9-CM equivalent but do not guarantee clinical equivalence.

This crosswalk is relevant in three practical scenarios:

• Legacy system audits comparing pre-2015 and post-2015 claims data
• Payer disputes referencing older claims filed under ICD-9-CM
• Research data pulls from Medicare files that span the ICD-9-to-ICD-10 transition period

The ResDAC guidance on ICD codes in Medicare files explains how to handle cross-era data correctly. For current claims, only R50.9 applies. Code 780.60 has not been valid since the ICD-10-CM transition date of October 1, 2015.

How Pabau keeps fever-code claims clean

A fever claim fails review when the note lacks a temperature reading or the code comes from the chief complaint alone. In Pabau, vitals, visit notes and the physician’s assessment sit in one patient record. The coder reads the whole encounter before choosing between R50.9 and a sibling code.

Claims then go out through Claim.MD, our US clearinghouse partner, as 837P electronic claims to thousands of US payers. The practice can check a patient’s eligibility before the claim goes out, and ERA remittances come back into Pabau.

Remittance data from ERA files shows which R50.9 scenarios a payer keeps denying. Billers can then fix the documentation rule behind the denial instead of appealing claim by claim.

Stop chasing fever-code denials

Pabau keeps the temperature reading, visit note and assessment in one record. Claims go out through Claim.MD, and ERA remittances show which fever-code denials keep repeating.

Book a demo

Conclusion

Fever is one of the most common chief complaints in outpatient medicine, so R50.9 comes up in most practices every week. Treat it as the code that remains once the note has ruled out every more specific option, never as the first one reached for.

The step worth taking now is to make that check routine. Read the full assessment, test the sibling codes, and confirm a temperature and an evaluation are on file before the claim leaves. A minute of review at coding time costs far less than a denial and an appeal.

Pabau keeps the fever encounter’s record and its claim in one place. Book a demo to see how documentation, Claim.MD submission and ERA-based denial tracking work together.

Continue your research

Need a clearinghouse that supports ICD-10 claim submission? Claim.MD clearinghouse overview explains how the integration handles 837P submissions, eligibility checks, and ERA remittances for US practices.

Want to understand the full revenue cycle behind your claims? Revenue cycle management explained covers the end-to-end process from encounter to payment posting.

Got a denial back on a fever claim? Denial codes in medical billing decodes the reason codes payers attach and what to fix before resubmitting.

Billing fever visits to Medicare? Medicare billing guide walks through how Medicare claims are built, submitted and paid.

Frequently asked questions