GoHealthcare Practice Solutions | Orthopedic, Spine & Pain | MSK Specialty Operations
  • Who we are
  • Leadership
  • Advisory Board
  • What We Do
  • RCM
  • Case Studies
  • Knowledge Center
    • 8 Excellence Frameworks™
    • CMS Ambulatory Specialty Model (ASM)
    • Procedure Library
  • Specialty Guides
    • MSK Radiology & Diagnostic Imaging
    • Hand & Upper Extremity Guide
    • Spine Specialty Hub
    • Occupational Medicine / Workers’ Compensation MSK
    • Pain Management Specialty Hub
    • Neurosurgery Specialty Hub
    • Orthopedic Surgery Specialty Guide
    • Physical Medicine & Rehabilitation (PM&R) Specialty Hub
    • Sports Medicine
    • Ambulatory Surgery Center Specialty Hub
  • GoHealthcare AI Governance Center
  • CLIENT PORTAL
  • READ OUR BLOG

Congress and Physician Independence in 2026: Two Bills, Two Approaches | GoHealthcare Practice Solutions

10/1/2026

 

Congress and Physician Independence in 2026: Two Bills, Two Approaches

Cluster: Health Policy & Physician Independence · Article ID: C14-01 · Pillar

By Pinky Maniri, Founder and Chief Executive Officer, GoHealthcare Practice Solutions

For most of the past decade, the story of physician practice ownership has moved in one direction. Independent practices sold to hospitals, health systems, insurers, and private equity-backed platforms, and physicians became employees. Orthopedics, spine, pain management, and anesthesiology have been among the most active specialties for these transactions. In 2026, Congress is paying attention in a way it has not before. Committees held hearings on consolidation. Physician members of Congress introduced a bipartisan bill to overhaul Medicare physician payment, arguing that underpayment drives doctors to sell. And in September, a group of Democratic lawmakers introduced legislation to ban the corporate practice of medicine nationwide and restrict the management services organizations that private equity uses to control practices. This pillar article explains what is happening in Congress, the two main legislative approaches, the arguments on each side, and what pain, orthopedic, and spine practices should watch.

The scale of consolidation

Recent data frame the debate. Research by the Physicians Advocacy Institute and Avalere Health found that more than 82 percent of physicians were employed by hospitals or corporate entities as of January 2026, and that hospitals and corporate entities owned 63.9 percent of physician practices, with corporate ownership, including private equity, insurers, and other non-physician owners, accounting for 33.2 percent. The same research found that 152,200 fewer physicians were operating independently in January 2026 than in 2018, and that corporate entities acquired more than 52,000 physician practices between 2018 and 2026.

Private equity is a smaller share of the total than its visibility suggests. A Government Accountability Office review found that about 6.5 percent of physicians worked in private equity-owned practices in 2024, compared with at least 47 percent employed by or affiliated with hospital systems. But private equity has been concentrated in certain specialties, including several relevant to MSK care, and its growth rate drew attention.

Recent market data also show a slowdown. Private equity health care deals fell 18.5 percent in the second quarter of 2026 compared with a year earlier, with deals in physician practice management and multispecialty groups on pace for about half their 2025 levels. Analysts cited economic factors and increased state regulatory scrutiny.

Why practices sell

Witnesses at a March 2026 House hearing on health care costs, including representatives of the American Medical Association, the American Academy of Family Physicians, and a large employer purchaser group, agreed that increasing government reimbursement for physicians would help practices remain independent. The AMA’s board chair described physicians as in crisis over payment, with costs for insurance, rent, and staff rising sharply.

The payment gap is measurable. According to the AMA, Medicare reimbursement for physician services, adjusted for inflation, declined 33 percent from 2001 to 2026. Physicians received a temporary 2.5 percent increase for 2026, but the proposed 2027 fee schedule would reduce the conversion factor by 1.68 percent for most physicians as that temporary increase expires.

Other factors cited by physicians and policy analysts include:

  • Site-of-service payment differences. Medicare often pays more for the same outpatient service in a hospital outpatient department than in a physician office, which rewards hospital acquisition of practices. CMS has taken limited steps toward site neutrality, including in its 2026 outpatient payment rule, but large differences remain.
  • Administrative burden. Prior authorization, quality reporting, algorithmic claim review, and complex billing rules require staff and technology that small practices struggle to afford.
  • Capital needs. Imaging, ASCs, EHRs, cybersecurity, and AI tools require investment.
  • Succession. Senior physicians often need a buyer to realize the value of practices they built.

Approach 1: Restrict who can own and control practices

On September 16, 2026, Senators Elizabeth Warren, Ron Wyden, and Jeff Merkley, and Representatives Val Hoyle, Alexandria Ocasio-Cortez, and Suhas Subramanyam introduced the Stop Corporate Takeovers of Physicians Act of 2026. The bill is modeled on Oregon’s 2025 corporate practice of medicine law.

Under the bill, it would generally be unlawful for a partnership or corporate entity that is not majority-owned and controlled by licensed health professionals to own or control a medical practice, employ a licensed health professional, or engage in the practice of medicine. The bill would also:

  • Prohibit management services organizations from controlling a practice through a “friendly” or “captive” physician, or by taking over functions such as hiring and firing, work schedules, compensation, disbursement of revenue or setting revenue targets, billing practices, and contracting.
  • Require physician owners to be meaningfully engaged in providing medical care in the state where the practice is located.
  • Prohibit corporate interference with clinical decisions.
  • Ban restrictive contract terms, including non-compete, nondisclosure, and non-disparagement agreements.

Supporters include the American Academy of Emergency Medicine and the American Economic Liberties Project. They argue that corporate ownership, particularly private equity with leveraged buyout financing, pressures physicians to change care delivery, raises prices, and has contributed to practice bankruptcies, and that state corporate practice laws have been circumvented through MSO structures.

Critics and skeptics raise several concerns. Commentators have noted that the bill would create a national framework in an area historically regulated by states, raising questions about federal-state interaction. Investors and some physicians argue that outside capital helps practices afford technology, expand access, and give retiring physicians a path to sell. Others ask how the bill would apply to existing arrangements, hospital employment, and legitimate management services. Opponents are also likely to argue that restricting private capital could push more practices toward hospital systems, which already employ far more physicians than private equity.

The bill was introduced by Democratic members. Its prospects in the current Congress are uncertain, and a separate article in this cluster examines its provisions in detail.

Approach 2: Pay independent practices enough to stay independent

A different approach focuses on Medicare payment. In July 2026, Representatives John Joyce, MD (R-PA), Greg Murphy, MD (R-NC), and Kim Schrier, MD (D-WA), with 23 original cosponsors, introduced the Patients First Act (H.R. 9693), a bipartisan proposal to reform the Medicare physician payment system. The AMA and many physician organizations support it.

Key provisions include:

  • Inflation-based updates. Replacing the current fixed updates with annual updates tied to the Medicare Economic Index, which measures the cost of running a practice, with a floor of 25 percent of MEI and a ceiling of 75 percent of MEI.
  • Budget neutrality reform. Raising the threshold that triggers across-the-board budget neutrality cuts to $57.64 million in 2028, indexed to MEI every five years, adding corrections when CMS overestimates utilization of new codes, updating practice cost inputs every five years, and limiting year-to-year swings in the conversion factor to 2.5 percent.
  • Alternative payment models. Freezing participation thresholds for three years, requiring notice and comment before CMS implements or substantially changes mandatory Innovation Center models, and directing a report on barriers to specialist participation.
  • Quality reporting. Replacing current reporting with a simplified system.

A related bill introduced earlier, the Provider Reimbursement Stability Act, focuses on the budget neutrality reforms.

Supporters argue that stable, inflation-adjusted payment would remove a major driver of consolidation and that budget neutrality rules have produced repeated cuts. The Medicare Payment Advisory Commission has recommended an inflation-based update, although at MEI minus one percentage point.

Critics focus on cost. The Committee for a Responsible Federal Budget noted that such proposals would add meaningfully to deficits without offsets, and estimated that MedPAC’s own recommendation would cost about $25 billion through 2035. Others question whether payment increases alone would reverse consolidation driven by other factors.

Other levers in play

  • Site-neutral payment. Proposals to equalize Medicare payment across settings would reduce the financial advantage of hospital ownership. Hospitals oppose broad site-neutral policies, arguing that they have higher costs and obligations.
  • State action. States have enacted and proposed laws requiring advance notice of health care transactions, strengthening corporate practice doctrines, and restricting private equity. Oregon’s 2025 law is the most prominent. Rhode Island requires notice for certain mergers producing groups of at least eight clinicians.
  • Antitrust enforcement. Federal and state antitrust agencies have scrutinized serial acquisitions in physician specialties.
  • Transparency. Proposals would require disclosure of practice ownership.

2026 at a glance

When Development
January 2026 Temporary 2.5 percent Medicare physician payment increase takes effect for the year
March 2026 House hearing examines provider consolidation and health care costs
March 2026 Provider Reimbursement Stability Act introduced to reform budget neutrality
Second quarter 2026 Private equity health care deal volume falls compared with 2025
July 2026 Patients First Act (H.R. 9693) introduced with bipartisan sponsors
July 2026 CY 2027 physician fee schedule proposed, with a conversion factor reduction for most physicians
September 2026 Stop Corporate Takeovers of Physicians Act introduced
November 2026 (expected) CY 2027 physician fee schedule final rule

How MSK specialties have been affected

Orthopedics, spine, pain management, and anesthesiology have been attractive to investors for several reasons: high procedure volume, ancillary and ASC revenue, fragmented markets with many small groups, and an aging population with growing musculoskeletal needs. Platforms built by acquiring multiple groups in a region have become common. Hospitals have also acquired orthopedic and spine practices to secure surgical volume for their operating rooms.

For physicians in these specialties, the consequences vary. Some report better access to capital, technology, and administrative support after joining a platform. Others report reduced autonomy, pressure on productivity, compensation changes after an initial period, and restrictive covenants that limit their options. Research from the Commonwealth Fund, based on interviews with physicians and advisers, found that outcomes depend heavily on deal terms, including compensation structures, governance rights, and non-compete provisions. That is why both legislative approaches matter to MSK physicians: one would change the rules for such deals, and the other would change the economics that drive them.

Questions physician owners are asking

Should we sell now before rules change? Decisions about selling should rest on the practice’s long-term goals and a careful review of terms, not on speculation about legislation. Regulatory uncertainty is a factor to weigh, not a reason to rush.

Could existing arrangements be unwound? Proposals differ on how they would treat existing arrangements. Oregon’s law phased in over several years. Any federal law would depend on its final text. Review agreements with counsel now so you understand your position.

Will payment reform pass? Physician payment reform has broad support among physician organizations and bipartisan sponsors, but cost is a significant obstacle. Plan for 2027 assuming the proposed cut, with upside if Congress acts.

How can we make our views known? Specialty societies and state medical associations coordinate advocacy on both payment reform and ownership legislation. Legislators pay most attention to concrete local examples, such as a practice that closed a location, stopped accepting new Medicare patients, or sold because of payment pressures, or conversely a practice that improved access after an investment.

Does any of this change our day-to-day operations now? Not directly. Neither bill is law. But the issues they address, payment adequacy and physician control, are worth acting on now through better revenue cycle performance and careful review of management agreements. Practices that act on these issues now will be better positioned whatever Congress ultimately does, and they will have better information for any decision about their future, including whether to stay independent, partner with others, or sell to a larger organization on favorable terms.

What this means for MSK practices

For independent pain, orthopedic, and spine practices, the policy debate matters in several ways:

  • Payment. If Medicare payment reform passes, independent practices would have more predictable revenue. If it does not, the pressure to consolidate continues, especially with the proposed 2027 cut.
  • Transactions. Practices considering a sale should expect more regulatory review, possible state notice requirements, and deal terms shaped by uncertainty about federal and state restrictions.
  • MSO relationships. Practices using management companies should review whether their agreements leave clinical and key business decisions with physicians. This is good practice regardless of legislation, and it is where federal and state proposals focus.
  • Mandatory models. The Patients First Act’s notice-and-comment provision would affect how CMS launches models like the Ambulatory Specialty Model, which begins January 1, 2027, for many low back pain specialists.
  • Operational excellence. Whatever Congress does, independent practices remain independent by running efficient revenue cycles, controlling costs, and adapting to payer and regulatory change.

