Coding Guidelines and Regulatory Compliance
What this domain tests
Compliance items ask whether a claim is supported, not merely whether a code exists. Expect HIPAA privacy, the False Claims Act, Anti-Kickback Statute and Stark, NCCI edits, LCD/NCD coverage, ABNs, audit response, and query practice.
Core rules
- Medical necessity must link the diagnosis to the service. A valid code can still be non-covered.
- NCCI Procedure-to-Procedure edits bundle the column-two code into the column-one code. Override only with documentation supporting modifier 25 (separate E/M) or 59/XS/XU/XP (distinct service).
- Modifier 25 requires a significant, separately identifiable E/M service above the procedure's usual work.
- An ABN is given before billing a Medicare beneficiary for a service likely to be denied as not medically necessary.
- A compliance program includes written policies, training, auditing, and a reporting mechanism; the OIG Work Plan signals audit targets.
Worked example
An established patient is seen for a painful shoulder and also asks about a new wart. The physician performs a level-3 E/M for the shoulder and destroys one wart (17110). The wart alone would not justify the E/M, but the shoulder assessment and prescription management are separately identifiable. Report 99213-25 and 17110, linking the shoulder diagnosis to 99213 and the wart diagnosis to 17110. If the note described only the wart, modifier 25 would be unsupported and the E/M would be denied or recouped.
Traps
Using modifier 59 to bypass every edit; appending 25 routinely; missing an ABN; cloning a prior note; billing before documentation is complete.