Wiki Need Resources!!

Messages
2
Location
Mesa, AZ
Best answers
0
Please if anyone out there has some cheat sheets, tools, resources, or would just be open to helping a fellow coder out, please let me know!
We recently added a neurologist, that will be doing neurosurgery, to the practice. Anything you have would be incredibly helpful! Thank you in advance!!
 
I just retired and have a large library of coding resources and cheat sheets that I posted online. These are a few examples. See post id: 7793304418 on Craigslist.
 

Attachments

  • expressreference1.jpg
    expressreference1.jpg
    748.4 KB · Views: 3
  • expressreference2.jpg
    expressreference2.jpg
    768.6 KB · Views: 3
  • fieldguide.jpg
    fieldguide.jpg
    19.6 KB · Views: 2
  • anatomy.jpg
    anatomy.jpg
    21.9 KB · Views: 2
  • modifiers.jpg
    modifiers.jpg
    13.9 KB · Views: 3
Forgot to add, talking with the provider is going to be a very good way to get an idea of what their practice is like. If they are not brand new and came from another group, you could ask if they have a CPT frequency report to see what their top ten procedures are and start there.
What is the type of surgery they perform, etc.
 
Yeah, I found all of those in a general search and Unfortunately, our surgeon came from a previous office where he didn't have to do much as far as coding or being held to a high standard with his documentation so he is not much help. We have a list of his common CPTs, it's more of disease processes and making sure that when he documents his dx that they are supported but my coder is not familiar with those specific dx so she is spending A LOT of time researching them and when she queries him it is not helpful (he uses terms such as "likely"). So, I'm more looking for someone that actually codes neurology/neurosurgery that would be willing to share their notes etc., if that makes sense. But I appreciate your help!
 
What is his practice focused on? Does your group have a policy and procedure for onboarding new providers? What is the audit plan?
If the provider is not always the best at documentation and you have a coder unfamiliar, that's going to be tough. Notes and cheat sheets really won't help much if his documentation is lacking and poor. :/
It also depends on the setup of the practice. Is he just clicking radio buttons or templates but not actually stating, in words, the diagnoses? It's always difficult to onboard a new provider. Is he the only neuro in the group?
If the coding and billing can't be completed in a timely manner, hold it until the documentation is corrected. When onboarding new providers I found having a 100% review period until they met metrics worked well. They get tired of re-doing things and having it sent back. Also, if the documentation is poor and unclear, it will be difficult to get prior auth. Not to mention all the other issues unrelated to coding/billing, etc.

I spent years coding neuro in a large ortho practice; folks can share notes but it's not going to help with what you are describing unfortunately.
 
Top