What to watch

  • Whether the Stop Corporate Takeovers of Physicians Act gains cosponsors, especially bipartisan ones, or hearings.
  • Whether the Patients First Act or budget neutrality reforms move through committees or become part of a larger legislative package.
  • The CY 2027 physician fee schedule final rule, expected in November, and any congressional response to the proposed cut.
  • State legislation in the 2027 sessions.
  • Transaction volume and deal structures in MSK specialties.

Operational takeaway

Congress is debating physician independence through two very different lenses. One approach, reflected in the Stop Corporate Takeovers of Physicians Act, would restrict who can own and control medical practices and limit the MSO structures used by private equity and other corporate investors. The other, reflected in the bipartisan Patients First Act, would reform Medicare physician payment so that independent practices can afford to stay independent. Each has supporters and critics, and neither is law. For MSK practice owners, the practical response is the same regardless of outcome: understand the proposals, review ownership and management arrangements with counsel, strengthen the revenue cycle and cost structure, and make decisions about independence based on sound operations rather than pressure.

Related reading: The Stop Corporate Takeovers of Physicians Act: What It Would Mean for MSK Practices · The Patients First Act and Medicare Payment Reform · Staying Independent: An Operational Playbook for MSK Practices · The Ambulatory Specialty Model · Revenue Cycle Due Diligence in MSK Practice Acquisitions


About the author

Pinky Maniri, MSc, BSc, CRCR, CSAPM, CSPPM, CSBI, CSPR, CSAF, Certified in Healthcare AI Governance, is Founder and Chief Executive Officer of GoHealthcare Practice Solutions. She has more than 30 years of experience in healthcare operations, revenue cycle, prior authorization, coding, compliance, and payer strategy. GoHealthcare, founded in 2006, combines specialty expertise, payer insight, disciplined operations, and smart technology to strengthen patient access, compliance, reimbursement, and scalable growth for interventional pain management, spine, orthopedic surgery, neurosurgery, neuromodulation, PM&R, and ASC organizations.

References

  1. Office of Senator Elizabeth Warren and co-sponsors. Press release introducing the Stop Corporate Takeovers of Physicians Act, September 2026.
  2. American Medical Association. Bill Would Put an End to Yearly Patches on Medicare Physician Pay (Patients First Act, H.R. 9693), September 2026, and National Advocacy Update, July 31, 2026.
  3. Physicians Advocacy Institute and Avalere Health. Physician employment and practice ownership research, 2026.
  4. Fierce Healthcare. To Tackle Healthcare Costs, Representatives Weigh Curbs on Provider Consolidation, March 2026.
  5. Committee for a Responsible Federal Budget. The Next Doc Fix Is Coming, May 2026.
  6. Medscape. States Tighten Private Equity Healthcare Oversight as Deals Slow, 2026.

This article is educational, reflects legislative status as of September 2026, and does not advocate for or against any legislation.

Charge Capture Workflow for Pain Management Practices | GoHealthcare Practice Solutions

10/1/2026

0 Comments

 

Charge Capture Workflow for Pain Management Practices

Cluster: Charge Capture & Documentation · Article ID: C05-01 · Pillar

By Pinky Maniri, Founder and Chief Executive Officer, GoHealthcare Practice Solutions

Charge capture is the point where clinical work becomes billable revenue. In interventional pain management, that conversion is more fragile than in most specialties. A single patient encounter can include an evaluation, one or more procedures across several spinal levels, imaging, sedation, and drugs, performed in an office procedure suite, an ASC, or a hospital outpatient department. Each element has its own code, unit rule, and documentation requirement. When any piece is missed, entered late, or entered wrong, the practice either loses the revenue or bills it incorrectly. This pillar article describes a complete charge capture workflow for pain practices, from the schedule through the claim, and the controls that keep it accurate.

What counts as a charge capture failure

Charge capture problems fall into four categories, and each has a different cause.

Missed charges. A service was performed and documented but never billed. Common examples in pain practices are drug lines for injectate, a second procedure performed in the same session, add-on levels, and visits in hospital or ASC settings that never make it back to the office billing team.

Late charges. The service is billed, but days or weeks after the date of service. Late charges delay cash and, for some payers, risk timely filing limits. They also make authorization mismatches harder to fix because retro-authorization windows close.

Incorrect charges. The wrong code, wrong units, wrong modifier, wrong place of service, or wrong rendering provider. These produce denials, underpayments, or compliance exposure.

Unsupported charges. The charge is correct for what the provider intended, but the documentation does not support it. These may be paid at first and recouped later in an audit.

A charge capture workflow has to address all four.

Where pain management charges originate

Before designing controls, map every location where billable work happens. For a typical interventional pain group, the list includes:

Setting Professional charges Facility or technical charges
Office clinic E/M visits, trigger point injections, joint injections, drug screens Drugs and supplies billed by the practice
Office procedure suite or office-based lab ESIs, facet procedures, RFA, nerve blocks Practice bills global; drugs billed by practice
Ambulatory surgery center Procedure with modifier as required by setting ASC bills facility claim separately
Hospital outpatient department Procedure professional component Hospital bills facility claim
Inpatient consults and hospital visits Consult or subsequent hospital visits Not billed by practice
Remote or telehealth E/M and medication management None
Device clinics Stimulator and pump programming and refills Drug for pump refills

Each setting needs its own capture path. The most common source of missed charges is work performed outside the office, because it is not on the practice’s own schedule.

The seven-step charge capture workflow

Step 1: Start from the schedule

Every charge capture workflow should begin with a complete list of what was supposed to happen. The daily schedule from the practice management system covers clinic and office procedures. ASC and hospital cases need their own schedule feeds, usually from the facility’s surgery schedule or the practice’s surgical scheduling log. Inpatient and consult work needs a census or a provider-maintained log.

Control: A single daily list of all scheduled encounters across settings, owned by a named person.

Step 2: Document at the point of care

Provider documentation drives every charge. Pain procedure notes should be built from structured templates that require the elements coders need:

  • Procedure name and approach (for example, transforaminal versus interlaminar).
  • Spinal region and each level treated.
  • Laterality for each level.
  • Imaging modality used.
  • Contrast use and findings.
  • Drugs injected, with name, dose, and volume, and any wasted amount from single-dose vials.
  • Sedation, if performed, with the required elements for sedation codes.
  • Pre- and post-procedure pain scores.
  • Complications or the absence of complications.

A separate evaluation on the same day needs its own history, exam, assessment, and plan to support modifier 25.

Control: Required fields in procedure templates that cannot be skipped. Free-text procedure notes are the most common source of coder queries.

Step 3: Capture the charge

There are three common models for converting documentation into charges:

  1. Provider-entered charges. The provider selects codes in the EHR at the end of the encounter. Fast, but accuracy depends on the provider’s coding knowledge.
  2. Coder-entered charges. A coder reviews the note and assigns codes. More accurate, but adds a step and depends on note completion.
  3. Hybrid. The provider selects the service at a high level, and a coder validates and finalizes it. Many pain groups find this the best balance.

For interventional procedures, GoHealthcare generally recommends coder validation before release, because procedure claims are high-value and rule-heavy. Office E/M visits can often be provider-entered with periodic audit.

Control: A documented policy stating who assigns codes for each encounter type and who validates them.

Step 4: Capture drugs and supplies separately

Drug lines are one of the largest sources of missed revenue in pain practices. Corticosteroids, local anesthetics, contrast (where separately payable), and drugs for pump refills are billed by HCPCS code with units that must match the code descriptor.

Control: A drug capture step built into the procedure template, with a unit conversion table for each drug the practice stocks. Reconcile drug usage from the procedure log against drug charges weekly. Apply JW for discarded amounts from single-dose containers and JZ when there is no waste, as Medicare requires.

Step 5: Reconcile every day

Charge reconciliation compares the list of scheduled encounters against the list of charges entered.

For each scheduled encounter, the result should be one of:

  • Charged: charges entered and matched.
  • No-show or canceled: documented reason, no charge expected.
  • Pending documentation: note not yet signed.
  • Pending coding: note signed, awaiting coder.
  • Missing: no charge and no explanation.

Control: A daily reconciliation report with every “missing” item resolved within one business day. Pending documentation should be tracked by provider with an escalation rule, such as notes unsigned after 48 hours going to the medical director.

Step 6: Validate against authorization

In pain management, the authorization is often the most important validation step. Before a procedure charge is released, compare:

  • CPT codes billed versus authorized.
  • Levels and units billed versus authorized.
  • Laterality billed versus authorized.
  • Date of service within the authorization window.
  • Place of service matching the authorization.

Control: Any mismatch goes to the authorization team for a corrected or retro-authorization request before the claim is submitted. Most payers allow a short window to update an authorization after the procedure; after the claim denies, that window is often closed.

Step 7: Scrub and release

The final step before submission is automated claim scrubbing with specialty-specific rules. For pain practices, useful custom rules include:

  • Imaging guidance codes (77003, 77012) billed with procedures that include guidance.
  • Transforaminal add-on codes without their primary code.
  • Facet and RFA units exceeding joint counts or MUE limits.
  • Modifier 50 versus RT/LT by payer.
  • E/M on a procedure day without modifier 25.
  • Drug lines without JW or JZ for Medicare.
  • Frequency checks against prior procedures for the same patient and region.

Control: Scrubber rule set reviewed quarterly against the top denial reasons.

Charge lag targets

Charge lag is the number of days between date of service and charge entry. Measure it separately by encounter type because the causes differ.

Encounter type Reasonable target Common cause of delay
Office E/M 1 to 2 days Unsigned notes
Office procedures 1 to 3 days Coder backlog, drug capture
ASC and HOPD procedures 2 to 5 days Operative note routing from facility
Hospital consults and visits 2 to 5 days Provider logs not submitted

The targets are practical starting points, not published standards. The key is to measure consistently and address the category with the longest lag first.

Documentation standards that support clean charges

Charge capture and documentation are inseparable. The following standards prevent most coder queries and audit findings in pain practices:

  • Name the approach and the levels explicitly. “L4-5 and L5-S1 right transforaminal epidural steroid injection” is codeable. “Lumbar ESI” is not.
  • Count facet procedures by joint. Name the joints treated, not only the nerves.
  • Record drug amounts precisely. Record the amount administered and the amount wasted.
  • Document conservative care and pain scores in structured fields. These support medical necessity and are required for repeat procedures.
  • Separate the E/M note from the procedure note. A separate evaluation needs its own assessment and plan.
  • Sign notes promptly. Unsigned notes stop the entire workflow.

Charge capture in multi-location groups

Pain groups with several offices, procedure suites, and ASC relationships face an added challenge: every location develops its own habits. One office enters drug charges at the point of care, another relies on the coder, and a third batches charges at week’s end. Standardize the workflow across locations with a single charge capture policy, identical procedure templates, and one reconciliation report that lists every location side by side. Assign a charge capture owner at each site who is accountable for that location’s daily reconciliation. Compare charge lag, missing charge counts, and drug capture rates by location each month. The best-performing location usually shows what the others are missing, and its practices can be copied. When a new location opens, build its schedule feeds, templates, and reconciliation into the launch checklist rather than adding them after the first month of lost charges.

Roles and ownership

Role Charge capture responsibility
Providers Complete, timely documentation; code selection where policy allows
Clinical staff Procedure log, drug usage log
Coders Code assignment or validation; queries
Authorization team Authorization match review
Charge entry or billing staff Daily reconciliation; charge entry for outside settings
Billing manager Charge lag monitoring; scrubber rules; escalations
Compliance Periodic audits of documentation support

Auditing the workflow

A monthly audit should sample encounters from each setting and verify:

  • The encounter was charged.
  • Codes, units, and modifiers match the documentation.
  • Drug lines match the procedure log.
  • The authorization matched the billed services.
  • The charge was entered within the lag target.

Track findings by category and by provider. Recurring findings point to a template gap, a training need, or a workflow step that is being skipped.

Capturing charges from outside settings

Work performed outside the practice’s own clinic and procedure suite is the most common source of missed charges. Each setting needs its own path back to the billing team.

