Audit Radar
About this game
Claims cross the scope one at a time and you have thirty seconds each: pass it or flag it, then say what is wrong. Passing a clean claim scores exactly as much as catching a dirty one — because in real auditing, flagging everything is its own kind of wrong, and knowing when to leave a claim alone is half the skill.
Every code that appears here has a full reference page on this site — descriptions, inclusion terms, Excludes1/Excludes2 notes, and crosswalks. Look one up →
Study aid only — not coding, billing, legal, or medical advice. Verify every code against the current official code set and your payer’s policy before billing.
- Recognising upcoding, unbundling and cloned notes
- Judging when a modifier is genuinely supported
- Resisting false positives on legitimate claims
Leaderboard
Top 10- 1Sofia D.Provo, UT · 9/10 calls · 5 issues named2,675
- 2Priya K.Chandler, AZ · 8/10 calls · 4 issues named2,275
- 3Danielle C.Wichita, KS · 7/10 calls · 4 issues named2,150
- 4Crystal M.Duluth, MN · 7/10 calls · 4 issues named2,150
- 5Brandi W.Duluth, MN · 7/10 calls · 3 issues named1,950
- 6Tamika T.Tampa, FL · 6/10 calls · 3 issues named1,750
- 7Grace G.Mesa, AZ · 6/10 calls · 3 issues named1,700
- 8Sean N.Peoria, IL · 6/10 calls · 3 issues named1,700
- 9Jasmine A.Mesa, AZ · 6/10 calls · 3 issues named1,675
- 10Michelle M.Tampa, FL · 6/10 calls · 3 issues named1,625
Scores are submitted by players and shown as entered. Play a round to add yours.
Enjoying Audit Radar?
Give it a heart so other coders can find it, and send it to someone on your team who needs the practice.
Keep playing
