
Many billing teams struggle to connect a four-digit reason code to the actual operational failure behind it, whether that's a lapsed authorization, a site-of-care mismatch, or a diagnosis that doesn't support the billed drug. This article separates the code types involved, walks through the denial categories that show up most often in ID billing, and lays out how to correct, appeal, or prevent each one.
Key Takeaways
- CARCs and RARCs explain payment decisions; ICD-10-CM, CPT, and HCPCS codes describe the clinical service itself
- Eligibility, authorization, medical necessity, coding linkage, bundling, timely filing, and enrollment drive most ID denials
- Read the full remittance and payer policy before picking a corrected claim, reconsideration, or formal appeal
- Track denials by service line, payer, and root cause instead of fixing each one in isolation
- Confirm code descriptions and payer rules against current CMS and X12 sources before resubmitting
What Are Medical Billing Denial Codes?
A denial code is a payer-supplied reason explaining why a claim was refused, reduced, suspended, or sent back for more information. Interpretation isn't universal. The same code can carry slightly different meaning depending on the payer, the claim type, and the specific contract behind it.
Three separate systems get lumped together under "denial codes," and they're not interchangeable.
| Code type | What it does | Example |
|---|---|---|
| CARC | Identifies the broad payment adjustment reason | CARC 197: authorization absent |
| RARC | Adds explanatory detail or processing instructions | N54: claim inconsistent with authorized services |
| ICD-10-CM / CPT / HCPCS | Describes the diagnosis, service, or drug billed | Not a denial code at all |
According to X12's code reference, CARCs describe why a claim or service line paid differently than it was billed. They show up on the electronic remittance advice, the explanation of benefits, or a payer portal, almost always paired with a remark code and claim-line detail that explain the adjustment further.
A quick example
An ID practice bills a home infusion visit. The ERA returns CARC 197 (authorization absent) with RARC N54 (inconsistent with authorized services), tied to a specific HCPCS drug code and the ICD-10-CM diagnosis for the treated infection.
The CARC tells you payment was adjusted for authorization. The RARC tells you the service didn't match what was approved. Neither code tells you whether the fix is a corrected claim, a retroactive authorization request, or an appeal.
Always verify current code descriptions against CMS, X12, and the specific payer before acting.
Rejection versus denial
These aren't the same thing.
A front-end rejection means the claim never entered adjudication, usually because of a data error or missing field. It needs correction and resubmission, not an appeal.
A post-adjudication denial means the claim was processed and a decision was made. That decision can be corrected, reconsidered, or appealed, but it already carries a determination behind it.
Why Are Denial Codes Important in Infectious Disease Billing?
ID claims rarely involve a single service line. A typical OPAT episode combines evaluation and management, lab monitoring, drug acquisition, infusion administration, and follow-up visits, often across different billing entities. Each handoff is a point where claim data can conflict.
A denial code often exposes a process failure, not a coding mistake:
- Missing or lapsed authorization mid-course
- An eligibility record that doesn't match the date of service
- Incomplete clinical documentation
- Incorrect claim sequencing between facility and professional bills
- A payer-specific coverage limitation nobody checked beforehand
ID-specific documentation risks compound this. The IDSA's OPAT guideline states that the infection, including primary site and any secondarily seeded sites, must be identified before treatment begins.
Claims that fail to connect the documented organism, treatment duration, clinical severity, or the reason for outpatient IV therapy to the billed service are exposed to medical-necessity and diagnosis-mismatch denials alike.
Denials delay payment, add accounts-receivable work, and obscure which service line is actually profitable. A practice running OPAT, infusion, and consult billing side by side needs to know which one is bleeding, not just that the total AR number grew.

Rather than leaning on generalized industry denial rates, review your own payer mix, service volumes, and remittance history.
GrowInfectiousDisease publishes free, ungated tools built specifically for this kind of practice-economics review. ID physicians and administrators can test denial and revenue-cycle questions against their own numbers rather than someone else's benchmark.
The tools don't replace payer guidance or coding advice, but they are a starting point for seeing where your numbers diverge from expectations.
Common Types of Medical Billing Denial Codes
Group denials by the action required to resolve them rather than by code number. Verify every illustrative CARC/RARC below against current X12 and payer documentation before using it operationally.
Eligibility, coverage, and coordination-of-benefits denials
These stem from inactive coverage, incorrect subscriber data, noncovered benefits, or a secondary-payer sequencing error. For ID practices, this surfaces during:
- Recurring OPAT visits where coverage changes mid-course
- Home infusion coordination across medical and pharmacy benefits
- Services split across facility and professional claims
Fix: verify coverage for the actual date of service, correct demographics or payer order, document the verification, and confirm whether rebilling is permitted under the payer's rules.
Prior authorization and referral denials
An authorization number doesn't guarantee the billed service matches what was approved. CARC 197 means authorization is absent; CARC 198 means it was exceeded, according to X12's code set.
Check these fields against the approval before resubmitting:
- Approved dates, units, and drug or service identifiers
- Site of care and rendering provider
- Whether the treatment plan changed mid-course
Example: an antimicrobial infusion authorized for a hospital outpatient suite gets delivered at home instead. That's a site-of-care mismatch, not a billing typo, and it may need retroactive review rather than a simple correction.
Medical necessity and level-of-care denials
These question whether the service, drug, setting, or duration was clinically justified. Documentation that supports ID medical necessity includes:
- The confirmed or suspected infection and relevant culture findings
- Severity, comorbidities, and prior treatment response
- The specific reason IV or prolonged outpatient therapy was chosen over oral alternatives
Review the applicable LCD, NCD, or commercial medical policy before appealing. Clinical documentation improvement means capturing what actually happened in more detail, not inflating acuity to win an appeal.
Diagnosis, procedure, and modifier mismatch denials
These happen when the ICD-10-CM code doesn't support the billed CPT/HCPCS service, when a more specific documented diagnosis goes unreported, or when modifiers and units don't match the record. Common ID triggers:
- A culture billed without a linked infection diagnosis
- Drug administration not connected to the treated condition
- Infusion time, dosage, and units misaligned with the clinical note
Coders shouldn't infer acuity, organism, or treatment intent. When documentation is unclear, route it back through a provider query instead of guessing.
Bundling, duplicate, mutually exclusive, and frequency-limit denials
These cover services considered included in another billed line, duplicate submissions, or units exceeding a frequency limit.
The CMS NCCI policy manual generally allows only one initial infusion service per encounter, with an exception for medically necessary separate IV access sites. Routine flushing of an access device isn't separately billable.
Before adding a modifier or rebilling, compare the denial against NCCI edits, payer bundling rules, and claim history. Sometimes the bundle is correct, and the modifier is the error.

