12.1 AHIMA/ACDIS Compliant Query Standards & Ethical Principles

AHIMA Certified Coding Specialist CCS

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: ICD-10-CM Diagnosis Coding Fundamentals & UHDDS Guidelines

1.1 ICD-10-CM Structure, Formats, and Core Conventions 1.2 UHDDS Principal Diagnosis Selection Rules 1.3 Secondary Diagnoses Reporting & Present on Admission (POA) Indicators

2 Chapter 2: Circulatory, Cardiac & Vascular Inpatient Coding

2.1 Hypertension, Hypertensive Heart & Chronic Kidney Disease, and CAD 2.2 Acute Myocardial Infarction (AMI) Types & Sequencing 2.3 Heart Failure Types, Acuity & Cardiomyopathy 2.4 Cerebrovascular Disease, Acute Stroke, and Late Effects

3 Chapter 3: Respiratory, Sepsis & Infectious Conditions Coding

3.1 Sepsis, Severe Sepsis, and Septic Shock Guidelines 3.2 Pneumonias, Aspiration Pneumonia, and Influenza 3.3 COPD, Asthma, and Acute Respiratory Failure

4 Chapter 4: Renal, Endocrine, Gastrointestinal & Nutritional Disorders

4.1 Acute Kidney Injury (AKI) & Chronic Kidney Disease (CKD) 4.2 Diabetes Mellitus Types, Manifestations & Complications 4.3 Protein-Calorie Malnutrition & Endocrine Emergencies 4.4 Gastrointestinal Bleeding, Ulcers, and Acute Abdominal Pathologies

5 Chapter 5: Neoplasms, Obstetrics, Perinatal, Injury & Trauma Coding

5.1 Neoplasm Table, Primary, Secondary & Encounters for Therapy 5.2 Obstetrics, Normal/Complicated Deliveries & Puerperium 5.3 Perinatal Conditions & Congenital Malformations 5.4 Traumatic Injuries, Fractures & 7th Character Extensions

6 Chapter 6: ICD-10-PCS Architecture, Conventions & Approaches

6.1 ICD-10-PCS 7-Character System Architecture & Conventions 6.2 ICD-10-PCS The Seven Surgical Approaches 6.3 General PCS Guidelines & Multiple Procedure Rules

7 Chapter 7: ICD-10-PCS Root Operations: Cutting Out, Taking Out & Altering Body Parts

7.1 Excision vs Resection vs Destruction 7.2 Extraction, Drainage, and Extirpation 7.3 Detachment & Amputation Coding 7.4 Release vs Division

8 Chapter 8: ICD-10-PCS Root Operations: Putting In, Putting Back & Moving Body Parts

8.1 Replacement vs Supplement vs Insertion 8.2 Reposition, Transfer, and Reattachment 8.3 Bypass, Dilation, Occlusion, and Restriction

9 Chapter 9: High-Volume Inpatient Surgical & Medical Procedures in ICD-10-PCS

9.1 Coronary Artery Bypass Grafting (CABG) & Percutaneous Coronary Interventions 9.2 Total Joint Arthroplasties & Spinal Fusion 9.3 Mechanical Ventilation & Extracorporeal Therapies

10 Chapter 10: Outpatient CPT & HCPCS Level II Coding & Modifiers

10.1 CPT Evaluation and Management (E/M) Guidelines 10.2 CPT Surgical, Radiology, Pathology & HCPCS Level II Coding 10.3 CPT Modifiers in Hospital Outpatient & Professional Coding

11 Chapter 11: Inpatient Record Review, Clinical Validation & Documentation Integrity

11.1 Inpatient Health Record Analysis & UHDDS Documentation Hierarchy 11.2 Clinical Validation of Diagnoses vs Coding Compliance 11.3 Identifying Reportable Secondary Conditions & Complications

12 Chapter 12: Compliant Provider Queries & AHIMA/ACDIS Standards

12.1 AHIMA/ACDIS Compliant Query Standards & Ethical Principles 12.2 Compliant Query Formats: Open-Ended, Multiple-Choice & Yes/No 12.3 High-Impact Clinical Query Scenarios & Provider Workflow

