Documentation, Compliance, and Regulatory Requirements
Concepts to master
Compliance coding depends on documentation that is accurate, complete, timely, and attributable. Medical necessity must support the service and the code. Coders should understand HIPAA privacy and security basics, the False Claims Act, anti-kickback and Stark rules, OIG work plan priorities, NCDs and LCDs, and Advance Beneficiary Notices. Documentation must include authentication, date, and intent. EHR tools can create cloned or copied documentation, which is a major audit risk. Queries to providers should be nonleading and include the clinical indicators needed to resolve ambiguity.
Traps in questions
If a service or diagnosis is not documented, it cannot be coded. Do not code from memory or from a problem list alone. Copy-paste and cloned notes may not reflect the encounter. Late entries and amendments must be clearly identified. Signatures and credentials matter. Do not change documentation to support a claim; correct errors through proper amendment. Watch for “possible” or “rule out” language in outpatient records and for unsupported medical necessity. Ensure ABN use when required.
Worked example
An outpatient note states “possible pneumonia” and documents cough and fever. Do not assign a pneumonia code. Code the documented signs and symptoms, such as cough and fever, according to index guidance. Rule of thumb: if it is not documented, it was not done-and if it is uncertain in the outpatient setting, code the symptom.