Use these practical tips to navigate new split/shared billing rules

Subscribe or sign in to view the full article.

Note:  The following article synopsis was NOT provided by HCPro. It was created by Find-A-Code/innoviHealth.

Article Overview

This article covers Medicare’s new split/shared billing policy and the practical documentation issues it creates for provider-based clinics and other facility settings. It explains the relationship between split/shared and incident-to billing, discusses timing for implementation, and reviews general considerations for physician and non-physician practitioner documentation, telehealth, compliance, and payer variation. It is aimed at coders, billing staff, compliance teams, and clinicians who need to understand the policy change at a high level without relying on the premium article for operational detail.

Why This Topic Matters

The policy affects how facility-based evaluation and management visits are reported and documented, which can influence reimbursement, compliance risk, and audit exposure. Practices that work with physicians and non-physician practitioners need a clear overview of the applicable settings and documentation expectations.

Article Sections

  1. Split/shared policy overview and implementation timing

    Introduces Medicare’s new split/shared policy and the reported implementation timing. Summarizes the confusion it creates in provider-based clinic settings.

  2. When split/shared applies versus incident-to

    Compares the two billing approaches by place of service and outlines the settings where each framework is discussed in the article. Focuses on the broad distinction between office and facility environments.

  3. Substantive portion and documentation considerations

    Reviews the transition-year concepts used to determine the substantive portion of a shared visit. Discusses broad documentation themes for physicians and non-physician practitioners.

  4. Audit risk, specialty impact, and related considerations

    Addresses compliance concerns, documentation updates, and how the policy may affect certain specialties and practice models. Also covers telehealth and payer follow-up at a high level.

  5. Sidebar: Transitional guidance from CMS

    Summarizes a CMS open door forum exchange included as background on transitional policy interpretation. Explains that the sidebar provides additional context for the new shared-visit framework.

What You Will Learn

  • How Medicare’s split/shared policy is positioned relative to incident-to billing
  • Which settings are discussed as potentially subject to split/shared rules
  • What broad documentation and compliance issues practices should consider
  • Why the transition period matters for shared visit reporting
  • What general payer and telehealth considerations are mentioned

Who Should Read This

  • Medical coders
  • Billing staff
  • Compliance officers
  • Physicians
  • Non-physician practitioners
  • Practice administrators

Codes Discussed

Code Ranges Discussed

Modifiers Discussed


Subscribe or sign in to view the full article.

Official DecisionHealth® Newsletter Archives includes:

  • Includes over 25,000 articles from:
    • Coder Pink Sheets
    • Part B News
    • Answer Books newsletters
  • Current newsletters added each quarter
  • Timely news and guidance vital for your practice
  • Fully searchable through Find-A-Code's Comprehensive Search
  • Codes mentioned in articles are linked to the Find-A-Code Code Information pages
  • Code Information pages link back to related articles
  • Save yourself tons of research time, find everything in one place!
Access to this feature is available in the following products:
  • DecisionHealth Coding, Billing and Compliance Library

Related Articles

Articles are listed in order of calculated relevance.

demo
request yours today
subscribe
start today
newsletter
free subscription

Thank you for choosing Find-A-Code, please Sign In to remove ads.

Aimee- AI -powered coding assistant - Try it now for Free Would you like Aimee - AI
to help you with this?