Physician query management is the system clinical documentation improvement (CDI) teams use to ask physicians for missing or unclear information without influencing their clinical judgment. When a coder or CDI specialist can't assign the most accurate code because documentation lacks specificity, a compliant query fills that gap. This post explains how to write queries that meet AHIMA and ACDIS standards, avoid leading the provider, and protect your organization from compliance risk while capturing the clinical detail your revenue depends on.
You're walking a tightrope. Query too softly and you leave millions in unreported severity on the table. Query too aggressively and OIG investigators flag your program for upcoding. The answer isn't to query less. It's to query better.
What makes a physician query compliant
A compliant query asks a genuine clinical question. It doesn't suggest a diagnosis. It doesn't offer only high-severity answer choices. It doesn't cherry-pick facts that point toward one outcome.
AHIMA's 2019 query practice brief and ACDIS guidance both require queries to be clear, non-leading, and clinically defensible. That means your query must present all reasonable options based on the clinical indicators in the chart, not just the ones that increase your DRG weight or risk score.
The four non-negotiable query elements
Every query must include the patient name and medical record number, the clinical indicators that triggered the query, a specific question with multiple clinically reasonable answer choices, and space for the provider to document a different conclusion or decline to answer.
Skip any of these and you're writing a suggestion, not a query.
When to query and when to walk away
Query when documentation supports a diagnosis but doesn't name it. A patient admitted with fever, elevated white count, and positive blood cultures needs a documented source and organism. If the physician wrote "treated for infection" but didn't specify sepsis or the infectious agent, that's a valid query.
Don't query when the chart contains no clinical support. If labs are normal, imaging is negative, and the patient is asymptomatic, you can't ask "Does this patient have [condition]?" just because it would improve reimbursement. That's fishing.
How to structure queries that capture clinical specificity without leading
The structure of your query determines whether it reads as a clinical clarification or a coding wish list. Start with a neutral introduction: "The following clinical indicators have been noted." Then list objective findings directly from the chart.
Use lab values, vital signs, imaging results, and treatment actions. Avoid interpretive language. Don't write "patient appears septic." Write "patient presents with fever 101.8°F, heart rate 118, lactate 3.2, on broad-spectrum antibiotics."
Multiple-choice format that works
Present 3 to 5 answer choices based on documented evidence. Include the less severe option. If your choices are "sepsis," "severe sepsis," "septic shock," and "other," you've written a leading query. Add "infection without sepsis" or "clinical significance unclear" to balance it.
Always include "clinically undetermined" or "unable to determine" as an option. Physicians must be able to decline without writing an essay.
Open-ended queries for complex cases
When clinical indicators don't fit neatly into categories, use an open-ended query. "Given the findings of [list], please document your clinical assessment of this patient's [condition]." This works for cases where you need clarification but can't predict the answer.
Open-ended queries take longer for physicians to complete. Use them when multiple-choice would force an artificial choice.
Common physician query management mistakes that trigger audits
RAC auditors and OIG reviewers know what aggressive querying looks like. They see the same patterns in every program that crosses the line.
The first red flag: queries that only offer high-severity answers. If 90% of your query responses result in a higher DRG or HCC, expect scrutiny. CMS doesn't publish a safe threshold, but internal compliance programs typically investigate when query impact exceeds 75% upgrades.
The "yes/no" query trap
Never write a yes/no query. "Does this patient have acute respiratory failure?" is leading by design. It assumes the condition exists and asks the physician to confirm. Rewrite it as a multiple-choice query: "What is your assessment of this patient's respiratory status?" with answers including normal function, hypoxemia without failure, acute respiratory failure, and clinically undetermined.
Yes/no queries show up in every OIG settlement agreement involving upcoding. Don't use them.
Copy-paste clinical indicators without context
Some CDI software auto-populates queries with every abnormal lab and vital sign from the stay. That's not a query. That's a data dump. The physician has to re-review the entire case to figure out what you're asking.
List only the indicators directly relevant to your question. If you're querying for acute kidney injury, include creatinine trends and urine output. Don't include the CBC and chest X-ray.
Querying after discharge
Post-discharge queries are higher risk. Medicare allows them only when the clinical information wasn't available during the stay or the query addresses a documentation gap that couldn't reasonably have been identified earlier. If your CDI team routinely waits until after discharge to query, you're creating an audit trail that says your real-time documentation program doesn't work.
Concurrent queries close before the patient leaves. Post-discharge queries should represent less than 10% of your total query volume.
Physician query management software and workflow design
Technology doesn't make queries compliant. It makes compliant queries scalable. Most hospitals now use integrated CDI platforms that route queries through the EHR, track response rates, and flag queries for compliance review before they reach the physician.
The software should enforce your query policy automatically. If your policy prohibits yes/no queries, the system shouldn't let a CDI specialist submit one. If your policy requires at least 3 answer choices, the form should enforce that.
Response rate benchmarks and physician engagement
The national average physician query response rate is 85% to 92%. If your rate is below 80%, you have a workflow problem or a trust problem. Physicians ignore queries they perceive as coding exercises rather than clinical clarifications.
Track response time separately. Queries answered within 24 hours are typically seen as clinically relevant. Queries that sit unanswered for 5 days suggest the physician doesn't think the question matters.
Query education and physician feedback loops
CDI teams that share outcome data with physicians get better responses. When you can show a hospitalist that their pneumonia documentation has a 40% query rate compared to 12% for their peers, they start documenting differently.
Run quarterly sessions with your top queried physicians. Walk through 3 to 4 real cases. Show them what documentation would've eliminated the need to query. Most physicians want to document well. They just don't know what coders need.
Measuring query program performance without gaming the system
You can't manage what you don't measure, but you can't measure query programs the way you measure coding productivity. If you incentivize query volume, you'll get junk queries. If you incentivize financial impact, you'll get leading queries.
Track query necessity rate: what percentage of your queries resulted from legitimately unclear documentation versus what percentage could've been avoided with better real-time CDI education. A mature program sees necessity rates above 85%.
Agreement rate vs. compliance rate
Agreement rate is the percentage of queries where the physician chose an option that changed the code assignment. Compliance programs sometimes mistake a high agreement rate for success. It's not. A 95% agreement rate often means your queries are leading.
Compliance rate measures whether your queries follow policy. Randomly audit 20 queries per month against your written standards. If more than 2 fail, you have a training gap or a process gap.
Frequently asked questions about physician query management
Can a coder submit a physician query directly or does it have to go through CDI?
Coders can submit queries if your compliance policy allows it and they've been trained on query standards. Many hospitals limit coder queries to straightforward clarifications like laterality or episode of care, while CDI handles clinical severity queries. The key is consistent oversight regardless of who writes the query.
How long should a physician have to respond to a query?
Most hospitals set a 48 to 72-hour response window for concurrent queries. Post-discharge queries typically allow 5 to 7 business days. The timeframe should be written into your query policy and communicated to medical staff during onboarding. Unanswered queries should never be assumed as agreement.
What if the physician disagrees with all the query answer choices?
That's why you include "other" or a free-text option. If a physician consistently rejects your answer choices, your queries aren't reflecting the clinical reality in the chart. Review those cases with the CDI lead and physician advisor to understand the disconnect.
Are verbal queries allowed under AHIMA guidelines?
Verbal queries are allowed for urgent clarifications during concurrent review, but they must be followed by written documentation in the medical record. A verbal conversation with no written query and no physician attestation won't survive an audit. If the clarification matters enough to ask, it matters enough to document.
How do you prevent query fatigue among physicians?
Query fatigue happens when physicians feel like they're being asked to do the CDI team's job. Reduce query volume by improving front-end documentation templates, running physician-specific feedback reports, and eliminating low-value queries that don't change clinical or financial outcomes. If your query rate per case exceeds 0.4, you're probably over-querying.
Building a query program that survives audits and supports revenue integrity
Your query program has two jobs: capture the clinical story your physicians are treating and protect your organization from compliance risk. Those goals don't conflict. They're the same goal approached from different angles.
Write queries that a physician advisor would defend in an audit. If you wouldn't want to explain your query rationale to an OIG investigator, don't send it. Most query failures happen because someone prioritized the financial outcome over the clinical question.
If your CDI team is managing query volume without dedicated compliance oversight, or if your query response rates are below benchmark, you're leaving compliant revenue on the table. MedCodex Health provides CDI program support and physician query management designed to meet AHIMA standards while capturing the specificity your revenue cycle depends on. Talk to us about a query audit that shows you exactly where your program stands and what compliant improvement looks like. MedCodex Health brings 15 years of CDI and coding expertise to hospitals that want answers, not promises.