8.4 When Queries Are Not Appropriate

8.4 When Queries Are Not Appropriate

Quick Answer: Do not query when the finding was not evaluated, treated, or monitored; when the sign or symptom is integral to a disease already documented; when ICD-10-CM's "with" convention already presumes a link the record has not broken; when there is no business need; or when the answer would not clarify the clinical picture. Never send a query whose real purpose is to raise a DRG.

The 2026 ACDIS/AHIMA brief's "when to query" list is followed immediately by a limiter: queries are not necessary for every discrepancy, and organizational policy may decline a query when there is no business need or when the requested information would not add clarity. This independent OpenExamPrep section turns that limiter into an inpatient CCDS skill. Knowing when to stay quiet is as testable as knowing when to send the form.

Not evaluated, treated, or monitored

UHDDS additional diagnoses are conditions that required clinical evaluation, therapeutic treatment, diagnostic procedures, extended length of stay, or increased nursing care or monitoring. A sodium of 132 milliequivalents per liter that is called "incidental," not repeated, not treated, and not mentioned again does not become reportable hyponatremia if you extract a provider sentence. Querying that sodium wastes the attending's time and invites a code that will not survive a denials review.

The same refusal applies to a remote, inert "history of" that has no bearing on this stay, a problem-list line nobody addressed, and a prior-encounter diagnosis imported without a current trigger. The 2026 brief's Section X calls systematic hunting through old records for diagnoses to drop into the current encounter mining when no current indicator prompted the review. A prior echocardiogram may support a query about today's heart-failure type if today's notes already show heart failure. Last year's malnutrition diagnosis does not, by itself, justify a malnutrition query on a patient who is eating well and was never assessed for nutrition this stay.

Ask a practical question: if the provider answered exactly as you hope, would the condition still fail UHDDS? If yes, do not query.

Integral signs and symptoms

ICD-10-CM Section I.B.5 (conditions that are an integral part of a disease process) tells coders not to assign integral signs and symptoms of a definitive diagnosis as additional codes unless the classification says otherwise. Dyspnea is integral to acute respiratory failure. Nausea is integral to gastroenteritis. Chest pain is integral to an identified acute myocardial infarction. Querying the attending to "add nausea" as a CC when gastritis is already documented does not clarify the clinical picture. It attempts to manufacture a secondary diagnosis the guidelines would drop.

Integral is not the same as associated but separately reportable. Acute blood-loss anemia with gastrointestinal bleeding is often separately significant because it is evaluated and treated (transfusion, monitoring). Hypoxia that is the defining feature of documented acute respiratory failure is not a second disease. If you cannot explain why the extra code would survive the integral-symptom rule, you do not have a query.

Optional query-response language in the 2026 brief even includes choices such as "integral to" or "inherent to." That option exists so a provider can decline to turn a feature of the disease into a standalone diagnosis. It is not a prompt to go hunting for integral symptoms to code.

Presumed "with" linkage the guidelines already allow

ICD-10-CM's "with" convention (Section I.A.15) means "associated with" or "due to" when that word appears in a code title, the Alphabetic Index, or a Tabular instructional note. The classification presumes the causal relationship unless the documentation clearly states the conditions are unrelated, or unless a different guideline demands an explicit link (the sepsis-organ-dysfunction linkage is the famous exception).

So if diabetes and chronic kidney disease are both documented, and the Index links diabetes with chronic kidney disease, you do not query solely to obtain the words "CKD due to diabetes." The link is already presumed. You query only if the record unlinks them ("CKD from recurrent obstruction, not diabetes"), if a required relationship is not covered by "with," or if a needed specificity (CKD stage, diabetes type) is missing.

CDI programs that still send a "please link X and Y" query on every presumed pair are practicing 2015 habits, not 2026 brief-plus-guideline habits. The exam will offer you a tempting query that adds no clinical clarity because the classification already did the work.

No business need, and no added clarity

"Business need" in the 2026 brief is not a synonym for "this would pay better." It means the organization has a legitimate documentation, coding, quality-abstract, or patient-care reason to seek the clarification, consistent with policy. There is no business need to query:

• a typographical inconsistency that does not change any code or clinical meaning ("left" versus "L" when laterality is otherwise obvious and uncontested);
• a second copy of a diagnosis that is already reportable from another treating-provider note;
• a preference for one synonym over another when both code to the same concept;
• a request that the attending retype a query answer that is already authenticated in the permanent health record and is not contradicted;
• a quality nurse's desire to re-ask a question the provider already answered, solely because the first answer was not the preferred quality result.

"Would not clarify the clinical picture" overlaps with those examples and adds a clinical filter. If the missing word does not change the understanding of what is wrong with the patient, what was done, whether it was present on admission, or whether a documented diagnosis is valid, the query is optional at best and inappropriate at worst. The brief says query professionals should generate queries only when present (and relevant historical) clinical data support the need and the response options are appropriate. A query with no legitimate options is not a query you should send.

Still inappropriate even when a trigger looks nearby

Several refusals sit next to Section 8.3 triggers and are easy to reverse on a multiple-choice item:

• Reimbursement or quality language, or a query that exists only to raise a DRG or to defend a mortality index, remains forbidden even if indicators could have supported a clinical query you never actually wrote.
• Leading wording, highlighted answer options, and diagnosis-directing titles are not saved by a real clinical need. Rebuild the query or do not send it.
• Yes/no to introduce a new diagnosis, or yes/no based solely on RD or wound-nurse diagnostic labels, is the wrong format. Wrong format is not "better than nothing."
• Physician advisors who did not care for the patient cannot answer the query for coding purposes.
• Technology prompts that fail the same tests are still noncompliant. The 2026 brief applies the same standard to human and generated queries.

Worked refusals

Integral symptom. The discharge summary lists acute calculous cholecystitis. Nursing noted right-upper-quadrant pain and nausea, both treated as part of the biliary pathway. Querying to add nausea as a secondary diagnosis would not clarify anything the cholecystitis code does not already contain.

Presumed with. Type 2 diabetes and CKD stage 3 are both documented throughout the stay. No note says the kidney disease has another cause. Querying "Is the CKD due to diabetes?" is unnecessary. Querying "What is the CKD stage?" would have been unnecessary too, because stage 3 is already written. If the notes had said only "CKD" without a stage, specificity—not linkage—would have been the legitimate trigger.

No business need. Two progress notes say "acute hypoxic respiratory failure" and the discharge summary says the same. An encoder hint prefers the phrase "acute respiratory failure with hypoxia." There is no clinical gap. Do not query for synonym preference.

Would not clarify. A radiology addendum corrects a laterality typo that the attending's notes, the consent, and the operative report already agree on. The picture is clear. Facility policy may still want the report fixed as a record-integrity issue; that is an amendment workflow, not a diagnosis query.

How 8.3 and 8.4 fit together

Use Section 8.3 when current indicators support a missing, unusable, conflicted, or unsupported statement that would change diagnosis, procedure, POA, or clinical validity. Use this section when the missing words would not be reportable, would duplicate a guideline convention, would restate an integral feature, or would exist only to move money. The CCDS exam's analysis items often show a tempting CC/MCC sitting on the wrong side of that line. The professional answer is to leave it there.