Modifiers: This MAC Clarifies Use of Modifiers 54, 55 When Co-Managing Patients

Subscribe or sign in to view the full article.

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

Article Overview

This article reviews Medicare guidance on split global surgical billing when one physician performs the surgery and another provides postoperative management. It is aimed at physicians, surgeons, and billing staff who need to understand transfer-of-care documentation, carrier jurisdiction issues, and related billing scenarios for global surgical services. The discussion focuses on general modifier usage, common exceptions, and examples drawn from surgical and postoperative care workflows.

Why This Topic Matters

Claims for split surgical and postoperative care can be denied or misbilled if transfer of care is not documented and billed correctly. Understanding the MAC’s clarification helps practices coordinate claims across physicians, groups, and payment localities.

Article Sections

  1. Know the Rules

    Introduces the general concept of transfer of care during the global period and discusses the broad billing framework used when surgical and postoperative responsibilities are split.

  2. Avoid Modifier 56

    Addresses Medicare’s treatment of preoperative management and contrasts it with postoperative-only care in the context of global surgical billing.

  3. How payment works

    Summarizes how payment for surgical services is generally divided among the preoperative, surgical, and postoperative portions of a global service.

  4. Example 1

    Presents a sample transfer-of-care scenario involving a surgical case followed by postoperative management by another physician.

  5. Example 2

    Presents another sample scenario showing postoperative care after a surgery performed for an out-of-town patient.

  6. Remember

    Highlights coordination and claim-submission considerations for physicians who share care during the global period.

  7. Caution

    Notes a claim-processing issue that can arise if the surgical portion and postoperative portion are not reported consistently.

  8. Know These Exceptions

    Outlines broad situations in which postoperative visits may not be billed under the split global surgery approach.

  9. Two Carriers Might Be Involved

    Explains the relevance of payment locality and MAC jurisdiction when the surgical and postoperative portions occur in different service areas.

What You Will Learn

  • How Medicare global surgical billing can be divided when care is transferred between physicians
  • What documentation considerations are highlighted for transfer of postoperative care
  • Which broad categories of postoperative visits may follow different billing pathways
  • How payment locality and contractor jurisdiction can affect claim routing
  • What kinds of coordination issues arise when multiple practices share global care

Who Should Read This

  • Physicians
  • Surgeons
  • Billing staff
  • Coders
  • Practice managers
  • Revenue cycle professionals

Codes Discussed

Modifiers Discussed


Subscribe or sign in to view the full article.

Stay informed, get answers to your E/M coding and documentation questions, and find the help you need to bank your deserved pay with your subscription to TCI’s E/M Coding Alert.

  • Current newsletters added each month
  • Fully searchable archives - over 500 articles
  • ALL years/issues back to 2013 organized by year and issue
  • Codes mentioned in articles are linked to Code Information pages
  • Code Information pages link back to related articles

This feature is currently unavailable for online purchase. For more information, please call 801-770-4203 or Contact Us.

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?