J06.9 Acute Upper Respiratory Infection, Unspecified: The 2026 ICD-10 Coding and Billing Guide for Urgent Care

What Is ICD-10 Code J06.9?

J06.9 is the ICD-10-CM diagnosis code for an acute upper respiratory infection, unspecified. It is the catch-all URI code used when the infection is viral, spans multiple sites, or is not localized to a single structure. J06.9 is billable and HIPAA valid for FY2026 and carries into FY2027 unchanged when the new code set takes effect on October 1, 2026. Urgent care centers rely on it heavily for common colds, viral URIs, and undifferentiated respiratory complaints.

• What it covers: J06.9 captures upper respiratory infections of multiple or unspecified sites, including the undifferentiated cold and viral URI visits that make up a large share of urgent care volume.
• The Excludes1 traps: A confirmed strep test sends you to J02.0 and a confirmed influenza result sends you to J10.1 or J11.1. All three sit under an Excludes1 note in category J06, so none of them can ride on the same claim as J06.9.
• The pharyngitis rule: J06.9 and J02.9 are not barred by an Excludes note, but you report only the single code that matches the documented site. Stacking two unspecified codes reads as imprecise coding to a payer.

What Are the Symptoms Coded Under J06.9?

J06.9 covers the everyday symptom cluster of an upper respiratory infection when the provider does not localize it to one structure. The classic presentation includes nasal congestion, sneezing, cough, sore throat, and low-grade fever occurring together. Because these symptoms are integral to the URI diagnosis, they are not coded separately once J06.9 is assigned.

• Nasal congestion and runny nose.
• Sneezing and postnasal drip.
• Cough, usually dry early in the illness.
• Sore or scratchy throat.
• Low-grade fever and general malaise.

A symptom code such as R05.9 for cough or R07.0 for throat pain belongs on the claim only when the encounter ends without a confirmed diagnosis. Once the provider documents an acute URI, J06.9 carries those symptoms and the individual R codes drop off. Coding both the URI and its component symptoms is redundant and invites a specificity edit.

The exception is a condition that is not integral to a URI. A patient who presents with a viral URI and is also clinically dehydrated after two days of poor intake has a second, separately reportable diagnosis, and that dehydration supports a higher level of medical decision making than the URI alone would.

The most common issue we see providers run into here is the opposite problem: charts stripped down to J06.9 alone, losing the secondary diagnoses that justify the visit level. If dehydration is assessed and treated, code it. Our E86.0 dehydration coding guide walks through when that secondary code holds up on audit and when it does not.

Can J02.0 and J06.9 Be Billed Together?

No. J02.0 and J06.9 cannot be reported together for the same encounter. The ICD-10-CM Tabular places an Excludes1 note under category J06 that lists streptococcal pharyngitis, J02.0. Excludes1 means the two conditions are mutually exclusive and are never coded at the same time.

The logic is specificity. Strep pharyngitis is a confirmed, specific infection of the throat, so it outranks the nonspecific URI umbrella. When a rapid strep or culture is positive, you code J02.0 and drop J06.9 entirely. The unspecified URI code exists for infections that are not pinned down, which a positive strep result no longer is.

What most urgent care teams miss is that J02.0 is not the only Excludes1 sitting under J06. The same note also excludes influenza with other respiratory manifestations, which covers J09.X2, J10.1, and J11.1, along with unspecified acute lower respiratory infection at J22. That matters far more in practice than the strep rule, because a busy center runs rapid flu tests all winter. The moment a flu test comes back positive and the provider documents influenza, the encounter belongs to J10.1 or J11.1, not J06.9, and pairing the two on a single claim triggers the same Excludes1 edit that the strep pairing does.

Across the billing companies we vet, the flu pairing is a far more frequent scrubber hit than the strep pairing, largely because the strep rule is taught widely and the influenza rule is not. If your clearinghouse edits only flag J02.0 against J06.9, the influenza conflicts are passing straight through to the payer and coming back as denials.

