Logo for AiToolGo

Achieving a Compliant Query Practice: Best Practices for Clinical Documentation Integrity

In-depth discussion
Academic
 0
 0
 5
This AHIMA-ACDIS practice brief establishes industry-wide best practices for the clinical documentation integrity (CDI) query process. It defines queries, outlines general and compliant query standards, specifies when to query and when not to, and provides guidance on multiple-choice answer options, clinical indicators, problem lists, query templates, provider education, and the appropriate use of prior encounter information. The document serves coding, CDI, and compliance professionals and external reviewers across all healthcare settings.
  • main points
  • unique insights
  • practical applications
  • key topics
  • key insights
  • learning outcomes
  • • main points

    • 1
      Provides a comprehensive, structured framework covering definitions, standards, when to query, when not to query, and templates
    • 2
      Explicitly addresses compliance concerns such as leading queries, prohibited inclusion of reimbursement or quality impact, and query fatigue
    • 3
      Anchors guidance to official sources (ICD-10-CM/PCS Official Guidelines, AHA Coding Clinic) and the UHDDS requirements
  • • unique insights

    • 1
      Distinguishes 'unable to determine' from 'unable to rule out' and 'possible' as non-synonymous options, with guidance on when each is appropriate in POA and yes/no queries
    • 2
      Clarifies the difference between code accuracy and code specificity, noting that coders are not required to report the most specific code available
  • • practical applications

    • Serves as a directly applicable reference for drafting and auditing compliant query policies, designing query templates, training CDI and coding staff, and supporting compliance reviews or third-party audits.
  • • key topics

    • 1
      Query definition and general query standards
    • 2
      Compliant query construction: multiple-choice options, clinical indicators, non-leading statements
    • 3
      When to query and when not to query, including query fatigue considerations
    • 4
      Query template standards, problem list guidelines, and provider education
    • 5
      Appropriate use of prior encounter information in current queries
  • • key insights

    • 1
      Consolidates industry-consensus compliance standards for CDI queries into one authoritative reference
    • 2
      Offers concrete rules for avoiding leading queries and impactful titles, reducing audit and denial risk
    • 3
      Provides clear boundaries between legitimate review of prior encounters and prohibited 'mining'
  • • learning outcomes

    • 1
      Understand the definition of a clinical documentation query and the standards for constructing compliant, non-leading queries
    • 2
      Identify appropriate circumstances for issuing or withholding queries, including avoidance of query fatigue
    • 3
      Apply guidance on query templates, clinical indicator inclusion, and the permissible use of prior encounter information
examples
tutorials
code samples
visuals
fundamentals
advanced content
practical tips
best practices

“ Introduction and Purpose of the Practice Brief

The 2022 update of the Guidelines for Achieving a Compliant Query Practice, jointly issued by AHIMA and ACDIS, provides best-practice standards for the clinical documentation integrity query process. Its guiding goal is to ensure that the clinical documentation in the health record accurately represents the patient's clinical status. The brief serves coding and CDI professionals, physician advisors, and other stakeholders across inpatient and outpatient settings, as well as external reviewers such as payers, auditors, and the Office of Inspector General. It implements the ICD-10-CM/PCS Official Guidelines for Coding and Reporting and AHA Coding Clinic advice. Its applications include orienting staff, developing audit standards, updating policies, standardizing practices across the industry, supporting compliance and legal matters, and educating team members on how compliant querying affects organizational and professional billing. This update supersedes all prior versions.

“ Defining the Query and Key Terminology

A query is defined as a communication tool or process used to clarify health record documentation so that diagnosis, procedure, and service codes accurately reflect a single encounter. Queries may be initiated by a healthcare professional or generated automatically by a computer system. Terms such as clarification, prompt, nudge, or alert may describe a query; if the communication meets the definition, it is a query. Ambiguous documentation is documentation that fails to reflect the provider's intent, affects the clinical picture or code accuracy, or prevents code assignment. Query professionals (QPs) include coding, CDI, and physician advisor staff, as well as anyone who initiates clarification communication. Any QP may initiate a query when following these compliant guidelines. The term 'provider' refers to a physician or qualified practitioner legally accountable for establishing a patient's diagnosis, consistent with the ICD-10-CM Official Guidelines.

“ General Query Standards and Requirements