Ambulatory surgery centers. Obtain the ASC’s case schedule the day before and the completed case list the day after. Compare the completed case list with professional charges entered. When the practice has an ownership interest in the ASC, coordinate professional and facility coding so both claims describe the same procedure. Mismatched codes between the physician and facility claims invite payer review.

Hospital outpatient departments. Hospitals often do not send operative notes to the practice automatically. Assign someone to retrieve notes from the hospital EHR or portal daily. Track cases where the note is not yet available.

Inpatient consults and hospital visits. Providers should log each hospital encounter the same day, whether through a mobile charge capture application, a shared log, or a charge ticket. Compare logs against the hospital census when possible. Consults for patients the practice never sees again in clinic are particularly easy to lose.

Device clinics and pump refills. Intrathecal pump refills and neurostimulator programming visits are often scheduled separately from regular clinic. They involve both a service code and, for refills, a drug charge. Build these visit types with required drug fields so the medication line is never omitted.

Handling procedures that change on the table

Pain procedures do not always go as planned. A provider may add a level, switch sides, convert from a transforaminal to an interlaminar approach, or stop a procedure because of patient intolerance or anatomy. Each change has a charge capture consequence.

  • Added levels or sides need to be compared with the authorization immediately. Many payers allow a short window after the procedure to update the authorization. If the practice waits for the denial, that window is usually closed.
  • Changed approach requires a different code family. The note must describe what was actually done, not what was planned.
  • Discontinued procedures may be reportable with modifier 53 when the procedure was started and stopped for patient safety reasons, depending on payer rules. A procedure canceled before it began is not billed. The note must explain the reason for stopping and how far the procedure progressed.
  • Reduced services may be reported with modifier 52 when part of a procedure was intentionally not performed.

Control: The procedure template should include a “changes from plan” field. Any entry in that field sends the case to the authorization team the same day.

Engaging providers in charge capture

Providers control the two steps that most affect charge capture: documentation completeness and note signing. Three practices consistently improve provider engagement.

Share the data by provider. A monthly report showing each provider’s average note signing time, query rate, and charge lag, compared with the group average, prompts change more reliably than general reminders.

Make the template do the work. Providers resist adding documentation steps but accept templates that pre-populate standard elements and ask only for the specifics of the case.

Close the loop on denials. When a denial traces to documentation, show the provider the specific note and the specific gap. Most providers want to fix the problem once they see it.

Operational takeaway

In pain management, revenue is lost less often to complex coding questions than to ordinary workflow gaps: a drug line nobody entered, an ASC case that never came back to the office, a note left unsigned for a week, a level added on the table without an authorization update. A seven-step workflow of schedule, document, capture, drug capture, reconcile, authorization match, and scrub, each with an owner and a daily or weekly control, closes those gaps. The result is faster cash, fewer denials, and a record that holds up if a payer ever asks.

Related reading: Charge Lag Benchmarks and Reduction Tactics · Daily Schedule-to-Charge Reconciliation · Missed Charges in MSK Practices: Where Revenue Leaks · Procedure Note Templates That Support Clean Billing · Drug Billing for Pain Procedures: J-Codes and JW/JZ · Claim Scrubber Rules Every Pain Practice Should Build


About the author

Pinky Maniri, MSc, BSc, CRCR, CSAPM, CSPPM, CSBI, CSPR, CSAF, Certified in Healthcare AI Governance, is Founder and Chief Executive Officer of GoHealthcare Practice Solutions. She has more than 30 years of experience in healthcare operations, revenue cycle, prior authorization, coding, compliance, and payer strategy. GoHealthcare, founded in 2006, combines specialty expertise, payer insight, disciplined operations, and smart technology to strengthen patient access, compliance, reimbursement, and scalable growth for interventional pain management, spine, orthopedic surgery, neurosurgery, neuromodulation, PM&R, and ASC organizations.

References

  1. Centers for Medicare & Medicaid Services. National Correct Coding Initiative Policy Manual for Medicare Services, Chapter 8 (Nervous System) and Chapter 11 (Medicine).
  2. Centers for Medicare & Medicaid Services. JW and JZ Modifier Policy guidance for discarded drugs and biologicals.
  3. Centers for Medicare & Medicaid Services. Medicare Program Integrity Manual, Chapter 3 (Verifying Potential Errors and Taking Corrective Actions), documentation requirements.
  4. Healthcare Financial Management Association. MAP Keys mid-cycle key performance indicators.

This article is educational and reflects industry practice as of its publication date.

0 Comments

Radiofrequency Ablation Billing: CPT 64633–64636 Coding and Frequency Rules | GoHealthcare Practice Solutions

9/30/2026

0 Comments

 

Radiofrequency Ablation Billing: CPT 64633–64636 Coding and Frequency Rules

Cluster: Interventional Pain Coding & Billing · Article ID: C01-03

By Pinky Maniri, Founder and Chief Executive Officer, GoHealthcare Practice Solutions

Facet radiofrequency ablation (RFA) is a well-reimbursed procedure with a strict coverage pathway. Payers expect to see a documented diagnostic sequence before the first ablation and documented, sustained benefit before any repeat. When an RFA claim denies, the cause is almost always one of three things: the diagnostic blocks do not meet the policy threshold, units were counted by nerve instead of by joint, or a repeat ablation was performed before the payer’s minimum interval. This article covers the coding mechanics and the documentation chain that supports them.

The code set

CPT Description
64633 Destruction by neurolytic agent, paravertebral facet joint nerve(s), with imaging guidance; cervical or thoracic, single facet joint
64634 Cervical or thoracic, each additional facet joint (add-on)
64635 Lumbar or sacral, single facet joint
64636 Lumbar or sacral, each additional facet joint (add-on)

Two features of this code set drive most coding errors.

Units are counted per joint, not per nerve. Each facet joint is innervated by two medial branches, so ablating the L4 and L5 medial branches treats one joint (L5-S1 in the typical nomenclature used for lumbar RFA). Coders who count lesions or nerves instead of joints overstate units and trigger MUE denials. The procedure note should name the joint levels treated, not just the nerves lesioned.

Imaging guidance is included. Fluoroscopic or CT guidance is bundled into 64633–64636. Reporting 77003 or 77012 on the same claim will deny under NCCI.

Bilateral procedures

When the same joint level is treated on both sides, report the primary code with modifier 50, following the payer’s convention for the add-on code. Some commercial payers require RT and LT on separate lines. This is a payer-specific rule and belongs in your scrubber configuration.

The diagnostic pathway payers expect

Medicare Administrative Contractors adopted a common Facet Joint Interventions for Pain Management LCD in 2021, and many commercial payers follow a similar structure. The general sequence is:

  1. Clinical presentation consistent with facet-mediated pain, typically axial neck or back pain without radicular findings, with a documented history and exam.
  2. Failed conservative care for a defined period, documented with specifics.
  3. Two diagnostic medial branch blocks (64490–64495) at the same levels, each producing a defined percentage of pain relief consistent with the anesthetic used. Medicare’s LCD sets a high relief threshold for each block, and the percentage must be recorded using a pain scale, preferably with a post-procedure pain diary.
  4. Thermal RFA at the levels that responded.

Intra-articular facet injections do not substitute for medial branch blocks as the diagnostic step under the Medicare LCD. If the practice uses intra-articular injections first for therapeutic reasons, the record still needs the two medial branch blocks before RFA.

Repeat ablation rules

Repeat RFA is where frequency denials concentrate. Payers following the LCD structure generally require:

  • A minimum interval since the prior ablation at the same level, commonly six months.
  • Documented improvement from the prior RFA, expressed as a percentage reduction in pain or improvement in function that lasted for a defined period, commonly at least 12 weeks.
  • A cap on sessions per spinal region in a rolling 12-month period.
  • A cap on joint levels treated per session.

The practical problem is that the documentation for the repeat lives in visits months after the first procedure. If the follow-up notes do not record the percentage of relief and how long it lasted, the repeat cannot be supported regardless of how well the patient did. Build these two fields into the follow-up visit template.

Confirm the exact numeric thresholds against your MAC’s current LCD and billing and coding article, and against each commercial payer’s policy.

Pulsed and cooled RFA

Not every radiofrequency technique maps to 64633–64636. Pulsed radiofrequency is non-destructive, and many payers consider it investigational for facet pain; it should not be reported with the thermal destruction codes. Cooled RFA of the facet joint may be reported with the facet codes by some payers, while cooled or thermal ablation of the genicular nerves for knee pain uses a separate code (64624) and a separate coverage policy. Sacroiliac joint RFA also uses its own code (64625) and is subject to more restrictive coverage than facet RFA. Verify coverage before scheduling any of these.

Diagnosis coding

Facet RFA claims usually carry spondylosis codes without myelopathy or radiculopathy (the M47.81x family) matched to the treated region. Common errors include:

  • Reporting a radiculopathy diagnosis, which contradicts the facet-mediated clinical picture.
  • Using a region code that does not match the levels ablated, such as a lumbar code for a lumbosacral joint.
  • Omitting the diagnosis that was documented in the diagnostic block notes, creating an inconsistent record across the sequence.

Same-day services

  • E/M visits on the day of RFA require a separate, significant problem and modifier 25. The pre-procedure assessment is included in the procedure.
  • Moderate sedation may be separately reportable when performed and documented according to the sedation code requirements, but some payers and LCDs restrict routine sedation for facet procedures. Check the policy before building sedation into your standard RFA order set.
  • Drug lines for any local anesthetic or steroid injected after lesioning follow the same J-code unit and JW/JZ rules as other pain procedures.

Pre-billing checklist for RFA claims

Check Pass condition
Diagnostic blocks Two medial branch blocks at the same levels, each meeting the relief threshold, documented with scores
Units Counted per facet joint, not per nerve
Region Cervical/thoracic (64633/64634) vs. lumbar/sacral (64635/64636) matches note
Laterality Modifier 50 or RT/LT per payer rule
Imaging No 77003 or 77012 on claim
Repeat RFA Interval met; prior percentage relief and duration documented
Session and level caps Within the rolling 12-month and per-session limits
Technique Thermal RFA; pulsed RF not reported with these codes
Authorization Levels, laterality, and codes match the approval

Operational takeaway

RFA revenue depends on a documentation chain that spans three or more encounters: two diagnostic blocks and the ablation, then follow-up visits that justify the next one. Practices that treat each encounter as a standalone claim miss the gaps. A simple facet pathway tracker, with columns for each block date and relief percentage, RFA date, follow-up relief percentage, and duration, lets the authorization team see whether the patient qualifies before the case is scheduled.

Related reading: Facet Joint Injection and Medial Branch Block Billing · Epidural Steroid Injection Billing · Genicular Nerve Block and Ablation Billing · Frequency Limit Denials for Pain Procedures


About the author

Pinky Maniri, MSc, BSc, CRCR, CSAPM, CSPPM, CSBI, CSPR, CSAF, Certified in Healthcare AI Governance, is Founder and Chief Executive Officer of GoHealthcare Practice Solutions. She has more than 30 years of experience in healthcare operations, revenue cycle, prior authorization, coding, compliance, and payer strategy. GoHealthcare, founded in 2006, combines specialty expertise, payer insight, disciplined operations, and smart technology to strengthen patient access, compliance, reimbursement, and scalable growth for interventional pain management, spine, orthopedic surgery, neurosurgery, neuromodulation, PM&R, and ASC organizations.

References

  1. American Medical Association. CPT® Professional Edition, current year. Guidelines for 64490–64495 and 64633–64636.
  2. Centers for Medicare & Medicaid Services. Local Coverage Determination: Facet Joint Interventions for Pain Management and related Billing and Coding Article, as published by each Medicare Administrative Contractor. Medicare Coverage Database.
  3. Centers for Medicare & Medicaid Services. National Correct Coding Initiative Policy Manual for Medicare Services, Chapter 8 (Nervous System).
  4. Centers for Medicare & Medicaid Services. Medically Unlikely Edits (MUE) practitioner tables, current quarter.

This article is educational and reflects coding conventions as of its publication date. Confirm requirements against current CPT, payer policy, and your MAC’s LCD before billing.

0 Comments

Epidural Steroid Injection Billing: CPT 62320–62323 and 64479–64484 Explained | GoHealthcare Practice Solutions

9/29/2026

0 Comments

 

Epidural Steroid Injection Billing: CPT 62320–62323 and 64479–64484 Explained

