ICD-10 Codes for Ear Pain: H92.01 to H92.09

ICD-10 Codes for Ear Pain: H92.01 to H92.09

ICD-10 codes for ear pain, clinically called otalgia, are H92.01 (right ear), H92.02 (left ear), H92.03 (bilateral), and H92.09 (unspecified ear), all under category H92.0. Like most symptom codes, these apply when ear pain is the documented complaint without yet identifying a specific underlying cause such as otitis media or otitis externa.

This code family shows up constantly in family medicine billing, alongside pediatrics and urgent care, since ear pain is one of the most common presenting complaints across every age group.

Key Overview

  • Code category: H92.0 (Otalgia)
  • Common codes: H92.01 (right ear), H92.02 (left ear), H92.03 (bilateral), H92.09 (unspecified ear)
  • Code type: ICD-10-CM Chapter 8 (Diseases of the ear and mastoid process)
  • Typically used by: Family medicine, pediatrics, urgent care, and emergency medicine
  • Key rule: Laterality (right, left, bilateral, unspecified) must be selected based on documentation, not defaulted to unspecified
  • Closely related codes: H66.9 (otitis media, unspecified), H60.9 (otitis externa, unspecified), H92.1x (otorrhea)

What Is the ICD-10 Code for Ear Pain?

It depends on laterality: H92.01 for right ear, H92.02 for left ear, H92.03 for both ears, and H92.09 when the affected ear isn’t specified in the documentation.

Is Otalgia the Same as an Ear Infection?

No. Otalgia (H92.0x) is a symptom code for ear pain itself. Once a specific cause like otitis media or otitis externa is diagnosed, that condition’s own code is used instead of the symptom code.

Do I Need to Specify Which Ear Is Affected?

Yes, whenever the documentation supports it. Defaulting to H92.09 (unspecified) when the note actually states “right ear” or “left ear” under-codes the encounter and misses available specificity.

Can Otalgia Be Coded Alongside an Ear Infection Diagnosis?

Generally no, if the pain is a symptom integral to the diagnosed infection. Once otitis media or otitis externa is confirmed, that condition’s code replaces the otalgia symptom code.

What Age Groups Commonly Use Ear Pain Codes?

All ages, though pediatric visits account for a large share, since ear pain is one of the most frequent reasons for a pediatric sick visit, closely tied to eustachian tube differences in young children.

What ICD-10 Codes for Ear Pain Actually Cover

Otalgia codes sit in ICD-10-CM’s chapter for diseases of the ear, but they function like a symptom code in practice: they describe the complaint of ear pain without yet attributing it to a confirmed cause. The four subcodes differ only by laterality, which makes them one of the simpler symptom code families to apply correctly, provided the documentation actually states which ear is affected.

Because otalgia sits in the ear-and-mastoid chapter rather than the general symptoms chapter, it’s still billable and reportable even as a standalone complaint, but the same underlying principle applies as with any symptom code: once a specific diagnosis is confirmed, that diagnosis takes over. For the general ICD-10-CM convention on symptom versus confirmed-diagnosis coding, see the FY2026 ICD-10-CM Official Guidelines for Coding and Reporting.

You May Also Like: What Are CPT Codes in Medical Billing?

When to Use Ear Pain ICD-10 Codes

  • A patient presents with ear pain and, after examination, no specific cause (infection, wax impaction, TMJ-related) has been identified.
  • The exam is normal or inconclusive, and otalgia remains the working diagnosis for that encounter.
  • The documentation clearly states which ear is affected, supporting the correct laterality code.
  • The pain is being evaluated as a standalone complaint rather than a known symptom of an already-diagnosed condition.

When Not to Use Ear Pain ICD-10 Codes

Don’t use an otalgia code once a specific cause, such as otitis media or otitis externa, has been diagnosed; the definitive code replaces the symptom code. Don’t default to H92.09 (unspecified) when the note clearly documents a specific side.

Don’t use an otalgia code for pain that’s actually referred from a non-ear source, such as TMJ dysfunction or dental pain, if that source has already been identified; code the actual source condition instead. And don’t confuse otalgia (pain) with otorrhea (drainage) or otorrhagia (bleeding), which are separate H92 subcategories with their own codes.

Ear Pain ICD-10 Codes at a Glance

CodeLateralityWhen to Use
H92.01Right earDocumentation specifies right-sided ear pain
H92.02Left earDocumentation specifies left-sided ear pain
H92.03BilateralDocumentation specifies pain in both ears
H92.09UnspecifiedLaterality genuinely isn’t documented

Best Practices for Coding Ear Pain

Always Check the Note for Laterality Before Defaulting to Unspecified

Most ear pain documentation states which side is affected, and coding H92.09 when the chart actually says “left ear” is a missed-specificity error rather than a genuine unspecified presentation. A quick laterality check should be routine for every otalgia claim.

Confirm Whether a Cause Was Actually Identified

If the exam reveals a bulging tympanic membrane consistent with otitis media, that’s a confirmed diagnosis, not an unresolved symptom, and the otitis media code should replace the otalgia code entirely. Reviewing the assessment line rather than just the chief complaint catches this distinction.

Distinguish Otalgia From Otorrhea and Otorrhagia

These three H92 subcategories describe pain, drainage, and bleeding respectively, and they’re not interchangeable even though they share a parent category. Coding pain when the actual finding was drainage, or the reverse, is an avoidable specificity error.

Watch for Referred Pain With an Already-Identified Source

Ear pain can be referred from TMJ dysfunction, dental issues, or throat conditions. When the provider has already identified one of these as the actual source, the source condition’s own code is more accurate than an otalgia code.

