8.7 Provider Query Case Lab

Applying Query Judgment to Cases

CCS query questions rarely test definitions alone. They present a record excerpt and ask what the coder should do. The strongest approach is to separate three decisions: what can already be coded, what cannot be coded without clarification, and what should not be queried because the indicators are insufficient. This prevents two common errors: querying everything that might affect severity and failing to query a real ambiguity.

Use a repeatable case lab method. First, list the provider-documented diagnoses and procedures. Second, identify objective indicators such as labs, imaging, treatment, operative details, nursing findings, and consults. Third, compare the documentation to the coding need. Fourth, decide whether a query is needed. Fifth, choose a format and draft neutral wording. Sixth, decide how the provider response would affect coding.

Case Lab Workflow

1. State the existing documentation in provider terms.
2. State the clinical indicators without exaggeration.
3. Name the coding barrier: missing specificity, conflict, linkage, procedure detail, POA status, or clinical validation.
4. Decide whether the record supports a query.
5. Draft a non-leading question with reasonable options.
6. Handle the response: code, do not code, follow up, or escalate.
7. Document the audit trail according to facility policy.

Case 1: Inpatient Sepsis Ambiguity

A patient is admitted with pneumonia. The ED note documents fever 102.2, heart rate 118, respiratory rate 26, WBC 18.5, lactate 2.8, blood cultures drawn, IV ceftriaxone and azithromycin started, and fluid bolus given. The hospitalist history documents community-acquired pneumonia with systemic inflammatory response. Progress notes say pneumonia improving. The discharge summary lists pneumonia only. There is no provider diagnosis of sepsis.

The coder cannot code sepsis from indicators alone. The record contains enough indicators to ask whether sepsis was evaluated and treated, but the query must be neutral. A compliant query could state the indicators and ask: please clarify the diagnosis associated with the infection and systemic findings. Options might include sepsis due to pneumonia, pneumonia without sepsis, systemic inflammatory response due to another cause, other diagnosis, no additional diagnosis, or unable to determine. The query should not say that sepsis is needed for the DRG.

Case 2: Outpatient Lesion Excision Detail

An outpatient operative note says the provider excised a skin lesion from the left forearm and closed the wound. The note does not document lesion diameter, margins, final excised diameter, repair type, or whether pathology showed benign or malignant lesion. The coder cannot assign the most specific CPT code if required size and pathology elements are missing. A procedure detail query may be needed, or the coder may need to wait for pathology if facility policy links final code selection to the pathology result.

The query should ask for objective procedure details, not a code. A compliant prompt could ask the provider to clarify the lesion size including margins, anatomic site, repair type, and any other relevant procedure details. If pathology later shows malignancy, final coding may change depending on code set instructions and facility policy. The coder should not select a higher-complexity excision code simply because the procedure looked difficult.

Case 3: POA Pressure Injury Timeline

A patient is admitted through the ED for dehydration and altered mental status. Nursing admission assessment at 23:10 documents reddened sacral area. Wound care on hospital day two documents stage 3 sacral pressure injury. The provider documents sacral pressure injury but does not state whether it was present on admission. The diagnosis may be reportable if provider-documented, but POA status is unclear because the stage and timing need provider clarification.

A compliant POA query would present the ED or admission findings, nursing assessment, wound care findings, provider diagnosis, and timing. It would ask whether the stage 3 sacral pressure injury was present on admission, developed after admission, whether the provider is clinically unable to determine, or other. It should not tell the provider to mark it POA to avoid a hospital-acquired condition.

Case 4: ED Respiratory Failure Suggestion

An ED patient with asthma exacerbation receives nebulizer treatments and short-term oxygen. The oxygen saturation was 91 percent on room air, improved to 97 percent after treatment, and the patient was discharged home. The provider documents asthma exacerbation only. The encoder suggests acute respiratory failure. There is no provider diagnosis, no severe distress documented, no blood gas, no noninvasive ventilation, and no admission.

This may not be a strong query opportunity. The coder should not query simply because the encoder suggested a higher-severity diagnosis. If facility criteria and the record do not support clinical concern for acute respiratory failure, the correct action is to code the documented asthma exacerbation and any other supported services. If additional documentation elsewhere showed sustained hypoxia, severe work of breathing, escalation of respiratory support, and provider concern, the decision could change.

Mini Query Drafting Checklist

• Indicators are copied from the actual case, not a generic template.
• The query asks the missing clinical fact, not the desired code.
• Options include plausible alternatives and unable to determine when appropriate.
• Payment, MCC, CC, PSI, HAC, and denial language are excluded.
• The provider response will be authenticated and retained.

The case lab habit is to defend every query in one sentence: the record contains specific indicators, existing provider documentation is not sufficient for a coding decision, and the question is neutral. If that sentence fails, either the record already supports coding, the record does not support a query, or the query needs to be rewritten. That is the practical CCS distinction.