Every query must be compliant with the brief, clear, and concise. When clinical information is pulled from the record, it should be quoted and its source identified. Query content must include applicable clinical indicators from the health record, presented without subjective interpretation by the QP and without reference to reimbursement, quality measures, or other reportable data. Multiple-choice answer options should include only clinically relevant choices supported by the record, plus an 'other' option that lets the provider customize a response. Options such as 'unable to determine,' 'not clinically significant,' or 'unable to rule out' may be used where appropriate, but 'unable to determine' is not synonymous with 'possible,' 'probable,' or 'unable to rule out.' 'Unable to determine' is required in present-on-admission (POA) and yes/no queries. Answer options have no required minimum or maximum number and need not follow a particular order.

“ When to Query and When Not to Query

Queries are appropriate to support clinically evident conditions meeting UHDDS requirements that lack documentation; resolve conflicting provider documentation; clarify the reason for an encounter; validate diagnoses not clinically supported; confirm findings from licensed practitioners who are not providers; establish cause-and-effect relationships; add clinically supported specificity or acuity; determine whether a 'history of' condition is active; support POA assignment; rule diagnoses in or out; clarify procedure scope; clarify complications; and address unaddressed diagnoses in signed ancillary notes. Queries should not be sent for every discrepancy, as this promotes query fatigue. Do not query when the provider cannot clarify based on the existing record, when documentation already supports a valid code without indication of greater specificity, or when clinical data does not fully support the answer choices. Code accuracy, which is distinct from specificity, is governed by the requirement to report codes to the highest supported character level.

“ Principles of Compliant Query Construction

Compliant queries follow several tenets. Multiple-choice options must be supported by clinical indicators within the record, and any diagnosis not already documented must be supported by indicators included in the query itself. Query statements must be non-leading, clear, concise, and specific to the clinical scenario. Query titles visible to providers must also be non-leading and must not reveal reimbursement or quality impact, specific diagnoses not in the record, or the desired response. Clinical indicators must be specific to the patient and episode of care, support a more complete or accurate diagnosis or procedure, and, where a reported diagnosis is unsupported, meet clinical validation requirements. Uncertain-diagnosis terminology should rarely be used in the inpatient setting unless the provider has already documented uncertainty, though limited exceptions exist when concrete confirmatory data is absent, such as ATN without biopsy.

“ Problem List Considerations

A problem list records active diagnoses relevant to the current episode of care. Organizations should establish policies defining who may update the problem list after a query response. When selecting diagnoses and updating the list, identifiers that reflect financial or quality impact, such as relative weights, complications, PSIs, HACs, MCCs, CCs, HCCs, or mortality variables, should not be visible.

“ Query Template Governance and Design

Organizations should establish policies for creating, reviewing, and updating query templates, ideally on an annual schedule or when processes change, with provider and interdisciplinary input as appropriate. Templates should include patient identification when not auto-populated, editable fields, concise wording, and a non-descriptive topic title that does not name an undocumented diagnosis. Templates should accommodate clinical indicators with record citations and offer only clinically credible answer options worded to enable accurate code assignment. Instructions for template use should be provided.

“ Use of Prior Encounter Information in Queries

Code assignment is based on the current encounter, but prior documentation may support a compliant query when clinically pertinent. Appropriate uses include clarifying the presence or specificity of a current diagnosis such as heart failure type or CKD stage, referencing treatments or diagnoses tied to the current encounter, establishing a patient baseline, determining cause-and-effect relationships, clarifying etiology, verifying POA status, and clarifying historical conditions no longer present. Mining, which means reviewing prior records without a trigger in the current encounter, is not compliant. Queries drawing on prior records must be justified by a current-encounter trigger.

“ Provider Education and Ongoing Training

Provider education is essential because queries alone may not convey how to deliver effective clinical documentation integrity. Organizations should offer regular education and examples so providers understand their role and become comfortable reading and responding to queries. Case studies using de-identified actual queries are an effective teaching method.

“ Conclusion and Implementation Considerations

The Guidelines for Achieving a Compliant Query Practice (2022 Update) provides a unified framework for compliant, non-leading, clinically supported documentation clarification. Organizations should use it to develop and audit query policies, train staff and providers, standardize templates, and support compliance and legal review. Consistent adherence protects the accuracy of the health record, the integrity of coded data, and the credibility of the organization's clinical documentation program.

 Original link: https://ahima.org/media/51ufzhgl/20221212_acdis_practice-brief.pdf

Comment(0)

user's avatar

      Related Tools