13 Chapter 13: Inpatient Prospective Payment System (IPPS) & MS-DRG Mechanics

13.1 IPPS Reimbursement Structure & MS-DRG Grouping Logic 13.2 Complications and Comorbidities (CC) & Major CC (MCC) Impact 13.3 All-Patient Refined DRG (APR-DRG) System 13.4 Inpatient Transfer Policies, Cost Outliers & Short-Stay Rules

14 Chapter 14: Outpatient Reimbursement, Coding Edits & Fraud/Abuse Compliance

14.1 Hospital Outpatient Prospective Payment System (OPPS) & APCs 14.2 National Correct Coding Initiative (NCCI) Edits & MUEs 14.3 Hospital-Acquired Conditions (HAC) Reduction & Quality Programs 14.4 Healthcare Fraud, Abuse Laws, Audits & AHIMA Ethical Standards

15 Chapter 15: Health Information Technology, CAC, Encoders & Data Security

15.1 Electronic Health Records (EHR) & Computer-Assisted Coding (CAC) 15.2 Logic-Based Encoders, Groupers & Health Data Systems 15.3 HIPAA Privacy/Security, Cybersecurity & Internal Coding Audits

12.1 AHIMA/ACDIS Compliant Query Standards & Ethical Principles

Key Takeaways Explain This Topic AI

The joint AHIMA/ACDIS Practice Brief 'Guidelines for Achieving a Compliant Query Practice' establishes the national benchmark for provider queries, defining them as clinical communication tools designed to clarify medical record documentation for accurate, complete code assignment rather than financial optimization.

AHIMA's Standards of Ethical Coding (specifically Principles 2 and 4) mandate that coding and Clinical Documentation Improvement (CDI) professionals uphold clinical documentation integrity, strictly prohibiting any query that leads, suggests, or prompts a provider to document a specific diagnosis to enhance reimbursement or CC/MCC capture.

Compliant query triggers include conflicting documentation between providers, ambiguous or vague diagnostic statements, abnormal clinical indicators present without an associated diagnosis, unlinked cause-and-effect relationships, and undetermined Present on Admission (POA) status.

Inappropriate query practices include questioning clinical judgment, querying on clinically insignificant incidental findings, introducing unsupported diagnoses without clinical evidence in the record, and referencing financial impact, DRGs, or billing codes.

Last updated: August 2026

AHIMA/ACDIS Compliant Query Standards & Ethical Principles

AHIMA CCS Exam Focus: Mastering the principles of compliant provider queries is essential for both the Certified Coding Specialist (CCS) examination and everyday clinical practice. Candidates are tested extensively on the joint AHIMA/ACDIS Practice Brief Guidelines for Achieving a Compliant Query Practice , AHIMA's Standards of Ethical Coding , identifying legitimate clinical triggers for queries, recognizing non-compliant leading queries, and distinguishing appropriate clinical clarifications from inappropriate financial steering.

1. Regulatory Foundation and Evolution of Query Standards

In modern healthcare, the patient health record serves multiple concurrent purposes: it is a clinical document guiding direct patient care, a legal document substantiating medical decisions, a quality metric repository reflecting hospital performance, and the official evidentiary basis for medical coding and reimbursement. When clinical documentation within the record is incomplete, ambiguous, vague, or contradictory, medical coders and Clinical Documentation Improvement (CDI) specialists must bridge the gap through a formal, standardized communication mechanism known as a Provider Query .

The Joint AHIMA/ACDIS Practice Brief

To ensure uniformity and prevent abusive billing practices, the American Health Information Management Association (AHIMA) and the Association of Clinical Documentation Improvement Specialists (ACDIS) jointly established the authoritative national standard: Guidelines for Achieving a Compliant Query Practice (first issued in 2013, updated in 2016, 2019, and 2022). This practice brief governs all provider queries across all healthcare settings (inpatient acute care, outpatient clinics, emergency departments, and post-acute facilities). AHIMA / ACDIS Joint Standard

│
┌─────────────────────────┴─────────────────────────┐
▼ ▼
Clinical Integrity & Truth Non-Leading Communication
Medical record reflects true SOI/ROM • Objective clinical indicators
Accurate epidemiological data • Neutral questions
Compliant code assignment under HIPAA • Zero financial / DRG steering
Definition and Purpose of a Provider Query