Cluster: Interventional Pain Coding & Billing · Article ID: C01-01

By Pinky Maniri, Founder and Chief Executive Officer, GoHealthcare Practice Solutions

Epidural steroid injections (ESIs) are among the highest-volume procedures in interventional pain management, and they generate a disproportionate share of avoidable denials. Most of those denials trace back to four decisions made before the claim leaves the building: which code family applies, how many units and levels are reported, whether imaging is billed separately, and whether the medical record meets the payer’s coverage policy. This article walks through each decision in the order a coder should make it.

Step 1: Identify the approach

ESIs fall into two code families based on how the needle reaches the epidural space.

Interlaminar and caudal injections (62320–62323) are reported by spinal region and by whether imaging guidance was used:

CPT Region Imaging guidance
62320 Cervical or thoracic Without
62321 Cervical or thoracic With (fluoroscopy or CT)
62322 Lumbar or sacral (caudal) Without
62323 Lumbar or sacral (caudal) With (fluoroscopy or CT)

Transforaminal injections (64479–64484) are reported per level, with imaging guidance included in every code:

CPT Description
64479 Cervical or thoracic, single level
64480 Cervical or thoracic, each additional level (add-on)
64483 Lumbar or sacral, single level
64484 Lumbar or sacral, each additional level (add-on)

The operative note must state the approach explicitly. A note that says “epidural injection at L4-5 under fluoroscopy” without naming the approach forces the coder to query, and a query that sits in a work queue is charge lag.

Step 2: Report units and levels correctly

The two families count differently, and mixing up the counting rules is a frequent source of MUE denials.

  • Interlaminar and caudal codes are reported once per session per region, regardless of how many levels the injectate spreads across. An interlaminar injection at L5-S1 is one unit of 62323.
  • Transforaminal codes are reported per level. The primary code (64479 or 64483) covers the first level; each additional level is an add-on unit of 64480 or 64484.
  • Bilateral transforaminal injections at the same level are reported with modifier 50 on the primary and, where the payer requires it, on the add-on. Some commercial payers want RT/LT on separate lines instead. Build this as a payer-specific rule in your claim scrubber rather than relying on biller memory.

Step 3: Do not bill imaging separately

Every code in both tables that includes imaging guidance already bundles fluoroscopy or CT. Reporting 77003 (fluoroscopic guidance for spinal injection) or 77012 (CT guidance) alongside 62321, 62323, or any transforaminal code will trigger an NCCI edit and a denial. The only interlaminar scenario where separate imaging comes into question is with 62320 or 62322, which by definition were performed without guidance. If imaging was actually used, the correct fix is to code 62321 or 62323, not to add 77003.

Contrast injected to confirm needle placement is also part of the procedure and is not separately billable.

Step 4: Match the record to the coverage policy

Medicare Administrative Contractors adopted a common Local Coverage Determination for epidural steroid injections that took effect in December 2021, and many commercial payers mirror its structure. The core requirements to confirm in the chart before billing include:

  • Radicular pain or neurogenic claudication, documented with a diagnosis that supports it. Axial low back or neck pain without a radicular component is generally not a covered indication for an ESI.
  • At least four weeks of conservative care that failed or could not be tolerated, with specifics: what was tried, for how long, and the result.
  • Pain and function measured with a validated scale before the procedure.
  • Imaging guidance for every injection.
  • Session limits. The LCD restricts the number of ESI sessions per spinal region in a rolling 12-month period, restricts transforaminal injections to a limited number of levels per session, and limits interlaminar injections to one level per session.
  • Repeat injections supported by documented, sustained improvement from the prior injection.

Always pull your own MAC’s current LCD and billing and coding article before building workflows around specific numeric limits, because contractors revise language and code lists over time.

Step 5: Code the diagnosis with enough specificity

Diagnosis coding is where many ESI claims fail medical necessity edits even when the clinical story is sound. Common problems include:

  • Using M54.5x low back pain codes when the record documents radiculopathy (M54.1x) or disc disorder with radiculopathy (M51.1x).
  • Reporting an unspecified spinal region when the note clearly identifies lumbar versus lumbosacral.
  • Listing a diagnosis on the claim that does not appear in the procedure note or the most recent evaluation.

Check the diagnosis against the covered ICD-10 list in the payer’s billing and coding article, and make sure the physician’s assessment uses the same terminology.

Step 6: Handle the office visit on the same day

If the patient is seen for a separate, significant problem on the day of the injection, an E/M service can be reported with modifier 25. The decision to proceed with a minor procedure is part of the procedure’s global package, so a visit that only confirms the plan to inject does not qualify. When the E/M is legitimately separate, the note should read as a standalone evaluation with its own assessment and plan.

ESIs carry a 0-day global period, so follow-up visits on later dates are billed normally.

Step 7: Bill the drug correctly

Corticosteroid and anesthetic agents are reported with HCPCS J-codes when the practice purchases them. Units must match the HCPCS descriptor, not the vial size. Single-dose vial waste is reported with modifier JW, and when there is no waste, Medicare requires modifier JZ. Missing JZ is a small error that produces a steady stream of rejections.

A pre-billing checklist for ESI claims

Check Pass condition
Approach documented Interlaminar, caudal, or transforaminal named in the note
Code family matches 6232x for interlaminar/caudal; 6447x/6448x for transforaminal
Units One per region for interlaminar; one per level for transforaminal
Laterality Modifier 50 or RT/LT per payer rule
Imaging No 77003 or 77012 on the claim
Diagnosis Radicular or stenosis diagnosis on the payer’s covered list
Conservative care Four or more weeks documented with specifics
Frequency Session count within the rolling 12-month limit
Drug lines Correct J-code units with JW or JZ
Authorization Approval on file and matching codes, levels, and dates

Where practices lose money on ESIs

In GoHealthcare’s work with interventional pain groups, the most common revenue losses on ESIs are not coding errors. They are front-end failures: authorizations obtained for one level and a different level performed, frequency limits exceeded because nobody tracked prior injections from another provider, and conservative care documented in referral notes that never made it into the chart. The coding rules above matter, but the fix is usually a workflow that verifies the plan against the authorization and the coverage policy before the patient is on the table.

Related reading: Facet Joint Injection and Medial Branch Block Billing · Frequency Limit Denials for Pain Procedures · Imaging Guidance Bundling in Pain Procedures · Drug Billing for Pain Procedures: J-Codes and JW/JZ


About the author

Pinky Maniri, MSc, BSc, CRCR, CSAPM, CSPPM, CSBI, CSPR, CSAF, Certified in Healthcare AI Governance, is Founder and Chief Executive Officer of GoHealthcare Practice Solutions. She has more than 30 years of experience in healthcare operations, revenue cycle, prior authorization, coding, compliance, and payer strategy. GoHealthcare, founded in 2006, combines specialty expertise, payer insight, disciplined operations, and smart technology to strengthen patient access, compliance, reimbursement, and scalable growth for interventional pain management, spine, orthopedic surgery, neurosurgery, neuromodulation, PM&R, and ASC organizations.

References

  1. American Medical Association. CPT® Professional Edition, current year. Surgery/Nervous System guidelines for 62320–62327 and 64479–64484.
  2. Centers for Medicare & Medicaid Services. Local Coverage Determination: Epidural Steroid Injections for Pain Management and the related Billing and Coding Article, as published by each Medicare Administrative Contractor. Medicare Coverage Database.
  3. Centers for Medicare & Medicaid Services. National Correct Coding Initiative Policy Manual for Medicare Services, Chapter 8 (Nervous System).
  4. Centers for Medicare & Medicaid Services. JW and JZ Modifier Policy guidance for discarded drugs and biologicals.

This article is educational and reflects coding conventions as of its publication date. Confirm requirements against current CPT, payer policy, and your MAC’s LCD before billing.

0 Comments

Patient Intake Workflow for MSK Practices

9/28/2026

0 Comments

 

Patient Intake Workflow for MSK Practices

Cluster: Front-End Operations · Article ID: C04-01 · Pillar

By Pinky Maniri, Founder and Chief Executive Officer, GoHealthcare Practice Solutions

In pain management, orthopedic, and spine practices, the intake process decides more of the revenue outcome than most practice leaders realize. The payer, the line of business, the referral, the authorization pathway, and the patient’s financial responsibility are all determined, or mis-determined, before the patient ever sees a provider. When intake goes wrong, the error travels silently through the visit, the procedure, and the claim, and surfaces weeks later as a denial the billing team cannot fix. This pillar article lays out an intake workflow built for MSK practices, stage by stage, with the controls that prevent the most common downstream failures.

Why MSK intake is harder than primary care intake

Four characteristics make intake in musculoskeletal practices more complex than in general medicine.

Multiple lines of business. A single orthopedic or pain practice may see group health, Medicare, Medicare Advantage, Medicaid managed care, workers’ compensation, auto no-fault, and personal injury patients on the same day. Each has a different payer of record, different claim forms or submission rules, and different documentation expectations. A back injury that happened at work is not a group health claim, and billing it that way produces denials and potential compliance problems.

Referral dependence. Many MSK patients arrive from primary care, urgent care, emergency departments, other specialists, attorneys, or employers. Referral requirements vary by plan, and some HMO and Medicare Advantage products will not pay a specialist visit without an active referral.

Procedure-heavy care plans. A new pain or spine patient is often a candidate for injections, ablation, or surgery within weeks. Intake data quality directly affects the authorization team’s ability to secure approval before the procedure date.

High patient financial responsibility. Deductibles and coinsurance on procedures and surgery can be substantial. If intake does not capture accurate coverage and benefit information, the practice cannot produce a reliable estimate or collect appropriately.

The six stages of MSK intake

A well-designed intake process moves through six stages, each with a defined owner and a defined output.

Stage 1: Referral receipt and triage

The process starts when a referral, phone call, or online request arrives.

What to capture:

  • Referral source and referring provider name and NPI.
  • Reason for referral and body region.
  • Whether the condition is related to a work injury, motor vehicle accident, or other incident involving a third party.
  • Records received: office notes, imaging reports, prior injection history, therapy notes.

Control: A triage checklist that routes the referral by body region and specialty to the right provider type, and flags incident-related cases for the workers’ comp or personal injury coordinator before scheduling.

Referrals that arrive without records create problems later. Pain procedures and spine surgery require documentation of prior conservative care, and the best time to request it is at referral, not the week before a procedure.

Stage 2: Scheduling

What to capture:

  • Patient name exactly as it appears on the insurance card.
  • Date of birth, address, phone, and email.
  • Primary and secondary insurance, with subscriber name, relationship, and date of birth.
  • Visit type: new patient consult, second opinion, post-op, procedure.

Control: Scripted questions at scheduling. Two questions prevent a large share of line-of-business errors:

  1. “Is this problem related to an injury at work?”
  2. “Is this problem related to a car accident or any other accident where someone else may be responsible?”

If the answer to either is yes, the scheduler collects the claim number, adjuster or attorney contact, and date of injury, and routes the case to the appropriate coordinator. Workers’ comp and auto claims usually need authorization from the carrier before the first visit.

A third question matters for Medicare-age patients: “Do you have Original Medicare, or a Medicare plan through a private insurance company?” Patients frequently do not know the difference, and Medicare Advantage enrollment changes coverage rules, authorization requirements, and the payer of record.

Stage 3: Pre-visit verification

Verification should occur two to three business days before the visit, which leaves time to resolve problems.

What to verify:

  • Active coverage on the date of service.
  • Plan type and network status for the rendering provider and location.
  • Specialist copay, deductible status, and coinsurance.
  • Referral requirement and whether an active referral is on file.
  • Whether the plan requires authorization for office procedures commonly performed in the specialty, such as joint injections or trigger point injections.
  • Coordination of benefits: which plan is primary.

Control: A hard stop for inactive coverage or missing referral. The patient is contacted before the visit to resolve it, rather than discovering it at check-in or after the claim denies.

Real-time eligibility transactions return most of this information, but not all. Referral status, authorization rules for specific procedures, and some Medicare Advantage details may require the payer portal or a phone call. Document where each answer came from and the reference number.

Stage 4: Patient pre-registration

Digital pre-registration reduces check-in time and improves data accuracy because patients enter their own information.

