Anesthesiologists.com

Owner guide

Payer contracting and the No Surprises Act for groups

For an anesthesiology group, payer contracting is an operating decision with consequences for revenue, staffing, call coverage, and the ability to serve hospitals consistently. The No Surprises Act (NSA) changed the economics of some out-of-network encounters by protecting many patients from balance bills and creating a payment dispute process between providers and plans. It did not make every contract rate fair, every out-of-network claim negotiable, or every payment disagreement eligible for federal arbitration. Owners need a disciplined method to price agreements, model service-line effects, and manage claims from the contract file through final payment. This guide describes those mechanics for practice owners and partners; it is business and compliance information, not clinical or patient advice.

Billing specialist typing at a computer in a hospital office
Photo: Pavel Danilyuk / Pexels

1. Treat each contract as a portfolio of services and obligations

An anesthesia agreement cannot be evaluated from one headline conversion factor. The payment result for a group depends on the mix of base units, time units, qualifying modifiers, concurrency rules, eligible add-on codes, and how the payer edits claims. The same nominal conversion factor can produce different allowed amounts if one contract recognizes a modifier or time increment differently, applies a different rounding convention, or denies a portion of the group's commonly billed services. Build a rate model from actual paid claims and representative cases, not a rate sheet alone.

Start by identifying the contracting parties and products. A payer's commercial HMO, PPO, exchange product, Medicare Advantage plan, and self-funded employer plan administered by the same company may use distinct networks, fee schedules, and claim rules. Record the legal entity, product names, provider identifiers, covered locations, effective dates, as well as renewal and termination terms, and any delegated network or repricing vendor. A facility's participation status does not by itself establish that the anesthesiology group participates in the same product.

Map the contract's operational terms as carefully as its rates. Confirm credentialing and roster deadlines, required locations, claim submission limits, corrected-claim rules, timely filing, authorization responsibilities, records requests, payment remittance format, audit rights, recoupment procedures, and appeal deadlines. Clarify which provisions flow from a provider manual that the payer can revise unilaterally. Preserve the version of each manual and fee schedule incorporated into the agreement, and ask for written notice and a usable transition period before material rule changes.

Separate rates from non-rate obligations in the negotiation. A modest rate improvement can be outweighed by a restrictive clause that lets the payer apply the lowest rate across affiliates, extend its terms to future locations, or assign the agreement without meaningful notice. Review most-favored-nation language, exclusivity, assignment, unilateral amendment, termination without cause, and post-termination claims handling. Ask counsel to assess enforceability and interaction with the group's hospital contracts, particularly where a single hospital relationship depends on continuous coverage.

2. Price the agreement using contribution, not billed charges

The group's billed charge is generally a starting point for claim processing, not a forecast of collected revenue. A useful payer model estimates allowed payment by service category, then subtracts costs that vary with volume and staffing. For anesthesia, relevant categories can include routine facility cases, obstetric coverage, endoscopy, cardiac or other complex work, and medically directed or personally performed services. The group should model the case mix it expects to receive under the proposed agreement instead of relying on the payer's blended average.

For each category, calculate expected annual units and expected payment under the proposed fee schedule. Translate contract language into the actual algorithm used by the billing system: base units plus recognized time units, multiplied by the applicable conversion factor, with the payer's documented modifier and rounding rules. Compare the result against remittances under the current contract. Reconcile differences claim by claim until the modeled rate reproduces actual payments closely enough to be useful. If the model assumes a percentage of charges or a multiple of Medicare, retain the specific fee schedule and calculation that defines the reference amount.

Estimate contribution by subtracting direct labor and other costs that change with the work, then assess fixed costs and call requirements. A contract may increase volume but require overnight coverage, extra credentialing, administrative work, or a broader location commitment. Consider payment timing and denials: similar allowed amounts can produce different cash flow if one contract generates frequent disputes or slow corrections.

Negotiate a complete economic package. Request current fee schedules, code-level examples, and written answers about time-unit increments, modifiers, minimums, as well as maximums and multiple-procedure treatment. Ask the payer to show how the terms apply to representative claim patterns, unusual but recurring operational situations. Avoid accepting a generic promise that the group will be paid according to the payer's "standard policy" when the group cannot inspect that policy or determine how it changes.

Set an approval threshold before negotiations begin. Partners can specify minimum contribution, maximum administrative burden, acceptable termination exposure, and required notice for rate changes. This makes tradeoffs explicit instead of letting one percentage increase decide the matter.

3. Apply the NSA by claim type and plan rules

The NSA limits patient cost sharing and balance billing for specified out-of-network services when the law applies. Covered situations include emergency services, certain non-emergency services furnished by out-of-network providers at in-network facilities, and specified air ambulance services. Anesthesiology is among the ancillary specialties commonly covered when furnished by an out-of-network clinician at an in-network facility. The patient generally receives cost-sharing treatment based on applicable in-network rules, and the provider cannot collect an excess balance from the patient for a protected service. CMS summarizes the patient protections and covered settings.

