Revenue Cycle Partner Solutions for Infectious Disease Practices Infectious disease is one of the only specialties where a single patient can generate revenue in four different places — the hospital, the office, the infusion chair, and a payer's pharmacy benefit — often in the same week. Fellowship teaches you how to manage a central line infection. It doesn't teach you how to bill for the consult, the OPAT oversight, and the drug that made the treatment possible.

Many ID physicians and practice administrators discover this gap the hard way: through denied drug claims, stalled authorizations, or revenue that seems to disappear between the hospital discharge summary and the first infusion bill. A revenue cycle partner that only "submits claims" won't close that gap. The right partner connects documentation, coding, authorization, charge capture, posting, and denial management into one accountable process.

This guide covers what makes ID revenue cycles different, what a partner should actually provide, how to evaluate candidates, and how to measure whether the relationship is working.

Key Takeaways

  • Look for a partner fluent in OPAT, infusion, buy-and-bill, and consultative billing — not generalist claim submission.
  • Judge partners on process ownership, denial root-cause work, and reporting transparency, not a quoted collection percentage.
  • Set your own baseline for charge lag, A/R aging, and denial causes before accepting any vendor's numbers.
  • Confirm every coding or payer assumption against current CMS and payer guidance before changing workflows.

Why Infectious Disease Practices Need Specialized Revenue Cycle Support

Four Revenue Streams, One Fragile System

Sustainable independent ID practices typically draw income from four distinct sources: inpatient consultation, contracted hospital services (stewardship leadership, infection prevention directorship), outpatient clinic visits, and infusion/OPAT. An illustrative monthly model might look like $36,400 from hospital consultation, $38,480 from outpatient clinic, $12,000 from contracted services, and $53,300 from infusion and OPAT, roughly $140,180 combined.

Four infectious disease practice revenue streams monthly model

Each stream has its own documentation rules, payer logic, and failure points. A biller who understands outpatient E/M coding may have no idea how to flag a missing OPAT monitoring note or a discarded-drug reporting error.

Where Handoffs Create Leakage

Revenue doesn't usually disappear in one dramatic failure. It leaks through small, repeated gaps:

  • Hospital documentation that doesn't support the consult level billed
  • Authorizations obtained for the wrong site of care
  • Unclear ownership of supplies or drugs between practice, facility, and infusion provider
  • Charge entry delayed past timely-filing windows
  • Claim edits that sit unworked in a queue nobody owns

Each gap is small. Across a full OPAT caseload, they add up fast.

OPAT and Infusion Economics Aren't Just Professional Fees

Infusion and OPAT revenue depends on drug acquisition, administration coding, site of care, and whether the practice bears financial risk. Under buy-and-bill, the practice purchases, holds, administers, and bills for the drug, so a denied claim is a realized loss on inventory already consumed, not just deferred revenue.

Under white-bagging, a specialty pharmacy supplies the drug directly, removing acquisition risk but also removing control.

Medicare's drug billing rules add further precision requirements: bill in multiples of the HCPCS unit, report discarded single-dose amounts on a separate JW line, and use the JZ modifier to attest no waste occurred.

Place of service matters too. POS 11 (office) and POS 12 (home) are not interchangeable OPAT labels, and Medicare's home infusion benefit covers specific drugs delivered through a DME pump, not every home-administered antimicrobial.

Payer Rules Vary a Lot

Medical necessity, bundling, and authorization requirements shift by payer and by drug. Medicare doesn't recognize consultation codes 99242–99245 for Part B payment; practices must report the matching E/M visit code instead. Aetna separately distinguishes a specialist referral from service precertification — getting one doesn't satisfy the other.

A clinically correct service can still get delayed or denied if the authorization was obtained for the wrong setting, the documentation doesn't match the billed level, or the claim workflow never connects the three. A specialized revenue cycle partner is built to close that operational gap.

What a Revenue Cycle Partner Should Provide

Scope Across the Full Cycle

A partner's job shouldn't stop at claim submission. The scope should include:

  • Credentialing and payer enrollment, including infusion and OPAT site enrollment
  • Eligibility verification and prior authorization tracking, distinguishing medical from pharmacy benefit coverage
  • Charge capture and coding review
  • Claim creation, scrubbing, and submission
  • Payment posting and patient balance workflows
  • Denial management and appeals
  • A/R follow-up by payer, service type, and balance age

Persistex Medical Billing & Coding, which operates GrowInfectiousDisease's paid services arm, structures its catalog this way: splitting claims management, payment reconciliation, denial management, and A/R recovery into distinct service lines rather than one bundled "billing" product.

Documentation, Coding, and Denial Prevention

Good partners map every service to current CPT and ICD-10-CM requirements and flag missing documentation before submission, not after denial. Common under-capture points in a cognitive specialty include:

  • Under-leveling of consult or E/M codes
  • Incomplete time documentation supporting medical decision-making
  • Infusion hierarchy errors (initial versus subsequent versus sequential codes)
  • Drug-unit or discarded-amount mismatches

Denial prevention should be root-cause work, not resubmission. That means categorizing every denial by authorization status, site-of-care mismatch, drug-unit reporting, medical necessity, or coordination-of-benefits, then feeding those findings back to the clinical and front-office teams that can fix the source.

Five infectious disease billing denial root causes

Technology, Compliance, and Reporting

Your partner needs to work inside your actual systems: EHR, practice-management platform, clearinghouse, payer portals, and any infusion or lab interfaces, with role-based access controls and HIPAA-compliant handling throughout. Reporting should go beyond a monthly summary. Expect dashboards showing aging by payer and service line, denial trends by root cause, and a clear account of what the partner fixed versus what remains open.

