Let’s add to the discussion when NOT to defend your codes too strongly.
It isn’t unusual to be in a first coding job and recognize that those around you, maybe even those in charge, are making errors.
Tread softly.
There is not much you can do at this point. They are in charge. You do things their way unless it’s unethical or illegal. Your time will come.
Those in charge don’t always have the best of skills. They may have inherited that position because they knew someone or just due to longevity. It doesn’t matter. They are in a position of authority. They may also occasionally be right, so you won’t want to assume that they are always wrong. There are also instances where the physicians in charge have told them that this is the way they want it done. Period.
After you’ve shown them any appropriate guidelines, then drop it. Try to get a cheerful, “teachable” attitude and avoid being seen as someone who thinks they know more than those in charge. Keep a log for yourself to review at some time in the future when you switch jobs, so you can remember any errors that you will have to ‘unlearn’ at that point. Then, make sure that they never have to tell you twice how they want it done. They may begin to see that as a challenge to their authority or threat to their own position, that you (think that you) know more than they do.
The important thing right now is to put in your time, be alert and aware to the way YOU would code something if you were in charge, and …most important of all… don’t threaten those around you who may have not had the excellent training that you had.
The situation may fix itself.
*People come and go. A new supervisor may correct some of these problems.
*The whole group may get additional continuing education and become aware of some of their errors (not likely).
*You will put in your time and find a more excellent position where things are done correctly.
There is never a One-Size-Fits-All solution when we work with people. Right?