Last month, we discussed CMS’s new G-codes in a cleverly titled post, “Ain’t Nothin’ But a G-Code, Baby.” As the name implies, this new functional limitation reporting mandate is not nearly as daunting as you may think. In fact, if you use WebPT, it’s going to be as easy as pie—cherry pie, or maybe apple. Regardless, I digress. Here, we’ll discuss how with just a few clicks, and some clinical judgment, you can easily implement these new codes into your documentation workflow.
Need a refresher on the basics of functional limitation reporting and a clinical example? Click here to watch our webinar hosted by Heidi Jannenga, PT, MPT, ATC/L and download the slide deck. Or, this post is an in-depth functional limitation reporting article Heidi wrote for Physiospot.
Ready to jump into WebPT?
Although CMS is not requiring you to implement functional limitation reporting until July 1, 2013, we’ll make G-codes available to you within WebPT by mid-spring. This way, you’ll have plenty of time to practice before you risk not receiving reimbursement for your services. Here’s what you can expect:
- From the Subjective tab of your note, you’ll be able to select the appropriate primary functional limitation.
- Within the Inspection section on the Objective tab, you’ll be able to select from a dropdown of applicable G-codes (based on the category you chose).
- From here, you will also be able to select the appropriate modifier after you complete your outcome measurement tool.
- On the next line, you’ll find two dropdowns from which you can select the projected goal status G-code and the modifier.
Please note that based on your note type, the G-Code fields will default to the selection we believe is most appropriate, but you’ll still be able to choose from the entire list. On your progress note, you will also have the option to select a new primary functional limitation should your patient meet his or her original primary functional limitation goal and need continuing care for another.
Have questions? We’ve got answers. Write to us in the comments below or at firstname.lastname@example.org.