Use 4 team-based care scenarios to refresh your billing knowledge

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 explains how a practice can review Medicare incident-to and split/shared billing concepts through four team-based care scenarios. It is aimed at physicians, non-physician practitioners, coders, and compliance staff who need to understand general billing workflow, documentation, and compliance considerations for collaborative encounters.

Why This Topic Matters

Team-based billing can affect how services are reported and reimbursed, and mistakes may create compliance risk. The article helps readers recognize the kinds of encounters that warrant closer review during staff training and billing audits.

Article Sections

  1. Introduction

    Introduces the Medicare billing topics covered in the article and explains why practices review team-based encounter workflows. It also frames the compliance risk associated with collaborative care billing.

  2. Use 4 scenarios during your next training session

    Describes the purpose of using scenario-based training for incident-to and split/shared billing education. It summarizes the instructional approach and identifies the kinds of encounters discussed later in the article.

  3. Scenario 1

    Presents a team-based office encounter involving a planned follow-up procedure and discusses the billing approach in general terms. The section focuses on physician and non-physician practitioner participation within a practice setting.

  4. Scenario 2

    Covers a follow-up counseling visit performed by a nurse in a physician practice and the related Medicare billing considerations. The section highlights how staffing role affects the type of service being reported.

  5. Scenario 3

    Reviews an inpatient collaborative visit involving a physician and a physician assistant. The section addresses shared work in a hospital setting and references CMS guidance relevant to split/shared services.

  6. Scenario 4

    Describes a follow-up office encounter with a clinical nurse specialist after an earlier physician visit. The section focuses on how collaborative outpatient care is reviewed for Medicare reporting.

  7. Resources

    Lists related CMS and enforcement references provided with the article for further reading. This section serves as source material and background documentation.

What You Will Learn

  • How Medicare incident-to and split/shared concepts are presented in team-based training scenarios
  • How different clinical roles can affect billing workflow in a practice
  • Why collaborative encounters require attention to compliance and documentation
  • Which CMS references are cited as supporting material for the topic

Who Should Read This

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

Codes 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?