I do not look at RCM as a billing department. I look at it as an operating system. If the front end is weak, the back end spends its time cleaning up problems that should never have reached the claim.
GOHEALTHCARE SPECIALTY REVENUE CYCLE MANAGEMENT
RCM Services for Ambulatory Surgery Centers
ASC revenue cycle management for surgical authorization, case costing, implants, facility coding, denials, payer contracts, A/R and compliance.
Developed by GoHealthcare Practice Solutions
SPECIALTY RCM
ASC revenue is not physician-office billing on a larger claim. The facility has its own covered-procedure rules, payment methodology, implants, drugs, supplies, contracts, pre-op readiness and professional/facility reconciliation.
PRIMARY FINANCIAL OBJECTIVE
Capture all legitimate reimbursement, reduce preventable denials and leakage, identify underpayments and protect compliance.
REFERENCE YEAR
2026. Verify current code sets, payer policies, contracts, fee schedules, NCCI/MUE edits and jurisdiction-specific requirements.
01
EXECUTIVE ANSWER
RCM Services for Ambulatory Surgery Centers
Revenue cycle management for Ambulatory Surgery Centers has to be built around the specialty, not around a generic billing queue.
ASC revenue is not physician-office billing on a larger claim. The facility has its own covered-procedure rules, payment methodology, implants, drugs, supplies, contracts, pre-op readiness and professional/facility reconciliation.
At GoHealthcare, revenue does not begin when the claim is created. It begins when the patient enters the system. Registration, eligibility, benefits, authorization, clinical documentation, coding, charge capture, site of service, claim submission, payment posting, denial management, A/R follow-up and underpayment recovery all determine whether the organization receives the reimbursement it legitimately earned.
GOHEALTHCARE PRACTICE SOLUTIONS — RCM OPERATING POSITION
02
SPECIALTY ECONOMICS
Why This Specialty Is Financially Different
ASC revenue is not physician-office billing on a larger claim. The facility has its own covered-procedure rules, payment methodology, implants, drugs, supplies, contracts, pre-op readiness and professional/facility reconciliation.
That complexity changes how the revenue cycle has to be staffed and measured. A generic billing team may know how to transmit a claim, but specialty RCM requires staff who can recognize when a procedure is not ready, when a payer policy is being applied incorrectly, when a code set changed, when a modifier is unsupported, when a paid amount is below contract and when the documentation problem belongs upstream with the clinical team.
In 2026, CMS continues to update Medicare payment and coding policy through the Physician Fee Schedule and NCCI. Those changes affect surgical procedures, diagnostic imaging, outpatient interventions, interventional pain and orthopedic services. The practical implication is simple: a specialty RCM program cannot be static.
03
REVENUE LEAKAGE
Where Revenue Is Usually Lost
| Revenue-Cycle Struggle | Why It Hurts Revenue | Operational Control |
|---|---|---|
| The surgeon is authorized but the facility is not | Professional authorization does not automatically authorize the ASC, facility code set or implant. | Perform facility-specific verification and authorization for every case. |
| Case profitability is unknown until after payment | Implant-heavy or carve-out-dependent cases can be scheduled without a reliable expected margin. | Use pre-service case costing and expected reimbursement. |
| Covered procedure status changes | Medicare's ASC covered-procedure files and payer policies are date-specific. | Verify the current approved-code/payment file for the date of service. |
| Implant and device contracts are not tied to payer contracts | Clinical preference can create negative contribution margin on certain payer cases. | Model implant cost against expected facility payment and carve-outs. |
| Professional and facility claims contradict each other | Different codes, laterality, dates or operative descriptions can trigger payer review. | Reconcile surgeon and ASC claim data before final submission. |
| Drug and supply billing is inconsistent | Packaged versus separately payable rules vary by payer/system. | Maintain payer-specific facility billing rules. |
| Denials are high-dollar | One denied spine, orthopedic or neuromodulation case can equal many office claims. | Escalate high-dollar ASC denials immediately. |
| Credentialing/network defects surface at payment | Facility, surgeon or anesthesia network status may differ. | Verify all relevant contracting/enrollment elements before scheduling. |
04
DEEP DIVE
The Specialty-Specific Revenue Problems We See
The surgeon is authorized but the facility is not
Professional authorization does not automatically authorize the ASC, facility code set or implant. This is not a back-office inconvenience. In ASC, a front-end defect can become a treatment delay, a denied high-value claim, an unnecessary patient balance, a missed appeal deadline or an aged account that takes months to resolve.
Perform facility-specific verification and authorization for every case. The control has to be visible in the workflow. It should have an owner, a required data set, a deadline and an escalation route. If the organization cannot show when the control was performed and what happened when it failed, the control is not mature enough.
Case profitability is unknown until after payment
Implant-heavy or carve-out-dependent cases can be scheduled without a reliable expected margin. This is not a back-office inconvenience. In ASC, a front-end defect can become a treatment delay, a denied high-value claim, an unnecessary patient balance, a missed appeal deadline or an aged account that takes months to resolve.
Use pre-service case costing and expected reimbursement. The control has to be visible in the workflow. It should have an owner, a required data set, a deadline and an escalation route. If the organization cannot show when the control was performed and what happened when it failed, the control is not mature enough.
Covered procedure status changes
Medicare's ASC covered-procedure files and payer policies are date-specific. This is not a back-office inconvenience. In ASC, a front-end defect can become a treatment delay, a denied high-value claim, an unnecessary patient balance, a missed appeal deadline or an aged account that takes months to resolve.
Verify the current approved-code/payment file for the date of service. The control has to be visible in the workflow. It should have an owner, a required data set, a deadline and an escalation route. If the organization cannot show when the control was performed and what happened when it failed, the control is not mature enough.
Implant and device contracts are not tied to payer contracts
Clinical preference can create negative contribution margin on certain payer cases. This is not a back-office inconvenience. In ASC, a front-end defect can become a treatment delay, a denied high-value claim, an unnecessary patient balance, a missed appeal deadline or an aged account that takes months to resolve.
Model implant cost against expected facility payment and carve-outs. The control has to be visible in the workflow. It should have an owner, a required data set, a deadline and an escalation route. If the organization cannot show when the control was performed and what happened when it failed, the control is not mature enough.
Professional and facility claims contradict each other
Different codes, laterality, dates or operative descriptions can trigger payer review. This is not a back-office inconvenience. In ASC, a front-end defect can become a treatment delay, a denied high-value claim, an unnecessary patient balance, a missed appeal deadline or an aged account that takes months to resolve.
Reconcile surgeon and ASC claim data before final submission. The control has to be visible in the workflow. It should have an owner, a required data set, a deadline and an escalation route. If the organization cannot show when the control was performed and what happened when it failed, the control is not mature enough.
Drug and supply billing is inconsistent
Packaged versus separately payable rules vary by payer/system. This is not a back-office inconvenience. In ASC, a front-end defect can become a treatment delay, a denied high-value claim, an unnecessary patient balance, a missed appeal deadline or an aged account that takes months to resolve.
Maintain payer-specific facility billing rules. The control has to be visible in the workflow. It should have an owner, a required data set, a deadline and an escalation route. If the organization cannot show when the control was performed and what happened when it failed, the control is not mature enough.
Denials are high-dollar
One denied spine, orthopedic or neuromodulation case can equal many office claims. This is not a back-office inconvenience. In ASC, a front-end defect can become a treatment delay, a denied high-value claim, an unnecessary patient balance, a missed appeal deadline or an aged account that takes months to resolve.
Escalate high-dollar ASC denials immediately. The control has to be visible in the workflow. It should have an owner, a required data set, a deadline and an escalation route. If the organization cannot show when the control was performed and what happened when it failed, the control is not mature enough.
Credentialing/network defects surface at payment
Facility, surgeon or anesthesia network status may differ. This is not a back-office inconvenience. In ASC, a front-end defect can become a treatment delay, a denied high-value claim, an unnecessary patient balance, a missed appeal deadline or an aged account that takes months to resolve.
Verify all relevant contracting/enrollment elements before scheduling. The control has to be visible in the workflow. It should have an owner, a required data set, a deadline and an escalation route. If the organization cannot show when the control was performed and what happened when it failed, the control is not mature enough.
05
PATIENT ACCESS
The Revenue Cycle Starts Before the Encounter
Patient access should establish the demographic, insurance, coordination-of-benefits, referral, authorization and financial facts required for payment. In complex MSK care, the cost of an access error rises with the value of the planned service.
Before a high-value service is scheduled, the team should know the active payer and product, network status, benefit coverage, deductible/coinsurance information when available, referral requirements, authorization status, ordering/referring provider requirements, site of service and the exact service being considered. The front desk should not be expected to interpret a complex medical policy in real time; those cases need a defined escalation path.
GOHEALTHCARE CONTROL
The schedule is the output of readiness. A patient should not appear on a high-value procedural schedule before the organization knows whether the case is clinically, administratively and financially ready.
06
AUTHORIZATION
Prior Authorization Is Part of Revenue Integrity
Prior authorization is not a separate administrative department that hands a number to billing. It is one of the earliest revenue-integrity controls. The authorization record should identify the member, payer/product, servicing provider, facility, service, code family when required, laterality/anatomy, units, approval dates and any conditions attached to the approval.
The most important control is the authorization-to-claim match. When the final service differs materially from what was approved, the team needs a change-management workflow rather than an assumption that the original authorization will protect the claim. Authorization also does not override medical necessity, benefit exclusions, coding rules, network status or payer contract terms.
07
HIGH-VALUE SERVICES
High-Value and High-Risk Revenue Categories
| High-Value / High-Risk Service | Revenue-Cycle Risk | GoHealthcare Control |
|---|---|---|
| Orthopedic surgery | Facility payment, implants and multiple procedures. | Before billing, reconcile the clinical service, authorization/benefit status, documentation, code family, units/modifiers where applicable, site of service and expected payer treatment. |
| Spine surgery | High implant/device cost and code complexity. | Before billing, reconcile the clinical service, authorization/benefit status, documentation, code family, units/modifiers where applicable, site of service and expected payer treatment. |
| Pain procedures | High volume, NCCI, authorization and drug issues. | Before billing, reconcile the clinical service, authorization/benefit status, documentation, code family, units/modifiers where applicable, site of service and expected payer treatment. |
| Neuromodulation | Device-heavy, high-dollar trial/implant/revision. | Before billing, reconcile the clinical service, authorization/benefit status, documentation, code family, units/modifiers where applicable, site of service and expected payer treatment. |
| Hand surgery | Multiple small anatomical procedures and laterality. | Before billing, reconcile the clinical service, authorization/benefit status, documentation, code family, units/modifiers where applicable, site of service and expected payer treatment. |
| Anesthesia coordination | Separate provider, network and claim stream. | Before billing, reconcile the clinical service, authorization/benefit status, documentation, code family, units/modifiers where applicable, site of service and expected payer treatment. |
| Implants/grafts | Cost, inventory, charge capture and carve-outs. | Before billing, reconcile the clinical service, authorization/benefit status, documentation, code family, units/modifiers where applicable, site of service and expected payer treatment. |
| Drugs/biologics | Packaged/separately payable status. | Before billing, reconcile the clinical service, authorization/benefit status, documentation, code family, units/modifiers where applicable, site of service and expected payer treatment. |
| Pre-op testing | Coverage, ownership and patient financial readiness. | Before billing, reconcile the clinical service, authorization/benefit status, documentation, code family, units/modifiers where applicable, site of service and expected payer treatment. |
| Post-op complication/return cases | Clinical and payment classification. | Before billing, reconcile the clinical service, authorization/benefit status, documentation, code family, units/modifiers where applicable, site of service and expected payer treatment. |
08
SERVICE DEEP DIVE
How the Major Services Affect Reimbursement
Orthopedic surgery
Facility payment, implants and multiple procedures. The revenue-cycle team should know what documentation must exist before the service, which payer policy may apply, whether authorization or benefit investigation is needed, which billing entity will submit the claim, what site-of-service rules matter and how expected reimbursement will be validated after payment.
The objective is not to increase the number of billable lines. The objective is to make sure every service actually furnished is accurately documented, correctly coded, submitted under the proper entity and setting, and paid according to the applicable contract or fee schedule. If the service is bundled, noncovered or included in another payment, the workflow should recognize that before the claim is released.
Spine surgery
High implant/device cost and code complexity. The revenue-cycle team should know what documentation must exist before the service, which payer policy may apply, whether authorization or benefit investigation is needed, which billing entity will submit the claim, what site-of-service rules matter and how expected reimbursement will be validated after payment.
The objective is not to increase the number of billable lines. The objective is to make sure every service actually furnished is accurately documented, correctly coded, submitted under the proper entity and setting, and paid according to the applicable contract or fee schedule. If the service is bundled, noncovered or included in another payment, the workflow should recognize that before the claim is released.
Pain procedures
High volume, NCCI, authorization and drug issues. The revenue-cycle team should know what documentation must exist before the service, which payer policy may apply, whether authorization or benefit investigation is needed, which billing entity will submit the claim, what site-of-service rules matter and how expected reimbursement will be validated after payment.
The objective is not to increase the number of billable lines. The objective is to make sure every service actually furnished is accurately documented, correctly coded, submitted under the proper entity and setting, and paid according to the applicable contract or fee schedule. If the service is bundled, noncovered or included in another payment, the workflow should recognize that before the claim is released.
Neuromodulation
Device-heavy, high-dollar trial/implant/revision. The revenue-cycle team should know what documentation must exist before the service, which payer policy may apply, whether authorization or benefit investigation is needed, which billing entity will submit the claim, what site-of-service rules matter and how expected reimbursement will be validated after payment.
The objective is not to increase the number of billable lines. The objective is to make sure every service actually furnished is accurately documented, correctly coded, submitted under the proper entity and setting, and paid according to the applicable contract or fee schedule. If the service is bundled, noncovered or included in another payment, the workflow should recognize that before the claim is released.
Hand surgery
Multiple small anatomical procedures and laterality. The revenue-cycle team should know what documentation must exist before the service, which payer policy may apply, whether authorization or benefit investigation is needed, which billing entity will submit the claim, what site-of-service rules matter and how expected reimbursement will be validated after payment.
The objective is not to increase the number of billable lines. The objective is to make sure every service actually furnished is accurately documented, correctly coded, submitted under the proper entity and setting, and paid according to the applicable contract or fee schedule. If the service is bundled, noncovered or included in another payment, the workflow should recognize that before the claim is released.
Anesthesia coordination
Separate provider, network and claim stream. The revenue-cycle team should know what documentation must exist before the service, which payer policy may apply, whether authorization or benefit investigation is needed, which billing entity will submit the claim, what site-of-service rules matter and how expected reimbursement will be validated after payment.
The objective is not to increase the number of billable lines. The objective is to make sure every service actually furnished is accurately documented, correctly coded, submitted under the proper entity and setting, and paid according to the applicable contract or fee schedule. If the service is bundled, noncovered or included in another payment, the workflow should recognize that before the claim is released.
Implants/grafts
Cost, inventory, charge capture and carve-outs. The revenue-cycle team should know what documentation must exist before the service, which payer policy may apply, whether authorization or benefit investigation is needed, which billing entity will submit the claim, what site-of-service rules matter and how expected reimbursement will be validated after payment.
The objective is not to increase the number of billable lines. The objective is to make sure every service actually furnished is accurately documented, correctly coded, submitted under the proper entity and setting, and paid according to the applicable contract or fee schedule. If the service is bundled, noncovered or included in another payment, the workflow should recognize that before the claim is released.
Drugs/biologics
Packaged/separately payable status. The revenue-cycle team should know what documentation must exist before the service, which payer policy may apply, whether authorization or benefit investigation is needed, which billing entity will submit the claim, what site-of-service rules matter and how expected reimbursement will be validated after payment.
The objective is not to increase the number of billable lines. The objective is to make sure every service actually furnished is accurately documented, correctly coded, submitted under the proper entity and setting, and paid according to the applicable contract or fee schedule. If the service is bundled, noncovered or included in another payment, the workflow should recognize that before the claim is released.
Pre-op testing
Coverage, ownership and patient financial readiness. The revenue-cycle team should know what documentation must exist before the service, which payer policy may apply, whether authorization or benefit investigation is needed, which billing entity will submit the claim, what site-of-service rules matter and how expected reimbursement will be validated after payment.
The objective is not to increase the number of billable lines. The objective is to make sure every service actually furnished is accurately documented, correctly coded, submitted under the proper entity and setting, and paid according to the applicable contract or fee schedule. If the service is bundled, noncovered or included in another payment, the workflow should recognize that before the claim is released.
Post-op complication/return cases
Clinical and payment classification. The revenue-cycle team should know what documentation must exist before the service, which payer policy may apply, whether authorization or benefit investigation is needed, which billing entity will submit the claim, what site-of-service rules matter and how expected reimbursement will be validated after payment.
The objective is not to increase the number of billable lines. The objective is to make sure every service actually furnished is accurately documented, correctly coded, submitted under the proper entity and setting, and paid according to the applicable contract or fee schedule. If the service is bundled, noncovered or included in another payment, the workflow should recognize that before the claim is released.
09
DOCUMENTATION
Clinical Documentation Is Financial Infrastructure
Documentation should support the clinical decision before it supports the claim. Strong documentation explains the diagnosis, objective findings, relevant testing or imaging, functional impairment, prior treatment, response, why the current service is reasonable and the plan after treatment. It should not be written as a payer checklist disconnected from the actual patient.
For revenue-cycle purposes, documentation must also identify the details that drive coding: anatomy, laterality, levels, units, drug/device details, procedure components, complications, assistant/co-surgeon involvement where relevant and the medical reason for separately reportable same-day services. If those facts are not in the record, billing should not invent them.
GOHEALTHCARE PRACTICE SOLUTIONS — DOCUMENTATION
I would rather delay a claim and fix the documentation than submit a high-dollar claim we cannot defend. Fast billing is not strong RCM if the claim is wrong.
10
CODING
Coding and Charge Capture
Coding converts documented work into the standardized language used for payment. It should be accurate, current and specific, but it should never become a strategy for forcing reimbursement. Review current CPT/HCPCS, ICD-10-CM, NCCI, MUE, modifier and payer instructions before billing. Full proprietary CPT descriptors should be obtained from licensed AMA sources.
Charge capture should reconcile the final clinical/operative report to the authorized and scheduled service. Missed charges create leakage; unsupported charges create compliance exposure. A high-performing RCM team detects both.
- Bill only services actually furnished and documented.
- Use modifiers only when the actual circumstance satisfies the code/payer rule.
- Review same-session code pairs against current NCCI and payer edits.
- Validate units for drugs, therapy, diagnostic studies and multi-unit procedures.
- Verify global, professional/technical and facility components where applicable.
- Reconcile unlisted services with payer-specific submission requirements.
- Maintain annual code-set and quarterly payer-edit updates.
11
CLAIM READINESS
The Claim Should Be the Output of a Controlled Process
A clean claim should be more than technically accepted by the clearinghouse. It should be the output of verified eligibility, correct authorization, complete documentation, accurate coding, correct billing entity, correct place of service, current payer rules and a known expected reimbursement.
First-pass acceptance is useful, but it is not sufficient by itself. A claim can pass every electronic edit and still be undercoded, miscoded, underpaid, billed under the wrong entity or vulnerable to recoupment. That is why claim readiness and revenue integrity have to be measured together.
12
DENIAL MANAGEMENT
Denials Should Be Diagnosed Before They Are Worked
| Denial / Payment Failure | Typical Root Cause | Correct Response |
|---|---|---|
| Facility not authorized | Only professional approval exists. | Identify the actual root cause first. Correct the workflow defect when possible; appeal only when the policy, contract and patient-specific record support an appeal. |
| Code not on ASC covered list | Medicare/payer setting rule. | Identify the actual root cause first. Correct the workflow defect when possible; appeal only when the policy, contract and patient-specific record support an appeal. |
| Implant not separately payable | Contract/payment methodology issue. | Identify the actual root cause first. Correct the workflow defect when possible; appeal only when the policy, contract and patient-specific record support an appeal. |
| Multiple-procedure reduction | Expected allowance mis-modeled. | Identify the actual root cause first. Correct the workflow defect when possible; appeal only when the policy, contract and patient-specific record support an appeal. |
| Bundling | Facility edits combine services. | Identify the actual root cause first. Correct the workflow defect when possible; appeal only when the policy, contract and patient-specific record support an appeal. |
| Network denial | ASC or provider status issue. | Identify the actual root cause first. Correct the workflow defect when possible; appeal only when the policy, contract and patient-specific record support an appeal. |
| Medical necessity | Documentation/authorization does not support the surgical case. | Identify the actual root cause first. Correct the workflow defect when possible; appeal only when the policy, contract and patient-specific record support an appeal. |
| Underpayment | Contract terms or carve-outs not applied. | Identify the actual root cause first. Correct the workflow defect when possible; appeal only when the policy, contract and patient-specific record support an appeal. |
13
DENIAL DEEP DIVE
What the Denials Are Actually Telling You
Facility not authorized
Only professional approval exists. A strong denial team does not simply resubmit the same claim with a different modifier or a longer cover letter. The account should be classified by root cause: eligibility, benefit, authorization, medical necessity, coding, bundling, site of service, payer processing, contract underpayment or patient-responsibility issue.
The resolution should then match the cause. Correctable data errors are corrected. Authorization defects are escalated through the appropriate pathway. Medical-necessity disputes use the controlling policy and patient-specific record. Contract underpayments are worked against the expected allowed amount. True noncovered services are handled through the appropriate patient-financial and compliance workflow.
Code not on ASC covered list
Medicare/payer setting rule. A strong denial team does not simply resubmit the same claim with a different modifier or a longer cover letter. The account should be classified by root cause: eligibility, benefit, authorization, medical necessity, coding, bundling, site of service, payer processing, contract underpayment or patient-responsibility issue.
The resolution should then match the cause. Correctable data errors are corrected. Authorization defects are escalated through the appropriate pathway. Medical-necessity disputes use the controlling policy and patient-specific record. Contract underpayments are worked against the expected allowed amount. True noncovered services are handled through the appropriate patient-financial and compliance workflow.
Implant not separately payable
Contract/payment methodology issue. A strong denial team does not simply resubmit the same claim with a different modifier or a longer cover letter. The account should be classified by root cause: eligibility, benefit, authorization, medical necessity, coding, bundling, site of service, payer processing, contract underpayment or patient-responsibility issue.
The resolution should then match the cause. Correctable data errors are corrected. Authorization defects are escalated through the appropriate pathway. Medical-necessity disputes use the controlling policy and patient-specific record. Contract underpayments are worked against the expected allowed amount. True noncovered services are handled through the appropriate patient-financial and compliance workflow.
Multiple-procedure reduction
Expected allowance mis-modeled. A strong denial team does not simply resubmit the same claim with a different modifier or a longer cover letter. The account should be classified by root cause: eligibility, benefit, authorization, medical necessity, coding, bundling, site of service, payer processing, contract underpayment or patient-responsibility issue.
The resolution should then match the cause. Correctable data errors are corrected. Authorization defects are escalated through the appropriate pathway. Medical-necessity disputes use the controlling policy and patient-specific record. Contract underpayments are worked against the expected allowed amount. True noncovered services are handled through the appropriate patient-financial and compliance workflow.
Bundling
Facility edits combine services. A strong denial team does not simply resubmit the same claim with a different modifier or a longer cover letter. The account should be classified by root cause: eligibility, benefit, authorization, medical necessity, coding, bundling, site of service, payer processing, contract underpayment or patient-responsibility issue.
The resolution should then match the cause. Correctable data errors are corrected. Authorization defects are escalated through the appropriate pathway. Medical-necessity disputes use the controlling policy and patient-specific record. Contract underpayments are worked against the expected allowed amount. True noncovered services are handled through the appropriate patient-financial and compliance workflow.
Network denial
ASC or provider status issue. A strong denial team does not simply resubmit the same claim with a different modifier or a longer cover letter. The account should be classified by root cause: eligibility, benefit, authorization, medical necessity, coding, bundling, site of service, payer processing, contract underpayment or patient-responsibility issue.
The resolution should then match the cause. Correctable data errors are corrected. Authorization defects are escalated through the appropriate pathway. Medical-necessity disputes use the controlling policy and patient-specific record. Contract underpayments are worked against the expected allowed amount. True noncovered services are handled through the appropriate patient-financial and compliance workflow.
Medical necessity
Documentation/authorization does not support the surgical case. A strong denial team does not simply resubmit the same claim with a different modifier or a longer cover letter. The account should be classified by root cause: eligibility, benefit, authorization, medical necessity, coding, bundling, site of service, payer processing, contract underpayment or patient-responsibility issue.
The resolution should then match the cause. Correctable data errors are corrected. Authorization defects are escalated through the appropriate pathway. Medical-necessity disputes use the controlling policy and patient-specific record. Contract underpayments are worked against the expected allowed amount. True noncovered services are handled through the appropriate patient-financial and compliance workflow.
Underpayment
Contract terms or carve-outs not applied. A strong denial team does not simply resubmit the same claim with a different modifier or a longer cover letter. The account should be classified by root cause: eligibility, benefit, authorization, medical necessity, coding, bundling, site of service, payer processing, contract underpayment or patient-responsibility issue.
The resolution should then match the cause. Correctable data errors are corrected. Authorization defects are escalated through the appropriate pathway. Medical-necessity disputes use the controlling policy and patient-specific record. Contract underpayments are worked against the expected allowed amount. True noncovered services are handled through the appropriate patient-financial and compliance workflow.
14
A/R
Accounts Receivable Is a Work Inventory
A/R should not be managed as a static aging report. Every open balance should have a reason it remains open, an owner, a next action and a deadline. Segmenting A/R only by 0–30, 31–60, 61–90 and over 90 days hides the operational cause of the balance.
For specialty practices, I want A/R segmented by payer, provider, location, procedure family, balance size and root cause. High-dollar procedural accounts deserve earlier escalation. Appeals should not sit in the same queue as missing EOBs. Contract underpayments should not be treated like claim denials. Patient balances should not be generated until payer adjudication and contractual adjustments are correct.
15
UNDERPAYMENTS
Paid Is Not the Same as Paid Correctly
Underpayment recovery begins with an expected-allowable model. The organization needs contracted rates, fee schedules, multiple-procedure methodologies, component payment rules, implant or carve-out terms where applicable and payer-specific payment logic. Without that baseline, payment posting can only tell leadership what the payer sent, not whether the payment is correct.
Prioritize high-value variances, repeated payer patterns and discrepancies that affect many claims. Once a systematic underpayment is identified, quantify the exposure, correct the configuration if needed, pursue recovery and monitor future remits to ensure the problem does not recur.
16
REIMBURSEMENT
How to Maximize Reimbursement — Compliantly
Maximizing reimbursement does not mean maximizing codes. It means capturing all reimbursement legitimately earned for medically necessary, properly authorized, accurately documented and correctly billed services while eliminating preventable leakage and identifying payer underpayments.
1. Create pre-service case profitability estimates for high-cost cases.
This is a revenue optimization strategy only when it is implemented compliantly. The practice should establish the baseline, assign ownership, measure the defect or leakage being addressed, monitor the financial effect and audit for unintended behavior. The goal is to capture reimbursement that is legitimately earned under the record, code set, payer policy and contract—not to manufacture reimbursement through aggressive coding.
2. Require facility-specific authorization hard stops.
This is a revenue optimization strategy only when it is implemented compliantly. The practice should establish the baseline, assign ownership, measure the defect or leakage being addressed, monitor the financial effect and audit for unintended behavior. The goal is to capture reimbursement that is legitimately earned under the record, code set, payer policy and contract—not to manufacture reimbursement through aggressive coding.
3. Reconcile professional and facility code sets before billing.
This is a revenue optimization strategy only when it is implemented compliantly. The practice should establish the baseline, assign ownership, measure the defect or leakage being addressed, monitor the financial effect and audit for unintended behavior. The goal is to capture reimbursement that is legitimately earned under the record, code set, payer policy and contract—not to manufacture reimbursement through aggressive coding.
4. Maintain payer/implant carve-out matrices.
This is a revenue optimization strategy only when it is implemented compliantly. The practice should establish the baseline, assign ownership, measure the defect or leakage being addressed, monitor the financial effect and audit for unintended behavior. The goal is to capture reimbursement that is legitimately earned under the record, code set, payer policy and contract—not to manufacture reimbursement through aggressive coding.
5. Audit covered-procedure and quarterly ASC payment updates.
This is a revenue optimization strategy only when it is implemented compliantly. The practice should establish the baseline, assign ownership, measure the defect or leakage being addressed, monitor the financial effect and audit for unintended behavior. The goal is to capture reimbursement that is legitimately earned under the record, code set, payer policy and contract—not to manufacture reimbursement through aggressive coding.
6. Track contribution margin by procedure, payer and surgeon.
This is a revenue optimization strategy only when it is implemented compliantly. The practice should establish the baseline, assign ownership, measure the defect or leakage being addressed, monitor the financial effect and audit for unintended behavior. The goal is to capture reimbursement that is legitimately earned under the record, code set, payer policy and contract—not to manufacture reimbursement through aggressive coding.
7. Create high-dollar denial escalation within 24 hours.
This is a revenue optimization strategy only when it is implemented compliantly. The practice should establish the baseline, assign ownership, measure the defect or leakage being addressed, monitor the financial effect and audit for unintended behavior. The goal is to capture reimbursement that is legitimately earned under the record, code set, payer policy and contract—not to manufacture reimbursement through aggressive coding.
8. Integrate inventory/implant reconciliation with charge capture.
This is a revenue optimization strategy only when it is implemented compliantly. The practice should establish the baseline, assign ownership, measure the defect or leakage being addressed, monitor the financial effect and audit for unintended behavior. The goal is to capture reimbursement that is legitimately earned under the record, code set, payer policy and contract—not to manufacture reimbursement through aggressive coding.
9. Validate anesthesia/network readiness.
This is a revenue optimization strategy only when it is implemented compliantly. The practice should establish the baseline, assign ownership, measure the defect or leakage being addressed, monitor the financial effect and audit for unintended behavior. The goal is to capture reimbursement that is legitimately earned under the record, code set, payer policy and contract—not to manufacture reimbursement through aggressive coding.
10. Work underpayments against contract terms instead of accepting payer allowed amounts blindly.
This is a revenue optimization strategy only when it is implemented compliantly. The practice should establish the baseline, assign ownership, measure the defect or leakage being addressed, monitor the financial effect and audit for unintended behavior. The goal is to capture reimbursement that is legitimately earned under the record, code set, payer policy and contract—not to manufacture reimbursement through aggressive coding.
17
COMPLIANCE
Compliance Is a Revenue-Cycle Control
Compliance and financial performance are not opposing goals. Accurate claims are easier to defend, easier to appeal and less likely to create takebacks, refunds or audit disruption. OIG's compliance guidance emphasizes internal monitoring and auditing, standards, accountable leadership, education, communication, corrective action and enforcement. Those elements belong inside RCM governance.
- Do not add supply/device charges that are not separately reportable under payer rules.
- Do not schedule Medicare ASC cases without confirming covered-procedure status.
- Do not unbundle facility services to increase reimbursement.
- Maintain accurate implant/drug inventory and charge records.
- Verify beneficiary financial responsibility and applicable notice requirements.
- Audit professional/facility consistency.
- Address identified overpayments and credit balances.
- Maintain compliance program controls around vendors, implants and coding.
GOHEALTHCARE COMPLIANCE RULE
If a reimbursement strategy depends on a diagnosis that is not supported, a modifier that does not describe the service, units that were not furnished, or a code chosen to avoid a noncoverage policy, it is not revenue optimization. It is a compliance problem.
18
AUDIT
Prebill and Post-Payment Audit Strategy
Not every claim requires manual review, but high-risk and high-value claims should be sampled or routed according to a risk-based audit plan. Prebill audits should focus on authorization alignment, documentation support, modifiers, units, same-session code pairs, site of service, drug/device reporting and high-risk specialty rules. Post-payment audits should look for systematic underpayments, overpayments, credit balances, payer recoupments and recurring staff/provider patterns.
Audit findings should drive education and system changes. Repeated errors are not solved by correcting one claim at a time.
19
CONTRACTS
Payer Contract and Fee-Schedule Intelligence
Revenue cycle teams need to know the difference between a payer processing error and a contract outcome. Contract intelligence should include fee schedules, multiple-procedure rules, modifier reductions, implant/device treatment where applicable, timely filing, appeal limits, authorization terms, network products and delegated entities.
For Medicare, use current CMS fee schedule and payment-system files and the applicable MAC coverage rules. For commercial plans, maintain current contract and medical-policy sources. For workers' compensation, use the governing jurisdiction's fee schedule and dispute rules. Do not use one reimbursement assumption across all payers.
20
TECHNOLOGY
Technology, Automation & AI
Automation can improve eligibility checks, work-queue routing, authorization tracking, claim edits, denial classification, payment variance detection and policy surveillance. AI can assist staff with retrieval and classification, but it should not autonomously create unsupported diagnoses, select aggressive modifiers, invent payer criteria or determine regulatory status without human validation.
The best automation removes clerical friction while preserving human accountability for clinical, coding, compliance and financial decisions.
21
KPIs
RCM Scorecard for This Specialty
| KPI | Why It Matters |
|---|---|
| Case readiness | Authorization, benefits, codes, implants, patient balance. |
| Contribution margin | By payer/procedure. |
| Facility denial rate | By root cause. |
| Implant variance | Expected vs actual cost/payment. |
| Days in A/R | Facility accounts. |
| Clean claim rate | ASC claims. |
| Underpayment recovery | Contract variances. |
| Cancellation rate | Authorization/financial/network reasons. |
Every KPI should have a defined numerator, denominator, data source, owner and review cadence. Leadership should be able to drill from enterprise performance to payer, provider, location, procedure family and denial cause.
22
90-DAY PLAN
A 90-Day Specialty RCM Improvement Plan
| Period | Executive Priorities |
|---|---|
| Days 1–30 | Baseline denials, A/R, payer mix, high-dollar procedures, authorization defects, charge lag, coding risks, underpayments and staffing/work queues. |
| Days 31–60 | Implement specialty-specific readiness controls, denial taxonomy, expected-reimbursement models, documentation feedback, prebill edits and high-dollar escalation. |
| Days 61–90 | Measure financial effect, recover underpayments, close aged high-value accounts, retrain recurring defects, update payer policies and establish executive governance cadence. |
The first ninety days should not be judged by how many reports are produced. It should be judged by whether the organization can identify the major leakage points, assign ownership, close high-value gaps and prevent the same defect from recurring.
23
CASE
Operational Case Example
A ASC organization sees strong gross charges but cash is inconsistent and A/R is aging. Leadership initially assumes the billing staff need to work harder. The RCM assessment shows a different problem: high-value cases are entering the schedule before authorization and documentation are complete, coding is being built from scheduled services rather than final documentation, paid claims are not compared with expected allowables, and denials are categorized only as "payer denial." The organization redesigns the front-end readiness process, creates specialty-specific prebill controls, assigns high-dollar accounts to senior staff and implements contract variance review. The financial improvement comes from preventing avoidable defects and collecting reimbursement already supported by the clinical work—not from adding unsupported charges.
24
LEADERSHIP
What Physician and Executive Leaders Should Ask
- Can we identify our top five denial causes by payer and procedure?
- How many high-dollar claims are over 60 and 90 days, and who owns each one?
- Are our authorizations reconciled to the actual service performed?
- Do we know our expected allowed amount before the remit arrives?
- Which providers or locations have recurring documentation or coding defects?
- Where are we missing legitimate charge capture?
- Where are we receiving payment below contract?
- Which denials are preventable and which are policy-level?
- What overpayment or credit-balance risks have we identified?
- Can our dashboard explain why revenue moved this month?
25
FAQ
Frequently Asked Questions
Why is RCM for Ambulatory Surgery Centers different from general medical billing?
ASC revenue is not physician-office billing on a larger claim. The facility has its own covered-procedure rules, payment methodology, implants, drugs, supplies, contracts, pre-op readiness and professional/facility reconciliation. General billing workflows can process a clean claim but still miss the specialty-specific medical-necessity, authorization, coding, bundling, site-of-service and payment issues that determine whether the account is fully and compliantly reimbursed.
How can a practice maximize reimbursement without creating compliance risk?
Start by eliminating preventable leakage: verify benefits and authorization, support medical necessity, complete documentation, code only services actually furnished, capture legitimate charges, use correct modifiers, reconcile payer contracts, work denials by root cause and pursue true underpayments. Maximizing compliant reimbursement is different from maximizing the number of codes on a claim.
Does prior authorization guarantee payment?
No. Authorization does not guarantee eligibility, benefit coverage, medical necessity at the date of service, correct coding, network status, site-of-service compliance, timely filing or contract payment. The authorization must also match what was actually performed.
What is the fastest way to reduce denials?
Do not start with appeals. Start with denial root-cause data. Identify the top preventable categories by payer, provider, procedure and location, then correct the front-end or mid-cycle process producing them.
How should high-dollar accounts be managed?
Use a separate high-dollar work queue with faster escalation, expected-reimbursement validation, senior ownership and documented next action. A single unresolved high-value claim can materially affect cash flow and A/R.
Why is underpayment recovery part of RCM?
A paid claim is not necessarily a correctly paid claim. Contractual rates, multiple-procedure rules, component payment, facility methodology, implants, carve-outs and payer edits can produce an incorrect payment that will be missed if staff simply post the remit and close the balance.
What should be audited regularly?
Audit the highest-risk intersections: authorization-to-claim match, documentation-to-code support, modifiers, units, NCCI edits, site of service, global services where relevant, drug/device reporting, underpayments, credit balances and repeated denial patterns.
What should executives see on an RCM dashboard?
At minimum: collections, net collection rate, first-pass acceptance, initial and final denial rates, days in A/R, A/R aging, charge lag, payment lag, authorization-related denials, coding/documentation denials, underpayments, appeal cycle time and high-dollar unresolved accounts.
26
INTERNAL LINKS
GoHealthcare RCM & Specialty Resources
| GoHealthcare Resource | Why It Matters | URL |
|---|---|---|
| Revenue Cycle Management | Flagship RCM authority page. | https://www.gohealthcarellc.com/revenue-cycle-management.html |
| Full-Service RCM | Core service offering. | https://www.gohealthcarellc.com/rcm-full-services.html |
| RCM Process | End-to-end operating workflow. | https://www.gohealthcarellc.com/revenue-cycle-management-process.html |
| Revenue Integrity | Revenue leakage, coding and payment integrity. | https://www.gohealthcarellc.com/revenue-integrity-msk-specialty-care.html |
| Revenue Cycle Coding | Coding controls and audit readiness. | https://www.gohealthcarellc.com/revenue-cycle-coding.html |
| Prior Authorization Resource Center | Pre-service medical necessity and payer workflow. | https://www.gohealthcarellc.com/overview.html |
| Procedure Library | Procedure-specific coding, medical necessity and payer intelligence. | https://www.gohealthcarellc.com/procedure-library.html |
| Ambulatory Surgery Centers Specialty Guide | Specialty-specific operations and clinical/payer intelligence. | https://www.gohealthcarellc.com/ambulatory-surgery-center-hub.html |
| Case Study Library | Operational case studies. | https://www.gohealthcarellc.com/case-studies.html |
27
REFERENCES
Authoritative References
| Authority | Reference |
|---|---|
| CMS | 2026 ASC Final Rule https://www.cms.gov/medicare/payment/prospective-payment-systems/ambulatory-surgical-center-asc/asc-regulations-and-notices/cms-1834-fc |
| CMS | 2026 ASC Payment Addenda https://www.cms.gov/medicare/payment/prospective-payment-systems/ambulatory-surgical-center-asc/asc-payment-rates-addenda |
| CMS | 2026 NCCI Policy Manual https://www.cms.gov/medicare/coding-billing/national-correct-coding-initiative-ncci-edits/medicare-ncci-policy-manual |
| OIG | General Compliance Program Guidance https://oig.hhs.gov/compliance/general-compliance-program-guidance/ |
| CMS | 2026 Medicare Physician Fee Schedule https://www.cms.gov/newsroom/fact-sheets/calendar-year-cy-2026-medicare-physician-fee-schedule-final-rule-cms-1832-f |
| CMS | 2026 NCCI Policy Manual https://www.cms.gov/medicare/coding-billing/national-correct-coding-initiative-ncci-edits/medicare-ncci-policy-manual |
| OIG | General Compliance Program Guidance https://oig.hhs.gov/compliance/general-compliance-program-guidance/ |
| AMA | CPT Licensing https://www.ama-assn.org/practice-management/cpt/cpt-licensing |
Your revenue cycle should produce more than claims. It should produce performance.
GoHealthcare can assess where your ASC revenue cycle is losing reimbursement, creating denials, aging high-value A/R or carrying unnecessary compliance risk.
GOHEALTHCARE RCM AUTHORITY CENTER
Explore All 150 RCM Authority Pages
Move across the complete GoHealthcare MSK and Injury Revenue Cycle Management knowledge system: specialty RCM, medical billing and coding, coverage and reimbursement intelligence, injury cases, workers’ compensation, in-network and out-of-network RCM, and ancillary MSK services.
Revenue Cycle Management — Main Flagship PageAmbulatory Surgery Centers
Hand & Upper Extremity
Interventional Pain Management
MSK Radiology & Diagnostic Imaging
Neuromodulation
Neurosurgery
Occupational Medicine / Workers’ Compensation MSK
Orthobiologics & Regenerative MSK Medicine
Orthopedic Surgery
Physical Medicine & Rehabilitation (PM&R)
Spine & Interventional Spine
Sports Medicine
Medical Billing, Coding & Reimbursement Intelligence
- Medical Billing Strategy for Specialty Healthcare
- Medical Coding Strategy for MSK & Injury Care
- ICD-10-CM Diagnosis Coding & Medical Necessity
- Diagnosis-to-Procedure Alignment in Specialty RCM
- CPT Coding Strategy for MSK & Injury Services
- HCPCS Coding for Drugs, Devices, DME & Supplies
- Modifier Strategy & Compliance
- NCCI Edits in MSK & Injury Revenue Cycle Management
- Medically Unlikely Edits & Unit-Based Billing Controls
- Global Surgery & Postoperative Billing
- Place-of-Service Coding & Reimbursement
- Professional vs Facility Billing
- Site-of-Service Reimbursement Strategy
- Drug, Biologic, Injectable & J-Code Billing
- Implant, Device & Supply Reimbursement
- Unlisted Codes & Emerging Procedure Billing
- Clinical Guidelines vs Coverage Policies
- Medicare NCD, LCD & MAC Coverage Intelligence
- Commercial Payer Medical Policy & Utilization Management Intelligence
- Payer Contracts, Fee Schedules, Expected Allowables & Payment Integrity
Injury Case RCM
- Injury Cases Revenue Cycle Management Hub
- Workers’ Compensation RCM Services
- Auto Accident RCM Services
- Auto Accident Medical Billing Services
- PIP & No-Fault Medical Billing
- MedPay Medical Billing & Reimbursement
- Personal Injury Medical Billing
- Medical Lien RCM Services
- Letter of Protection / LOP Medical Billing
- Attorney, Lien & Medical Receivable Management
- Injury Case Documentation, Diagnosis & Causation
- Injury Case A/R, Settlement Timing & Receivable Risk
- Medicare Secondary Payer, Coordination of Benefits & Third-Party Liability
- Injury Case Compliance, Patient Financial Responsibility & Medical Records
In-Network & Out-of-Network RCM
- Network Status & Reimbursement Strategy Hub
- In-Network Revenue Cycle Management Strategy
- Out-of-Network RCM Services
- In-Network vs Out-of-Network Revenue Cycle Management
- Out-of-Network Medical Billing Services
- Out-of-Network Benefits Verification & Financial Clearance
- Out-of-Network Prior Authorization & Medical Necessity
- Out-of-Network Allowed Amounts & Reimbursement Methodologies
- Out-of-Network Denial Management & Appeals
- Out-of-Network A/R & Underpayment Recovery
- No Surprises Act & Out-of-Network RCM
- Good Faith Estimates & Patient Financial Disclosure
- Single Case Agreements & Network Exceptions
- Self-Funded / ERISA Out-of-Network Claims
- Out-of-Network Facility & Professional Billing, Compliance & Payment Resolution
DEVELOPED BY
GoHealthcare Practice Solutions
28
SPECIALTY RCM CENTER
Explore the Ambulatory Surgery Centers RCM Authority Center
This specialty RCM hub now connects to seven deeper pages, each designed around a distinct search and operational intent rather than duplicate service-page language.
| Specialty RCM Resource | What It Covers |
|---|---|
| Medical Billing Services | The billing problem is rarely the claim form itself. It is whether the claim that reaches the payer accurately represents a clinically appropriate, authorized, documented and correctly coded specialty service. |
| Medical Coding & Documentation | Coding is not a clerical translation exercise. In complex specialty care, coding quality depends on whether the documentation clearly identifies the clinical work, anatomical detail, medical necessity, units, modifiers, site of service and same-session relationships. |
| Prior Authorization & Revenue Protection | Prior authorization is one of the earliest revenue-protection controls in specialty healthcare. When the approval does not match the service, provider, site, date, anatomy, units or final treatment plan, the financial defect exists before the claim is ever created. |
| Denial Management & Appeals | A denial is usually the visible end of an earlier defect. The fastest denial team is not necessarily the best denial team; the best team identifies why the claim failed, resolves the account correctly and prevents the same defect from recurring. |
| A/R & Underpayment Recovery | Accounts receivable is not an aging report. It is a work inventory. Every open balance should have a reason, owner, next action and deadline. Underpayment recovery adds another layer: a paid claim must be compared with what the payer should have paid. |
| Revenue Integrity & Compliance | Revenue integrity protects both sides of the equation: it finds revenue legitimately earned but missed, and it prevents reimbursement that is not supported. That is why coding, authorization, documentation, charge capture, contracts, overpayments and compliance belong in one control framework. |
| Reimbursement Optimization & RCM KPIs | Reimbursement optimization is the disciplined process of improving payment performance without creating coding or compliance risk. It combines patient access, authorization, documentation, coding, contract intelligence, denial prevention, underpayment recovery and executive measurement. |
Professional, Coding & Reimbursement Disclaimer
This material is provided for general professional, operational and educational purposes only. It is not medical, legal, regulatory, compliance, coding, billing, reimbursement, financial, payer-specific or contractual advice. Coverage requirements, utilization-management criteria, code sets, NCCI/MUE edits, payment methodologies, fee schedules, payer policies, contracts and clinical guidance may change. Organizations must independently verify current official sources, applicable payer contracts, CMS/MAC guidance, state requirements and licensed code sets before making operational, coding or reimbursement decisions. No authorization, payment, reimbursement, financial result or compliance outcome is guaranteed.