Timely filing, corrected-claim, and appeal-deadline denials
A medically necessary service still gets denied if it was submitted, corrected, or appealed past the payer's deadline. Track:
- Original submission date and acceptance report
- Corrected-claim indicators used
- Appeal level and proof of timely submission
Deadlines vary by payer and contract. Don't assume a generic 90-day or 180-day window applies; check the governing plan document.
Provider enrollment, credentialing, and claim-submission errors
CARC 185 signals the rendering provider isn't eligible for the billed service, but it won't tell you the exact enrollment gap. ID physicians working across office, hospital, infusion, and home settings face this often, since billing-provider and rendering-provider relationships shift by location.
Run a pre-bill check for:
- NPI and taxonomy accuracy
- Payer enrollment status for the specific service and location
- Group affiliation and reassignment requirements
How to Choose the Right Response to a Denial Code
The correct response depends on the underlying error and the payer's instructions, not the code number itself.
- Corrected claim: Use when the submitted data was wrong or incomplete (incorrect member ID, diagnosis pointer, modifier, unit count, or provider identifier).
- Documentation submission or reconsideration: Use when the claim was accurate but the payer needs supporting records (authorization evidence, clinical notes, lab results, or proof of medical necessity).
- Formal appeal: Reserve this for a genuine disagreement with the payer's coverage or adjudication decision. Include the denial reason, relevant policy language, the clinical record, authorization evidence, and a specific argument tied to the billed service.
- Nonbillable or contractual adjustment: Some denials should not be rebilled or passed to the patient at all, depending on contract terms. Route these through compliance or billing leadership before posting an adjustment.
Decision sequence:
- Read the full remit, not just the CARC
- Verify the claim data against the clinical record
- Identify the root cause
- Confirm the payer's deadline
- Select the permitted response
- Document the action taken
- Monitor the outcome
A denial log helps more than memory does. Track these fields in one place:
- Payer, provider, and service line
- Denial category and CARC/RARC
- Date received and responsible owner
- Action taken, appeal deadline, and final resolution
Review hard-denial dollars by root cause each month. Assign each category an owner and a target date so the same mistake does not repeat across three claims before anyone notices the pattern.

What to Check Before Finalizing a Denial Response
A CARC or RARC is a starting point, not a full explanation. Before submitting any response:
- Review the full remittance, claim line, payer policy, authorization record, and clinical documentation together
- Never change a diagnosis or procedure code solely to get paid; every correction needs documentation support
- Identify the real issue type before choosing a workflow: duplicate, bundling, eligibility, authorization, medical necessity, timely filing, enrollment, or coordination of benefits
- Use the payer's required form, corrected-claim indicator, attachments, and submission channel
- Protect patient information using the payer's approved secure transmission method, and retain submission confirmation
- Review recurring denials by payer and service line for upstream fixes (EHR prompts, authorization checkpoints, claim-scrubbing edits)
Run a quarterly payment-variance review comparing your highest-value drug claims against contracted rates. That check catches short-pays and NDC mismatches a denial log alone often misses, because those claims pay something, just not the right amount.
Conclusion
Denial codes point to where a claim, record, authorization, or workflow broke down. They don't do the diagnostic work themselves.
The most effective denial program does three things well:
- Keeps CARCs and RARCs separate from diagnosis and procedure codes
- Chases root cause instead of patching symptoms
- Matches each denial category to the correction or appeal path it requires
For a practice running OPAT, infusion, and consultative lines at once, that discipline keeps denial management from becoming a permanent drag on cash flow.
Use current payer guidance and your own remittance data, not generic industry assumptions, to improve performance across every ID revenue stream you run.
Frequently Asked Questions
What is the ICD-10 code for intravenous antibiotic therapy (IV ABX)?
There's no single universal code for IV antibiotic therapy. Selection depends on the infection treated, the drug and administration service, and the setting. Mismatched diagnosis and treatment documentation commonly drives denials, so verify current ICD-10-CM, CPT, and HCPCS guidance before billing.
What is the ICD-10 code for prophylactic antibiotic therapy?
Prophylaxis coding depends on the clinical circumstance. Long-term prophylactic use generally points to Z79.2; short-term use typically needs no separate drug-status code. Confirm the code against documentation rather than defaulting to one code for every scenario.
What is the ICD-10 code for a history of antibiotic therapy?
A history of prior antibiotic use has no single universal code and should not be confused with long-term current therapy or an active infection. Verify whether the record supports a history, current-use, or condition-specific code.
What is the ICD-10 code for an adverse effect of antibiotics?
Document the specific antibiotic, reaction, and encounter context for adverse-effect coding. Sequence the manifestation first, then the applicable T36 family drug code with the correct adverse-effect character. Verify sequencing rules and payer requirements before submitting.


