What is CDI Query Process? Definition, Formula, and Benchmark

The CDI query process is the formal workflow by which clinical documentation improvement (CDI) specialists request clarification or additional documentation from providers to support accurate coding and reporting. Queries address ambiguous, incomplete, inconsistent, or clinically-unsupported documentation, asking providers to clarify so coders can assign accurate codes. The process operates under strict compliance requirements to ensure queries are ethical, non-leading, and do not pressure providers to inappropriately modify clinical documentation.

When to query: CDI and coders issue queries when documentation is: ambiguous (condition mentioned without specificity — "pneumonia" without specifying type or causative organism), incomplete (condition listed but without supporting clinical evidence — "sepsis" without documenting SIRS criteria or infection source), inconsistent (documentation contradicts itself or other documentation), or clinically-unsupported (a condition is not documented despite clinical evidence — labs suggesting acute blood loss anemia without anemia documented). Queries address the gap between clinical reality and documentation, not to drive specific coding outcomes.

Compliant query principles are codified in AHIMA and ACDIS (Association of Clinical Documentation Integrity Specialists) practice briefs and position papers. Core principles include: queries must be non-leading (not suggest specific answers), provide all clinically-relevant options (when a diagnosis has multiple possible codes, query should offer multiple options rather than steering toward one), include specific clinical indicators from the record supporting the query, allow "other" or "clinically undetermined" as provider response options, and not pressure providers to document conditions not clinically supported. Queries violating these principles create compliance exposure.

Query formats include: verbal query (CDI specialist discusses with provider; provider subsequently documents in chart — verbal queries must be followed by chart documentation), written query on paper (traditional approach; decreasing as EHRs mature), electronic query in EHR (integrated workflow; provider responds within the chart; maintains audit trail), and query workflow tools (specialized CDI platforms like Nuance Clintegrity, 3M CDIS, or Iodine — support query generation, tracking, and analytics).

Query response and documentation: Providers respond to queries by documenting the clarified information in the chart (typically in the problem list, assessment, or other appropriate section). The documented response — not the query form itself — becomes the official medical record supporting coding. Coders cannot code based on query forms alone; the information must appear in provider-authored chart documentation.

Audit and compliance oversight: Query processes are a specific focus of coding compliance audits. OIG work plans have included CDI query practices as audit focus areas. Audit reviews examine: query appropriateness (is the query clinically justified), query construction (is it compliant with non-leading principles), provider response documentation (did the provider document appropriately), and coding of query-cleared conditions (is coding accurate based on documented response).

Technology and workflow: Modern CDI platforms use AI to identify query opportunities — analyzing clinical documentation in real-time to flag potential documentation gaps for CDI specialist review. AI can surface: conditions clinically-suspected but undocumented (based on labs, imaging, medications), specificity opportunities (conditions documented generically that have specific codes available), and compliance concerns (unusual coding patterns warranting review). Human CDI specialist judgment remains essential; AI surfaces candidate queries but doesn't replace expert review.

For RCM operations, CDI query process quality directly affects coding accuracy, compliance defensibility, and revenue. Well-run CDI programs improve DRG capture (through specificity clarification), reduce denial risk (through better documentation), and support both inpatient and outpatient coding accuracy. Programs also contribute to quality measurement (accurate problem documentation supports quality calculations) and risk adjustment (HCC documentation for VBC arrangements).

Provider education and engagement are central to CDI success. Query volume itself is not a success measure — too many queries indicates poor baseline documentation; too few indicates missed opportunities. Provider engagement (query response rate, quality of responses, changes in documentation behavior over time) is the meaningful outcome. Mature programs track provider-level query metrics, provide education on common query types, and work with provider leadership on systematic documentation improvement.