Why CDI Queries Matter
A clinical documentation improvement query is a compliant written communication from a CDI specialist or coding professional to a treating provider requesting clarification, specification, or confirmation of a clinical condition already evidenced in the medical record — enabling accurate ICD-10 coding, HCC assignment, and risk adjustment capture without altering the provider's clinical judgement or care decisions.
Clinical documentation improvement queries are the mechanism through which documentation gaps are identified and resolved. In the context of risk adjustment, every undocumented or under-specified condition represents a missed RAF score component — revenue that is clinically justified but never captured because the medical record does not reflect the provider's clinical assessment.
The fundamental challenge is not that providers lack clinical knowledge. It is that clinical documentation habits are optimized for patient care communication, not for coding specificity. A cardiologist who writes "heart failure, stable" has communicated the essential clinical information to the next provider. But that note lacks the specificity — type (systolic, diastolic, combined), severity (reduced, preserved, or mid-range ejection fraction), and acuity (acute, chronic, acute-on-chronic) — needed for accurate ICD-10 coding and HCC assignment.
CDI queries bridge this gap by asking providers to clarify, specify, or confirm clinical conditions based on evidence already present in the record. When done well, queries improve documentation accuracy without changing clinical care. When done poorly, they annoy providers, generate non-compliant documentation, or go unanswered entirely. The difference lies in query design, delivery, and programmatic management. This connects directly to broader CDI program strategy for risk adjustment.
Documentation Gap Impact
Industry studies show that 20-35% of HCC-relevant conditions present in patient records are under-documented or under-specified. Effective CDI query programs recover 60-75% of these missed conditions through compliant provider engagement.
Query ROI
Each successful CDI query that results in a documented HCC condition generates $800-$3,500 in annual RAF value per member. High-performing CDI programs achieve query ROI ratios of 10:1 or higher against program operating costs.
Types of CDI Queries
Not all queries serve the same purpose. Understanding the different query types enables CDI specialists to select the appropriate format for each documentation gap and increases the likelihood of a clinically accurate provider response.
- Clarification Queries: Used when the record contains conflicting or ambiguous information. Example: the problem list states "diabetes type 2" but a recent note references "insulin-dependent diabetes" without confirming type. The query asks the provider to clarify which type applies.
- Specificity Queries: Issued when a condition is documented but lacks the detail needed for accurate ICD-10 coding — the same gaps flagged by an ICD-10 guideline auditor API. Example: "heart failure" documented without type (systolic/diastolic) or ejection fraction classification. The query asks the provider to specify the clinical details that differentiate between HCC categories.
- Clinical Indicator Queries: Generated when clinical evidence (lab values, imaging, medication lists) suggests a condition that is not explicitly documented. Example: albumin of 2.8 g/dL with weight loss and low BMI — clinical indicators of protein-calorie malnutrition that has not been diagnosed in the record.
- Status Queries: Request confirmation of whether a previously documented condition remains active, has resolved, or has progressed. These are particularly important for risk adjustment because HCCs must be actively recaptured annually.
- Addendum Queries: Used in retrospective CDI programs to request documentation amendments after the encounter has occurred. These must follow strict compliance guidelines — the provider must personally review the record and attest to the clinical accuracy of any addendum.
Writing Effective Queries
The quality of a CDI query directly determines the quality of the provider response. Poorly written queries produce poor results — low response rates, non-specific answers, or clinically inaccurate documentation. Effective queries follow established principles.
- Reference Specific Clinical Evidence: Always cite the specific clinical indicators that prompted the query. "Based on the HbA1c of 9.2% documented on [date] and current treatment with insulin and metformin, please clarify the current status and type of the patient's diabetes." This grounds the query in clinical reality, not financial motivation.
- Use Open-Ended Language: Queries must not lead the provider to a specific answer. Instead of "Does this patient have protein-calorie malnutrition?" use "Based on the albumin of 2.6 g/dL, BMI of 17.5, and documented weight loss, please document the clinical significance of these findings, if applicable." The provider determines the diagnosis — the query only asks for documentation.
- Provide Clinical Context: Include relevant lab values, vital signs, medication lists, and prior documentation that support the query. Providers are more likely to respond when the clinical picture is clearly presented. Queries without supporting evidence appear arbitrary and are ignored at higher rates.
- Keep Queries Concise: Queries longer than one paragraph have significantly lower response rates. State the clinical indicators, ask the specific question, and stop. Providers reading queries between patients need clarity, not dissertations.
- Include Response Options When Appropriate: For specificity queries, listing clinically valid options can improve response quality. "Please clarify the type of heart failure: (a) systolic/HFrEF, (b) diastolic/HFpEF, (c) combined systolic and diastolic, (d) other — please specify, (e) clinically unable to determine." This is not leading — it offers all clinically valid options including the option to decline.
Three downloads risk adjustment teams actually use
Checklists, playbooks, and frameworks — built for analysts, auditors, and VPs working RAF, RADV, and HCC.
2026 RADV Audit Readiness Checklist
12-point compliance checklist for documentation, diagnosis code validation, extrapolation defense, and pre-audit scrub workflows.
RAF Score Optimization Playbook
Tactical guide for analysts: HCC recapture workflows, V28 transition impacts, prospective gap-closure plays, and KPIs that move RAF lift.
Risk Adjustment Analytics Playbook
How payer leaders sequence prospective and retrospective risk adjustment for compounding RAF lift. Deployment patterns, KPIs, and a VP-level operating rhythm.
Query Compliance and Regulations
CDI query compliance is governed by AHIMA (American Health Information Management Association) and ACDIS (Association of Clinical Documentation Integrity Specialists) guidelines, as well as AHRQ documentation standards and CMS expectations for coding integrity. Non-compliant queries create legal and regulatory risk.
- Non-Leading Requirement: Queries must never suggest, imply, or direct the provider toward a specific diagnosis. A query that asks "Would you agree this patient has malnutrition?" is leading. The provider's clinical judgment must drive the documentation — the query only prompts the provider to exercise that judgment.
- Clinical Basis Requirement: Every query must be supported by clinical evidence in the medical record. Queries based solely on financial impact — "This HCC would increase the RAF score" — are prohibited and constitute potential fraud risk. The clinical indicators must justify the query independently of any financial outcome.
- Provider Autonomy: The provider must be free to disagree with any query. A query process where providers feel pressured to agree, or where non-agreement triggers escalation, is non-compliant. The "agree rate" is a performance metric, not a compliance target — a 60% agree rate with clinically accurate responses is better than a 95% agree rate driven by provider pressure.
- Documentation in the Legal Medical Record: Provider responses to queries become part of the permanent medical record. The response must reflect the provider's genuine clinical assessment and be signed and dated. Template responses, auto-populated answers, or responses entered by non-provider staff are not compliant.
- Retrospective Query Limitations: Queries issued after the encounter (retrospective) face additional scrutiny. The provider must be able to recall the clinical circumstances and attest to the accuracy of any addendum. Queries sent months after the encounter with no mechanism for clinical verification raise compliance concerns.
Tracking Query Outcomes
A CDI program without outcome tracking operates blind. Measuring query performance identifies what is working, what needs improvement, and where to invest additional resources.
- Query Volume: Total queries issued per period, segmented by query type, clinical condition, and provider. This metric reveals whether CDI specialists are identifying documentation gaps at expected rates. Low query volume may indicate insufficient record review or overly conservative query thresholds.
- Response Rate: Percentage of queries that receive a provider response within the defined timeframe. Benchmark: 80%+. Low response rates require analysis — is the delivery mechanism effective? Are providers receiving queries at the right workflow point? Are queries too long or unclear?
- Agree Rate: Percentage of queries where the provider agrees with the suggested documentation improvement. Benchmark: 70-80%. An agree rate above 90% may indicate leading queries. An agree rate below 50% may indicate poor clinical indicator identification.
- HCC Impact Rate: Percentage of agreed queries that result in a new or changed HCC. This connects CDI activity directly to risk adjustment outcomes. Not every query produces an HCC change — specificity improvements may result in the same HCC category — but this metric quantifies revenue-relevant impact.
- Provider-Level Analytics: Track metrics by individual provider to identify documentation patterns. Providers with consistently high query rates may need targeted education. Providers who never receive queries may be over-documenting or working in specialties with fewer HCC-relevant conditions.
- Query Turnaround Time: Measure the time from query issuance to provider response. Faster turnaround improves coding timeliness and encounter data submission. Queries that remain open for more than 14 days should trigger escalation workflows.
Building a Query Excellence Program
Moving from ad hoc query activity to a systematic query excellence program requires organizational commitment, defined processes, and continuous improvement cycles.
- Standardized Query Templates: Develop condition-specific query templates that embed compliance guardrails, clinical indicator prompts, and appropriate response options. Templates improve consistency across CDI specialists and reduce the risk of non-compliant query language. Templates should be reviewed quarterly and updated based on outcome data.
- CDI Specialist Training: Invest in clinical education for CDI staff. The most effective CDI specialists combine coding knowledge with clinical understanding — they can read a chart, identify documentation gaps, and articulate the clinical question in language that resonates with providers. Ongoing training should cover new HCC conditions, clinical indicator identification, and query writing workshops.
- Provider Education and Engagement: Providers who understand why CDI queries exist — and how documentation specificity affects both coding accuracy and patient care quality — respond at higher rates and with better clinical detail. Quarterly provider education sessions, individualized documentation scorecards, and peer-to-peer feedback programs build engagement.
- Technology-Enabled Query Workflows: Implement CDI technology that integrates query creation, delivery, tracking, and analytics into a single platform. Manual query processes using paper forms, fax machines, or email threads cannot scale to the volume required for effective risk adjustment CDI programs.
- Quality Assurance Reviews: Audit a sample of queries monthly for compliance, clinical appropriateness, and writing quality. Peer review among CDI specialists identifies best practices and corrects emerging issues before they become systemic. Quality assurance should focus on both the query itself and the provider response — ensuring that responses meet documentation standards.
- Executive Reporting: Connect CDI query outcomes to organizational financial and quality metrics. Report HCC impact, RAF score improvement, and documentation accuracy trends to leadership. CDI programs that demonstrate measurable impact receive sustained investment; those that cannot quantify their value face budget pressure.