How to Evaluate and Select a Revenue Cycle Partner

Build a Due-Diligence Checklist

Before signing anything, confirm:

  1. ID-specific experience: ask for references from comparable independent ID or infusion practices, not general primary care billing clients
  2. Staffing credentials: certified coders and billers (CPC, CPB, RHIT, CCS-level credentials are a reasonable bar)
  3. Coverage and escalation: who handles urgent authorization issues outside business hours
  4. Subcontractor transparency: is any work outsourced further, and to whom

One practical test: ask to speak with an ID or infusion practice of similar size that has used the same system or vendor for at least two years.

Separate Revenue Streams Before Comparing Proposals

Ask every finalist to walk through how they'd review your inpatient consultation, contracted hospital services, outpatient clinic, and infusion/OPAT revenue separately before proposing anything. A vendor that collapses all four into one blended "collection rate" hasn't actually looked at your practice.

Compare Pricing Models and Contract Terms

Pricing structure What to clarify
Percentage-based Does it apply to charges or actual collections? How do refunds affect the fee?
Per-claim/fixed fee Is there a minimum monthly charge regardless of volume?
Hybrid Which service lines fall under which model?
Startup/credentialing fees Are these one-time or recurring?

Also clarify contract duration, termination terms, and (critically) who owns follow-up on your existing aged A/R during the transition.

Require Transparency and Compliance Safeguards

Request sample reports with defined KPIs, a documented audit trail for coding decisions, and a written process for correcting partner errors.

On compliance, confirm:

  • A signed HIPAA business associate agreement
  • Role-based access controls
  • Data retention and destruction terms
  • A clear method for handling suspected overpayments

Run the same de-identified workflow questions past every finalist so you're comparing substance, not sales pitches.

Four revenue cycle compliance safeguards for medical billing partners

Plan Implementation and Measure Results

Phase the Transition

Credentialing timelines, not construction or staffing, usually gate your first collection date. Sequence the work accordingly:

  1. Baseline current performance before changing anything
  2. Inventory existing systems, payer contracts, and fee schedules
  3. Complete payer enrollment for any new sites or services
  4. Clean demographic and payer data
  5. Test interfaces between EHR, practice-management system, and clearinghouse
  6. Define a go-live escalation path with a named owner

Your practice-management system should also be able to hold contracted fee schedules, track authorization expiration dates, and report denials by dollars and root cause, not just by count.

KPIs to Track Using Your Own Baseline

No independently verified ID-specific benchmark exists for most of these metrics, so treat your own historical data as the baseline, not an industry average. According to MGMA's 2026 analysis, first-submission denial rates across practices have held at 7–8% over the preceding four years, with targeted process changes capable of pushing that below 5%, though this isn't an ID-specific figure.

Medical billing denial rate comparison from MGMA analysis

Track at minimum:

  • Charge lag (days from service to charge posting)
  • Clean-claim rate, defined per HFMA's MAP Keys as claims passing edits without manual intervention
  • Days in A/R and A/R over 90 days, by payer and service line
  • Denial rate by dollars, not just claim count (critical for drug-heavy infusion exposure)
  • Payment variance against contracted rates, which requires loaded fee schedules to detect underpayment

Authorization turnaround is another area worth watching closely. CMS's prior authorization rule sets 72-hour expedited and seven-day standard decision timeframes for specified payers starting in 2026, though drug authorizations are excluded, so infusion-specific turnaround still needs its own tracking.

Review Monthly With Both Sides of the Table

Monthly reviews should assign hard-denial dollars to root causes and hold someone accountable for each one: the practice, the partner, or the payer. Separate issues your partner controls (coding accuracy, claim scrubbing) from issues they don't (payer policy changes, clinician documentation gaps, staffing turnover).

If you want to pressure-test your own assumptions before a vendor conversation, GrowInfectiousDisease publishes free, browser-based tools, including an Infusion & OPAT Economics Calculator and an Independent ID Practice Economics Calculator, built so you can plug in your own numbers instead of relying on invented benchmarks.

Conclusion

A revenue cycle partner worth keeping functions as a transparent extension of your practice, not a vendor that disappears after claims go out the door. It should understand that inpatient consultation, contracted hospital services, outpatient clinic, and infusion/OPAT are four different financial engines requiring four different kinds of attention.

Before you sign anything:

  • Document your current revenue streams and pain points
  • Request proposals built on the same baseline data
  • Verify every coding and payer assumption against current guidance
  • Pick the partner that can show you exactly how its work will be measured

Frequently Asked Questions

What does the CPT code 87880 mean?

CPT 87880 describes infectious agent antigen detection for Group A Streptococcus by immunoassay with direct optical (visual) observation. Always confirm the current descriptor against the active CPT code set and payer guidance before billing.

What are the billing guidelines for CPT code 87880?

Billing requires documented medical necessity, the test method and result, and confirmation that CLIA complexity requirements (including the QW modifier for waived testing) are met. Payer-specific rules vary, so verify current guidance before submission.

What is the CPT code for a strep throat swab test?

A rapid visual antigen test typically uses 87880. Culture often uses 87081, and amplified nucleic acid testing uses 87651. Match the code to the method performed, not the specimen type alone.

Does throat culture check for strep?

Yes, a throat culture can detect Group A Streptococcus, but it's coded and billed differently than a rapid antigen or molecular test. Confirm the specific method used and check current payer policy before submitting the claim.