Merle's PearlsEvolving Landscape of Compliant Query Practice
Merle's Pearls Educational Series
Although the fundamental principles of compliant query practice remain consistent from 2022 into 2026, advances in technology have significantly expanded their scope and application. Developing effective departmental policies requires a thorough understanding of how modern electronic queries function within this updated technological environment.
Compliant Query Practice
The principles remain consistent. What has changed is how electronic queries are delivered, accessed, and resolved across modern care teams.
Modernizing Query Delivery and Escalation Protocols
Query escalation protocols must be revised to reflect the increased efficiency of current delivery mechanisms:
Shift from Individual to Record-Level Attachment
Queries are no longer directed solely to an individual clinician via email; instead, they are attached directly to the patient's electronic health record, allowing any documenting provider to supply clarification or specificity.
Integrated EHR Delivery
Modern workflows embed queries directly into the clinical record instead of relying solely on individual email delivery.
Limitations of Traditional Protocols: Conventional escalation models rely on waiting out set timeframes for an individual provider's response before escalating through supervisory channels. These workflows do not align with integrated EHR models, such as HITEKS, which embed queries directly into clinical workflows.
Shared Responsibility
While documentation accountability remains critical, resolving queries has transitioned from a single-provider task to a shared responsibility across the care team.
Driving Adoption and Provider Engagement
For implementations of this nature, tracking provider engagement and technology adoption serves as a key metric of success. Because solutions that simultaneously enhance documentation quality and efficiency appeal broadly to clinicians, robust education and training programs on tool usage are essential for achieving optimal outcomes.
Dr. Hoo's Workflow Pearl
Update departmental policies around how the query is attached to the record and resolved by the care team, not only around which individual receives it first.
Compliance Summary
HITEKS Sage360 and the ACDIS/AHIMA 2026 Query Guidelines
Sage360, formerly CAPD360 for NoteReader CDI in Epic, operationalizes the 2026 Guidelines for Achieving a Compliant Query Practice. Technology-generated prompts, nudges, and alerts are held to the same compliance standard as manually constructed queries.
1Sec. V.I.A and V.II.ANonleading titles and answer options
Guideline requirement
Query titles and answer choices must never suggest or direct the provider toward a preferred response, and must be free of emphasis such as bolding, arrows, or highlighting.
How HITEKS Sage360 complies
Sage360 delivers a compliant query prompt with neutral, non-diagnosis-directing titling and plain-text answer choices. It uses no color, bolding, or ordering bias toward any diagnosis option.
2Sec. V.I.BNo reimbursement or quality references
Guideline requirement
Queries must never reference reimbursement impact, quality measures, denial mitigation, or reporting initiatives in connection with the clarification requested.
How HITEKS Sage360 complies
Sage360 prompt language is restricted to clinical clarification only. DRG weight, quality-measure impact, and reimbursement outcomes are never surfaced to the provider within the query itself.
3Sec. V.I.C and V.I.C.1 to 2Sourced, objective clinical indicators
Guideline requirement
Clinical indicators must be cited to their location in the health record and presented without subjective interpretation by the query professional.
How HITEKS Sage360 complies
Sage360 provides embedded links to clinical indicators directly within Epic, letting the provider jump to the exact source note, lab, or result. Indicators are shown as objective, sourced data, not staff interpretation.
4Sec. V.II.AClinically relevant options plus Other
Guideline requirement
Every multiple-choice query must include at least one clinically valid, indicator-supported option and an open-ended way for the provider to supply an alternative explanation.
How HITEKS Sage360 complies
Sage360 presents multiple diagnosis suggestions supported by the chart, always paired with an Other free-text option, so the provider can confirm, refine, or override every suggestion with independent clinical judgment.
5Sec. V.I.FNeutral clinical definitions and diagnostic criteria
Guideline requirement
Nationally recognized diagnostic criteria may be included, but must be presented without highlighting or indicating a preferred answer.
How HITEKS Sage360 complies
When applicable criteria are relevant, Sage360 surfaces them through neutral in-Epic links. A Learn More link lets the provider review the evidence in place without leaving Epic or tracking down outside references.
6Sec. IXSending multiple queries
Guideline requirement
It is improper to repeatedly issue the same or substantially similar query in a way that pressures or circumvents a provider's prior clinical judgment.
How HITEKS Sage360 complies
Once a provider documents the target diagnosis, the Sage360 nudge automatically resolves and does not keep re-triggering for that encounter, eliminating repeat-prompt pressure.
7Sec. IV and XIIOrganization-specific governance
Guideline requirement
Organizations must shape query templates and criteria within their own facility policies, clinical definitions, and regulatory requirements, with defined approval and version control.
How HITEKS Sage360 complies
Sage360 is configured to capture each client's own clinical and coding policies, including approved definitions, escalation paths, and specialty-specific criteria, rather than generic vendor-defined query logic.
8Sec. XI.IReal-time, workflow-integrated technology queries
Guideline requirement
CAPD tools are expected to operate in real time during the encounter. Any communication meeting the definition of a query is held to full compliance standards regardless of its label.
How HITEKS Sage360 complies
As an embedded CAPD tool inside Epic NoteReader, Sage360 triggers immediately within the provider's native note-writing and review workflow, providing concurrent, in-context clarification.
9Sec. XI.IIIHuman oversight of technology-generated queries
Guideline requirement
Query and compliance professionals must be involved in evaluating, configuring, and monitoring any technology that generates queries.
How HITEKS Sage360 complies
Because Sage360 logic is configured to the organization's approved clinical and coding policies, the client's CDI and compliance teams retain direct control over prompt content, criteria, and ongoing review.
10Sec. V.I and VIII.IPreserving independent provider judgment
Guideline requirement
A query must allow the provider to exercise independent clinical judgment. Technology must not auto-populate an answer field or suggest a diagnosis without provider validation.
How HITEKS Sage360 complies
Sage360 never auto-populates a diagnosis. Multiple diagnosis suggestions and the Other option let the provider select, revise, or reject every suggestion.
2026 ACDIS/AHIMA Position Paper
Guidelines for Achieving a Compliant Query Practice
This summary is provided for internal HITEKS reference and does not constitute legal or compliance advice. Organizations remain responsible for governance, auditing, and vendor oversight of technology-generated query processes.
Key Takeaway
Compliant query practice still depends on sound policy, clear accountability, and non-leading communication. Modern technology changes the delivery environment, making record-level access, shared resolution, adoption tracking, and provider education essential considerations for departmental protocols.