Study guide
23.3 Detecting Leading, Biased and Unsupported Queries
AHIMA Certified Documentation Integrity Practitioner CDIP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Authoritative Coding Resources & Conventions
1.1 Official Coding Resources: Scope, Authority & Research 1.2 General Coding Conventions, Punctuation & Instructional Notes 1.3 Chapter-Specific and Setting-Specific Coding Guidelines
2 Chapter 2: Principal & Secondary Diagnosis Determination
2.1 UHDDS Definitions & Principal Diagnosis Selection 2.2 Two or More Diagnoses Equally Meeting Criteria 2.3 Secondary Diagnosis Reporting Standards & POA Status
3 Chapter 3: Procedure Coding & Sequencing Standards
3.1 ICD-10-PCS Root Operations & Inpatient Procedure Coding 3.2 Principal Procedure Selection & Surgical Sequencing 3.3 Applying Official References to Ambiguous Records
4 Chapter 4: Inpatient Prospective Payment & DRG Grouping
4.1 MS-DRG Logic, CC/MCC Exclusions & Severity Levels 4.2 Working vs. Final DRG Assignment & Optimization vs. Maximization 4.3 CDI-Coding Reconciliation & Annual Regulatory Updates
5 Chapter 5: Enterprise CDI Promotion & Program Value
5.1 Articulating CDI Value to C-Suite & Hospital Leadership 5.2 Organizational Models, Inpatient/Outpatient Scope & Staffing 5.3 Cross-Functional Collaboration: HIM, Quality & Case Management
6 Chapter 6: Cross-Functional Alignment & Improvement Projects
6.1 Partnering with Nursing, Pharmacy & Allied Health Professionals 6.2 Documentation Improvement Project Identification & Scoping 6.3 Executing, Piloting & Measuring CDI Project Outcomes
7 Chapter 7: Physician Champion Engagement & Clinical Advocacy
7.1 Selection, Role & Credibility of the CDI Physician Champion 7.2 Peer-to-Peer Engagement, Coaching & Overcoming Resistance 7.3 Developing Standard CDI Operational Policies & Procedures
8 Chapter 8: Compliant Policy Architecture & Query Governance
8.1 AHIMA/ACDIS Practice Brief Standards in Policy Construction 8.2 Medical Record Integration of Provider Query Responses 8.3 Policies for Electronic, Paper, and Verbal Query Communications
9 Chapter 9: Query Escalation & Professional Communication
9.1 Chain of Command & Protocols for Unanswered Queries 9.2 Conflict Resolution & Professional Feedback Mechanisms 9.3 Assessing Stakeholder Learning Needs & Specialty Curricula
10 Chapter 10: Educational Delivery & Broader Healthcare Impacts
10.1 Delivery Methods: Microlearning, Case Studies & Grand Rounds 10.2 Documentation Impacts on Clinical Research & Epidemiology 10.3 Documentation Impacts on Case Management, LOS & Reimbursement
11 Chapter 11: Clinical Record Synthesis & Encounter Trajectory
11.1 Synthesizing Provider Notes, Consults & Progress Trajectory 11.2 Interpreting Diagnostic Imaging, Pathology & Labs 11.3 Resolving Conflicting, Ambiguous & Copy-Forward Entries
12 Chapter 12: Advanced Clinical Concepts & Review Prioritization
12.1 Pharmacotherapy, Clinical Trajectories & Disease Correlations 12.2 Inpatient Review Prioritization: High-Risk & High-Volume 12.3 Payer Prioritization, Length of Stay & Re-Review Cadence
13 Chapter 13: Clinical Indicator Mapping & Gap Recognition
13.1 Systematic Identification of Documentation Gaps 13.2 Sepsis Definitions, SEP-1, and Coding 13.3 AKI Criteria, Tubular Injury, and CKD Staging
14 Chapter 14: Diagnostic Precision in High-Impact Conditions
14.1 Respiratory Failure: Acuity, Evidence, and Sequencing 14.2 Heart Failure Phenotype, Acuity, and Hypertensive Combinations 14.3 Encephalopathy, Delirium, and Acute Cognitive Change
15 Chapter 15: Clinical Validation & Complication Discrepancies
15.1 Malnutrition Assessment, Severity, and Provider Documentation 15.2 Principles of a Compliant, Nonleading Query 15.3 Open-Ended, Multiple-Choice, and Yes/No Queries
16 Chapter 16: Query Mechanics & Direct Provider Collaboration
16.1 Electronic Query Systems, Templates, and Technology Oversight 16.2 Collaborating With the Appropriate Query Recipient 16.3 Capturing and Clarifying Query Responses
17 Chapter 17: Quality Indicators & Post-Discharge Clarification
17.1 Present on Admission Clarification and Selected HAC Rules 17.2 Clarifying Acuity, Cause, Site and Severity 17.3 Post-Discharge Query Opportunities and Limits 17.4 Managing Post-Discharge Query Workflows
18 Chapter 18: CDI Operational Dashboards & Quality Auditing
18.1 Departmental Metrics: Definitions, Calculations and Dashboard Use 18.2 Internal CDI Quality Audits and Reviewer Calibration 18.3 Query Trends: Understanding the Process and Provider Experience
19 Chapter 19: Benchmarking, Productivity & Data-Driven Workflow
19.1 Provider Documentation Benchmarking 19.2 External Benchmarking: CMI, Severity, Mortality and Length of Stay 19.3 Evaluating CDI Professional Performance 19.4 Using Data to Design CDI Workflow and Staffing
20 Chapter 20: Ethical CDI Standards & Regulatory Frameworks
20.1 Applying AHIMA Ethics to CDI Decisions 20.2 Responding to Financial Pressure and Upcoding Risks 20.3 Maintaining Competence and Professional Integrity
21 Chapter 21: Regulatory Compliance & Enforcement Landscapes
21.1 False Claims, Overpayments and Referral Laws 21.2 Regulatory Agencies, Review Contractors and Appeals 21.3 EHR Templates, Copied Text and Record Integrity
22 Chapter 22: Technology Risks & Second-Level Review Protocols
22.1 CAC, NLP and AI: Context, Oversight and Performance 22.2 Selecting Cases for Second-Level Review 22.3 Conducting and Closing a Second-Level Review
23 Chapter 23: Clinical Validation Queries & Risk Mitigation
23.1 Clinical Validation and Coding Clarification 23.2 Clinical Validation Queries and Denial Evidence 23.3 Detecting Leading, Biased and Unsupported Queries
24 Chapter 24: Noncompliant Query Remediation & Query Lifecycle Management
24.1 Query Remediation and Corrective Action 24.2 Query Timeframes, Aging and Measurement 24.3 Query Records, Retention and Evidence Preservation
23.3 Detecting Leading, Biased and Unsupported Queries
Key Takeaways Explain This Topic AI
Review the source record, question, options, title, formatting and related conversation together.
Yes/no is permitted for appropriate clarification of existing documentation; it should not introduce a previously undocumented diagnosis.
A supported multiple-choice option plus an alternate-explanation opportunity can satisfy the answer-choice rule; a fixed trio of exit options is not universally required.
Unsupported choices or selective evidence remain defects even when an Other field is present.
Audit methods and technology controls are locally designed. A query defect warrants appropriate review and correction, not an automatic fraud or repayment conclusion.
Last updated: October 2026
Detecting Leading, Biased and Unsupported Queries
Review the whole communication when assessing a query: the source record, question, answer options, provider-visible title, formatting and any related conversation. The central issue is whether it seeks accurate clarification while preserving the provider's independent judgment. A polished template or an “Other” field cannot cure unsupported options or pressure to produce a preferred answer.
The August 2026 AHIMA/ACDIS brief supplies the professional query framework. It does not make every deviation a federal offense. A compliance finding should identify the actual defect, affected communication and required correction. Any separate legal analysis must address the applicable law and facts.
Identify the mechanism of influence
Defect What the reviewer should examine Example of the problem
Direction toward a preferred answer Wording, visual emphasis, preselected responses and conversation A new diagnosis is already checked before the provider sees the form
Unsupported response options Whether each proposed clinical answer fits the record Offering hypernatremia solely from a documented sodium of 122 mEq/L
Selective evidence Omitted findings or clinical explanations that materially change the question Quoting one abnormal result while hiding the provider's documented explanation and relevant follow-up
Outcome pressure References to reimbursement, quality results or denial avoidance Asking the provider to confirm a diagnosis so the account retains an MCC
Improper format or recipient Whether the format and provider role fit the clarification A yes/no query introducing a diagnosis found only in an ancillary clinician's assessment
These concerns may overlap. Avoid treating them as a rigid official taxonomy or inferring motive from a single word. “Length of stay,” for example, may describe actual clinical chronology. The defect is using payment or performance consequences to influence diagnosis, not the mere presence of every term that might also appear in a financial discussion.
Distinguish valid formats from leading use
A yes/no format is not inherently leading. Under the 2026 brief it is appropriate for specified clarification of an already documented diagnosis or relationship, with the required response opportunities. It should not introduce a previously undocumented diagnosis. A query based only on a registered dietitian's malnutrition assessment requires provider-driven multiple-choice clarification when needed; an ancillary cosignature is not reliable diagnostic adoption.
Multiple choice must include at least one supported clinical option and an avenue for an alternative explanation. There is no fixed minimum number of diagnoses. A supported option plus “Other, please specify” can meet the answer-choice requirement. That does not automatically certify the remainder of the query: review its purpose, indicators, source citations and neutrality too.
“Unable to determine,” “ruled out” and “not clinically significant” are useful when suitable to the circumstances; they are not an obligatory trio on every multiple-choice form. POA yes/no queries specifically require yes, no and unable to determine. An inability to determine does not mean an uncertain diagnosis such as probable or unable to rule out.
Apply the rules to concrete communications
New diagnosis from a narrow observation. A query asks, “Do you agree that sodium 131 and confusion represent metabolic encephalopathy due to hyponatremia?” The stem introduces a diagnosis and causal explanation that the provider has not documented. The reviewer should assess the full record before deciding whether a query is justified, then use a suitable format with supported choices and alternate explanation. Do not infer encephalopathy, delirium subtype or causation from a sodium value alone.
Response menu built around a payment target. A respiratory query lists only variants of acute respiratory failure despite a record that supports other explanations of the presentation. “Other” does not excuse including unsupported variants. Review baseline status, provider assessments and relevant observations; revise the question and options around the actual unresolved issue. Do not assume edema automatically supports heart failure or that all chronic heart-failure codes lack CC status.
Blood loss after surgery. A hemoglobin fall with no transfusion does not itself prove either acute blood-loss anemia or harmless hemodilution. Review the operative record, fluid course, provider assessment, monitoring and other care. Avoid demanding the diagnosis from the laboratory change; also avoid a blanket rule that no symptoms or transfusion makes all clarification impermissible. The concern and reporting requirements must be evaluated in context.
A diagnosis is already supported and clear. Do not query merely to replace it with a more favorable code. First apply the Index, Tabular List and reporting rules. A genuine conflict, missing specificity or support concern may justify clarification; the existence of a higher-paying classification does not.
Audit the communication and its use
A useful audit records the sampled population, actual query version, encounter, indicator sources, format, recipient, response and disposition. Include vendor-generated prompts, automated nudges and patient-specific verbal clarification. Compare reviewers' conclusions and calibrate disagreements before presenting a rate as established performance.
Sample size, frequency and any focused pre-delivery review are organizational decisions. A keyword filter may help find communications for review, but it is not required NLP infrastructure and cannot replace judgment. A filter can miss a leading paraphrase or flag a harmless quotation from the record. The 2026 framework permits qualified oversight through review before delivery or ongoing structured audit; it does not mandate physician-advisor approval of every complex query.
Use findings to correct the relevant unit: a flawed shared template may affect many users, while a correct template can still be misused in one encounter. Preserve appropriate versions and disposition history. Distinguish draft, delivered-unanswered, answered and claim-paid situations rather than applying one “void and delete code” instruction to all of them. Section 24.1 develops that remediation workflow.
Separate query defects from claim and legal findings
An improper query does not establish that the underlying condition was absent, that every related payment was excessive or that all elements of a False Claims Act violation are met. It also cannot be ignored simply because a provider signed the answer. Review clinical documentation, code assignment, claim impact and any necessary HIM/provider amendment with the appropriate owners.
For a Medicare Part A/B overpayment, apply the current identification, deadline, suspension and reporting provisions of 42 CFR 401.305. Its framework does not automatically govern every commercial payment. False Claims Act analysis distinguishes the alleged conduct, knowledge and other applicable elements; a query defect or missed general deadline alone is not a complete statutory finding. Escalate credible concerns promptly, preserve evidence, and document the correction and follow-up rather than declare liability from an audit label.
Sources: 2026 AHIMA/ACDIS query brief , FY2027 ICD-10-CM guidelines , 31 USC 3729 , and 42 CFR 401.305 .