Infectious disease billing isn't like billing for a typical outpatient specialty. You're dealing with consultative services, hospital follow-up, OPAT, infusion drugs and supplies, prior authorizations, and documentation that has to justify both a clinical decision and a dollar amount. A proposal built for a generalist practice won't capture any of that.
This guide walks through what belongs in an infectious disease billing proposal: a scope-of-services framework, specialty-specific prompts for OPAT and infusion, pricing and KPI questions, compliance safeguards, and implementation requirements. GrowInfectiousDisease is a free resource hub built to help independent ID practices understand the financial mechanics behind these decisions, so you can apply your own numbers instead of someone else's assumptions.
Key Takeaways
- Anchor the proposal to your services, payers, systems, and claim volume—not a generic billing-company pitch.
- Assign clear ownership for coding, authorizations, drug billing, denial appeals, and unresolved accounts receivable.
- Demand reproducible pricing, defined KPIs, security commitments, and a written transition plan before comparing vendors.
- Treat sample rates and improvement claims as assumptions until your own data confirms them.
What to Include in an Infectious Disease Medical Billing Services Proposal
A proposal documents the intended relationship before anyone signs a final agreement. It should spell out services, responsibilities, assumptions, pricing, reporting, and implementation, in that order.
According to the HBMA's proposal checklist, a complete proposal covers qualifications, scope of service, staffing, quality and security controls, reporting cadence, and references. Keep pricing separate from the executive summary.
Core Components Worth Requiring
Build the document around these sections:
- Executive summary identifying the practice, the billing partner, the primary pain points, and the intended next step
- Company and team profile covering specialty experience, billing and coding credentials, account-management structure, and verifiable references
- Current-state assessment reflecting provider count, locations, EHR/PM systems, payer mix, service lines, and existing A/R aging
- Scope of services covering coding, charge capture, claim scrubbing, denial management, patient statements, credentialing, and hospital or infusion coordination
- Exclusions and client responsibilities, so physicians, front-office staff, and other vendors know what stays on their plate
Persistex Medical Billing & Coding, the billing partner behind GrowInfectiousDisease, structures proposals this way for independent ID practices across New England and nationwide. The team holds CPC, CPB, RHIT, and CCS credentials.
Always include a disclaimer. The proposal is not a substitute for a final service agreement or legal review, particularly for HIPAA obligations, indemnification, termination, and data ownership. Save those commitments for the contract, not the pitch.
How to Tailor the Template to Infectious Disease Revenue Streams
Most sustainable independent ID practices model revenue separately across four streams before combining them: inpatient consultation, contracted hospital services, outpatient clinic, and infusion or OPAT. A proposal that treats these as one undifferentiated bucket will miss where the money actually moves.
Start with a service-line inventory. Ask the practice to list:
- Office visits and outpatient follow-up
- Inpatient consultation and hospital follow-up
- Telehealth, where applicable
- OPAT oversight and infusion services
- Buy-and-bill drug administration
- Laboratory-related billable work
OPAT and Infusion Need Their Own Section
OPAT delivery happens through at least three distinct pathways in the US: home infusion, an outpatient infusion center or suite, and skilled nursing facilities, according to the IDSA's 2018 OPAT guideline. Site of care changes who bills what, so the proposal should define responsibility for:
- Capturing the professional service, drug, supply, administration, and monitoring components separately
- Confirming documentation, medical necessity, authorization status, and place-of-service rules before a claim goes out
- Tracking denied items by claim component, not as one lump encounter
Don't let a proposal insert generic drug margin figures. Acquisition costs, payment rates, and margins are practice-specific and shift by drug, purchasing arrangement, and quarter. Any vendor quoting universal profitability numbers is guessing.
GrowInfectiousDisease's Infusion & OPAT Economics Calculator exists precisely because these figures need to come from the practice's own contracts, not a template.
Add documentation prompts covering diagnosis specificity, treatment rationale, duration of therapy, and care transitions. Then map the workflow: documentation → charge capture → coding → authorization → submission → payment posting → reconciliation.
Ask the billing partner how it catches recurring problems, like missing documentation or authorization mismatches, and what training or audit evidence it can produce, not just a broad claim of expertise.
How to Compare Pricing, KPIs, and Financial Commitments
Pricing models vary, and a proposal should name the structure without pretending there's one universal rate. Common structures include:
- Percentage of collections
- Per-claim or per-transaction fees
- Monthly flat fees or minimums
- Hybrid arrangements (percentage for some payers, flat fee for others)
- Separate charges for credentialing, legacy A/R, appeals, or implementation
Require the fee base to be spelled out:
- Which collections count
- How refunds and adjustments are treated
- Whether patient payments are included
- When invoices get issued
Ask for a cost-comparison worksheet built from the practice's own historical volume, not an industry average.
Defining KPIs So They Actually Mean Something
A proposal that says "we'll improve your clean claim rate" without defining the measurement stage is close to meaningless. Each KPI needs a numerator, denominator, reporting period, and action threshold.
Key metrics worth requiring:
| KPI | What it should define |
|---|---|
| Clean-claim/acceptance rate | Measured at claims-tool stage, not payment outcome |
| Denial rate (by dollars) | Separated by payer, service line, and root cause |
| Days in accounts receivable | Aging by payer, age band, and missing-info status |
| Charge lag | Days from service to claim posting |
| Net collection rate | Collected against entitled, adjusted for refunds |
Denial rate by dollars matters more than denial rate by count for infusion-heavy practices, since one high-value drug claim can outweigh a month of office visits. Persistex's internal benchmark set tracks nine such metrics, including A/R over 90 days and payment variance against contracted rate, but keeps benchmark values blank until licensed data confirms a source and vintage.
That's a deliberate choice: do not present unverified figures as guaranteed outcomes. A proposal should never promise a specific collection percentage or denial reduction. Instead, it should commit to baseline reporting, review dates, and a process for investigating unfavorable trends.
Practices can run these numbers themselves with GrowInfectiousDisease's browser-based calculators, which require no email and store nothing entered.
Compliance, Security, Quality Assurance, and Implementation Requirements
Billing and claims processing qualify as business-associate activities under HIPAA. Any billing vendor needs a written business associate agreement covering permitted PHI uses, safeguards, and breach reporting, per HHS guidance on business associates.
A proposal should confirm:
- Minimum-necessary access controls and workforce training
- Secure transmission, audit logs, and disaster recovery
- Breach notification timelines (no later than 60 days after discovery)
- Pre-submission claim edits, documentation queries, and periodic audits
- How data access is removed when staff or the engagement changes
Implementation Shouldn't Be an Afterthought
Ask for a written timeline with owners for data gathering, system access, workflow configuration, staff training, and go-live testing. Equally important: define the transition of existing A/R:
- Which claims stay with the outgoing team?
- Which move to the incoming partner?
- How are pending appeals handed off without duplicate work?
After go-live, quality assurance continues through coding review. Quarterly audits should examine both under-leveling and over-leveling of evaluation and management codes, with under-leveling treated as a training issue rather than a compliance failure.
None of this replaces legal review. Have qualified counsel review the final agreement for liability, indemnification, termination notice, and data return.
Proposal Assembly and Final Review Checklist
Assemble the proposal in this practical order:
- Cover page
- Executive summary
- Practice-needs assessment
- Scope of services
- ID-specific service-line assumptions
- Responsibilities matrix
- Compliance controls
- KPIs
- Pricing
- Implementation
- References
- Next steps
Use a responsibilities matrix to assign ownership across:
- Coding and documentation queries
- Authorizations and credentialing
- Charge capture and claim submission
- Denials, appeals, and patient balances
- Reporting and system administration
Before accepting any proposal, test it against three scenarios:
- A representative office encounter
- A complex OPAT or infusion workflow
- A denied or underpaid claim (with no identifiable patient data)
Then ask the same six questions of every vendor:
- Who performs the work?
- Who owns exceptions?
- What evidence supports the proposed approach?
- Which metrics get reported?
- What stays with the practice?
- What is the complete cost?
Proofread for invented benchmarks, vague terms, and language that reads like a guarantee. Those are red flags, not reassurance.
Frequently Asked Questions
Can you give me an example of a medical billing services proposal?
A typical structure includes an executive summary, practice-needs assessment, ID-specific scope, responsibilities matrix, KPIs, pricing, compliance section, implementation plan, and next steps. Remember: a proposal is not the final contract.
What are the most important KPIs in medical billing?
Clean-claim or acceptance rate, denial and rejection rates, days in A/R, aging by payer, charge lag, payment posting timeliness, and net collection rate all matter. Each needs a consistent, stated definition.
What should an infectious disease practice include in a medical billing proposal?
Cover your service lines, OPAT or infusion workflows where applicable, coding and documentation responsibilities, authorizations, payer mix, systems, reporting cadence, pricing, and compliance commitments.
Should OPAT and infusion services have their own section in the proposal?
Yes, when offered. Professional services, drugs, supplies, administration, and documentation often involve different workflows and external-party coordination than standard office visits.
How should a medical billing services proposal explain pricing?
It should define the fee base, pricing model, included services, exclusions, adjustments, and termination costs using the practice's own data, not generic industry rates.
Is a medical billing services proposal the same as a contract?
No. A proposal describes the intended solution and commercial terms. The final contract legally governs services, privacy, liability, payment, and termination obligations.
