10.1 Compliant versus Leading and Other Noncompliant Queries

10.1 Compliant versus Leading and Other Noncompliant Queries

Quick Answer: A compliant query is nonleading, cites patient-specific clinical indicators with their location in the record, never mentions reimbursement or quality-outcome impact, and leaves independent clinical judgment with the treating provider. Leading is the subset of noncompliance that steers the provider toward an unsupported or preferred diagnosis or procedure. A query can fail the 2026 brief without being leading—for example, when indicators are generic, interpreted by the query professional, or missing sources. Do not highlight, bold, underline, or otherwise emphasize answer options.

Why Domain III tests this distinction

The Association of Clinical Documentation Integrity Specialists (ACDIS) Certified Clinical Documentation Specialist (CCDS) examination for inpatient practice scores medical record documentation as 23 of 120 scored items. Independent OpenExamPrep teaching for this section uses the August 2026 ACDIS and American Health Information Management Association (AHIMA) Guidelines for Achieving a Compliant Query Practice as the current professional standard. That update supersedes the 2022 edition. This chapter is not an ACDIS or AHIMA product and does not claim official approval, review, or partnership with either organization.

On the exam and on the unit, the trap is collapsing every bad query into the single word leading. The 2026 brief draws a second drawer: a query may be noncompliant without being leading. Drawer one is influence—did the title, stem, emphasis, or incentive language push a preferred answer? Drawer two is construction—even a politely worded, open-ended question fails if it is not sourced, not specific to this patient and this stay, or if the query professional interpreted the data instead of quoting or listing it.

The four-part 2026 core test

A compliant query, as the 2026 brief defines the term, meets all four of these core requirements. Substantial compliance with this core—not a hunt for isolated formatting nits—is the standard the brief sets for external review. Isolated technical misses, such as a missing source date on one of several otherwise cited indicators, do not by themselves make a query noncompliant when the core four are satisfied. Section 10.2 develops that review standard. This section stays on how to recognize leading versus other noncompliance in the query you actually send.

Medicare Severity Diagnosis-Related Group (MS-DRG) assignment, complication or comorbidity (CC) or major CC (MCC) capture, and Patient Safety Indicator (PSI) profiles are downstream uses of coded data. They are not allowed to appear in the query that produces that data.

What "leading" means

A query is leading when it directs or influences the provider toward a specific diagnosis or procedure instead of leaving room for independent clinical judgment. Influence can be explicit ("please document metabolic encephalopathy as the cause of the confusion") or implied (listing only the diagnosis the specialist hopes to capture, stacking that diagnosis under an arrow, or wrapping the ask in payment or quality language).

Leading is not the same as listing clinically supported answer choices. The 2026 brief treats options that are substantiated by sourced indicators as clarification, not as the introduction of new facts. Offering a diagnosis the chart already supports, plus "Other, please specify" or similar open-ended wording, is not leading merely because a diagnosis appears as a choice. Offering a high-severity diagnosis when the cited findings cannot reasonably support it, and then asking the hospitalist to "confirm the MCC," is leading: the option is unsupported and the ask prefers a reimbursement result.

Leading patterns you should be able to name

• Preferred-diagnosis steering. The statement names the diagnosis the query professional wants rather than asking what condition is being evaluated or treated.
• Unsupported option sets. Choices the cited indicators cannot reasonably support, or a single favored choice dressed up as multiple choice.
• Incentive language. Any mention of MS-DRG shift, CC/MCC capture, PSI impact, mortality index, length of stay, case-mix, or denial risk.
• Emphasis as a pointer. Highlighting, bolding, underlining, arrows, colored fonts, or asterisks on one answer option. The 2026 brief is categorical: highlighting should never be used within the answer options of a query. Emphasis in the body is also inappropriate when it could be read as pointing to a preferred answer. Preserving emphasis that already existed in the source display (for example, a laboratory system that flags an abnormal value in the original view) is a different issue; organizational policy may leave that formatting or strip it. You do not add emphasis of your own.
• Interpretive labels. Replacing the record's numbers and quoted findings with the query professional's diagnosis. If two documented blood pressures are 76/40 mm Hg, the indicator is the blood pressure and its source—not "shock" invented in the query body.
• Visible titles that name the desired diagnosis. A tracking title the provider sees as "Query: add metabolic encephalopathy now" influences the answer. A title such as "CDI provider query — mental status" does not.

