ICD-10 Code R42: Dizziness and giddiness billing guide

Key takeaways

ICD-10 Code R42 (Dizziness and giddiness) is a billable, specific ICD-10-CM code valid for FY2026 HIPAA-covered transactions, effective October 1, 2025.

R42 carries an Excludes1 restriction against the entire H81.- vestibular disorder block and T75.23 (vertigo from infrasound), so it can never be coded with either.

The most common coding error is assigning R42 when a confirmed vestibular diagnosis exists. Always code the most specific condition when documented.

Pabau’s claims management software embeds ICD-10 diagnosis code search directly in the clinical workflow, helping practices reduce R42 coding errors and submit cleaner claims.

Dizziness sends an estimated 4.8 million Americans to the emergency department each year, according to an analysis of CDC/NHAMCS data from 2016 to 2022. For coders, that volume means R42 is one of the most frequently assigned symptom codes in the ICD-10-CM system. It is also one of the most frequently miscoded.

Misapplying R42 when a more specific vestibular diagnosis is available is a denial trigger that costs practices revenue.

Tight documentation and a clear grasp of the excludes notes are what separate a clean claim from a rejected one. This guide covers billability, synonyms, includes and excludes restrictions, CPT code pairings, documentation requirements, and the coding errors most likely to trigger a denial. Effective revenue cycle management starts with getting the diagnosis code right.

ICD-10 Code R42: Definition, billability, and chapter classification

R42 is a billable, specific ICD-10-CM diagnosis code. Its official short descriptor is Dizziness and giddiness. The 2026 edition of ICD-10-CM R42 became effective on October 1, 2025 and is valid for submission on HIPAA-covered transactions through September 30, 2026.

R42 sits within Chapter 18: Symptoms, Signs and Abnormal Clinical and Laboratory Findings, Not Elsewhere Classified (R00-R99). Specifically, it falls within the sub-block R40-R46 (Symptoms and signs involving cognition, perception, emotional state and behavior).

According to the CDC/NCHS ICD-10-CM web tool, Chapter 18 codes are appropriate when a definitive diagnosis has not been established. They also apply when the presenting symptom is the reason for the visit and no underlying cause is documented.

Because R42 is a symptom code, it is valid as a primary diagnosis when dizziness or giddiness is the documented reason for the encounter. This applies only when no more specific underlying condition has been identified or confirmed. Once a specific vestibular or neurological cause is diagnosed, the more specific code takes precedence.

Approximate synonyms and clinical terms included under R42

R42 covers a range of clinical presentations beyond the literal terms dizziness and giddiness. Coders frequently encounter these terms in clinical notes, and all of them map to R42 when no more specific diagnosis is documented.

• Dizziness (general, non-specific)
• Giddiness
• Vertigo NOS (not otherwise specified – use only when no specific vestibular syndrome is confirmed)
• Light-headedness / lightheadedness
• Disequilibrium
• Presyncope (near-fainting without confirmed syncopal cause)
• Wooziness
• Swimming of the head
• Dix-Hallpike vertigo (unconfirmed BPPV – if BPPV is confirmed, use H81.1x instead)
• MdDS (Mal de débarquement syndrome) NOS (when not otherwise classified)

The distinction between “Vertigo NOS” and a confirmed vestibular syndrome is where most coding errors originate. When a clinician documents “vertigo” without a confirmed mechanism, R42 is appropriate. Once positional testing confirms BPPV, the H81.1x series applies. Reviewing the AAPC ICD-10-CM code lookup alongside the official tabular notes clarifies these boundaries quickly.

R42 includes and excludes notes

The excludes notes for R42 are where payers scrutinize claims most closely. Getting these wrong means claim denial or, worse, a compliance audit. The two types of exclusion work differently, and coders must apply each correctly.

Excludes1 (never code together)

An Excludes1 note means the excluded condition is mutually exclusive with R42. The two codes cannot appear on the same claim for the same encounter under any circumstances. R42’s Excludes1 note covers the entire H81.- block (disorders of vestibular function) and T75.23 (vertigo from infrasound). If a patient has a confirmed condition from either, that code replaces R42 entirely.

Excludes2 (may code together if both present)

An Excludes2 note means the excluded condition is not included in R42 but may coexist. When both conditions are independently present and documented, you can report both codes in the same encounter.

R42 carries no standard Excludes2 notes in the current ICD-10-CM tabular list. However, coders should note that related symptom codes such as R55 (Syncope and collapse) may be reported alongside R42. This applies only when both are independently documented and clinically distinct.

Related ICD-10 codes to know alongside R42

Dizziness workups frequently uncover related conditions that require their own codes, or conditions that must be actively differentiated from R42. The table below summarizes the codes most commonly documented alongside or instead of R42, drawing on the ICD-10-CM code reference. Familiarity with these related neurological codes reduces the risk of under-coding a serious underlying diagnosis.

CPT codes commonly billed with R42

R42 pairs with a range of evaluation and management (E/M) and diagnostic procedure CPT codes depending on the clinical setting and the workup performed. Choosing the right CPT code alongside R42 is essential for medical necessity alignment and for generating an accurate superbill.

For practices submitting electronic claims, Pabau’s Claim.MD clearinghouse integration carries a built-in CPT and ICD-10 catalog that validates pairing combinations before submission.

Note: CPT 92540 is commonly cited as a frequent pairing with R42 by multiple billing guide sources. Verify coverage against the payer’s local coverage determination (LCD) before billing, since payer policies vary. Payers who participate in electronic claims through Pabau can validate eligibility in real time via the insurance eligibility verification process before the appointment.

