6.4 Documentation and Query Compliance
Key Takeaways
Per the AHIMA/ACDIS 2026 update, a compliant query must be supported by clinical indicators in the record and must not lead the provider to a desired answer.
Multiple-choice queries can be used in any circumstance; open-ended queries are allowed but are not the preferred format; yes/no queries are limited to an already-documented diagnosis, POA status, or a cause-and-effect link between documented conditions.
Copy-forward (cloning) threatens documentation integrity by carrying outdated or unsupported information into new notes.
An amendment changes an existing entry while an addendum adds new information later; both must preserve the original entry and be dated, timed, and authenticated.
Compliant Physician Queries
A query is a communication to a provider asking for clarification when documentation is conflicting, incomplete, ambiguous, or imprecise. The professional standard is the joint AHIMA/ACDIS Guidelines for Achieving a Compliant Query Practice (2026 Update), published August 2026, which supersedes all previous versions, including the 2022 version. 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: Multiple-choice can be used in any circumstance and must include at least one clinically valid option supported by the record plus "other" or another open-ended option (choices such as "unable to determine" are optional, except that "unable to determine" is required in POA yes/no queries); open-ended queries may be used in any circumstance but are not the preferred format because they can be hard to interpret; and yes/no is allowed only in narrow cases — to substantiate a diagnosis already documented by a provider, to establish present-on-admission status, or to establish or negate a cause-and-effect relationship between documented conditions. A yes/no query must never be used to obtain a new, previously undocumented diagnosis.
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 supported choices plus an "other" or open-ended 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:
| Term | Definition |
|---|---|
| Amendment | Clarifies or corrects an existing entry; original stays visible, new text dated/timed/signed |
| Addendum | Adds new information after the original entry was complete; references the original |
| Late entry | Adds omitted information, labeled "late entry," with current date/time |
| Correction | Fixes an error; strike-through (paper) or audit-trailed change (EHR), original retained |
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.
According to the AHIMA/ACDIS Guidelines for Achieving a Compliant Query Practice, a compliant query must:
State the reimbursement impact so the provider understands the stakes
Use a single yes/no format for any new diagnosis
Direct the provider toward the most specific billable diagnosis
Be supported by clinical indicators in the record and be non-leading
A clinician adds new test results to a progress note three days after the original note was completed, referencing the original entry. This is best classified as a(n):
Amendment
Correction
Addendum
Deletion
Why is copy-forward (cloning) in the EHR a documentation-integrity and compliance concern?
It permanently deletes the original author's note
It can carry outdated or unsupported information into new notes
It is prohibited by the Stark Law
It automatically increases the MS-DRG weight
Sections you finish are checked off in the contents.