Can J06.9 and J02.9 Be Billed Together?

Technically there is no Excludes note barring J06.9 and J02.9 together, so they are not mutually exclusive in the Tabular. In practice you should report only one. J06.9 is a nonspecific umbrella for a multi-site or unspecified URI, and J02.9 is a nonspecific code for the pharynx, so stacking both is redundant and reads as imprecise coding to a payer.

Choose the code that matches the documentation. If the infection is localized to the throat, J02.9 stands alone. If the provider describes a broader upper respiratory infection across multiple or unspecified sites, J06.9 stands alone. The ICD-10-CM chapter note for diseases of the respiratory system reinforces the principle: when a respiratory condition is described as occurring in more than one site and is not specifically indexed, it is classified to the lower anatomic site rather than split across two codes.

Here is how J06.9 stacks up against the codes it most often gets confused with or wrongly paired against.

Read that final column as a claim scrubber would. Four rows are hard stops enforced by an Excludes1 note, one is a soft stop a payer reads as sloppy coding, and one replaces J06.9 outright. None of the six belongs on a clean claim next to J06.9, which is why a URI encounter should resolve to exactly one respiratory diagnosis.

J06.9 Coding Rules Most Urgent Care Teams Miss

Beyond the Excludes conflicts, J06.9 carries a handful of instructions that quietly drive denials and lost specificity when they are skipped. These are the five rules worth posting at the coder workstation.

• Add the organism code when it is known. J06.9 carries a use additional code note directing you to B95 through B97 to identify the infectious agent when documented, such as B97.4 for respiratory syncytial virus. The organism code is always secondary, never first listed.
• Drop J06.9 when COVID-19 is confirmed. A confirmed SARS-CoV-2 result is coded U07.1. J06.9 applies only when the specific virus is not identified or documented, so it should never stand in for a positive COVID test.
• Code to four characters, never three. The three-character J06 is a category header and is not billable. You must code to J06.0 for acute laryngopharyngitis or J06.9 for the unspecified URI to submit a valid code.
• Check the flu result before the strep result. The Excludes1 note under J06 covers influenza at J09.X2, J10.1, and J11.1. A positive flu test outranks J06.9 the same way a positive strep test does, and the flu pairing is the more frequent denial trigger.
• Keep the encounter above the larynx. If documentation moves the infection into the lower tract, J22 applies and is also Excludes1 against J06. A URI that has progressed to bronchitis is no longer a J06.9 encounter.

What Changes for J06.9 on October 1, 2026?

Nothing changes for J06.9 itself. The FY2027 ICD-10-CM code set takes effect October 1, 2026 and runs through September 30, 2027, and J06.9 carries forward with the same description and the same Excludes1 notes. That is consistent with its full history: J06.9 has not been revised in any annual update since ICD-10-CM went live on October 1, 2015.

CMS and the CDC have already published the FY2027 diagnosis code files, and you can pull the tabular addenda directly from the CMS ICD-10 code update page. The FY2027 update includes 190 new diagnosis codes, 30 deletions, and 8 description revisions. The respiratory chapter picks up new specificity rather than losing any, which is the pattern across most of the update.

Two respiratory additions matter for an urgent care coder working URI encounters. The first is a new odontogenic sinusitis series at J34.830 through J34.839, which gives sinus infections of dental origin their own codes by sinus rather than defaulting into a broader sinusitis or unspecified URI bucket. The second is J4B for pulmonary mycetoma. Neither replaces J06.9, but the odontogenic series is exactly the kind of change that pulls a small slice of encounters out of unspecified territory when the provider documents the dental source.

The practical takeaway for October 1 is a documentation one rather than a code one. J06.9 stays valid, so nothing in your fee schedule or superbill breaks. What changes is that a payer reviewing a high volume of unspecified URI codes in FY2027 has more specific alternatives to point at, which raises the value of documenting a localized site or a confirmed organism whenever the encounter supports it.

