15.3 Open-Ended, Multiple-Choice, and Yes/No 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

15.3 Open-Ended, Multiple-Choice, and Yes/No Queries

Key Takeaways Explain This Topic AI

Open-ended queries may be used in any circumstance, but a free-text field does not guarantee neutrality or a particular response rate.

A multiple-choice query needs at least one clinically valid supported option and a way to provide an alternative explanation; unsupported diagnoses should not be added to satisfy an invented minimum.

Yes/no queries clarify existing provider documentation and appropriate relationships; they should not introduce a previously undocumented diagnosis.

A dietitian’s malnutrition diagnosis alone supports evidence for an appropriate provider query, not a yes/no request to adopt that diagnosis.

POA yes/no queries require Yes, No, and Unable to determine. Unable to determine is not the same as a probable diagnosis or unable to rule out.

Last updated: October 2026

Open-Ended, Multiple-Choice, and Yes/No Queries

Choose a query format after identifying what needs clarification and what is already documented. The August 2026 AHIMA/ACDIS brief, Section V.II , describes multiple-choice, yes/no, and open-ended formats. Each must preserve provider judgment, include relevant sourced indicators, and avoid a preferred outcome. No format guarantees compliance merely because its response field has the right shape.

Compare the actual requirements

Format Appropriate use Response structure

Open-ended Any circumstance, especially when the situation is complex or suitable options are unclear Neutral question with relevant indicators and free text

Multiple-choice Clarification supported by clinically relevant diagnostic or explanatory options At least one supported clinically valid option and an alternative explanation route, such as “Other, specify”

Yes/no Clarification of an already-documented diagnosis, including appropriate timing or relationship questions Yes and No, plus a third route for inability to determine or further free-text information

POA yes/no Whether a documented condition was present at inpatient admission Yes, No, and Unable to determine

The brief permits multiple-choice answers in any order. Do not emphasize a preferred choice with arrows, added bolding, or similar cues. An organization's template conventions may help consistency, but a particular answer order is not a universal compliance rule.

Open-ended: let the provider explain

An open-ended query supplies the issue and relevant facts without diagnostic choices. It can be useful when a complex clinical course is difficult to represent fairly with a short menu. The 2026 brief allows this format in any circumstance; it also notes potential difficulty interpreting the response. It does not declare open-ended questions the universally preferred or safest format.

Consider a hypothetical record in which the October 21 admission note documents new confusion and the October 22 progress note describes improvement but leaves the diagnosis unresolved. A free-text query could cite those notes and the pertinent evaluation and ask: “Based on your clinical judgment, please clarify the condition, if any, responsible for the documented mental status change.” The provider may explain a diagnosis, describe remaining uncertainty, or identify another interpretation.

An open-ended request can still lead. A title such as “Query for acute metabolic encephalopathy,” a selective presentation of evidence, or a request to improve a mortality score can influence the answer even when no boxes are provided. Check the whole communication. Do not assume that a free-text field eliminates audit concerns or establishes a particular response-rate advantage.

Multiple-choice: include supported answers, not a quota

A multiple-choice query can introduce a diagnosis for consideration when indicators support it. Every proposed diagnostic choice must fit the record. The list must permit an explanation other than the listed diagnosis or diagnoses. There is no required minimum number of diagnostic differentials beyond at least one clinically valid supported option. “Unknown,” “Unable to determine,” “Not clinically significant,” or similar responses may be useful, but they are not mandatory in every multiple-choice query.

Hypothetical nutrition example: The dietitian's October 22 assessment documents intake of 40% of estimated needs for seven days and reliable weights of 75 kg one month earlier and 69 kg currently. The assessment identifies severe malnutrition in the context of acute illness. The provider's October 22 note records poor intake but no nutritional diagnosis. After review confirms that clarification is needed, a multiple-choice request could read:

