What is physician query management and why it matters in 2026
Physician query management is the process clinical documentation improvement (CDI) specialists use to clarify ambiguous or incomplete documentation before claim submission. A properly written query asks the provider to document clinical findings that are present but missing from the record — without leading them toward a specific answer.
The stakes are higher than ever. CMS finalized updated E/M documentation guidelines effective January 1, 2026, requiring clearer links between assessment and medical decision-making. RAC audits recovered $2.1 billion in FY 2025, with 38% of denials tied to insufficient documentation supporting the billed service. Your query program either protects revenue or creates compliance risk.
This guide covers how to write compliant queries that improve response rates, reduce audit exposure, and capture accurate clinical information without crossing the line into leading documentation.
The compliance line: what makes a query leading vs. compliant
A leading query suggests a specific diagnosis or severity level. A compliant query presents clinical facts and asks the provider to interpret them.
Here's the difference. Leading query: "Patient has severe sepsis. Do you agree?" That's not a question. It's a suggestion with a yes/no button.
Compliant query: "Patient admitted with SIRS criteria (HR 118, RR 24, WBC 15.2, temp 101.8°F). Blood cultures positive for E. coli. Lactate 3.2 mmol/L. Does the clinical presentation support sepsis, severe sepsis, or septic shock? Please document your clinical judgment."
The compliant version presents objective findings. It lists possible options without favoring one. It asks the provider to make the clinical call based on facts already in the chart.
AHIMA and ACDIS query standards you need to follow
AHIMA's 2024 updated query practice brief requires queries to be clinically valid, supported by documentation, and free from financial bias. Every query must cite specific clinical indicators from the existing record. You can't query based on a hunch or because a code would pay better.
ACDIS standards add that queries should offer all clinically reasonable options, including "not documented" or "clinically undetermined." If the provider can't determine severity from available evidence, that's a valid answer. Forcing a choice creates false documentation.
OIG guidance from their 2025 work plan flags "patterns of upgraded diagnoses following queries" as a red flag. If your query program consistently results in higher-severity codes, auditors assume the queries are leading. Your CDI team needs defensible clinical rationale for every query.
When queries cross into upcoding territory
You cross the line when financial motivation drives the query instead of clinical clarity.
Example: querying every pneumonia case for "severe" or "with sepsis" because those versions pay more. If clinical indicators don't support the question, you're fishing for upgrades.
Another red flag: querying only high-dollar DRGs. If you query heart failure severity on Medicare Advantage patients but not commercial, auditors notice. Query criteria must apply consistently across payer types.
Template queries that insert diagnosis options without patient-specific clinical facts fail compliance. "Select: acute respiratory failure, chronic respiratory failure, acute on chronic" with no supporting ABG values, oxygen requirements, or ventilator status? That's leading.
How to structure queries that physicians actually answer
Providers ignore vague queries. They respond to queries that show you read the chart and asked a specific clinical question they can answer quickly.
Use this structure: clinical scenario, specific question, multiple-choice options with an "other" field, and space for clarification. Keep it under 100 words.
Start with the clinical facts. "Patient admitted 6/14 with chest pain. Troponin peaked at 2.8 ng/mL (normal <0.04). EKG shows ST elevation in leads II, III, aVF. Cath lab report documents 90% RCA occlusion, stent placed."
Ask the specific question. "Does this clinical presentation support a diagnosis of STEMI, NSTEMI, or unstable angina?"
Offer all reasonable options. "Please select:
- STEMI
- NSTEMI
- Unstable angina
- Other (please specify)
- Unable to determine from available information
Close with an invitation. "If additional details would help clarify, please document in the progress note."
Multiple-choice vs. open-ended queries
Multiple-choice queries get answered. Open-ended queries get ignored.
Response rates for multiple-choice queries average 76% within 24 hours, according to a 2025 ACDIS benchmarking survey. Open-ended queries ("Please document the severity of this condition") average 41% response within 48 hours.
Use multiple-choice when clinical options are clear and limited. Offer 3-5 choices that cover the reasonable clinical possibilities based on documented findings.
Use open-ended queries when you need narrative detail the record lacks entirely. Example: "Operative report states 'extensive adhesions.' Please describe location, density, and organs involved to support Medical Necessity Review documentation."
Hybrid works best for complex cases. Provide options, then add "Please clarify: [specific clinical detail]" to capture nuance.
Query timing: concurrent vs. retrospective
Concurrent queries sent during the hospital stay get answered 82% of the time. Retrospective queries sent after discharge get answered 34% of the time.
Send queries as soon as you identify the gap. If day 2 labs show acute kidney injury but the provider hasn't documented it, query day 3. Don't wait until day 5 when the patient's stable and the provider has moved on.
For short stays, query within 12 hours of identifying the issue. Observation cases and same-day surgeries discharge fast. If you wait, you're chasing post-discharge queries with terrible response rates.
Post-discharge queries work only when they're simple and well-documented. "You documented 'dehydration' — does this meet criteria for volume depletion (ICD-10 E86.0)?" with lab values attached might get answered. Complex clinical judgment calls won't.
Common query scenarios and compliant templates
Certain clinical situations generate queries across every hospital. Here's how to handle the most common scenarios without leading.
Sepsis severity queries
Sepsis queries fail compliance when they assume the diagnosis. Don't ask "Is this severe sepsis?" if the provider hasn't documented sepsis at all.
Compliant approach: "Patient meets SIRS criteria (temp 101.9°F, HR 112, RR 26, WBC 16,200). Source identified as UTI with positive urine culture (E. coli >100K CFU). Lactate 2.8 mmol/L. Creatinine elevated to 2.1 from baseline 0.9. Does the clinical presentation support:
- Sepsis
- Severe sepsis with acute organ dysfunction
- Septic shock
- SIRS due to infection (non-sepsis)
- Unable to determine
That query works because it presents objective criteria, offers the full clinical spectrum, and doesn't assume severity.
Acute kidney injury vs. acute renal failure
CMS eliminated "acute renal failure" as a term in 2024 guidance, clarifying that acute kidney injury (AKI) is the correct clinical term. But coding distinction still matters for severity staging.
Query template: "Creatinine increased from baseline 1.0 mg/dL (documented 5/12) to 2.4 mg/dL on admission 6/14. Meets KDIGO stage 2 criteria (>2x baseline increase). Does this support AKI stage 1, stage 2, or stage 3? Please document stage based on KDIGO criteria if clinically appropriate."
Include the staging reference so the provider doesn't have to look it up. Make it easy to answer accurately.
Heart failure acuity and specificity
Heart failure queries need to address both acuity (acute vs. chronic) and type (systolic, diastolic, combined) without leading toward the highest-paying combination.
Template: "Patient admitted with dyspnea, orthopnea, and lower extremity edema. BNP 1,850 pg/mL. Echo shows LVEF 35% (prior echo 2024 showed LVEF 40%). Chest X-ray shows pulmonary edema. History of heart failure documented in problem list. Does the clinical presentation support:
- Acute systolic heart failure
- Acute on chronic systolic heart failure
- Chronic systolic heart failure
- Acute diastolic heart failure
- Acute on chronic diastolic heart failure
- Combined systolic and diastolic heart failure
You're asking for clinical specificity the code set requires. You're not steering toward "acute on chronic combined" because it pays more.
MCC-generating complications
Queries that only target MCC conditions create audit risk. Query the same way whether the condition affects DRG payment or not.
If you query respiratory failure on every pneumonia case but ignore it on cellulitis cases, your pattern shows financial motivation. Apply the same clinical criteria across all diagnoses.
Building a defensible query tracking system
You need data to prove your query program is clinically driven, not revenue-driven. Track every query: date sent, clinical indication, query type, response rate, and resulting documentation.
Your tracking system must capture the clinical rationale for each query. "Why did you query this case?" should have a documented answer tied to specific clinical indicators, not "to capture the MCC."
Monitor response patterns. If one provider answers 92% of queries and another answers 18%, you have an education opportunity. If queries sent on Fridays get answered 40% less often than Monday queries, adjust your workflow.
Track agreement rates. If providers agree with your suggested diagnosis 98% of the time, auditors assume your queries are leading. Healthy programs show 65-75% agreement with some "unable to determine" and "other" responses mixed in.
Metrics that prove program integrity
OIG looks for these red flags: query volume that spikes at year-end, queries concentrated in high-reimbursement DRGs, and agreement rates above 90%.
Track and defend these metrics:
- Percentage of queries with cited clinical indicators: target 100%
- Queries per 100 discharges: typical range 8-15 for acute care hospitals
- Percentage of queries offering "unable to determine" option: should be 100%
- Provider selection of "unable to determine": healthy range 8-12%
- Query response time: median under 24 hours for concurrent queries
- Post-discharge query volume: should be under 5% of total queries
If your metrics fall outside these ranges, document why. A new EHR might temporarily increase query volume. A hospitalist group change might affect response rates. Auditors want context.
Physician education reduces query volume
The best query program is the one that sends fewer queries because providers document clearly the first time.
Run quarterly documentation training focused on high-query diagnoses. Show providers their personal query data. "You received 23 sepsis queries last quarter. Here's what was missing from your notes."
Create EHR templates with prompts for common gaps. Heart failure admission template should prompt for LVEF, NYHA class, and acuity. Sepsis template should prompt for SIRS criteria, source, and organ dysfunction.
Share compliant query examples during medical staff meetings. When providers see what CDI needs, they start documenting it proactively. MedCodex Health clients typically see query volume drop 30-40% after implementing structured CDI Program Support with embedded physician education.
Technology and workflow automation for query programs
Manual query tracking in spreadsheets doesn't scale past 50 queries per month. You need a system that integrates with your EHR, tracks clinical indicators automatically, and generates compliant query templates.
CDI software should flag potential query cases based on coded diagnosis, clinical indicators in the chart, and lab values. It shouldn't auto-generate the query text. Human review ensures clinical appropriateness.
Your workflow should include: case identification, CDI review to validate clinical need, query drafting with cited evidence, provider notification through the EHR, response tracking, and escalation for non-responses after 24 hours.
Route queries through the EHR task system, not email. Queries sent via email get lost. EHR tasks stay visible in the provider's workflow until answered.
AI tools for query drafting: use with caution
AI tools can pull relevant clinical data from notes and suggest query scenarios. They can't determine clinical appropriateness or write compliant queries without human oversight.
An AI tool might flag every elevated troponin for a possible MI query. A human CDI specialist knows to check the trend, timing, and context before querying. Not every troponin elevation is an infarction.
Use AI to surface potential cases and draft initial query text. Always have a certified CDI specialist review for clinical validity and compliance before sending.
Frequently asked questions about physician query management
What's the difference between a compliant query and a leading query?
A compliant query presents objective clinical findings already documented in the chart and asks the provider to interpret them based on their clinical judgment. A leading query suggests a specific diagnosis or severity level and asks the provider to agree. Compliant queries offer all clinically reasonable options, including "unable to determine." Leading queries guide the provider toward a predetermined answer, creating compliance risk and potential false claims liability.
How quickly should physicians respond to clinical documentation queries?
Concurrent queries sent during an active hospital stay should be answered within 24 hours to support accurate coding and claim submission timelines. Most hospitals set a 24-hour response expectation for inpatient queries and 12 hours for observation or short-stay cases. Retrospective queries sent after discharge typically see much lower response rates and should be avoided when possible by improving concurrent query workflows.
Can I query a physician to add a diagnosis that isn't documented anywhere in the chart?
No. Every query must be based on clinical indicators already present in the medical record. You can't query for a diagnosis that has no supporting documentation. If labs, imaging, or physical exam findings suggest a condition the provider hasn't mentioned, you can query and cite those specific findings, asking if they support a particular diagnosis. But you can't ask a provider to diagnose something with zero clinical evidence in the chart.
What percentage of queries should physicians agree with?
Healthy query programs typically see provider agreement rates between 65% and 75%, with 8-12% of responses selecting "unable to determine" or "other" options. Agreement rates consistently above 90% raise red flags during audits because they suggest queries are leading providers toward predetermined answers rather than asking genuine clinical clarification questions. If your agreement rate is very high, review your queries for potential leading language or implicit bias toward specific diagnoses.
Should I query more often for Medicare patients than commercial patients?
No. Query criteria must be applied consistently across all payer types based on clinical need, not reimbursement potential. Querying more frequently for Medicare, Medicare Advantage, or other high-reimbursement patients creates a pattern of financial motivation that fails compliance standards and creates significant audit risk. Your query rate per 100 discharges should be consistent across payer classes when adjusted for case mix and severity.
What happens when your query program creates audit risk
If your query program drives revenue