How J06.9 Pairs With Urgent Care Billing Codes

A URI visit pairs J06.9 with an evaluation and management service and, depending on the contract, the urgent care S-codes. The most common billing error is not the diagnosis but the service layer built around it.

Report the E/M with place of service 20 for urgent care, using 99202 through 99215 based on the level of service. Where the payer contract requires the S9083 global fee, that flat case rate stands alone and you do not add an E/M or S9088. Where the payer runs fee for service, the E/M can carry the S9088 urgent care add-on when the contract allows it, though S9088 often pays zero and simply flags the setting. Never bill S9083 and S9088 together, since the global fee already represents the full visit.

Providers often come to us after discovering that a batch of rapid test claims denied on the same payer, and the root cause is always the same: the S9083 global fee contract already bundles the rapid strep at 87880 or rapid flu at 87804, so submitting the test separately triggers a duplicate denial. On fee for service contracts the test is separately payable, but the E/M then depends on modifier 25 holding up. That distinction is invisible until the denials land.

Our breakdown of the 2027 modifier 25 payment cut for urgent care covers what that reduction does to a URI visit with a same-day test.

Centers that also bill emergency department levels, or that share a tax ID with a freestanding ED, should keep the two documentation standards separate. Our guide to CPT 99281 and its documentation thresholds shows how quickly a low-acuity URI encounter falls apart when it is leveled against the wrong code family.

Why Do J06.9 Claims Get Denied?

J06.9 denials come from code conflicts and setting rules, not from the code being invalid. The leading causes are pairing J06.9 with an Excludes1 code, using J06.9 when COVID-19 or influenza was confirmed, stacking it with J02.9, and mismanaging the S9083 global fee. All are avoidable with a tighter documentation to claim workflow.

The six denial patterns we see most on URI claims:

• Reporting J06.9 with J02.0 on the same claim in violation of the Excludes1 note.
• Reporting J06.9 alongside J10.1 or J11.1 after a positive influenza test.
• Using J06.9 when SARS-CoV-2 was confirmed and U07.1 was required.
• Stacking J06.9 and J02.9 when a single site-appropriate code was correct.
• Submitting a separate rapid strep or flu test on an S9083 global fee contract that bundles it.
• Billing S9083 and S9088 together, which the payer reads as an unbundled duplicate.

One question we hear constantly from urgent care practice managers is why these denials never show up as a single large loss. They do not, and that is the problem. A URI claim is a low dollar claim, so a center can absorb hundreds of them before anyone runs the report. The fix is a front-end scrubber rule rather than a back-end appeal, because the appeal on a bundled rapid flu test costs more staff time than the test pays.

A Real-World J06.9 Scenario

A 34-year-old arrives at urgent care with three days of congestion, cough, sneezing, and a mild sore throat. The rapid strep and rapid flu tests are both negative and COVID-19 is not confirmed, so the provider documents an acute viral upper respiratory infection. The clean claim is a 99213 E/M with place of service 20 and J06.9 as the single primary diagnosis, with the negative tests supporting medical necessity.

Every alternative code is off the table for a documented reason, and that is what makes the claim defensible. The negative strep rules out J02.0. The negative flu rules out J10.1 and J11.1. The absence of a confirmed COVID result rules out U07.1. Because the illness spans multiple sites rather than the throat alone, J06.9 is the better fit than J02.9, and because nothing is documented below the larynx, J22 does not apply.

Now change one fact. If the rapid flu had returned positive, the entire claim changes: J06.9 comes off, J11.1 or J10.1 goes on depending on whether the virus type is identified, and on an S9083 contract the separately submitted 87804 comes off as well. That single test result moves three lines on the claim, which is why the posting and scrubbing rules around URI visits deserve more attention than a low dollar diagnosis usually gets.

Frequently Asked Questions