7.1 AHIMA Ethical Standards & Compliant Queries

AHIMA Ethical Standards & Compliant Queries

Healthcare compliance begins with ethical coding practices. The AHIMA Standards of Ethical Coding serve as a definitive guide for coding professionals, ensuring that clinical documentation and assigned codes accurately reflect the patient's condition and the services provided, without undue influence from reimbursement motivations. A deep understanding of these standards, along with the precise mechanics of generating compliant physician queries, is essential for any coding professional and is heavily tested on the CCS-P examination.

AHIMA Standards of Ethical Coding

The AHIMA Standards outline the core principles that all coding professionals must follow. These standards emphasize honesty, integrity, and clinical accuracy. They are designed to protect the integrity of the healthcare data ecosystem, which relies on accurate coding for reimbursement, public health tracking, research, and quality measurement.

Key principles include:

• Accuracy and Completeness: Assigning codes based only on what is explicitly documented in the medical record. Coders must review the entire record to ensure all relevant diagnoses and procedures are captured accurately.
• Integrity: Never changing a code solely to increase reimbursement or satisfy facility financial goals. Codes must be justified by clinical documentation. If a code does not accurately describe the clinical scenario, it must not be reported simply because it yields a higher payment.
• Confidentiality: Protecting patient health information in accordance with HIPAA and other privacy laws. This includes ensuring that coding activities do not unnecessarily expose patient data.
• Professionalism: Maintaining current knowledge of coding guidelines, participating in continuing education, and advocating for proper documentation practices within the organization.
• Reporting Unethical Behavior: Coding professionals have a duty to report unethical coding practices through appropriate organizational channels.

Compliant Queries: The AHIMA/ACDIS Brief

A query is a communication tool used to clarify documentation in the health record for accurate code assignment. It bridges the gap between clinical language and coding classification systems. The joint AHIMA and ACDIS (Association of Clinical Documentation Integrity Specialists) practice brief provides essential guidelines on how to construct compliant queries.

When to Query

A query should be generated when the documentation is:

1. Conflicting: Two different providers document contradictory diagnoses (e.g., the attending physician documents 'pneumonia' while the consulting pulmonologist documents 'bronchitis').
2. Incomplete: Key information needed for specific code assignment is missing, such as acuity (acute vs. chronic), specificity (e.g., the specific organism causing an infection), or laterality.
3. Ambiguous: The documentation leaves doubt about the patient's condition or treatment, or uses non-standard abbreviations.
4. Inconsistent: The clinical indicators (labs, vitals, medications, imaging) do not align with the documented diagnosis. For example, the patient is receiving IV antibiotics, but no infection is documented.
5. Illegible: The provider's handwriting cannot be deciphered, rendering the documentation unusable for coding purposes.

Principles of a Non-Leading Query

The most critical rule for queries is that they must be non-leading. A query cannot tell the provider what to document or imply that a certain answer is preferred, especially if that answer leads to higher reimbursement or affects quality metrics.

• Do not state the financial impact of the query (e.g., "If you document sepsis, the hospital gets paid more").
• Do not ask questions that force a 'yes' or 'no' answer when asking for a new diagnosis.
• Do provide all relevant clinical indicators from the record to support the query. The query must present the clinical facts objectively.
• Do allow the provider to exercise their independent clinical judgment.

Formats for Compliant Queries

There are several acceptable formats for querying providers, each with specific rules to ensure they remain non-leading.

1. Multiple-Choice Queries

Multiple-choice queries are common because they are easy for providers to answer, but they must be carefully constructed. To be compliant, they must include options that allow the provider to state they don't know or the condition isn't relevant. This prevents the provider from being forced into choosing a diagnosis that doesn't fit.

Required options include:

• Other (with a blank line for the provider to specify their own diagnosis)
• Clinically undetermined (if the provider is unsure of the diagnosis based on current information)
• Not clinically significant (if the clinical indicators are present but do not represent a codable condition)
• Integral to (if the symptoms are merely part of another established condition)

Example of a Non-Compliant Multiple-Choice Query: "Is the patient's acute kidney injury due to dehydration or sepsis?" (This is leading because it limits the options to only two choices).

Example of a Compliant Multiple-Choice Query: "Based on the patient's rising BUN/Creatinine and decreased urine output, please select the most appropriate diagnosis: [ ] Acute Kidney Injury due to dehydration [ ] Acute Kidney Injury due to sepsis [ ] Acute Kidney Injury, etiology undetermined [ ] Other: ___________ [ ] Not clinically significant"

2. Open-Ended Queries

Open-ended queries allow the provider to freely document their clinical conclusion based on the presented facts. These are often considered the safest and most compliant type of query because they do not restrict the provider's options or suggest a specific answer.

• Example: "Based on the patient's WBC count of 15,000, fever of 102F, and new order for IV antibiotics, please document the diagnosis being treated."

3. Yes/No Queries

Yes/No queries have the strictest rules due to their high potential to be leading. They can only be used in very specific scenarios:

• Present on Admission (POA): To determine if a diagnosis was present at the time of admission (e.g., "Was the patient's pressure ulcer present on admission? Yes / No / Clinically Undetermined").
• Conflicting Documentation: To clarify conflicting documentation from multiple providers (e.g., "Dr. A documented pneumonia, but Dr. B documented bronchitis. Do you agree with pneumonia? Yes / No / Other: _______").
• Cause-and-Effect Relationships: To establish relationships between conditions (e.g., linking hypertension and chronic kidney disease).
• Underlying Conditions: To resolve underlying conditions if a patient has a documented manifestation but the underlying cause is unclear.

Yes/No queries cannot be used to introduce a new diagnosis that has not been previously documented in the record. Like multiple-choice queries, they should include options like "Other" and "Clinically undetermined."

Conclusion

Ethical coding is non-negotiable in the healthcare industry. Coding professionals are the gatekeepers of clinical data integrity. By adhering strictly to the AHIMA Standards of Ethical Coding and utilizing compliant, non-leading query practices, coders ensure that healthcare data is accurate, reliable, and trustworthy, which ultimately supports better patient care and appropriate reimbursement.