What to collect:

  • Demographic confirmation and emergency contact.
  • Front and back images of insurance cards and photo identification.
  • Medical history, current medications, and allergies.
  • Pain and function questionnaires appropriate to the specialty, such as a numeric pain rating and a validated disability index for back or neck pain.
  • Prior treatment history: physical therapy, chiropractic, injections, surgery, and medications, with approximate dates and results.
  • Consent forms, HIPAA acknowledgment, financial policy acknowledgment, and assignment of benefits.
  • For Medicare patients, the Medicare Secondary Payer questionnaire.

Control: The prior treatment history is not just a clinical item. It is the foundation of the conservative care documentation that payers require for injections, ablation, and surgery. Collecting it in structured form at intake means the provider can confirm and document it at the first visit, and the authorization team can find it later.

Stage 5: Financial clearance

Before the visit, the practice should know what the patient owes and how it will be collected.

What to prepare:

  • Estimated patient responsibility for the visit, based on verified benefits.
  • Outstanding prior balances.
  • For self-pay patients, a Good Faith Estimate as required under the No Surprises Act when the service is scheduled far enough in advance.
  • For patients likely to proceed to procedures or surgery, an early conversation about expected costs and payment options.

Control: A financial policy that the patient acknowledges during pre-registration, stating when payment is expected, what forms of payment are accepted, and how balances are handled. Front-desk staff should have scripts for requesting payment, handling hardship, and offering payment plans within defined limits.

Stage 6: Check-in

Check-in confirms rather than collects.

What to confirm:

  • Photo ID matches the patient.
  • Insurance card on file is current; ask every visit, “Has anything changed with your insurance?”
  • Forms are complete and signed.
  • Copay and any prior balance are collected.

Control: A check-in quality checklist that must be completed before the patient is roomed. Many practices build this into the practice management system as required fields.

The intake data that billing depends on

A useful exercise is to trace each claim field back to the intake step where it originates.

Claim element Intake source Common failure
Patient name and DOB Scheduling, pre-registration Nickname or typo; mismatch with payer file
Subscriber ID and relationship Scheduling, card image Dependent billed as subscriber
Payer of record Scheduling questions WC or auto billed to group health; MA billed to Medicare
Referring provider Referral receipt Missing NPI; referral expired
Coordination of benefits Verification, MSP questionnaire Wrong primary
Accident indicators and date of injury Scheduling questions Missing, causing payer to pend for accident questionnaire
Prior authorization Verification, authorization team Not requested or not matching service

Every one of these failures produces a rejection or denial that costs staff time and delays payment. Most cannot be fixed by the billing team without going back to the patient.

Staffing and roles

In small practices, one person may handle several intake stages. In larger groups, specialization improves accuracy.

  • Referral coordinator: receives and triages referrals, requests missing records.
  • Scheduler or call center agent: schedules visits and asks the line-of-business questions.
  • Insurance verification specialist: completes pre-visit verification and resolves coverage problems.
  • WC/PI coordinator: manages workers’ comp, auto, and personal injury intake, carrier authorization, and attorney communication.
  • Front-desk representative: completes check-in and point-of-service collection.
  • Front-end supervisor: monitors intake KPIs, audits accuracy, and trains staff.

Whatever the structure, each stage needs a named owner. Handoffs without ownership are where data gets lost.

Measuring intake performance

Intake quality is measurable, and it should be measured weekly.

KPI Formula Why it matters
Pre-visit verification rate Visits verified 48 hours or more before DOS ÷ total visits Time to fix problems before the visit
Registration error rate Claims rejected or denied for registration causes ÷ total claims Direct measure of intake accuracy
Referral compliance Visits requiring referral with active referral on file ÷ visits requiring referral Prevents specialist visit denials
Pre-registration completion Patients completing digital pre-registration before arrival ÷ total patients Check-in efficiency and data quality
Point-of-service collection rate Collected at or before visit ÷ patient responsibility known at visit Cash and bad debt prevention
Line-of-business misclassification WC, auto, or PI cases initially registered to group health ÷ total incident cases Compliance and denial prevention

Reviewing registration denials by the staff member who registered the patient is not about blame. It shows where training is needed and which steps are being skipped.

Technology that helps

  • Real-time eligibility integrated with the practice management system, run automatically before each visit.
  • Digital intake and pre-registration with structured history and outcome questionnaires.
  • Card and ID capture with automatic data extraction and human review.
  • Referral management that tracks referral status and expiration dates.
  • Automated reminders that include pre-registration links and payment requests.
  • Work queues for verification exceptions so problems are resolved before the visit.

Technology does not replace the scripted questions at scheduling. No eligibility system knows that the patient hurt their back lifting boxes at work.

A 30-day intake improvement plan

Week 1: Measure the baseline. Pull 90 days of registration-related rejections and denials and group them by cause. Measure pre-visit verification rate and point-of-service collection rate.

Week 2: Fix the scripts. Add the work injury, accident, and Medicare Advantage questions to every scheduling script and train schedulers.

Week 3: Tighten verification. Move verification to two to three days before the visit, set hard stops for inactive coverage and missing referrals, and create a work queue for exceptions.

Week 4: Add accountability. Assign owners for each intake stage, publish the intake KPIs weekly, and review the top three error causes with front-end staff.

Most practices see measurable reductions in registration denials within the first two months.

Special intake scenarios in MSK practices

Several patient situations come up often enough in pain, orthopedic, and spine practices that each deserves a written procedure.

Second opinions for spine surgery

Patients seeking a second surgical opinion often arrive with imaging on disc, reports from another surgeon, and a pending authorization under the other surgeon’s name. Intake should collect the prior surgeon’s name and notes. It should also confirm whether the patient’s plan requires a referral for a second opinion. Some plans cover second opinions differently from standard specialist visits. Make sure imaging is loaded before the visit so the surgeon’s time is used on the evaluation.

Transfers of care

When a patient transfers from another pain practice, the new practice inherits the patient’s procedure history, and with it the frequency limits. A patient who had three epidural injections elsewhere in the past year may have little or no remaining allowance under the payer’s policy. Intake should request procedure notes for the prior 12 months and record the dates, levels, and procedures in a structured field. The authorization team can then see the history before planning the next procedure. For patients on chronic opioid therapy, intake should also collect the prior prescriber’s information and any existing treatment agreement, following the practice’s controlled substance policy.

Post-operative patients from outside surgeons

Orthopedic groups sometimes assume post-operative care for patients operated on elsewhere. Examples include traveling patients, patients who relocated, or cases where the original surgeon is unavailable. These visits may be billable, but only under specific rules for split global care. Intake should capture the surgery date, procedure, and surgeon so the billing team can apply the correct approach instead of treating the visit as a new problem.

Patients switching insurance mid-treatment

Coverage changes at the start of a plan year, or after a job change, can invalidate an authorization that was obtained under the prior plan. Intake should flag any patient with a procedure on the schedule whose coverage changed since the authorization was obtained. The authorization must be re-requested under the new plan, and the new plan’s benefits verified before the procedure date.

Minors and guardians

Sports medicine and orthopedic practices see many minor patients. Intake must identify the legal guardian, the guarantor for the account, and the subscriber on the insurance plan, which may be three different people. Consent forms must be signed by someone authorized to consent. The financial policy must be acknowledged by the guarantor.

Language access and accessibility

Intake materials and scripts should be available in the languages commonly spoken by the practice’s patients. The practice should have a documented process for interpreter services. Accurate intake depends on the patient understanding the questions, particularly the injury and coverage questions that determine the payer of record.

Operational takeaway

Intake is the first step of the revenue cycle and the one with the most leverage. In MSK practices, where lines of business are mixed, referrals and authorizations are common, and patient financial responsibility is high, a structured six-stage intake process prevents the errors that billing teams cannot fix after the fact. The practices that get intake right collect more at the time of service, submit cleaner claims, and spend less time chasing denials.

Related reading: Insurance Eligibility Verification for Pain and Ortho Practices · Procedure Benefits Verification: What to Ask the Payer · Referral Management in Orthopedic and Pain Practices · The Medicare Secondary Payer Questionnaire · Front-End Denial Prevention Program for MSK Practices · Workers’ Compensation Billing for Orthopedic Practices


About the author

Pinky Maniri, MSc, BSc, CRCR, CSAPM, CSPPM, CSBI, CSPR, CSAF, Certified in Healthcare AI Governance, is Founder and Chief Executive Officer of GoHealthcare Practice Solutions. She has more than 30 years of experience in healthcare operations, revenue cycle, prior authorization, coding, compliance, and payer strategy. GoHealthcare, founded in 2006, combines specialty expertise, payer insight, disciplined operations, and smart technology to strengthen patient access, compliance, reimbursement, and scalable growth for interventional pain management, spine, orthopedic surgery, neurosurgery, neuromodulation, PM&R, and ASC organizations.

References

  1. Centers for Medicare & Medicaid Services. Medicare Secondary Payer Manual, Chapter 3 (MSP Provider, Physician, and Other Supplier Billing Requirements).
  2. Centers for Medicare & Medicaid Services. No Surprises Act guidance on Good Faith Estimates for uninsured and self-pay individuals.
  3. Healthcare Financial Management Association. MAP Keys patient access key performance indicators.
  4. American Association of Healthcare Administrative Management. Patient access professional resources.

This article is educational and reflects industry practice as of its publication date.

0 Comments

How Is CMS Measuring Low Back Pain Specialists Under the Ambulatory Specialty Model?

9/27/2026

0 Comments

 
CMS Ambulatory Specialty Model

A specialty practice cannot manage ASM with annual reporting alone. It needs a continuous view of who is included, which episodes are attributed, how performance is calculated, and what operational behaviors are driving results.

Direct answer: CMS measures selected low-back-pain specialists under ASM through a defined performance framework that includes quality, cost, improvement activities, and Promoting Interoperability. The exact technical specifications and weighting should be taken from current CMS materials, but the operational requirement is clear: practices need reliable attribution data, measure ownership, care coordination, and performance monitoring at the clinician and episode level.

A score is only useful when leadership can identify which workflow, referral pattern, documentation process, or utilization trend is driving it. Internal leading indicators should therefore sit alongside official CMS measures.

For an MSK organization, the practical question is not only what the rule, payer, technology, or compliance principle says. The practice also needs to know how that requirement changes intake, clinical readiness, scheduling, authorization, documentation, coding, claim submission, payment, escalation, and executive oversight. A reliable workflow makes those dependencies visible before the patient or claim reaches the next step.

Why This Matters in MSK Specialty Operations

  • ASM is a mandatory CMS Innovation Center model for selected specialists in selected geographic areas.
  • The model includes a low-back-pain cohort relevant to pain management, interventional pain, orthopedics, neurosurgery, anesthesiology, and PM&R.
  • Performance is measured before the corresponding payment adjustment year.
  • Practices need operational ownership of quality, cost, care coordination, interoperability, and performance data.

Orthopedic, spine, pain management, neurosurgery, PM&R, and ASC operations are highly interdependent. A defect that begins in an office note can later appear as an authorization delay, a cancellation, a coding question, a denial, an underpayment, or a compliance finding. Leadership should therefore evaluate the entire episode rather than assigning every downstream problem to the department where it was finally discovered.

What the Workflow Should Verify

Control What to Verify Issue It Helps Prevent
Participation Confirm TIN/NPI participation and selected geography using current CMS data. Missed mandatory participation
Episode attribution Understand the CMS episode methodology and reconcile it with internal case lists. Wrong denominator
Performance data Assign owners for each performance category and data source. Unmanaged score
Care coordination Define closed-loop handoffs across the low-back-pain episode. Fragmentation
Financial modeling Estimate downstream payment exposure under current CMS methodology. Unplanned revenue impact

How to Operationalize These Controls

Participation

Confirm TIN/NPI participation and selected geography using current CMS data. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Missed mandatory participation becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Episode attribution

Understand the CMS episode methodology and reconcile it with internal case lists. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Wrong denominator becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Performance data

Assign owners for each performance category and data source. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Unmanaged score becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Care coordination

Define closed-loop handoffs across the low-back-pain episode. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Fragmentation becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Financial modeling

Estimate downstream payment exposure under current CMS methodology. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Unplanned revenue impact becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