Under official AHIMA/ACDIS standards, a Provider Query is defined as:

"A communication tool used to clarify clinical documentation in the health record for accurate code assignment, clinical documentation integrity, and precise reflection of the patient's severity of illness (SOI) and risk of mortality (ROM)."

Crucially, a query is not :

A mechanism to artificially maximize hospital revenue or inflate Medicare Severity Diagnosis Related Group (MS-DRG) weights.

A tool to question or challenge a physician's licensed clinical judgment.

An invitation for a provider to create diagnoses out of thin air that lack objective clinical support.

A method to bypass established ICD-10-CM/PCS coding guidelines or UHDDS definitions.

2. Ethical Standards: AHIMA Standards of Ethical Coding

Medical coders are bound by the AHIMA Standards of Ethical Coding , which establish professional obligations to maintain data integrity, adhere to official coding rules, and refuse participation in fraudulent or abusive documentation schemes. Two specific principles directly govern provider queries:

Principle 2: Quality and Integrity of Health Data

Mandate: Coding professionals must apply accurate, complete, and consistent coding practices that yield quality health data.

Application to Queries: Coders must ensure that every code assigned is supported by physician documentation in the health record. Coders must never initiate queries designed to manipulate diagnostic coding or fabricate complications simply to achieve a financial threshold.

Principle 4: Querying and Consultation

Mandate: Coding professionals must query and/or consult as needed with the provider for clarification and additional documentation to ensure proper code assignment, adhering to established query standards.

Application to Queries: Queries must be conducted in an objective, professional, and compliant manner. Coders must never present queries that lead the provider to a specific diagnosis or procedure. AHIMA Ethical Coding Principles

┌─────────────────────────────────────────┬─────────────────────────────────────────┐
│ Principle 2: Data Integrity │ Principle 4: Compliant Query │
├─────────────────────────────────────────┼─────────────────────────────────────────┤
│ • Report only documented conditions │ • Query when documentation is unclear │
│ • Refuse revenue-driven code inflation │ • Never use leading questions │
│ • Protect epidemiological truth │ • Include balanced clinical choices │
│ • Comply with official ICD guidelines │ • Base queries purely on record facts │
└─────────────────────────────────────────┴─────────────────────────────────────────┘
3. The Non-Leading Query Mandate

The central pillar of compliant query practice is the non-leading standard . A query is compliant only if it allows the provider full clinical autonomy to render their unbiased medical opinion.

What Constitutes a "Leading" Query?

A query is defined as leading (and therefore non-compliant and potentially fraudulent) if it:

Directs or prompts the provider toward a specific diagnosis or procedure: The query frames the question in a manner that nudges or pressures the physician to choose a specific clinical term (e.g., "The patient's creatinine is elevated; please document Acute Kidney Injury." ).

Contains financial, DRG, or CC/MCC references: The query explicitly or implicitly mentions financial reimbursement, relative weights, CC/MCC capture rates, case mix index (CMI), or billing edits (e.g., "Documenting severe protein-calorie malnutrition will add an MCC and increase payment by $3,200." ).

Omits reasonable alternative clinical explanations: The query provides only one desired diagnosis while ignoring other clinically plausible etiologies supported by the clinical indicators.

Fails to include non-committal options: In multiple-choice queries, omitting options such as "Other," "Clinically unable to determine," or "Condition ruled out / Not clinically significant" makes the query leading by forcing a forced-choice answer.

Pre-checks or pre-populates the provider's answer: The query template arrives with the desired answer box already marked.

Critical Compliance Rule for the CCS Exam: Any query containing references to financial impact, reimbursement, MS-DRG shifts, CC/MCC status, or quality scorecards is strictly non-compliant and violates AHIMA/ACDIS standards, regardless of clinical accuracy.

4. Legitimate Clinical Query Triggers

A provider query cannot be generated at random or simply because a coder desires higher specificity. A compliant query must be triggered by specific, identifiable clinical circumstances within the health record:

Clinical Trigger Description & Rationale Inpatient Clinical Example