Verbal queries can be leading for the same reasons as written ones. If the hallway conversation is "we need you to add severe malnutrition for the MCC," writing a clean template afterward does not convert that encounter into a compliant query. Record the nonleading statement actually used, the indicators presented, and the options, if any, and get the provider's response into the permanent health record before coding.

Noncompliant without being leading

The 2026 brief states that a query can be considered noncompliant without being leading. Compliance still requires that clinical indicators are specific to the patient and episode of care, support a more complete or accurate diagnosis or procedure (or identify a documented diagnosis that lacks support), and are free from subjective interpretation by the query professional. Section V of the brief is equally direct: if required elements are missing, the query may be noncompliant even if it does not overtly direct or lead the provider to a specific answer.

That second drawer includes:

• Generic or population-level indicators. "Elderly patient with fever" is not a sourced, patient-specific indicator set. You need this patient's temperature, white-cell count, cultures, imaging, and where those facts live in the record.
• Missing location citations. Indicators without a place to look (note type, date, and author when applicable) fail the sourcing rule even if the wording is polite and open-ended.
• Subjective interpretation. Calling a creatinine of 1.9 mg/dL "acute kidney injury" inside the indicator list is interpretation. The indicator is the value, the documented baseline if present, and the source. The provider names the diagnosis.
• Clinically irrelevant options. A multiple-choice list that includes a condition the indicators cannot support is a construction failure. It may also be leading if the unsupported option is the one the program wants.
• Yes/no used to introduce a new diagnosis. That format is reserved for already-documented conditions or relationships, including present on admission (POA) with an unable-to-determine choice. Using yes/no to plant a never-documented diagnosis is noncompliant and is often leading as well.
• Quotation and sourcing gaps. Direct pulls from the record may be placed in quotation marks when they are unedited. Every indicator still needs a source so the provider can go look.

Independent judgment is a design feature

Leaving independent clinical judgment with the provider is one of the four core requirements, not a courtesy. In practice that means a nonleading statement that names the documentation gap without naming the desired code; at least one clinically valid option plus an open-ended Other (or similar) on multiple-choice queries; no auto-populated answer and no pre-checked box; and genuine acceptance of "unable to determine," "not clinically significant," or an alternative diagnosis when the provider selects it. The 2026 brief does not require a minimum option count beyond one clinically valid choice plus an open-ended alternative. Repeating the same query to a different attending in order to shop for a yes is a pattern-and-intent problem, not a productivity win.

Worked inpatient examples (original teaching cases)

Scenario A — leading. Night-shift clinical documentation integrity (CDI) sends: "Please document acute on chronic systolic heart failure as an MCC. Echo shows reduced function." An echocardiogram may exist, but the query names the preferred diagnosis, labels it an MCC, and does not source the study date, the documented ejection fraction, or the current-stay symptoms and treatment. Failures: leading, reimbursement language, weak sourcing.

Scenario B — noncompliant, not necessarily leading. A retrospective query asks, "Can you further clarify the patient's nutritional status?" and adds, "malnutrition is common in this DRG." No preferred diagnosis is named in the options, but there are no patient-specific weights, intake notes, or physical findings, and the body mentions a DRG. Failures: missing patient-specific indicators and reporting-language. The open-ended wording does not rescue it.

Scenario C — compliant shape. Indicators: hospitalist progress note (hospital day 2) documents new confusion and a sodium of 118 mEq/L; nursing flowsheet (same date) records seizure precautions; 3% saline is ordered. Statement: "Based on these findings, please clarify the condition you are evaluating and treating." Options include a clinically relevant diagnosis those findings can support, an alternative the same findings could also support, and "Other explanation of clinical findings, please specify." No DRG talk, no highlighted option, and no heading that already announces the diagnosis as a fact.

Audit the query before you send it

Walk the four-part test in order. If the title, stem, or options push one diagnosis, rewrite. If the indicators could belong to any patient on the unit, source this chart. If any sentence mentions payment, quality stars, PSI, or audit risk, delete that sentence—not the diagnosis, the sentence. If a provider could not reasonably disagree or offer another explanation, you have not left independent judgment. Treat the highlighting rule as a hard stop: never emphasize answer options. If the query tool auto-bolds the first choice, that is a technology-compliance problem, not a style preference.

Uncertain-diagnosis wording (possible, probable, likely) belongs only when the inpatient record and ICD-10-CM Official Guidelines for Coding and Reporting support that use—typically when the provider already used uncertain language that is missing at discharge, or when treatment is underway without a confirmatory test. Do not use a leading "please document probable X" as a shortcut to a CC.