What an ASM Performance Dashboard Should Show

  • Participant status by TIN/NPI.
  • Attributed low-back-pain episode volume.
  • Performance-category status and data completeness.
  • Cost and utilization trends by episode and referral pathway.
  • Care-coordination exceptions and unresolved handoffs.
  • Projected financial exposure based on current CMS methodology.

A score is only useful when leadership can identify which workflow, referral pattern, documentation process, or utilization trend is driving it. Internal leading indicators should therefore sit alongside official CMS measures.

A Practical Example

Performance models become manageable only when practices translate technical specifications into everyday operations. A specialty group may discover, for example, that avoidable imaging duplication, poor handoffs, or uncoordinated acute-care utilization is increasing episode cost. The official score identifies the outcome; internal operational metrics help explain why it happened and what can be changed.

Common Failure Pattern

The most common pattern is late discovery. A requirement is missing, inconsistent, outdated, or assigned to the wrong owner, but the case continues to move. By the time the defect is found, the practice may already have scheduled the patient, used physician time, committed facility capacity, submitted a claim, or received payment. The cost of correction is then much higher than it would have been at the point of origin.

A stronger model uses readiness gates. The case advances only when the evidence required for that stage is present and internally consistent. When a material element changes, such as payer, provider, site, service, code, level, laterality, device, clinical plan, or technology configuration, the workflow explicitly reopens the affected controls rather than assuming the prior work remains valid.

What Practice Leaders Should Measure

  • Participant roster accuracy
  • Attributed episode volume
  • Quality performance status
  • Cost and utilization trends
  • Data completeness
  • Projected financial exposure under current methodology

Metrics should be segmented where useful by payer, provider, location, procedure family, site of service, and root cause. Counting volume alone is not enough. Leadership needs to understand which defects create the most patient disruption, staff rework, physician interruption, compliance exposure, or financial loss.

GoHealthcare Perspective

The practice should translate CMS technical specifications into operational controls that physicians and managers can use during the performance year.

What Practice Leaders Should Do Now

  1. Confirm participant status using current CMS data.
  2. Review the current ASM participant roadmap and technical materials.
  3. Assign an accountable program owner.
  4. Build a performance dashboard with leading indicators.
  5. Review cost and utilization outliers.
  6. Model future payment implications.

Leadership Questions to Ask

  • Who owns this workflow from intake through final closure?
  • What information must be present before the case can move to the next step?
  • Where does the organization discover missing information too late?
  • Which payer, service, site, provider, or vendor generates the most rework?
  • What metric tells leadership whether the corrective action actually worked?

Frequently Asked Questions

Is the CMS Ambulatory Specialty Model voluntary?

CMS describes ASM as mandatory for selected participants who meet the model criteria.

Which specialists can be affected?

CMS identifies defined specialist types within the model. Practices should verify the current CMS participant criteria and participant data rather than assume inclusion.

Why should a practice act before payment adjustments occur?

Because performance is measured before the corresponding payment consequences. Operational improvement must occur during the active performance period.

Who should own ASM?

A cross-functional team may contribute, but one accountable executive or program owner should coordinate operations, data, performance, and financial modeling.

Related GoHealthcare Resources

Prior Authorization Resource Center MSK Specialty Procedure Library Revenue Cycle Management Resource Center Specialty Guides Case Study Library Revenue Integrity for MSK Specialty Care

References

Use current primary sources before operational reliance. Coverage, coding, payment, utilization-management criteria, enforcement priorities, contracts, technology requirements, and regulations can change.

  1. CMS Ambulatory Specialty Model

Need Help Strengthening the Workflow?

GoHealthcare Practice Solutions supports pain management, orthopedic surgery, spine, neurosurgery, PM&R, ASC, and broader MSK organizations across patient access, prior authorization, clinical readiness, documentation, coding, revenue cycle, payer strategy, compliance, performance intelligence, and responsible technology.

Request Help Explore Specialty Guides
This article is for educational and healthcare-operations purposes. It is not legal, clinical, coding, reimbursement, cybersecurity, or payer-specific advice. Coverage, authorization, medical necessity, coding, payment, contract, privacy, security, enforcement, and regulatory requirements vary by payer, plan, jurisdiction, provider, facility, procedure, patient, technology, and service circumstances. Verify current CMS, Medicare Administrative Contractor, payer, delegated utilization-management, HHS OIG, HHS OCR, DOJ, CISA/DHS, contract, code-set, and patient-specific requirements before use.
0 Comments

Understanding CMS ASM Ambulatory Specialty Model in 2027

9/26/2026

0 Comments

 
CMS Ambulatory Specialty Model

ASM moves selected specialty practices toward measurable accountability for the total performance of defined episodes. Pain practices should understand participation status, attribution, data, workflows, and performance categories before the payment consequences arrive.

Direct answer: The CMS Ambulatory Specialty Model is a mandatory Innovation Center model that uses defined performance periods and includes selected specialists treating low back pain or heart failure in selected geographic areas. For pain practices in the low-back-pain cohort, the operational issue is not only future payment adjustment. It is the need to manage quality, cost, care coordination, interoperability, and episode performance during the performance year.

Waiting until the payment year is too late because the performance that drives payment has already occurred. The practice needs leading indicators that help explain cost, utilization, quality, and coordination before the performance period closes.

For an MSK organization, the practical question is not only what the rule, payer, technology, or compliance principle says. The practice also needs to know how that requirement changes intake, clinical readiness, scheduling, authorization, documentation, coding, claim submission, payment, escalation, and executive oversight. A reliable workflow makes those dependencies visible before the patient or claim reaches the next step.

Why This Matters in MSK Specialty Operations

  • ASM is a mandatory CMS Innovation Center model for selected specialists in selected geographic areas.
  • The model includes a low-back-pain cohort relevant to pain management, interventional pain, orthopedics, neurosurgery, anesthesiology, and PM&R.
  • Performance is measured before the corresponding payment adjustment year.
  • Practices need operational ownership of quality, cost, care coordination, interoperability, and performance data.

Orthopedic, spine, pain management, neurosurgery, PM&R, and ASC operations are highly interdependent. A defect that begins in an office note can later appear as an authorization delay, a cancellation, a coding question, a denial, an underpayment, or a compliance finding. Leadership should therefore evaluate the entire episode rather than assigning every downstream problem to the department where it was finally discovered.

What the Workflow Should Verify

Control What to Verify Issue It Helps Prevent
Participation Confirm TIN/NPI participation and selected geography using current CMS data. Missed mandatory participation
Episode attribution Understand the CMS episode methodology and reconcile it with internal case lists. Wrong denominator
Performance data Assign owners for each performance category and data source. Unmanaged score
Care coordination Define closed-loop handoffs across the low-back-pain episode. Fragmentation
Financial modeling Estimate downstream payment exposure under current CMS methodology. Unplanned revenue impact

How to Operationalize These Controls

Participation

Confirm TIN/NPI participation and selected geography using current CMS data. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Missed mandatory participation becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Episode attribution

Understand the CMS episode methodology and reconcile it with internal case lists. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Wrong denominator becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Performance data

Assign owners for each performance category and data source. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Unmanaged score becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Care coordination

Define closed-loop handoffs across the low-back-pain episode. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Fragmentation becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Financial modeling

Estimate downstream payment exposure under current CMS methodology. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Unplanned revenue impact becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

What Pain Practices Should Build in

  • A participant registry and responsible executive owner.
  • A dashboard connecting CMS performance categories to operational measures.
  • Care coordination workflows for low-back-pain episodes.
  • Processes to capture and validate data before reporting deadlines.
  • A financial model that translates performance scenarios into future Medicare revenue exposure.

Waiting until the payment year is too late because the performance that drives payment has already occurred. The practice needs leading indicators that help explain cost, utilization, quality, and coordination before the performance period closes.

A Practical Example

Performance models become manageable only when practices translate technical specifications into everyday operations. A specialty group may discover, for example, that avoidable imaging duplication, poor handoffs, or uncoordinated acute-care utilization is increasing episode cost. The official score identifies the outcome; internal operational metrics help explain why it happened and what can be changed.

Common Failure Pattern

The most common pattern is late discovery. A requirement is missing, inconsistent, outdated, or assigned to the wrong owner, but the case continues to move. By the time the defect is found, the practice may already have scheduled the patient, used physician time, committed facility capacity, submitted a claim, or received payment. The cost of correction is then much higher than it would have been at the point of origin.

A stronger model uses readiness gates. The case advances only when the evidence required for that stage is present and internally consistent. When a material element changes, such as payer, provider, site, service, code, level, laterality, device, clinical plan, or technology configuration, the workflow explicitly reopens the affected controls rather than assuming the prior work remains valid.

What Practice Leaders Should Measure

  • Participant roster accuracy
  • Attributed episode volume
  • Quality performance status
  • Cost and utilization trends
  • Data completeness
  • Projected financial exposure under current methodology

Metrics should be segmented where useful by payer, provider, location, procedure family, site of service, and root cause. Counting volume alone is not enough. Leadership needs to understand which defects create the most patient disruption, staff rework, physician interruption, compliance exposure, or financial loss.

GoHealthcare Perspective

ASM should be managed as an operating model, not a reporting project. The practice needs to connect clinical pathways, access, utilization, care coordination, data, and revenue.

What Practice Leaders Should Do Now

  1. Confirm participant status using current CMS data.
  2. Review the current ASM participant roadmap and technical materials.
  3. Assign an accountable program owner.
  4. Build a performance dashboard with leading indicators.
  5. Review cost and utilization outliers.
  6. Model future payment implications.

Leadership Questions to Ask

  • Who owns this workflow from intake through final closure?
  • What information must be present before the case can move to the next step?
  • Where does the organization discover missing information too late?
  • Which payer, service, site, provider, or vendor generates the most rework?
  • What metric tells leadership whether the corrective action actually worked?

Frequently Asked Questions

Is the CMS Ambulatory Specialty Model voluntary?

CMS describes ASM as mandatory for selected participants who meet the model criteria.

Which specialists can be affected?

CMS identifies defined specialist types within the model. Practices should verify the current CMS participant criteria and participant data rather than assume inclusion.

Why should a practice act before payment adjustments occur?

Because performance is measured before the corresponding payment consequences. Operational improvement must occur during the active performance period.

Who should own ASM?

A cross-functional team may contribute, but one accountable executive or program owner should coordinate operations, data, performance, and financial modeling.

Related GoHealthcare Resources

Prior Authorization Resource Center MSK Specialty Procedure Library Revenue Cycle Management Resource Center Specialty Guides Case Study Library Revenue Integrity for MSK Specialty Care

References

Use current primary sources before operational reliance. Coverage, coding, payment, utilization-management criteria, enforcement priorities, contracts, technology requirements, and regulations can change.

  1. CMS Ambulatory Specialty Model
  2. CMS Medicare Physician Fee Schedule Rulemaking

Need Help Strengthening the Workflow?

GoHealthcare Practice Solutions supports pain management, orthopedic surgery, spine, neurosurgery, PM&R, ASC, and broader MSK organizations across patient access, prior authorization, clinical readiness, documentation, coding, revenue cycle, payer strategy, compliance, performance intelligence, and responsible technology.

Request Help Explore Specialty Guides
This article is for educational and healthcare-operations purposes. It is not legal, clinical, coding, reimbursement, cybersecurity, or payer-specific advice. Coverage, authorization, medical necessity, coding, payment, contract, privacy, security, enforcement, and regulatory requirements vary by payer, plan, jurisdiction, provider, facility, procedure, patient, technology, and service circumstances. Verify current CMS, Medicare Administrative Contractor, payer, delegated utilization-management, HHS OIG, HHS OCR, DOJ, CISA/DHS, contract, code-set, and patient-specific requirements before use.
0 Comments

Who Can Help a Pain Management Practice With Prior Authorization? | GoHealthcare

9/25/2026

0 Comments

 
Commercial Intent - Prior Authorization

Prior authorization is not a generic administrative task in interventional pain. The partner must understand the clinical sequence, procedure details, payer criteria, and downstream revenue impact.

Direct answer: A pain management practice can use an internal team, a general authorization vendor, a specialty-focused partner, or a hybrid model. The right choice depends on procedure complexity, payer mix, volume, staffing, clinical documentation quality, escalation needs, technology, and the level of accountability the practice expects. For interventional pain, specialty knowledge and clinical review capability are especially important.

