It started with a yellow sticky note.

In a busy multi-specialty practice, a veteran billing coder noticed a denial for a common joint injection. She knew the provider, Dr. Miller, was swamped. To save him time, she stuck a note on his desk: “Hey Dr. M—payer denied the injection. If you document ‘osteoarthritis,’ we can resubmit the claim today and get it paid. Thanks!”

Sarah wasn’t trying to commit fraud; she was trying to be helpful. She wanted the practice to be reimbursed for work already performed. But in that one-sentence note, this seasoned biller/coder had unknowingly stepped into a high-stakes compliance minefield. She had just issued a non-compliant provider query.

It seems harmless. In many physician practices, messages like this happen every day. Someone in billing or coding is simply trying to help the provider understand what went wrong and how to fix it.

But from a compliance perspective, that “quick message” may actually be something else entirely. A provider query.

And if it is a provider query, it must follow the same compliance standards used in hospitals.

This is where many healthcare organizations run into trouble. There is a long-standing misconception that provider query standards apply only to hospital clinical documentation integrity (CDI) programs. In reality, the concept of a query is much broader.

According to the AHIMA/ACDIS Guidelines for Achieving a Compliant Query Practice, a query is simply a communication used to clarify documentation in the medical record so that diagnoses, procedures, or services can be accurately reported. Importantly, these guidelines apply to all healthcare settings, including outpatient and physician practice environments.

In other words, whenever someone asks a provider to clarify documentation in the health record, they are performing a provider query whether they realize it or not.

 

How This Misconception Started

To understand why many people associate queries with hospitals, it helps to look at where structured query processes first gained traction.

In the early 2000s, hospitals began building clinical documentation integrity programs to address increasing scrutiny around documentation accuracy. Government audits, DRG-based reimbursement, and quality reporting programs made it essential that medical records clearly supported the diagnoses being coded.

CDI programs introduced formal processes for querying physicians when documentation was unclear or incomplete. These queries were structured, standardized, and designed to ensure documentation reflected the true clinical picture of the patient.

Because these programs were so visible in hospital settings, the idea took hold that provider queries were a hospital-only concept.

But the underlying principle, clarifying documentation to ensure accurate coding, applies just as much to outpatient and physician practice environments.

Where Queries Really Happen in Physician Practices

In physician offices, queries rarely look like formal CDI requests. Instead, they often show up as quick conversations or short electronic messages:

A coder might ask:

“Did you mean diabetes with neuropathy?”

A billing team member might write:

“The payer denied this procedure. Can you update the note?”

An appeals specialist might say:

“If we document chronic pain, the payer will approve this.”

These interactions may feel routine, but they still meet the definition of documentation clarification. And once documentation clarification enters the conversation, the same compliance standards apply.

Without realizing it, organizations can move from helping providers clarify documentation to influencing documentation for reimbursement purposes, which is where compliance risks begin.

When Helping Becomes Leading

One of the most common compliance issues occurs when a query begins to steer the provider toward a specific diagnosis.

Consider this message:

“Please add osteoarthritis so we can get this injection paid.”

The intent may be to help resolve a denial quickly, but the message does several things that create risk. It suggests a diagnosis, connects the diagnosis to reimbursement, and does not reference any clinical indicators from the record.

Compare that with a compliant approach:

“The record documents knee pain and decreased mobility. Imaging from the same encounter notes degenerative changes. Can you clarify the diagnosis associated with the patient’s knee symptoms?”

The difference is subtle but important. The second message focuses on the clinical information already present in the record and allows the provider to determine the appropriate diagnosis independently.

The AHIMA/ACDIS guidance emphasizes that queries must be non-leading and supported by clinical indicators from the health record.

Seeing the Difference: Compliant vs. Non-Compliant Queries

Scenario

Non-Compliant Query

Why It Creates Risk

Compliant Query

Diagnosis clarification

“Please add osteoarthritis so we can get this injection paid.”

Suggests diagnosis for reimbursement

“The record notes knee pain and degenerative changes on imaging. Can you clarify the diagnosis associated with the patient’s symptoms?”

Medical necessity denial

“This test will be covered if you document CKD.”

Connects diagnosis directly to payment

“The record shows decreased eGFR and monitoring of kidney function. Can you clarify whether a diagnosis related to renal impairment is present?”

Procedure justification

“Please document irritation so the lesion removal meets Medicare requirements.”

Directs provider toward payer coverage criteria

“Can you clarify the clinical reason for the lesion removal documented during this encounter?”

Documentation change

“Add diabetes with complications so we can rebill.”

Encourages documentation change for reimbursement

“The record documents diabetes and neuropathy. Can you clarify whether the neuropathy is related to diabetes?”

 

Why Third-Party Billing Vendors Must Pay Close Attention

Third-party billing vendors often work closely with providers to resolve claim denials and documentation issues. Because of this role, they may communicate with providers more frequently about documentation than anyone else in the organization.

Without clear query standards, those communications can unintentionally cross into risky territory.

Messages suggesting diagnoses that will make a service payable or asking providers to “update documentation to meet payer requirements” can easily be interpreted as leading queries or documentation manipulation.

Both the vendor and the provider could face scrutiny if auditors determine documentation was influenced by reimbursement concerns.

 

A Provider Query Is Not the Time to Educate

Another situation where organizations unintentionally create compliance risk is when education is mixed into the query process.

Imagine a provider reviewing a denial for benign skin lesion removal and saying:

“I don’t understand what the Medicare LCD requires for medical necessity.”

It might seem helpful to respond with an explanation of the coverage criteria. But if that explanation is included within the query itself, the communication can quickly become leading.

For example:

“Medicare requires symptoms such as irritation or bleeding. Please update the note if the lesion was symptomatic.”

Now the provider has effectively been told what documentation will allow the procedure to be paid.

Instead, the query should stay focused on clarifying the clinical record:

“The procedure note documents removal of benign skin lesions. Can you clarify the clinical reason for the lesion removal during this encounter?”

Possible responses might include symptomatic lesions, cosmetic removal, or another clinical explanation.

This approach allows the provider to document the true clinical reason for the procedure without being guided toward payer criteria.

So When Should Education Happen?

Provider education is essential but it should occur outside the query process.

The AHIMA/ACDIS guidance emphasizes that ongoing provider education is a key part of improving documentation practices.

Education works best when it happens proactively. Organizations can review denial trends with providers, offer specialty-specific documentation guidance, and share summaries of common payer requirements before services are performed.

When providers understand documentation expectations ahead of time, they are far more likely to document appropriately during the encounter reducing the need for clarification later.

Provider query compliance is not limited to hospitals.

Any time someone asks a provider to clarify documentation in the health record, whether they are a coder, a billing team member, or a third-party vendor, they are engaging in the query process.

Recognizing this distinction helps organizations protect the integrity of the medical record while reducing compliance risk.

And sometimes, the difference between a compliant query and a risky one is as simple as this:

Are we asking the provider to clarify the clinical picture, or are we telling them what will get paid?