Nutritional status clarification. The dietitian assessment dated October 22 documents intake of 40% of estimated needs for seven days, weight change from 75 kg to 69 kg over one month, and its assessment of severe malnutrition. Your October 22 note documents poor intake. Based on your clinical judgment, please clarify the patient's nutritional status:

• Severe malnutrition
• Other explanation of the clinical findings, please specify: ______

This illustrates a supported diagnosis plus an open alternative. It does not require inserting unsupported mild malnutrition, chronic cachexia, or age-related sarcopenia to reach a numerical target. A local template may add an appropriate inability-to-determine option. The dietitian's assessment remains clinical evidence for a provider determination; it does not independently establish the reportable medical diagnosis.

When several alternatives are genuinely supported, include them. When the supporting evidence is insufficient, revise the query or gather the missing information rather than filling the list with increasingly severe labels. “Other” does not cure an unsupported diagnosis already placed in the menu.

Yes/no: clarify existing documentation

Section V.II.B says that yes/no queries should not obtain a previously undocumented diagnosis in any setting. It identifies uses including POA, substantiating a medical diagnosis already in provider documentation, and establishing or negating a relationship between documented conditions. The relationship category also includes an appropriate question about a complication or adverse reaction. These are not an exclusive statutory list of four exceptions.

Relationship example: The admission H&P documents an E. coli urinary tract infection and an indwelling Foley catheter; the record also documents catheter exchange and antibiotics. A neutral query may cite those sources and ask whether the documented UTI is due to the catheter. Provide Yes, No, and a route for other explanation or further information. The question addresses the relationship; catheter presence alone does not establish causation.

A diagnosis in a pathologist's or radiologist's provider documentation may support a substantiation query under the brief. This is distinct from treating an inpatient diagnostic report alone as the encounter's medical diagnosis. Select the appropriate involved provider for clinical clarification and apply the setting-specific coding rules.

By contrast, a dietitian's malnutrition diagnosis alone is not a basis for a yes/no request asking the provider to agree with it. The brief directs a multiple-choice approach in that circumstance, using the ancillary assessment as evidence. Likewise, an elevated creatinine without a documented renal diagnosis does not permit a yes/no question that introduces acute kidney injury. Use a supported multiple-choice or an appropriate open-ended request.

POA needs a specific uncertainty option

POA refers to the condition's presence at the time of the inpatient admission order, including conditions arising during the preceding emergency or observation encounter. It does not mean “first written in a progress note on admission day.” Use the FY2027 POA reporting guidelines with the query brief.

For a hypothetical case, suppose the provider documents pneumonia on October 23, the admission nursing assessment on October 21 records a cough beginning before arrival, and the record leaves timing unclear. A POA query should cite the relevant documented condition, dated admission order, and pertinent earlier and later evidence, then ask whether the pneumonia was present at inpatient admission:

• Yes
• No
• Unable to determine

Additional free-text clarification can be available, but “Other” alone does not replace the specifically required Unable to determine choice. Do not preselect Yes because the patient had a cough or No because the diagnosis was documented later. The provider interprets the complete clinical course.

Interpret the response without upgrading it

“Unable to determine” means the provider cannot reach the requested conclusion. It does not mean the condition is probable, possible, or unable to be ruled out. FY2027 inpatient uncertain-diagnosis rules apply to the actual qualifying diagnosis and setting; they do not convert every uncertain reply into permission to code the proposed condition.

If an answer does not resolve the issue, evaluate it under the organization's follow-up and escalation policy. A legitimate further question may clarify specificity or new information. Repeatedly seeking a preferred answer undermines neutrality. Close an exhausted query according to policy and code from the usable record rather than converting nonresponse into agreement.

Before release, check the documentation basis, relevant evidence, permitted format, response routes, recipient, and visible wording. After response, confirm authentication and permanent-record availability. A compliant response need not be recopied everywhere when it already meets those requirements and the record is consistent. Format selection is one part of the process; the final record must still support accurate reporting.