The lowest-cost model can become expensive when the practice absorbs physician interruptions, cancellations, rework, and denied claims. Vendor selection should therefore evaluate total operating value rather than only transaction price.

For an MSK organization, the practical question is not only what the rule, payer, technology, or compliance principle says. The practice also needs to know how that requirement changes intake, clinical readiness, scheduling, authorization, documentation, coding, claim submission, payment, escalation, and executive oversight. A reliable workflow makes those dependencies visible before the patient or claim reaches the next step.

Why This Matters in MSK Specialty Operations

  • Specialty expertise matters because MSK workflows combine clinical, payer, coding, and financial complexity.
  • A low-cost transaction model can become expensive when it creates rework, denials, cancellations, or physician interruptions.
  • Transparent metrics are necessary to distinguish activity from results.
  • Outsourcing work does not eliminate the practice's responsibility for governance, privacy, security, and quality.

Orthopedic, spine, pain management, neurosurgery, PM&R, and ASC operations are highly interdependent. A defect that begins in an office note can later appear as an authorization delay, a cancellation, a coding question, a denial, an underpayment, or a compliance finding. Leadership should therefore evaluate the entire episode rather than assigning every downstream problem to the department where it was finally discovered.

What the Workflow Should Verify

Control What to Verify Issue It Helps Prevent
Specialty expertise Does the partner understand the procedures, terminology, and payer requirements relevant to the specialty? Generic processing
Clinical capability Can qualified staff identify genuine documentation gaps without inventing clinical content? Weak submissions
Payer operations Can the team manage portals, delegated UM vendors, RFIs, denials, and escalations? Avoidable delay
Metrics Are turnaround, accuracy, denial, rework, and financial outcomes transparent? No accountability
Governance Are privacy, security, access, training, and quality controls defined? Operational risk

How to Operationalize These Controls

Specialty expertise

Does the partner understand the procedures, terminology, and payer requirements relevant to the specialty? This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Generic processing becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Clinical capability

Can qualified staff identify genuine documentation gaps without inventing clinical content? This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Weak submissions becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Payer operations

Can the team manage portals, delegated UM vendors, RFIs, denials, and escalations? This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Avoidable delay becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Metrics

Are turnaround, accuracy, denial, rework, and financial outcomes transparent? This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: No accountability becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Governance

Are privacy, security, access, training, and quality controls defined? This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Operational risk becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Questions to Ask a Prior Authorization Partner

  • Who actually performs the work, and what specialty or clinical training do they have?
  • How are payer-policy changes maintained and validated?
  • How are missing clinical elements escalated back to the practice?
  • What happens after an RFI, peer-to-peer request, or denial?
  • How does the partner measure accuracy, rework, and preventable denials?
  • Can the practice see case status, ownership, aging, and outcomes?

The lowest-cost model can become expensive when the practice absorbs physician interruptions, cancellations, rework, and denied claims. Vendor selection should therefore evaluate total operating value rather than only transaction price.

A Practical Example

Vendor selection should be based on the work the practice needs solved, not on a generic service description. A partner can promise fast turnaround while still generating repeated RFIs, physician interruptions, approval mismatches, or underpayment leakage. The better evaluation asks whether the vendor understands the specialty, can show transparent performance data, and has clear accountability when the case becomes complex.

Common Failure Pattern

The most common pattern is late discovery. A requirement is missing, inconsistent, outdated, or assigned to the wrong owner, but the case continues to move. By the time the defect is found, the practice may already have scheduled the patient, used physician time, committed facility capacity, submitted a claim, or received payment. The cost of correction is then much higher than it would have been at the point of origin.

A stronger model uses readiness gates. The case advances only when the evidence required for that stage is present and internally consistent. When a material element changes, such as payer, provider, site, service, code, level, laterality, device, clinical plan, or technology configuration, the workflow explicitly reopens the affected controls rather than assuming the prior work remains valid.

What Practice Leaders Should Measure

  • Turnaround time
  • Accuracy or first-pass quality
  • RFI and denial rate
  • Rework and staff touches
  • Physician escalation burden
  • Financial impact or recovered revenue

Metrics should be segmented where useful by payer, provider, location, procedure family, site of service, and root cause. Counting volume alone is not enough. Leadership needs to understand which defects create the most patient disruption, staff rework, physician interruption, compliance exposure, or financial loss.

GoHealthcare Perspective

GoHealthcare Practice Solutions approaches prior authorization as specialty operations rather than transaction processing. The strategic question is whether the partner can manage the clinical and payer complexity of the episode while preserving accountability, traceability, and revenue integrity.

What Practice Leaders Should Do Now

  1. Document the problems the practice expects a partner to solve.
  2. Compare partners on specialty depth, not price alone.
  3. Require transparent performance reporting.
  4. Test complex real-world cases before broad rollout.
  5. Define escalation and governance rules.
  6. Review results at an executive cadence.

Leadership Questions to Ask

  • Who owns this workflow from intake through final closure?
  • What information must be present before the case can move to the next step?
  • Where does the organization discover missing information too late?
  • Which payer, service, site, provider, or vendor generates the most rework?
  • What metric tells leadership whether the corrective action actually worked?

Frequently Asked Questions

Should a specialty practice outsource everything?

Not necessarily. A hybrid model be appropriate when the practice wants to retain selected clinical, financial, or escalation functions.

Is the lowest-cost vendor the best choice?

No. Rework, denials, cancellations, and internal labor can make a low-cost model expensive.

Why does specialty knowledge matter?

Because procedures, documentation, authorization, coding, and payer rules vary significantly across specialties.

What should a practice expect from a partner?

Reliable case ownership, accurate work, timely escalation, transparent metrics, and evidence that recurring defects are being reduced.

Related GoHealthcare Resources

Prior Authorization Resource Center MSK Specialty Procedure Library Revenue Cycle Management Resource Center Specialty Guides Case Study Library Revenue Integrity for MSK Specialty Care

References

Use current primary sources before operational reliance. Coverage, coding, payment, utilization-management criteria, enforcement priorities, contracts, technology requirements, and regulations can change.

  1. HHS OIG General Compliance Program Guidance
  2. CMS Interoperability and Prior Authorization Final Rule

Need Help Strengthening the Workflow?

GoHealthcare Practice Solutions supports pain management, orthopedic surgery, spine, neurosurgery, PM&R, ASC, and broader MSK organizations across patient access, prior authorization, clinical readiness, documentation, coding, revenue cycle, payer strategy, compliance, performance intelligence, and responsible technology.

Request Help Explore Specialty Guides
This article is for educational and healthcare-operations purposes. It is not legal, clinical, coding, reimbursement, cybersecurity, or payer-specific advice. Coverage, authorization, medical necessity, coding, payment, contract, privacy, security, enforcement, and regulatory requirements vary by payer, plan, jurisdiction, provider, facility, procedure, patient, technology, and service circumstances. Verify current CMS, Medicare Administrative Contractor, payer, delegated utilization-management, HHS OIG, HHS OCR, DOJ, CISA/DHS, contract, code-set, and patient-specific requirements before use.
0 Comments

What Is Revenue Integrity for an Orthopedic, Spine, or Pain Management Practice? | GoHealthcare

9/24/2026

0 Comments

 
Revenue Integrity

For MSK practices, revenue leakage often begins before a claim is created. Documentation, authorization, scheduling, site of service, coding, contract terms, and payer rules all shape the eventual payment.

Direct answer: Revenue integrity is the discipline of ensuring that the services a practice delivers are accurately documented, correctly coded, properly authorized when required, billed according to governing rules and contracts, and paid at the amount the organization should reasonably expect. It connects clinical operations to the revenue cycle rather than treating billing as a downstream function.

A practice can have strong collections and still lose revenue through underpayments, missed charges, authorization mismatches, or coding defects. Revenue integrity gives leadership a framework for measuring those gaps and assigning ownership.

For an MSK organization, the practical question is not only what the rule, payer, technology, or compliance principle says. The practice also needs to know how that requirement changes intake, clinical readiness, scheduling, authorization, documentation, coding, claim submission, payment, escalation, and executive oversight. A reliable workflow makes those dependencies visible before the patient or claim reaches the next step.

Why This Matters in MSK Specialty Operations

  • Revenue leakage often begins before a claim is created.
  • A clean claim can still be underpaid.
  • Authorization, documentation, coding, payer policy, and site of service all shape expected reimbursement.
  • Root-cause analytics are more valuable than counting completed billing tasks.

Orthopedic, spine, pain management, neurosurgery, PM&R, and ASC operations are highly interdependent. A defect that begins in an office note can later appear as an authorization delay, a cancellation, a coding question, a denial, an underpayment, or a compliance finding. Leadership should therefore evaluate the entire episode rather than assigning every downstream problem to the department where it was finally discovered.

What the Workflow Should Verify

Control What to Verify Issue It Helps Prevent
Clinical documentation Does the record support the service that was ordered, performed, and billed? Unsupported revenue
Authorization Does the approval match the final service, provider, site, date, units, levels, and laterality? Authorization-related denial
Coding Are codes, modifiers, diagnosis linkage, and units accurate? Claim defect
Expected payment What should the payer reimburse under the contract or fee schedule? Invisible underpayment
Payment reconciliation Did the remittance match expected reimbursement? Revenue leakage
Root-cause closure Was the upstream defect corrected and retested? Recurring variance

How to Operationalize These Controls

Clinical documentation

Does the record support the service that was ordered, performed, and billed? This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Unsupported revenue becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Authorization

Does the approval match the final service, provider, site, date, units, levels, and laterality? This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Authorization-related denial becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Coding

Are codes, modifiers, diagnosis linkage, and units accurate? This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Claim defect becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Expected payment

What should the payer reimburse under the contract or fee schedule? This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Invisible underpayment becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Payment reconciliation

Did the remittance match expected reimbursement? This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Revenue leakage becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Root-cause closure

Was the upstream defect corrected and retested? This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Recurring variance becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Revenue Integrity Versus Traditional Billing

  • Billing asks whether the claim was submitted and paid.
  • Revenue integrity asks whether the claim should have been created that way in the first place.
  • Revenue integrity also asks whether the payment was accurate under the contract or fee schedule.
  • It connects clinical, authorization, coding, payer, finance, and operational teams around one episode.
  • It treats underpayments and recurring workflow defects as management issues, not just billing exceptions.

A practice can have strong collections and still lose revenue through underpayments, missed charges, authorization mismatches, or coding defects. Revenue integrity gives leadership a framework for measuring those gaps and assigning ownership.

A Practical Example

Revenue leakage is often invisible because a claim can be paid and still be wrong. A payer may issue a remittance that appears clean while the allowed amount is lower than the contract or fee schedule expectation. Without expected-payment logic, the account closes as paid and the underpayment disappears into normal collections. Revenue integrity requires the organization to know what should have been paid and to reconcile the variance.

Common Failure Pattern

The most common pattern is late discovery. A requirement is missing, inconsistent, outdated, or assigned to the wrong owner, but the case continues to move. By the time the defect is found, the practice may already have scheduled the patient, used physician time, committed facility capacity, submitted a claim, or received payment. The cost of correction is then much higher than it would have been at the point of origin.

A stronger model uses readiness gates. The case advances only when the evidence required for that stage is present and internally consistent. When a material element changes, such as payer, provider, site, service, code, level, laterality, device, clinical plan, or technology configuration, the workflow explicitly reopens the affected controls rather than assuming the prior work remains valid.

What Practice Leaders Should Measure

  • Clean-claim rate
  • Preventable denial rate
  • Days in accounts receivable
  • Expected-versus-actual reimbursement
  • Underpayment dollars
  • Root-cause recurrence

Metrics should be segmented where useful by payer, provider, location, procedure family, site of service, and root cause. Counting volume alone is not enough. Leadership needs to understand which defects create the most patient disruption, staff rework, physician interruption, compliance exposure, or financial loss.

GoHealthcare Perspective

In a mature MSK organization, revenue integrity is a management system. Leaders should be able to trace a variance back to its origin, quantify its effect, assign an owner, and determine whether the corrective action reduced recurrence.

