On September 1, 2026, AHIMA and the Association of Clinical Documentation Integrity Specialists (ACDIS) released their 2026 update to the Guidelines for Achieving a Compliant Query Practice, replacing all prior editions. The update’s headline point is simple but consequential for anyone running agentic AI in a CDI program: a query is a query no matter where it comes from. Rana Abuzir, AHIMA’s director of health information practice advancement, put it plainly in the release, saying the standard for compliance “should remain the same” whether a query comes from a person or from technology.
That line matters because CDI teams are now deploying point-of-care prompts, nudges, and advisories generated by AI tools embedded in the EHR, and those outputs have mostly lived in a gray area — labeled as something other than a “query” and therefore assumed to sit outside the compliance rules written for human-authored ones. The 2026 update closes that gap.
What the 2026 Update Actually Changes
The guidelines define a query by function, not by format or label. If a communication presents a provider with a specific diagnosis or documentation option tied to a specific encounter, it is a query — regardless of whether it is labeled a prompt, a nudge, an advisory, or an alert, and regardless of whether a person or an algorithm generated it. Passive reference material that doesn’t steer the provider toward a particular answer is not a query. When a tool’s output is ambiguous, the guidance direction is to treat it as a query and hold it to query standards.
The guidance covers inpatient, outpatient, ambulatory, and professional-fee settings, with specific new attention to outpatient and ambulatory workflows — settings where AI-driven documentation tools have expanded fastest and where formal query policies have historically been thinner than on the inpatient side.
Why This Lands Differently for Agentic AI CDI Tools
Vendor and EHR-embedded CDI tools are not compliant by default just because a human reviews the chart afterward. Analysis of the draft guidelines published ahead of the September release laid out what a compliant AI-generated query needs before it ever reaches a provider: indicators sourced to actual clinical documentation rather than inferred from pattern-matching; nonleading titling; answer options that are clinically relevant and include a genuine “other” or “unable to determine” path; no visual or structural steering toward a preferred answer; and no automatic re-query without new clinical evidence to support it.
The Accountability Question Doesn’t Move to the Vendor
Organizations remain accountable for every query their systems deliver, whether a CDI specialist typed it or an AI tool generated it. That accountability can be satisfied through pre-delivery review of AI-drafted queries or through regular structured audits of what the tool is actually producing — but it cannot be satisfied by assuming a purchased platform has already solved compliance internally.
A Convergence With Risk-Adjustment Oversight
The timing lines up with separate scrutiny from the HHS Office of Inspector General, whose Medicare Advantage compliance guidance has flagged AI-generated prompts that encourage diagnoses a patient may not actually have. CDI analysts covering the update have pointed to that overlap as a signal that AI query practices are drawing attention beyond professional best-practice guidance — into territory regulators are already watching on the risk-adjustment side.
Five Checks Before an AI-Drafted Query Reaches a Chart
Based on the pre-flight criteria CDI analysts have outlined for the updated guidelines, a defensible review process for AI-generated queries should confirm:
- Sourced indicators — the clinical basis cited in the query traces to real documentation in that encounter, not an inferred pattern.
- Nonleading phrasing — the title and framing don’t point toward a specific diagnosis.
- Complete answer options — choices are clinically appropriate and include a legitimate “other” or “unable to determine” path.
- No structural steering — formatting, order, or emphasis doesn’t nudge the provider toward one answer.
- No evidence-free re-querying — a declined or answered query isn’t resent without new clinical information.
What CDI Programs Should Do Now
Programs running or piloting AI-assisted CDI tools have a reasonable amount of work ahead: mapping every AI-generated prompt type currently live in their EHR against the five checks above, confirming physician advisors are reviewing AI query logic as part of governance rather than only reviewing outcomes, and building (or requesting from vendors) an audit trail that shows which queries were AI-drafted, which were reviewed before delivery, and what changed in review. None of that requires slowing adoption of agentic AI in CDI — it requires treating the AI’s output with the same query discipline CDI specialists have applied to their own writing for years.
Coding and CDI teams evaluating where AI fits into that discipline — and where human review still has to sit in the loop — can see how Medikode’s automated medical coding platform approaches that balance for compliant, auditable coding and documentation workflows.