Coding Guidelines and Regulatory Compliance
Foundations of Compliance
Coding accuracy begins with the hierarchy of authority: statute (Social Security Act), regulation (CMS rules in 42 CFR), then national and local coverage determinations, then coding manuals and clinic policy. When a question asks what governs payment, the answer is usually the coverage determination, not the CPT descriptor alone.
Concepts You Must Know
- Medical necessity as the gatekeeper for every claim, documented in the record, not inferred.
- HIPAA privacy/security and the transaction standards that make claims electronic.
- False Claims Act and the concept of knowingly submitting inaccurate claims, including reckless disregard.
- Anti-kickback Statute and Stark Law distinctions: intent-based criminal vs. strict-liability civil physician self-referral.
- NCCI edits (bundling, modifier indicators) as payment policy, separate from CPT rules.
- Advance Beneficiary Notice (ABN) for services expected to be denied as not medically necessary.
Traps
Questions love to blur coding rules with payment rules. NCCI bundling is not a CPT guideline violation; it is a payer edit. Another trap: assuming a signed order alone proves necessity, or that a documentation error is automatically fraud (fraud requires intent or reckless disregard).
Rule of Thumb
If it is not documented, it was not done. For compliance questions, ask: Is it documented, medically necessary, correctly coded, and supported by an order? All four must be yes.
Worked Example
A provider performs a service and later adds a diagnosis code to justify payment without a supporting note. Correct answer: this is an unsupported claim; the fix is documentation of the actual condition, not retroactive code selection.