9.4 HHS Documentation Requirements and CDI

HHS Documentation Requirements

Domain 4 Task 3 is monitoring U.S. Department of Health and Human Services (HHS) clinical documentation requirements. In practice this means tracking the rules set by HHS agencies — chiefly the Centers for Medicare & Medicaid Services (CMS) through its Conditions of Participation, manuals, and National/Local Coverage Determinations, and the Office of Inspector General (OIG) through its Work Plan and compliance guidance. These define what documentation must exist to support a service: a signed and dated note, authentication of orders, medical necessity, and timely completion.

Key documentation anchors the RHIA monitors:

• Authentication — every entry signed/dated by its author; CMS prohibits unsigned or back-dated entries.
• Medical necessity — documentation must support that the service was reasonable and necessary (NCD/LCD criteria).
• Completeness and timeliness — records completed within facility/medical-staff deadlines, supporting POA and discharge coding.
• Copy-forward control — cloned notes are an OIG audit target; the record must reflect the current encounter.

CDI as Documentation Governance

Domain 4 Task 4 is conducting clinical documentation integrity (CDI) activities for revenue and quality. The exam framing is critical: CDI improves the clarity, completeness, consistency, and reliability of the record. Better-paying claims and better quality scores are downstream effects of accurate documentation, never the stated goal. A CDI program that exists only to raise the case-mix index is the wrong answer.

The central CDI tool is the compliant query. A query is appropriate when documentation is conflicting, incomplete, ambiguous, imprecise, illegible, or clinically inconsistent. Per AHIMA's Guidelines for Achieving a Compliant Query Practice, a query must be supported by clinical indicators in the record and must not lead the provider toward a particular answer.

A Worked Example

A patient has a documented sodium of 128 mEq/L, fluid restriction, and hypertonic saline orders, but no diagnosis of hyponatremia. A compliant multiple-choice query lists the clinical indicators and offers options including hyponatremia, another clinically reasonable cause, "other," and "clinically undetermined." A leading query that simply states "Please document hyponatremia" is non-compliant because it supplies the answer without letting the provider exercise clinical judgment.

Measuring CDI

Measure CDI across a balanced set of indicators so the program is judged on integrity, not just dollars:

1. Query metrics — query rate, response rate, and agreement rate.
2. Documentation impact — CC/MCC capture, specificity improvement, SOI/ROM (severity of illness / risk of mortality) shifts.
3. Quality — accuracy of risk-adjusted measures, mortality and complication indices.
4. Revenue — case-mix index trend and DRG shifts, reviewed for plausibility, not as a target.
5. Denials — reduction in clinical-validation and documentation-related denials.

Common Exam Traps

The wrong answers issue leading queries, query without clinical indicators, set DRG or CMI targets for CDI staff, or hide queries from the record. The defensible choice clarifies genuine ambiguity, offers clinically reasonable options including an undetermined choice, documents the query and response, and measures the program on documentation integrity and quality alongside revenue. When a stem describes a query that names a single diagnosis with no alternatives, recognize it as leading and reject it.

Verbal Queries and the Documentation Trail

Queries may be written or verbal, but every query and its response must be documented and retained according to facility policy. A verbal query left unrecorded is non-compliant because it cannot be audited and creates the appearance that a diagnosis was added through undocumented conversation. The exam often hides this defect inside an otherwise reasonable query: the clinical indicators are present and the options are fair, but the query was made by phone with no record. Recognize that as the flaw.

The compliant practice memorializes the verbal exchange in the record, including who was queried, the indicators presented, and the provider's response.

Equally important, the query response must result in a documented diagnosis in the body of the record before it is coded. A provider answering a query form is not enough on its own; the agreed diagnosis must appear in a signed progress note or discharge summary so the code rests on the record, not on the query form alone. This protects the code if the claim is later audited.

When Not to Query, and Retrospective Limits

The administrator must also know when a query is inappropriate. Do not query to confirm a diagnosis that is already clearly and consistently documented, do not query without clinical indicators in the record, and do not issue a query whose only purpose is to reach a higher-weight DRG. Post-discharge and retrospective queries are permitted but carry tighter rules: they should still be supported by clinical indicators present at the time of care, and they must not introduce conditions the record never suggested. A pattern of post-bill queries that consistently raise the DRG is itself an OIG audit flag.

Finally, governance the program with a query policy approved by HIM, CDI, the medical staff, and compliance, defining triggers, formats, escalation for unanswered queries, and retention. When a stem pits a CDI specialist against a provider who will not respond, the defensible answer escalates through the documented policy and the medical staff, never by the CDI specialist resolving the ambiguity unilaterally or coding an unsupported diagnosis.