Do not infer protection status solely from a remittance or the hospital's network status. For each claim, establish coverage type, as well as service and setting, facility network status for that product, the group's participation status, and whether an exception or another payment regime applies. Medicare, as well as Medicaid and other public coverage have separate frameworks; some state laws and All-Payer Model arrangements also determine out-of-network payment and displace federal IDR for specified claims.

The NSA also contains notice-and-consent exceptions for certain non-emergency services, but the exception is limited and does not generally permit a patient to waive protections for ancillary services such as anesthesiology at an in-network facility. Consent paperwork should not be treated as a blanket route to balance billing. Build the group's policy around the service categories actually eligible for an exception and the specific statutory and regulatory conditions; obtain legal review of forms and workflows before relying on them.

Keep protected claims separate from ordinary out-of-network receivables. A protected patient balance is not a substitute for a payer dispute, and staff should not send a balance bill while a protected claim remains unresolved. Configure billing edits to suppress patient statements above applicable cost sharing for protected claims. Route disagreements to payer follow-up, state processes, or federal IDR only after eligibility is established. CMS provides provider requirements and resources, materials on applicability and dispute steps.

4. Make an out-of-network decision with a realistic fallback

Leaving a network can improve use only if the group understands what happens to its claims and operations afterward. Before terminating or declining an agreement, estimate which patients and facilities are affected, which products remain in network, the likely volume shift, and whether the facility contract requires the group to accept a particular payer arrangement. Confirm that patients are not exposed to balance bills where the NSA applies. A strategy that assumes the group can bill its full charge to every patient is not a viable business plan.

Develop a payer-specific out-of-network forecast. Model historical allowed amounts, the plan's stated QPA where available, past out-of-network remittances, and realistic IDR outcomes separately. Include negotiation, screening, documentation, fees, vendor charges, management review, and delayed cash. For a high-volume payer, portfolio results matter more than one favorable determination.

Use a coverage map for each hospital and product. A group may have a strong position at one site because the facility is in network and the payer needs stable anesthesia coverage, while another site has competing groups or a different product mix. Bring facility leadership into the planning when the group's network status can disrupt a hospital's service arrangement. Keep discussions focused on contract terms and continuity obligations, not on steering individual patients or communicating pressure through patient billing.

If the group considers termination, follow the written notice and dispute provisions exactly. Maintain a transition plan for claims incurred before the effective date, credentialing records, and payer contacts. Request a final roster and rate confirmation in writing. Do not assume that ending a contract removes duties related to prior dates of service, records, audits, or recoupments; the survival clause and applicable rules determine those obligations.

5. Run the payment dispute process as a controlled work queue

For a qualifying out-of-network claim, the federal process generally begins after the plan makes an initial payment or issues a denial. The parties have a 30-business-day open negotiation period. The initiating party must start open negotiation within the applicable 30-business-day window after receiving the payment or denial, using the required notice and contact information. If no agreement is reached, a party may initiate federal IDR during the period that follows open negotiation. The time limits are short enough that a weekly or monthly batch review can lose rights; the group needs a daily or near-daily intake queue. CMS describes the open negotiation and IDR sequence.

At intake, preserve the claim, remittance or denial, QPA information, network records, as well as correspondence and proof of notice dates. Record payer, plan type, service code, facility, service date, group NPI or TIN, initial payment, patient cost sharing, and deadlines. Assign an owner to reconcile the notice against the source claim. A case queue should flag missing documents and approaching deadlines.

Before paying to initiate IDR, confirm the claim is eligible for the federal process and that state law or an All-Payer Model does not govern it. Verify that the dispute involves a protected, qualifying item or service, the correct plan or issuer, and an unresolved payment amount. Check the payer's QPA and any explanation of a downcoded service code or modifier. The QPA is a required reference point in the process, but it does not automatically settle the dispute. The parties make offers, submit supporting information permitted by the rules, and a certified IDR entity selects one offer under the applicable standard.

Build a case file that supports the offer with comparable contracted rates for the same or similar service and specialty, relevant case characteristics, clinician training and experience, market conditions, and other factors allowed by the rules. Identify the source and period for each data point. Avoid prohibited factors, the billed charge as a standalone measure or the patient's circumstances. Tie the offer to auditable evidence.

IDR is a claim-resolution expense, so set a minimum case value and a portfolio review. Compare the expected incremental recovery to the fee, staff time, vendor charges, and time value of delayed payment. Track outcomes by payer, code family, as well as facility and case characteristics. Stop repeating a strategy that produces low net recovery even if it wins some individual disputes. CMS publishes IDR process reports that can inform market monitoring, but aggregate data do not guarantee a result for the group's facts.

6. Use batching carefully and learn from a worked example

