8.3 Diagnosis, Procedure, Severity, and POA Query Patterns
Key Takeaways
- Diagnosis queries commonly address missing acuity, type, cause, linkage, ruled-in status, complication status, or clinical consistency.
- Procedure queries focus on objective facts such as body part, approach, depth, device, laterality, root operation intent, lesion size, and whether a service was diagnostic or therapeutic.
- Severity and POA queries require timeline discipline because reimbursement, quality measures, HACs, PSIs, and audit risk can be affected.
- A good pattern is reusable, but the indicators and response options must be tailored to the individual record.
Match the Query Pattern to the Missing Fact
Not every provider query asks the same kind of question. A diagnosis specificity query may ask whether heart failure is systolic, diastolic, combined, acute, chronic, or acute on chronic. A linkage query may ask whether diabetes is related to chronic kidney disease, neuropathy, or a foot ulcer when the record contains indicators but the provider has not stated the relationship. A procedure query may ask for the depth of debridement, the body part removed, the device left in place, or whether a biopsy was excisional.
A POA query may ask whether a pressure injury, infection, fracture, or complication was present at the time of inpatient admission.
The safest pattern begins with the unresolved coding fact. If the missing fact is acuity, do not ask a cause question. If the missing fact is complication status, do not ask a yes/no question that assumes the procedure caused the condition. If the missing fact is POA timing, present the timeline and ask the provider to clarify whether the condition was present on admission, developed after admission, clinically unable to determine, or other. The query form should make it easy for the provider to answer the actual documentation gap.
Query Pattern Map
| Pattern | Missing fact | Indicators to include | Neutral prompt |
|---|---|---|---|
| Diagnosis specificity | Type, acuity, stage, organism, laterality | Current diagnosis, treatment, test results, provider notes | Please clarify the type or acuity of the documented condition |
| Cause or linkage | Relationship between conditions | Diabetes, kidney disease, neuropathy, ulcer, medication exposure, infection | Please clarify whether these conditions are related, unrelated, or unable to determine |
| Clinical validation | Diagnosis appears inconsistent with indicators | Provider diagnosis plus conflicting vitals, labs, imaging, treatment, consults | Please clarify the diagnosis supported by the record |
| Procedure detail | Root operation, depth, approach, device, body part | Operative report, pathology, implant log, imaging, technique | Please clarify the procedure objective and details |
| POA timing | Present at inpatient admission or developed later | Admission assessment, ED note, early labs, later notes, wound documentation | Please clarify present-on-admission status |
| Complication status | Whether condition is a complication or expected outcome | Procedure timing, provider statements, treatment, severity | Please clarify the clinical significance and relationship to the procedure |
Diagnosis severity queries are high risk because they often affect MCC or CC capture. A compliant severity query should avoid saying that the diagnosis has severity impact. For example, if the record documents encephalopathy but not type, the query might list acute confusion, altered mental status from baseline, ammonia level if relevant, infection, hypoxia, sedating medications, treatment, and mental status improvement.
It can ask whether the encephalopathy is metabolic, toxic, toxic-metabolic, other specified, unspecified, no additional diagnosis, or unable to determine if those options are clinically appropriate.
Procedure queries are not only inpatient PCS issues. In outpatient and ED cases, missing procedure details can affect CPT or HCPCS code selection, modifiers, and medical necessity support. If an ED note documents laceration repair, the coder may need length, location, complexity, and whether debridement was performed. If a surgeon documents lesion excision, the coder may need lesion size, margins, anatomic site, and pathology. In PCS, the coder may need to know whether the physician removed a body part, cut out a portion, drained fluid, inspected a body cavity, or inserted a device.
POA queries require careful attention to the inpatient admission point. Present on admission does not always mean documented in the first note, and not present on admission does not always mean first documented late. The question is whether the condition was present at the time the inpatient admission order occurred. Indicators may come from the ED, history and physical, early nursing assessment, wound photographs, labs collected before admission, imaging, or provider assessment. If the record is unclear, a query may be appropriate.
Complication queries need neutral language because the word complication has clinical, quality, and payment consequences. Do not ask, was this a surgical complication? in a way that implies the answer. Present the timeline and the provider's existing statements. Ask the provider to clarify whether the condition represents an expected postoperative outcome, a complication of the procedure, a condition unrelated to the procedure, another explanation, or unable to determine. The coder should not infer complication status from timing alone.
Clinical validation queries are especially nuanced. Coding professionals do not diagnose patients, and they do not disregard provider diagnoses merely because they personally disagree. However, records may contain diagnoses that are not clinically supported, are contradicted by other documentation, or appear copied forward. If facility policy supports clinical validation review, the query should present the diagnosis and the conflicting or incomplete indicators and ask for clarification. It should not accuse the provider or demand that a diagnosis be removed.
The exam may combine several gaps. A patient admitted with pneumonia develops acute kidney injury after IV contrast, has creatinine rise, nephrology consult, fluid management, and discharge documentation of renal insufficiency. The coder may need both diagnosis specificity and complication relationship. A single query can ask for clarification of the renal diagnosis and relationship to contrast if the indicators support it, but the wording must stay neutral and offer alternatives. If the questions are too different, separate queries may be cleaner.
Use reusable query templates cautiously. Templates help standardize compliance, but the content must be patient-specific. A template that always asks for sepsis, severe malnutrition, or acute respiratory failure based on a canned list can become leading if the indicators do not fit the record. For CCS-level practice, write the pattern first, then tailor the facts.
Which query pattern best fits a record that documents CHF but does not identify acuity or type?
An operative report states debridement of a foot wound but does not describe depth or excisional versus non-excisional technique. What query pattern is most appropriate?
Which fact is central to a POA query?