Documentation requirements for R42

Symptom codes live or die by the quality of the clinical note. Because R42 lacks the specificity of a confirmed diagnosis, payers apply extra scrutiny to the supporting documentation. Meeting the medical billing compliance requirements for symptom-based codes takes a detailed chart.

It must contain enough clinical detail to justify why a more specific code was not assigned. Organized, thorough documentation is also what makes submitting a clean claim possible on the first pass.

The chart must address each of the following elements to support R42 billing. Think of this as a denial-risk checklist: missing even one item can prompt a payer to downcode or reject the claim.

• Onset and duration: When did dizziness begin? Is it episodic or constant?
• Character of dizziness: Rotational (spinning), positional, pre-fainting, or floating sensation?
• Aggravating and relieving factors: Head movements, position changes, specific activities
• Associated symptoms: Nausea, vomiting, tinnitus, hearing loss, headache, visual changes, falls
• Neurological exam findings: Cranial nerves, gait, Romberg, Dix-Hallpike result (positive/negative)
• Workup ordered or reviewed: MRI, CT, audiology, blood pressure orthostatic measurements
• Why no specific diagnosis was assigned: State explicitly (e.g. “vestibular testing inconclusive,” “awaiting MRI results,” “no confirmed vestibular pathology identified”)

The seventh point is easy to skip under time pressure, but it matters most to payers. Documenting the reason a symptom code is used rather than a definitive diagnosis is a simple sentence, but it significantly strengthens the claim’s defensibility.

The same principle applies to other symptom-based ICD-10 codes: when a definitive diagnosis cannot be confirmed, the record must explain why.

Common coding errors to avoid with R42

Three patterns account for the majority of R42 claim denials and audit findings. Knowing each one reduces rework and protects revenue. The same specificity requirements that apply to R42 apply broadly across other symptom-based ICD-10 codes. That’s a useful pattern for the coding team to recognize.

1. Using R42 when a more specific code exists

This is the highest-frequency error. When a clinician documents a confirmed vestibular diagnosis – BPPV, Ménière’s disease, vestibular neuronitis – R42 must not appear on the claim. The Excludes1 restriction makes this a hard rule, not a judgment call.

If the chart contains a confirmed H81.x diagnosis but the billing team codes R42 out of habit, the claim will deny. Repeat patterns can also trigger a compliance review.

2. Ignoring the Excludes1 restriction entirely

Some coders attempt to append R42 alongside H81.x codes as a secondary code. The Excludes1 rule prohibits this. Unlike an Excludes2 notation, there is no clinical scenario that justifies coding both simultaneously.

If the claim goes out with both codes, the payer’s edit will catch it and reject the claim. Effective denial management strategies include a pre-submission edit check for exactly this kind of code pairing conflict.

3. Underdocumentation of the presenting complaint

R42 draws more documentation scrutiny than most symptom codes because dizziness is a known upcoding target in certain specialties. Payers want to see that the visit complexity justified the E/M level billed. A chart that says only “patient complains of dizziness, plan: vestibular exercises” is unlikely to support a 99214 alongside R42.

The documentation checklist in the section above provides the framework. The medical billing workflow must include a documentation quality review before claims leave the practice.

How Pabau supports accurate R42 coding and billing

Practices that manage high volumes of dizziness and vestibular complaints face a recurring documentation challenge. The clinical note must capture enough detail to justify R42, even though visits are brief and presentations are often non-specific. Pabau addresses this at two points in the workflow.

First, Pabau’s claims management software integrates ICD-10 code search directly into the invoicing and clinical note interface. Coders don’t need to leave the platform to look up the R42 excludes notes.

They can confirm which H81.x code applies directly, when a vestibular diagnosis is confirmed. The code is selected at the point of care, reducing re-entry errors and the lag time between visit and submission.

Second, consultation templates in Pabau can be pre-structured to capture the documentation elements the ICD-10-CM guidelines require for symptom codes. These elements include onset, duration, character, associated symptoms, neurological exam findings, and the explicit statement that no more specific diagnosis was established.

This turns the documentation checklist into an embedded clinical workflow rather than a reminder coders have to apply manually after the fact.

Electronic claims submitted through Pabau route via the Claim.MD clearinghouse integration. This integration supports real-time eligibility checks, 837P electronic claim submission, and ERA/835 remittance processing for thousands of US payers.

Stop losing revenue to preventable R42 denials

Pabau embeds ICD-10 diagnosis code search and documentation prompts directly into the clinical workflow. Coders and clinicians capture the right detail at the point of care. See how it works for your practice.

Book a demo

Conclusion

R42 looks simple on the surface: a single billable code for dizziness and giddiness. The risk is in the details. The Excludes1 restrictions against H81.x vestibular syndrome codes create denial exposure when handled carelessly. So do the documentation specificity requirements for symptom codes and the CPT pairing complexity.

Pabau’s integrated claims workflow addresses each of these pressure points. It embeds code lookup, documentation prompts, and electronic claim submission through the Claim.MD clearinghouse into a single platform. If your practice is ready to reduce R42 denials and clean up the dizziness billing workflow, book a demo. See how it fits your existing setup.

Continue your research

Need to understand how claim denials are tracked and resolved? Denial management in healthcare covers the frameworks practices use to reduce denial rates and recover lost revenue.

Want to understand the clearinghouse that handles your electronic R42 claims? Claim.MD clearinghouse overview explains how electronic remittance and payer connectivity work in practice.

Looking for guidance on building a compliant billing workflow? Revenue cycle management fundamentals outlines the end-to-end process from diagnosis code to payment posting.

Frequently asked questions