The 2026 ACDIS/AHIMA Guidelines for Achieving a Compliant Query Practice represent more than a routine update. They redefine compliant querying for a healthcare environment increasingly influenced by clinical validation reviews, risk adjustment, quality reporting, and AI-driven documentation tools.
Several key themes emerge from the new guidance.
Here are nine key changes every organization should know:
- Compliant querying now extends well beyond inpatient CDI. Quality professionals, case management professionals, utilization management professionals, HCC coders, revenue cycle teams, consultants, vendors, and technology platforms generating documentation clarification requests are all expected to meet the same core requirements. If a communication functions as a query, it should comply as a query.
- The guidelines introduce the concept of substantial compliance. This recognizes that minor technical deviations should not automatically render a query noncompliant when core principles are met.
- The guidelines are not a stand-alone basis for denials or audit findings. The document explicitly states they should not be used alone to justify claim denials, payment recoveries, or adverse audit findings.
- Providers retain full authority over clinical indicators. There is no required number of indicators needed to support a query, and providers ultimately determine clinical significance.
- Query titles must remain neutral. Visible query names cannot direct providers toward a specific diagnosis. For example, “CDI Provider Query: Respiratory Status” is compliant, while “Query for Acute Hypoxic Respiratory Failure” is not.
- The same compliance standards now explicitly apply to technology. This includes CAPD, CAC, AI-generated queries, EHR alerts, prompts, nudges, and large language model applications.
- Organizations must govern their query technology. This means providing oversight, auditing, governance, and education for any tool that generates documentation clarification requests.
- Reviewing prior encounters is appropriate, within limits. Looking back to establish baseline conditions, support specificity, or clarify active versus historical diagnoses is appropriate when supported by a current clinical trigger.
- Systematically “mining” prior records is not appropriate. Searching prior records solely to import diagnoses into the current encounter falls outside compliant practice.
Ultimately, the 2026 update reflects healthcare’s movement toward clinical validity, defensible documentation, and ethical data integrity. Query practice is no longer simply a CDI function. It is an enterprise-wide responsibility requiring collaboration among CDI, coding, quality, compliance, physician leadership, and technology teams.
Leadership Question: If your AI-generated prompts, HCC clarification requests, CDI queries, and quality documentation reviews were audited today, would they all meet the same compliant query standards?
The 2026 ACDIS/AHIMA Query Practice Guidelines have officially expanded compliant querying beyond CDI. AI-generated prompts, HCC clarification requests, quality documentation reviews, and technology-assisted queries are now clearly within scope.
Key takeaway: If it functions like a query, it must comply like a query.
Is your organization ready?
Reference:
American Health Information Management Association and HCPro, LLC. (2026). Guidelines for Achieving a Compliant Query Practice. Retrieved 8/25/2026 from: ACDIS/AHIMA Guidelines for Achieving a Compliant Query Practice—2026 Update | ACDIS
