• If this is your first visit, be sure to check out the FAQ & read the forum rules. To view all forums, post or create a new thread, you must be an AAPC Member. If you are a member and have already registered for member area and forum access, you can log in by clicking here. If you've forgotten the password it can be reset on our sign in section by entering your registered Email Address or Username here. To start viewing messages, select the forum that you want to visit from the selection below..

Wiki Op report coding

Create Wiki
A

Anna Weaver

Guest
Messages
765
Location
Kokomo, IN
Best answers
0
Okay, here's for today. I am looking for the documentation to support the fact that you should not code from the Op report heading (i.e. procedure performed), rather use it as a confirmation of what is in the body of the report. I cannot find this, but know I have read it somewhere. Can anyone help?
 
I don't have a source to point you to, but I would not code straight from the OP report heading either. Oftentimes I have found that I need to confirm certain details that affect code assignments that are only found in the actual report. (i.e. approach, accompanying conditions *such as bypass procedures*, etc.) Personally, I think coding directly from the heading is somewhat lazy coding. Although I'm sure it's faster, and you will get the correct answer sometimes (or even a lot of the time), I just think it's a bad policy for professional coders. That's just my two cents... :)
 
OP report coding

Junebug, I agree wholeheartedly, The Dr's however think it's okay because they've already listed the procedure in there once. I too have had procedures listed in the heading that were not exact to what was in the body or not in the body at all. We're trying to find the documentation guidelines for this to show the Doc's so they will know we're not just saying this to make their life miserable.
 
You must log in or register to reply here.
Top