8.1 When a Query Is Needed
Key Takeaways
- A query is needed when the health record contains clinical indicators but the provider documentation is incomplete, conflicting, ambiguous, clinically inconsistent, or missing required specificity.
- Queries clarify provider intent; they are not a tool for directing the provider to a code, DRG, MCC, CC, PSI, HAC, or payer outcome.
- CCS scenarios often test whether the coder can distinguish a true query opportunity from a code assignment that is already supported.
- The strongest query decision starts with record review, official guideline logic, and a clear statement of what cannot be coded without provider clarification.
Query Need Starts With a Coding Barrier
A provider query is appropriate when the record contains enough clinical context to support a clarification question but not enough provider documentation to code, sequence, validate, or report the case accurately. The coder is not asking the provider to create a diagnosis from nothing. The coder is asking the provider to resolve a documentation barrier that prevents compliant coding.
On the CCS exam, this usually appears as an incomplete diagnosis, a conflict between notes, unclear acuity, missing cause-and-effect language, uncertain present-on-admission status, or a procedure description that does not identify the objective of the service.
A query should have a concrete coding purpose. That purpose may be diagnosis specificity, procedure specificity, sequencing, POA status, complication status, clinical validation, or clarification of whether a condition was ruled in or ruled out. If the coder can assign the correct code using existing provider documentation and official guidelines, a query is unnecessary. If the coder merely wants a higher paying DRG, an MCC, a CC, or a cleaner denial defense without a genuine documentation gap, the query is improper.
Common Query Triggers
| Documentation issue | Example in the record | Why a query may be needed |
|---|---|---|
| Ambiguous diagnosis | Progress note says urosepsis; discharge summary says UTI | The coder cannot assume sepsis without clear provider documentation |
| Missing acuity | Provider documents CHF only | ICD-10-CM coding may need acute, chronic, or acute on chronic status and type |
| Missing cause | Encephalopathy documented with infection, hypoxia, and medication exposure | Code selection may depend on toxic, metabolic, or other specified cause |
| Conflicting documentation | Surgeon says expected postoperative anemia; hospitalist says acute blood loss anemia | The coder needs provider clarification before assigning a complication or acute condition |
| POA uncertainty | Pressure injury found soon after admission but not clearly present at admission | POA reporting affects quality and payment logic |
| Procedure objective unclear | Operative note describes removal of tissue but not whether a lesion, body part, or device was removed | PCS root operation or CPT assignment may be unclear |
The first step is always to identify the exact unresolved issue. Do not start with the desired code. Start with the question: what fact is missing from provider documentation? For example, if the record shows fever, leukocytosis, blood cultures, IV antibiotics, hypotension, and a discharge diagnosis of pneumonia, the missing fact may be whether sepsis was evaluated and ruled in or ruled out. If the provider never documented sepsis, the coder cannot code it just because the clinical picture suggests it. A compliant query may present the indicators and ask the provider to clarify the diagnosis being treated.
Query Decision Workflow
- Review the complete record, including discharge summary, progress notes, consults, operative reports, ED record, labs, imaging, medication records, pathology, and nursing documentation.
- Identify the documentation barrier in plain language: missing specificity, conflict, ambiguity, POA uncertainty, cause-and-effect uncertainty, or clinical inconsistency.
- Confirm that clinical indicators exist in the record and are relevant to the question.
- Decide whether official coding guidelines already answer the issue without a query.
- Draft a non-leading query that includes patient-specific indicators and clinically reasonable response options.
- Route the query through the facility-approved process and retain the audit trail according to policy.
- Code only from the final documented provider response and the rest of the record.
A query is not needed for every abnormal test result. A low sodium value does not automatically create a query for hyponatremia. The coder should look for provider evaluation, treatment, monitoring, or clinical significance. If the provider documents hyponatremia and it is treated or monitored, coding may be supported. If the only evidence is one abnormal lab with no provider statement and no clinical impact, the better answer may be no code and no query.
If the record shows repeated severe sodium abnormality, fluid restriction, medication changes, and daily monitoring, but the provider never names the condition, a query may be appropriate.
A query may also be needed when documentation is internally inconsistent. Suppose the ED diagnosis is acute respiratory failure, the admission history says COPD exacerbation with hypoxia, progress notes document oxygen by nasal cannula, and the discharge summary lists COPD exacerbation only. If acute respiratory failure affects coding and the record contains relevant indicators, the coder should not choose the diagnosis based on the note that gives the highest severity.
The compliant approach is to ask the provider to clarify whether acute respiratory failure was present and treated, or whether another respiratory condition best explains the findings.
Provider documentation can also be too vague for procedure coding. In inpatient PCS, root operation selection depends on the objective of the procedure, not a casual procedure label. If an operative note says debridement was performed but does not identify excisional versus non-excisional technique, depth, body part, or tissue removed, the coder may need clarification. In outpatient CPT coding, the same record may require lesion size, number of lesions, approach, laterality, imaging guidance, or whether a diagnostic or therapeutic service was performed.
For CCS purposes, remember that query need is a documentation and compliance judgment, not a reimbursement shortcut. The exam may ask which action is best after showing a case with a potential MCC. If the diagnosis is already clearly documented and reportable, assign the code. If the record has clinical indicators but lacks provider documentation, query. If there are no meaningful indicators, do not query just to ask the provider to add a severe diagnosis.
Which situation most clearly supports a compliant provider query?
A provider documents acute on chronic systolic heart failure in the discharge summary, and treatment with IV diuretics is documented. What is the best coding action?
Which question best defines the first step in deciding whether to query?