What Practice Leaders Should Do Now

  1. Define expected reimbursement logic by payer and service.
  2. Create authorization-to-claim reconciliation for high-risk procedures.
  3. Track underpayments separately from denials.
  4. Measure defects by upstream root cause.
  5. Report financial impact by payer, provider, site, and procedure.
  6. Retest corrected workflows.

Leadership Questions to Ask

  • Who owns this workflow from intake through final closure?
  • What information must be present before the case can move to the next step?
  • Where does the organization discover missing information too late?
  • Which payer, service, site, provider, or vendor generates the most rework?
  • What metric tells leadership whether the corrective action actually worked?

Frequently Asked Questions

Is revenue integrity the same as RCM?

Revenue integrity is part of the broader revenue cycle but focuses on the accuracy and defensibility of revenue from clinical documentation through payment.

Is denial management enough?

No. Underpayments, missed charges, authorization mismatches, and coding defects can cause leakage without a traditional denial.

Who owns revenue integrity?

It is cross-functional, but one accountable leader should coordinate the work.

What should leadership measure?

Expected versus actual reimbursement, preventable denials, underpayments, authorization defects, coding variance, and recurrence by root cause.

Related GoHealthcare Resources

Prior Authorization Resource Center MSK Specialty Procedure Library Revenue Cycle Management Resource Center Specialty Guides Case Study Library Revenue Integrity for MSK Specialty Care

References

Use current primary sources before operational reliance. Coverage, coding, payment, utilization-management criteria, enforcement priorities, contracts, technology requirements, and regulations can change.

  1. HHS OIG General Compliance Program Guidance
  2. CMS Medicare NCCI FAQ Library
  3. CMS Medicare Coverage Database

Need Help Strengthening the Workflow?

GoHealthcare Practice Solutions supports pain management, orthopedic surgery, spine, neurosurgery, PM&R, ASC, and broader MSK organizations across patient access, prior authorization, clinical readiness, documentation, coding, revenue cycle, payer strategy, compliance, performance intelligence, and responsible technology.

Request Help Explore Specialty Guides
This article is for educational and healthcare-operations purposes. It is not legal, clinical, coding, reimbursement, cybersecurity, or payer-specific advice. Coverage, authorization, medical necessity, coding, payment, contract, privacy, security, enforcement, and regulatory requirements vary by payer, plan, jurisdiction, provider, facility, procedure, patient, technology, and service circumstances. Verify current CMS, Medicare Administrative Contractor, payer, delegated utilization-management, HHS OIG, HHS OCR, DOJ, CISA/DHS, contract, code-set, and patient-specific requirements before use.
0 Comments

What Should Pain Management Practices Know About Medicare Medical Necessity Audits? | GoHealthcare

9/23/2026

0 Comments

 
Pain Management Compliance

Audit readiness is not the same as producing a longer note after a request arrives. The strongest defense is documentation and workflow that were accurate at the time care was delivered.

Direct answer: A Medicare medical necessity audit tests whether the record supports that the billed service was reasonable and necessary under the requirements that applied to the patient, service, jurisdiction, and date of service. Pain practices should be able to reconstruct the full episode: clinical indication, examination, diagnostics, prior treatment, procedure details, repeat-service criteria, coding, and payment.

Practices should not create unsupported facts after the service date. Lawful corrections and amendments should follow policy, but audit readiness should come from accurate contemporaneous documentation and reliable workflow controls.

For an MSK organization, the practical question is not only what the rule, payer, technology, or compliance principle says. The practice also needs to know how that requirement changes intake, clinical readiness, scheduling, authorization, documentation, coding, claim submission, payment, escalation, and executive oversight. A reliable workflow makes those dependencies visible before the patient or claim reaches the next step.

Why This Matters in MSK Specialty Operations

  • Medical necessity, documentation, coding, billing, overpayments, referral arrangements, privacy, security, and vendor activity can all create compliance exposure.
  • Government audit and enforcement activity can reveal risk patterns that practices should test internally.
  • Paid claims can still be reviewed after payment.
  • Compliance programs are strongest when they change workflow and produce evidence that controls actually operate.

Orthopedic, spine, pain management, neurosurgery, PM&R, and ASC operations are highly interdependent. A defect that begins in an office note can later appear as an authorization delay, a cancellation, a coding question, a denial, an underpayment, or a compliance finding. Leadership should therefore evaluate the entire episode rather than assigning every downstream problem to the department where it was finally discovered.

What the Workflow Should Verify

Control What to Verify Issue It Helps Prevent
Risk assessment Identify material clinical, billing, privacy, security, and business-arrangement risks. Unprioritized risk
Audit plan Test high-risk workflows using actual cases and transactions. Unknown defects
Training Target education to observed issues and role-specific responsibilities. Generic compliance
Reporting and investigation Maintain channels and defined response processes for credible concerns. Unresolved issues
Corrective action Assign owners, due dates, remediation, and retesting. Recurring risk

How to Operationalize These Controls

Risk assessment

Identify material clinical, billing, privacy, security, and business-arrangement risks. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Unprioritized risk becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Audit plan

Test high-risk workflows using actual cases and transactions. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Unknown defects becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Training

Target education to observed issues and role-specific responsibilities. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Generic compliance becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Reporting and investigation

Maintain channels and defined response processes for credible concerns. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Unresolved issues becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Corrective action

Assign owners, due dates, remediation, and retesting. This control should be explicit enough that the next team member can verify the requirement without reconstructing the case from memory, informal messages, or disconnected systems.

Why it matters: Recurring risk becomes more likely when this step is vague, delayed, or owned by no one. The practice should define what evidence closes the step, who is accountable, and what event requires the case to be reopened or revalidated.

Build an Audit-Ready Episode, Not an Audit Packet

  • Identify the policy and billing guidance that governed the date of service.
  • Preserve original clinical and procedural documentation in a retrievable format.
  • Verify repeat-treatment criteria and response documentation where applicable.
  • Trace coding, modifiers, units, levels, laterality, and diagnosis linkage back to source documentation.
  • Use internal audits to identify recurring patterns before they become external findings.

Practices should not create unsupported facts after the service date. Lawful corrections and amendments should follow policy, but audit readiness should come from accurate contemporaneous documentation and reliable workflow controls.

A Practical Example

A useful compliance review follows real cases and transactions. If an audit identifies a documentation or billing defect in one sample, leadership should ask whether the same workflow, template, code logic, compensation structure, or vendor process affects a larger population. The purpose of auditing is not simply to find exceptions; it is to determine whether the control environment is working.

Common Failure Pattern

The most common pattern is late discovery. A requirement is missing, inconsistent, outdated, or assigned to the wrong owner, but the case continues to move. By the time the defect is found, the practice may already have scheduled the patient, used physician time, committed facility capacity, submitted a claim, or received payment. The cost of correction is then much higher than it would have been at the point of origin.

A stronger model uses readiness gates. The case advances only when the evidence required for that stage is present and internally consistent. When a material element changes, such as payer, provider, site, service, code, level, laterality, device, clinical plan, or technology configuration, the workflow explicitly reopens the affected controls rather than assuming the prior work remains valid.

What Practice Leaders Should Measure

  • Defect rate in targeted audits
  • Repeat findings by provider or workflow
  • Overpayments or recoupments identified
  • Time to complete corrective action
  • Training completion tied to specific findings
  • Retest results after remediation

Metrics should be segmented where useful by payer, provider, location, procedure family, site of service, and root cause. Counting volume alone is not enough. Leadership needs to understand which defects create the most patient disruption, staff rework, physician interruption, compliance exposure, or financial loss.

GoHealthcare Perspective

Audit readiness should be designed into operations. The organization should know which services deserve targeted monitoring, what evidence must exist before treatment, and who owns corrective action when a pattern appears.

What Practice Leaders Should Do Now

  1. Review current OIG, DOJ, CMS, OCR, and payer activity relevant to the practice.
  2. Build a risk-based audit plan.
  3. Quantify findings by scope, dollars, patient impact, and recurrence.
  4. Assign corrective actions to accountable owners.
  5. Escalate material legal questions to qualified counsel.
  6. Retest controls after remediation.

Leadership Questions to Ask

  • Who owns this workflow from intake through final closure?
  • What information must be present before the case can move to the next step?
  • Where does the organization discover missing information too late?
  • Which payer, service, site, provider, or vendor generates the most rework?
  • What metric tells leadership whether the corrective action actually worked?

Frequently Asked Questions

Does an audit finding mean fraud occurred?

No. Error, noncompliance, overpayment, and fraud are not interchangeable. The facts and applicable legal standards matter.

Is prior authorization proof of medical necessity?

No. Authorization does not replace documentation, coverage, coding, and post-payment compliance requirements.

Should every external enforcement story trigger an internal audit?

No. Practices should assess relevance, exposure, and control strength first.

What makes a compliance program effective?

Clear ownership, risk assessment, training, auditing, reporting, investigation, corrective action, and evidence that controls work.

Related GoHealthcare Resources

Prior Authorization Resource Center MSK Specialty Procedure Library Revenue Cycle Management Resource Center Specialty Guides Case Study Library Revenue Integrity for MSK Specialty Care

References

Use current primary sources before operational reliance. Coverage, coding, payment, utilization-management criteria, enforcement priorities, contracts, technology requirements, and regulations can change.

  1. CMS Medicare Coverage Database
  2. HHS OIG General Compliance Program Guidance
  3. HHS OIG Sacroiliac Joint Injection Audit
  4. HHS OIG Work Plan

Need Help Strengthening the Workflow?

GoHealthcare Practice Solutions supports pain management, orthopedic surgery, spine, neurosurgery, PM&R, ASC, and broader MSK organizations across patient access, prior authorization, clinical readiness, documentation, coding, revenue cycle, payer strategy, compliance, performance intelligence, and responsible technology.

Request Help Explore Specialty Guides
This article is for educational and healthcare-operations purposes. It is not legal, clinical, coding, reimbursement, cybersecurity, or payer-specific advice. Coverage, authorization, medical necessity, coding, payment, contract, privacy, security, enforcement, and regulatory requirements vary by payer, plan, jurisdiction, provider, facility, procedure, patient, technology, and service circumstances. Verify current CMS, Medicare Administrative Contractor, payer, delegated utilization-management, HHS OIG, HHS OCR, DOJ, CISA/DHS, contract, code-set, and patient-specific requirements before use.
0 Comments
<<Previous
    Pinky Maniri Pescasio CEO and Founder of GoHealthcare Practice SolutionsPinky Maniri is the Founder & CEO of GoHealthcare Practice Solutions and a sought-after national healthcare speaker. She speaks at select medical conferences and industry events, including Becker’s Healthcare and PAINWeek.

    View my Profile on Linkedin
    View my profile on LinkedIn

    search here


DISCLAIMER        PRIVACY POLICY        TERMS OF USE       CONTACT US  

GoHealthcareAI Solutions Investor Relations   |  GoHealthcareAxis™ Investor Relations

GOHEALTHCARE KNOWLEDGE CENTER

Search GoHealthcare Practice Solutions

Search our procedure library, specialty guides, prior authorization resources, revenue cycle guidance, case studies, AI governance content, compliance resources, and healthcare operations insights.

Popular:
Procedure Library Specialty Guides Prior Authorization Revenue Cycle Case Studies Blog

Search results open in a new browser tab.


© COPYRIGHT 2026 GoHealthcare Practice Solutions LLC. ALL RIGHTS RESERVED.
Photos from shixart1985 (CC BY 2.0), www.ilmicrofono.it, shixart1985
  • Who we are
  • Leadership
  • Advisory Board
  • What We Do
  • RCM
  • Case Studies
  • Knowledge Center
    • 8 Excellence Frameworks™
    • CMS Ambulatory Specialty Model (ASM)
    • Procedure Library
  • Specialty Guides
    • MSK Radiology & Diagnostic Imaging
    • Hand & Upper Extremity Guide
    • Spine Specialty Hub
    • Occupational Medicine / Workers’ Compensation MSK
    • Pain Management Specialty Hub
    • Neurosurgery Specialty Hub
    • Orthopedic Surgery Specialty Guide
    • Physical Medicine & Rehabilitation (PM&R) Specialty Hub
    • Sports Medicine
    • Ambulatory Surgery Center Specialty Hub
  • GoHealthcare AI Governance Center
  • CLIENT PORTAL
  • READ OUR BLOG