Healthcare Compliance and Regulatory Environment
What to know
Healthcare auditors must map a provider's obligations across overlapping regimes: Medicare Conditions of Participation and coverage rules, the False Claims Act (FCA), Anti-Kickback Statute (AKS), Physician Self-Referral (Stark) law, the Civil Monetary Penalties Law, HIPAA, and the Office of Inspector General (OIG) Compliance Program Guidance. Know the difference between a condition of payment (the claim is false if unmet) and a condition of participation (facility may lose certification). Understand that AKS is intent-based and covers remuneration for referrals of federally payable items, while Stark is a strict-liability civil statute limited to designated health services and physician financial relationships, with exceptions that must be met exactly.
Traps
Questions conflate AKS and Stark: AKS requires intent and covers any item; Stark is strict liability and narrower. Watch for 'safe harbor' versus 'exception'-safe harbors belong to AKS, exceptions to Stark. Also distinguish the OIG's permissive guidance (advisory opinions, work plan) from binding regulation. A common trap: assuming a compliance program is legally mandatory for all providers-it is strongly encouraged and effectively expected, and mandatory for certain suppliers under the ACA.
Rule of thumb
Ask: Is the item federally payable, is there remuneration, and does a written arrangement fit an exact exception? If the arrangement fails any element, treat it as a compliance risk regardless of fair market value.
Worked example
A hospital leases office space from a referring physician below market rent. Stark's rental exception requires rent at fair market value and a signed, commercially reasonable lease. Below-market rent fails the exception, creating a strict-liability violation even without proof of intent-whereas an AKS theory would additionally need to show intent to induce referrals.