Conflicting Documentation Two or more credentialed providers document contradictory diagnoses or clinical conclusions. Attending physician documents "Aspiration Pneumonia" in the discharge summary, while the consulting Pulmonologist documents "Acute Bronchitis without pneumonia."

Ambiguous / Vague Documentation Clinical documentation lacks the specificity required by ICD-10-CM/PCS to assign a precise code. Provider documents "urosepsis," "acute renal insufficiency," "respiratory distress," or "altered mental status" without further clinical clarification.

Clinical Indicators Present Without Diagnosis Diagnostic test results, vital signs, physical exam findings, and clinical treatments strongly indicate a condition that the provider failed to explicitly name. Serum potassium is 2.7 mEq/L, ECG shows prominent U waves, and patient is administered 40 mEq IV potassium chloride, but "hypokalemia" is never documented.

Undocumented Cause-and-Effect Relationship Two conditions coexist that frequently have a causal relationship, but the provider has not documented an explicit link (where ICD-10 does not establish a presumed link). Patient presents with acute pancreatitis while taking azathioprine, or acute encephalopathy in the setting of severe sepsis, but the etiology is unlinked.

Undetermined Present on Admission (POA) Status A condition is documented, but the timing of onset (present prior to inpatient admission order vs. developed hospital-acquired) is unclear. Stage 3 pressure injury is documented on hospital day 4 with ambiguous nursing intake notes regarding whether it was present at the time of admission.

Incomplete Procedural Details The operative report omits critical details required by ICD-10-PCS root operations, body part values, or approaches. Surgeon documents "excisional debridement of sacral ulcer with scalpel," but fails to state the deepest anatomical layer excised (subcutaneous tissue vs. fascia vs. muscle).

Loading diagram...

5. Inappropriate and Prohibited Query Practices

Understanding when NOT to query is just as heavily tested on the CCS exam as knowing when to query. Submitting inappropriate queries creates administrative burden, physician frustration, and significant regulatory liability during Office of Inspector General (OIG) or Recovery Audit Contractor (RAC) audits.

1. Questioning Medical Judgment

A query may seek clinical validation when a documented diagnosis appears unsupported or conflicts with the record, but it must present the record’s evidence neutrally and allow the provider to affirm, revise, or rule out the diagnosis. A query should not pressure a provider to increase severity or replace documented clinical judgment with the query professional’s preferred diagnosis.

2. Querying on Clinically Insignificant Incidental Findings

Coders must not generate queries based solely on isolated abnormal diagnostic test findings that have no documented clinical evaluation, monitoring, diagnostic workup, or therapeutic treatment (often referred to as "incidentalomas").

Example: A routine complete blood count shows an isolated eosinophil count of 6% in a patient admitted for elective total knee arthroplasty, with no symptoms, no allergic workup, and no treatment. Querying for "eosinophilia" is inappropriate.

3. Clinical Bridging ("Fishing Expeditions")

A query should not be used to introduce a new diagnosis when the record contains no relevant clinical indicators. Generating a query asking "Does the patient have sepsis?" when the patient has normal vital signs, normal white blood cell count, normal lactate, and no organ dysfunction is an unsupported, noncompliant "fishing expedition."

4. Over-Querying / Query Fatigue

Querying every minor laboratory variance or sending queries that add no meaningful clarity to the clinical picture promotes query fatigue. Query purpose and prioritization should follow compliant organizational policy, not a desired reimbursement or quality outcome. Compliant vs. Inappropriate Queries

┌─────────────────────────────────────────┬─────────────────────────────────────────┐
│ COMPLIANT QUERY │ INAPPROPRIATE QUERY │
├─────────────────────────────────────────┼─────────────────────────────────────────┤
│ • Supported by documented lab/vital data│ • Based on isolated, untreated findings │
│ • Poses neutral, non-leading questions │ • Mentions DRG, CC/MCC, or reimbursement│
│ • Offers balanced clinical choices │ • Pushes a single high-paying diagnosis │
│ • Includes an alternate response option │ • Omits supported choices or alternate response│
│ • Clarifies conflicting provider notes │ • Pressures provider toward desired answer│
└─────────────────────────────────────────┴─────────────────────────────────────────┘