8.4 Multiple-Choice, Open-Ended, and Yes/No Query Design

Format Is a Compliance Decision

A provider query can be multiple-choice, open-ended, or yes/no, but the format must fit the documentation issue. The form does not make a query compliant by itself. A multiple-choice query can be leading if it lists only one severe diagnosis and weak alternatives. An open-ended query can be vague if it fails to identify the documentation issue. A yes/no query can be improper if it asks the provider to agree to a new diagnosis that is not already supported by the record. CCS candidates should evaluate both the words and the structure.

Multiple-choice queries work well when the record supports a defined set of clinically plausible answers. For example, a heart failure query may list acute systolic, chronic systolic, acute on chronic systolic, acute diastolic, chronic diastolic, combined type, other, unable to determine, or no additional clarification depending on what the record supports. The key is balance. Do not list only the option that increases severity. Do not include clinically impossible choices. Do not omit other and unable to determine when uncertainty is realistic.

Open-ended queries work well when the provider needs space to explain. They are useful for unusual presentations, broad differential diagnoses, complex postoperative relationships, unclear cause-and-effect issues, and situations where a multiple-choice list could accidentally steer the provider. A strong open-ended query still provides indicators and the specific documentation issue. It might ask, based on the indicators below, please clarify the diagnosis being evaluated and treated during this encounter. That is very different from a blank request that says, please improve documentation.

Yes/no queries require the most caution. They may be appropriate in limited situations, such as confirming a cause-and-effect relationship when both conditions are already documented, confirming whether a documented condition was present on admission when the record contains timing indicators, or confirming a diagnosis already documented by one provider when another provider's documentation conflicts. Facility policy matters. A yes/no query should not introduce a new diagnosis and ask the provider to agree when the diagnosis has not been documented or is not well supported.

Query Format Selection Table

A multiple-choice query for sepsis should not be written as sepsis, unable to determine. That is a funnel. If the record could support sepsis, localized infection without sepsis, systemic inflammatory response due to a noninfectious cause, other diagnosis, no additional diagnosis, or unable to determine, the options should reflect that clinical range. If the indicators are weak or the diagnosis is not plausible, the query should not be sent.

An open-ended query is often better for clinical validation. Suppose the provider documents acute respiratory failure, but the patient only had brief postoperative oxygen, no distress, no abnormal blood gas, and rapid return to room air. A query that says, please clarify the diagnosis supported by the respiratory findings, may be more neutral than a yes/no question asking, did the patient have acute respiratory failure? The provider can revise, confirm, or explain based on clinical judgment.

For yes/no design, consider a diabetic patient with documented diabetic neuropathy in one note and peripheral neuropathy in another. If the record contains diabetes, neuropathy, treatment, and a documentation inconsistency, a yes/no query asking whether the neuropathy is related to diabetes may be acceptable under facility policy. The query should include the relevant documentation and allow the provider to state no, other, or unable to determine. It should not say, please agree this is diabetic neuropathy for coding.

Format Selection Checklist

• What exact coding fact is missing or unclear?
• Are there multiple clinically reasonable answers?
• Would an option list narrow the provider's thinking too much?
• Is the proposed diagnosis already documented or strongly supported?
• Does facility policy allow this query type for this situation?
• Are other, no additional diagnosis, and unable to determine included when appropriate?
• Is the provider response authenticated and retained?

Verbal queries can be practical in fast-moving inpatient settings, ED encounters, and concurrent CDI work, but they carry audit risk if not documented. A compliant verbal query should be recorded with the same essential elements as a written query: indicators, question, provider response, date, identity of participants, and authentication according to policy. A coder should not rely on memory or informal messages when the clarification affects coding.

The exam may present four query drafts and ask which is compliant. Avoid the one that uses payment language, provides only one answer, includes no clinical indicators, or asks the provider to agree to a diagnosis that is not supported. Choose the one whose format fits the issue and whose response options preserve independent provider judgment.