Query and Documentation Clarification Boundary

When a Query Is Needed

A provider query is a routine communication asking for clarification when the health record does not clearly support code assignment. AHIMA's practice guidance identifies several legitimate triggers — documentation that is incomplete, conflicting, ambiguous, illegible, or clinically inconsistent with the rest of the record.

Typical exam triggers:

• Two physicians document different diagnoses for the same episode (conflicting).
• The provider documents a condition but no acuity, stage, or laterality needed for a valid code (incomplete).
• Clinical indicators (labs, vitals, treatment) strongly suggest a condition the provider never named (clinically inconsistent) — query, do not assume.
• An operative note omits the approach or device required for an ICD-10-PCS code (incomplete).

A query must be patient-specific, anchored to documentation in the record, and phrased so the provider remains the clinical decision-maker. It presents the relevant facts and asks for clarification.

Not every gap warrants a query, and the CCA tests that judgment too. A query is generally unnecessary when the missing detail does not affect code assignment, when the answer is already obvious from the record read as a whole, or when facility policy and the guidelines let you code what is documented (for example, coding a symptom in an outpatient setting when no confirmed diagnosis exists). Over-querying is itself a problem: it burdens providers and can appear to pressure documentation. The skill is recognizing the narrow band of situations where the record genuinely cannot support an accurate code without clarification.

Queries can be concurrent (sent while the patient is still being treated, common in inpatient settings) or retrospective (after discharge but before or after billing). Concurrent queries tend to yield better documentation because the provider still remembers the patient. Either way, the trigger is the same: a documentation gap material to coding, not a desire for a particular code.

The channel for a query also matters for compliance. A query may be written (paper or electronic) or verbal, but a verbal query and its answer must be documented so the basis for the final code is traceable. The provider's clarification belongs in the legal health record — typically as a progress note, addendum, or signed query response — rather than living only in an email thread or a coder's private notes. A code supported only by an undocumented verbal exchange will not survive an audit, which is exactly the kind of compliance gap the CCA tests in its scenarios about record integrity.

The Compliance Boundary

The defining rule of a compliant query is that it is non-leading: it must not suggest a specific diagnosis, point toward a higher-weighted CC/MCC, or hint at a reimbursement or denial outcome. A query written to "get" a particular code is non-compliant even if the resulting code happens to be correct.

What a Coder May Never Do

• Diagnose from lab results, imaging impressions, nursing notes, or problem lists beyond what guidelines permit.
• Write the desired answer into the query ("Doesn't this look like sepsis?").
• Query solely because a higher-paying code might be possible.
• Alter or add to the provider's documentation.

CCA compliance scenarios almost always reward the ethical boundary: interpret and clarify, never invent. When in doubt, the supported, documented answer beats the lucrative one.

Query Formats and Documentation Standards

AHIMA recognizes several compliant query formats, and the CCA may ask which is appropriate for a given situation. An open-ended query asks the provider to describe or clarify in their own words and is the least leading. A multiple-choice query is acceptable only when the options are clinically reasonable, include choices such as "other" and "clinically undetermined," and are all supported by the record. A yes/no query is the most restricted and is allowed only in narrow circumstances, such as confirming a relationship already implied by documentation.

Documentation Integrity and the Legal Record

The health record is a legal document, so any query and its response become part of it under facility policy. A coder may never alter, backdate, or add clinical content to the provider's note. If a provider responds to a query, the response — or a documented addendum — supports the final code; a verbal answer alone does not.

This ties directly to the CCA's compliance and confidentiality domains. Coding from unsupported assumptions risks upcoding (reporting a higher-paying code than documentation supports) or unbundling (separately reporting services that should be one code), both of which can trigger fraud and abuse liability under the False Claims Act. The exam frames these as ethics questions: the coder's duty is accurate, documentation-driven reporting, and the query is the lawful tool for resolving uncertainty — used neutrally, patient by patient, never to manufacture a more favorable claim.