Skip Navigation LinksHome | Editors' Blog
CMS scaled back many of the proposed changes to chronic and transitional care management services (CMS), but a few made it to the final rule. Next year you’ll have an add-on code for chronic care management code provided by clinical staff and two codes for management of a single high-risk condition.
 
The vast reshaping of E/M documentation standards and payment changes took a significant step closer to reality as CMS put a stamp of approval on its previous proposals to overhaul how medical practices report office and outpatient E/M services 2021.
 
Next year many providers will see a modest boost to the conversion factor that, along with relative value units (RVUs), dictates pay rates across all services in the Medicare physician fee schedule. The conversion factor will rise to $36.0896 in 2020, which CMS previously proposed, from $36.0391 in 2019, according to the final fee schedule. However, the anesthesia conversion factor will decrease to $22.2016 in 2020 from $22.2730 this year. That’s a drop from the proposed anesthesia conversion factor of $22.2774.
 
Recently Part B News gave you a heads-up on materials that you should store in case CMS audits your MIPS attestations. We got some added detail on the situation in a conversation with Lori Foley, managing principal with the PYA consultancy in Atlanta.
 
The 2020 physician fee schedule is under regulatory review, but that doesn't mean you can't gain a glimpse of the public comments about the pending E/M changes that CMS will be taking into consideration.
 
 
As part of an effort entitled the Regulatory Sprint to Coordinated Care, CMS and OIG released advance copies of proposed regulatory changes on Oct. 9. The proposed rules would modify regulations that have presented obstacles to physicians, hospitals and other providers as they transition away from traditional fee-for-service (FFS) payment models toward value-based arrangements.
 

Login

User Name:
Password:
Welcome to the new Part B News Online. If you are a returning user having trouble logging in, please click here.
Blog Archive
Back to top