Must Read: In-House vs. Outsourced Medical Billing

Apply the Same Symptom-vs-Diagnosis Logic Used Across ICD-10-CM

Otalgia follows the same general rule as any other symptom code: it’s appropriate when the cause is genuinely unknown, and it’s replaced once a cause is confirmed. Treating it as a special case separate from this general principle leads to inconsistent coding.

Recognize That Pediatric Documentation Often Specifies Laterality Clearly

Pediatric visits for ear pain frequently include a clear exam finding by side, given how common the complaint is in that population. Coders working pediatric charts should expect, and look for, that level of detail rather than assuming unspecified.

Confirm Bilateral Presentations Are Genuinely Documented as Both Sides

H92.03 requires that both ears are actually documented as affected, not just that the chief complaint mentions “ear pain” without specifying one or both sides. A single ambiguous phrase shouldn’t be read as bilateral without supporting exam detail.

Don’t Assume Chronicity Changes the Code Selection

Unlike some symptom categories, otalgia codes don’t have separate acute/chronic variants; the code selection depends entirely on laterality, not duration. Recurring ear pain across visits still uses the same laterality-based code unless a specific diagnosis has since been established.

Cross-Check Otalgia Claims Against the Exam and Any Imaging or Referral Ordered

If a claim for otalgia is accompanied by a referral to ENT or imaging, confirming that the diagnosis code still accurately reflects “cause unknown” at the time of referral avoids a mismatch between the code and the reason for the referral itself.

Helpful for you: HIPAA Compliance Changes For Medical Billing Companies

Documentation Checklist for Ear Pain Coding

  • A clear statement of which ear is affected (right, left, bilateral), or genuine absence of that detail.
  • Confirmation of whether a specific cause was identified on exam.
  • Any relevant exam findings (tympanic membrane appearance, canal findings) supporting the coding decision.
  • Referral or follow-up plans, if the cause remains unidentified at the end of the visit.

Mistakes to Avoid When Coding Ear Pain

  • Defaulting to H92.09 when the documentation actually specifies a side.
  • Coding otalgia alongside a confirmed diagnosis like otitis media instead of replacing it.
  • Confusing otalgia with otorrhea or otorrhagia codes.
  • Using an otalgia code when the pain has already been attributed to a non-ear source like TMJ dysfunction.
  • Assuming bilateral involvement without clear supporting documentation.

Common Reasons Ear Pain Claims Get Denied

  • Missing laterality when documentation supports it. Under-coded specificity weakens the claim.
  • Symptom-diagnosis overlap. Reporting otalgia alongside a confirmed ear infection diagnosis.
  • Wrong H92 subcategory. Coding pain when the actual finding was drainage or bleeding.
  • Referred pain misattribution. Using an otalgia code when the source has already been identified as non-ear.

More ICD-10 Coding Guides

This post is part of Spark’s ongoing series covering the ICD-10 codes practices ask about most. Related guides that may help:

Ear Pain ICD-10 Billing Example

A 6-year-old is brought in with two days of right ear pain and mild fussiness. On exam, the provider finds a normal tympanic membrane with no bulging, erythema, or effusion, and no other findings suggesting a specific cause. The assessment documents “otalgia, right ear, cause undetermined” with a plan to reassess if symptoms persist.

Because no specific diagnosis like otitis media was confirmed, the visit is coded to H92.01 (otalgia, right ear), reflecting both the documented laterality and the genuinely unresolved cause. Had the exam instead shown a bulging, erythematous tympanic membrane, the appropriate otitis media code would have replaced the otalgia code entirely.

Why Ear Pain Coding Benefits From Consistent Laterality Habits

Otalgia coding is straightforward in principle, but consistently capturing laterality, and knowing exactly when to replace the symptom code with a confirmed diagnosis, is where small, repeated errors accumulate across a high-volume complaint like this one. A medical billing audit that spot-checks laterality accuracy and symptom-versus-diagnosis coding on a sample of ear pain claims can catch a practice-wide pattern before it affects reimbursement broadly.

Conclusion

Ear pain coding comes down to two habits: capturing laterality whenever the documentation supports it, and dropping the otalgia code the moment a specific cause like otitis media is confirmed. Both are simple checks, but skipping either one is a common source of under-coding on one of the most frequently seen complaints in general practice.

FAQs

What is the ICD-10 code for ear pain?

It depends on laterality: H92.01 for right ear, H92.02 for left ear, H92.03 for bilateral, and H92.09 for unspecified.

Is otalgia the same as an ear infection?

No. Otalgia is a symptom code for ear pain itself. Once a cause like otitis media is diagnosed, that condition’s own code replaces the symptom code.

Do I need to specify which ear is affected?

Yes, whenever documentation supports it. Coding unspecified when the note actually states a side is a missed-specificity error.

Can otalgia be billed alongside an ear infection diagnosis?

Generally no. Once the infection is confirmed, its code replaces the otalgia symptom code rather than being reported alongside it.

What’s the difference between otalgia, otorrhea, and otorrhagia?

Otalgia is pain, otorrhea is drainage, and otorrhagia is bleeding. These are separate H92 subcategories with their own distinct codes.

Is ear pain more common in a specific age group?

It’s seen across all ages, but pediatric visits make up a large share due to how common the complaint is in young children.

What if ear pain is caused by TMJ dysfunction rather than an ear condition?

If the source has already been identified as TMJ dysfunction or another non-ear cause, that condition’s own code is more accurate than an otalgia code.