Clinical Documentation Integrity and Medical Necessity
What this domain tests
CDI is the discipline of making the record complete, accurate, and reflective of the patient's true clinical picture - not of maximizing payment. Concepts: the CDI specialist's role and scope; concurrent review and the query process; query formats (open-ended, multiple-choice, yes/no) and when each is appropriate; query compliance rules (non-leading, clinically supported, not directing a diagnosis); medical necessity - the 'why' behind admission, testing, and level of service; severity of illness and risk of mortality; and the distinction between a documentation gap and a coding error.
Traps that show up in questions
- A query that suggests the answer ('Would you agree the patient has sepsis?') - this is leading and non-compliant.
- Assuming CDI's job is to 'increase the CC capture' - the legitimate goal is accuracy and clinical validity.
- Confusing medical necessity (is the service justified?) with coding accuracy (is the code right?).
- Ignoring that a query must be based on clinical indicators in the record, not reviewer speculation.
- Missing that a resolved query still requires the provider's authenticated response in the record.
Rule of thumb
A compliant query is evidence-based, non-leading, and answerable. If your query could be answered 'yes' just because you asked it, rewrite it.
Worked example
A patient's labs show rising creatinine and the note says 'renal insufficiency.' A compliant query: 'Please clarify the etiology/type of renal insufficiency, or document if this is acute kidney injury, chronic kidney disease, or other, based on the clinical indicators.' A non-compliant query names AKI as the expected answer.