6.4 Documentation and Query Compliance

Compliant Physician Queries

A query is a communication to a provider asking for clarification when documentation is conflicting, incomplete, ambiguous, or imprecise. The authoritative standard is the joint AHIMA/ACDIS Guidelines for Achieving a Compliant Query Practice — 2022 Update. A compliant query must be:

• Supported by clinical indicators in the health record (labs, vitals, imaging, medications, treatment) — never "mined" from nothing.
• Non-leading — it must not direct the provider toward a specific diagnosis or a higher-paying answer.
• Tied to reimbursement-neutral intent — never sent solely to increase reimbursement.

Query formats: Open-ended (most defensible — the provider supplies the answer); multiple-choice (must include clinically supported options plus "other," "clinically undetermined," and an option to add free text); and yes/no, which is allowed only in narrow cases — to confirm a condition already documented elsewhere, to establish present-on-admission status, or to link a cause-and-effect relationship already implied in the record.

Query Do's and Don'ts

The brief draws clear lines that RHITs must apply when reviewing or writing queries:

Do:

• Cite the specific clinical indicators that prompted the query.
• Offer clinically reasonable choices and an "other/undetermined" option.
• Keep a record of all queries as part of the legal/business record per policy.
• Allow the provider to disagree and document their clinical judgment.

Don't:

• Indicate the financial impact of the response.
• Lead the provider to one answer (e.g., "Please document sepsis").
• Offer a single "yes/no" choice for an undocumented diagnosis.
• Question the provider's clinical judgment or pressure for a specific code.

A leading query — even one that produces a clinically accurate code — is a compliance failure because it taints the integrity of the documentation and exposes the organization to allegations of fraudulent upcoding.

Documentation Integrity, Cloning, and Corrections

Documentation integrity means the record is complete, accurate, and attributable to its true author. The electronic health record (EHR) introduces specific risks:

• Copy-forward / cloning — copying prior notes into a new encounter. This can propagate outdated, contradictory, or unsupported information, inflate documentation, and is a top OIG/auditor red flag.
• Authorship and authentication — every entry must identify its author and be authenticated (signed, dated, and timed). Auto-authentication of unreviewed entries and shared logins violate integrity standards.

Correcting the record is governed by strict rules — the original entry is never deleted or obscured:

The distinction is tested: an amendment alters/clarifies what was already there, while an addendum appends genuinely new information at a later time.

In the EHR, all corrections must leave an audit trail / metadata record showing the original content, the change, the author, and the date/time. Hard-deleting an entry destroys the legal record's integrity and is itself a compliance violation; the proper approach flags the original as erroneous while keeping it retrievable.

When to Query and When Not To

Recognizing the trigger for a query is as important as writing it compliantly. The AHIMA/ACDIS brief lists circumstances that warrant a query, including documentation that is:

• Conflicting — two providers document different diagnoses (e.g., one says "urosepsis," another "sepsis").
• Incomplete — a condition is treated (antibiotics given) but never named.
• Ambiguous — a finding is noted without clinical significance ("low sodium" with no diagnosis of hyponatremia).
• Imprecise / clinically unsupported — a diagnosis is stated but clinical indicators are absent, raising integrity (not just specificity) concerns.

Queries are not appropriate to confirm an already clearly documented diagnosis, to question sound clinical judgment, or to chase a diagnosis with no clinical basis simply because it pays more. A query that the provider declines is still valid — the provider's documented clinical judgment governs, and the coder assigns codes to what is finally documented.

Documentation Integrity and the Legal Health Record

The legal health record (LHR) is the formally defined record the organization discloses for legal and business purposes. Documentation-integrity controls — accurate authorship, authentication, version control, and disciplined use of copy functions — protect the LHR's credibility. When integrity fails, the consequences cascade: unreliable data feeds bad coding, bad coding feeds improper claims, and improper claims feed fraud-and-abuse exposure. This is why RHITs treat compliant queries and EHR-correction rules as front-line revenue-integrity and risk-management controls, not mere clerical formalities.

Authentication, Signatures, and Timeliness

CMS and accreditor standards are specific about authentication. An entry is authenticated when its author confirms it is complete and accurate — by handwritten signature, a compliant electronic signature, or a permitted rubber-stamp alternative for narrow circumstances. Auto-authentication, where a system signs an entry the provider never reviewed, is prohibited because it cannot attest that the content was verified. Each authenticated entry should carry the author's name, credential, date, and time.

Timeliness rules reinforce integrity: a late entry must be labeled as such and dated with the actual date written (never backdated to imply contemporaneity), and a discharge summary and history and physical carry defined completion windows. A record left incomplete past the medical-staff deadline becomes a delinquent record — a metric surveyors review and a frequent driver of suspended admitting privileges. By enforcing authorship, authentication, and timeliness, the HIM department keeps the legal health record both clinically trustworthy and legally defensible.