Batching can reduce repetitive work, but it is not simply combining every underpaid claim from one payer. Federal requirements generally tie a batch to the same provider or group identity, the same plan or issuer responsible for payment, eligible items that may be batched under the applicable criteria, and the permitted service period. The details of batching have changed through rulemaking and litigation, so the operations team must use the criteria governing the dispute instead of copying an old batch template. CMS's disputing-party guidance and batching FAQs explain the framework and pitfalls.

The source of payer identity matters. A single third-party administrator may process claims for several self-funded plans, but those plans are not automatically one payer for batching. For fully insured coverage, the same issuer may be relevant even when claims arise under different products, subject to the rules. Confirm the actual plan sponsor or issuer, not just the logo on the insurance card or the name of the claims administrator. Keep documentation that supports why each line belongs in the batch.

Illustrative worked example, all amounts and volumes illustrative: A group receives 24 eligible claims from one commercial issuer for the same qualifying anesthesia code family during a permitted period. Each remittance shows an initial total payment of $320, the plan payment and applicable patient cost sharing, while the group's documented offer is $510 per item. The group estimates that a favorable IDR result would yield $470 per item. If the entity selects that offer, the additional amount compared with the initial $320 is $150 per item, or $3,600 across 24 items before dispute expenses. If the group's total allocated filing, as well as vendor and staff cost for the batch is $1,800, the estimated net incremental recovery is $1,800. This is an expected-value illustration, not a promised outcome; the entity can select either party's offer, and the batch may fail eligibility review.

Suppose the same 24 claims include 16 claims paid by the issuer's fully insured product and eight claims administered by the same company for a self-funded employer. The group should not assume they can be combined. It should separate the plan identities, then test the service and timing requirements for each proposed batch. If three lines have different codes that do not meet the applicable similarity or related-condition standard, those lines may need separate treatment or may not qualify for batching. The staff time saved by a larger submission is irrelevant if an eligibility defect delays or defeats the entire filing.

Use the example's math as a decision template: multiply the per-item difference by eligible volume, subtract pursuit costs, and compare the result with accepting payment or continuing negotiation. Add a probability estimate based on the group's documented results, separate from legal entitlement. Review net as well as gross recovery so awards do not hide an uneconomic process.

7. Common mistakes that erode contract value

One recurring mistake is negotiating a rate increase without checking the claims configuration. If the payer's system rounds time differently, drops a modifier, or applies a stale fee schedule, the group may see no improvement despite a signed amendment. Compare the first remittances after an effective date against modeled claims and escalate discrepancies with claim-level evidence. Confirm that the amendment is loaded for every location, as well as clinician and product in its scope.

Another mistake is treating every denial as an NSA IDR case. A coding edit, eligibility failure, untimely filing, noncovered benefit, or credentialing gap can require a different correction or appeal. IDR does not repair poor claim data. Classify denial reason codes, correct what is fixable, and preserve payer correspondence before deciding whether a payment dispute remains.

Groups also lose money by missing deadlines, using the wrong plan identity, and filing batches that do not satisfy the rules. The payer's contact in a remittance may be the designated open negotiation recipient; sending an informal appeal to a general mailbox may not start the required period. A batch formed only by matching payer brand or anesthesia specialty may not be eligible. Use a checklist tied to the precise notice date, applicable process, and individual line items.

Finally, do not assume that the IDR offer should equal the group's billed charge or that one favorable case determines a market rate. Build support around permitted evidence and record outcomes across a meaningful sample. Do not let a vendor control the group's only copy of deadlines, as well as submissions and decisions. The owners retain the business risk and need access to the underlying record, cost schedule, and performance data.

8. Owner action checklist

  • Inventory every payer contract, product, location, fee schedule, and credentialed clinician; assign an owner and renewal date.
  • Model proposed rates using representative claims and actual payer edits. Include service mix, labor costs, and the staff time needed to maintain the contract.
  • Review amendment, termination, assignment, audit, as well as recoupment and unilateral change terms before signing.
  • Configure claim intake to identify protected NSA services, plan type, network status, remittance dates, and patient-billing restrictions.
  • Track open negotiation and IDR deadlines. Keep the notice, claim file, and delivery proof together.
  • Confirm state or federal dispute jurisdiction, payer identity, batching eligibility, and net expected value before filing.
  • Review payer performance and IDR outcomes quarterly, then use the evidence to adjust contract priorities and work queues.

Questions about your own practice? Contact richard@doctorsinvestorclub.com.

Richard C. Wilson

Backed by Richard C. Wilson and Family Office Club, the largest investor club in the world by media reach

  • $1B+In deals closed between members
  • 17MRegistered members across our networking groups
  • 19MSocial media followers
  • 340+Events hosted since 2007
  • 16In-person events a year
  • 50AI tools built on what works with family offices and investors

Family Office Club network figures. They describe the organization and its members, not a promise of investment or transaction results.