8.1 AHIMA/ACDIS Practice Brief Standards in Policy Construction

Use a practice brief to evaluate a policy decision

A practice brief helps a CDI team connect a proposed policy to a professional standard. The task is to identify the applicable publication, read the operative provision in context, and decide what the organization must define to put that guidance into practice. Copying a sample paragraph into a policy does not establish that the resulting workflow is appropriate.

The August 2026 ACDIS/AHIMA Guidelines for Achieving a Compliant Query Practice supersedes previous versions, including 2022. Use its actual text when evaluating current query policies. A presentation describing an older version can identify a question to investigate, but it should not substitute for the current provision. Retain the earlier source when explaining a historical decision rather than silently representing it as current guidance.

Establish what authority the source supplies

Sections I and IV describe the brief as educational, expert-informed professional guidance. It establishes the organizations' professional query standard; it is not itself a statute, a payer contract, or an organization's adopted policy. It does not replace independent professional judgment or the separate authority of regulators and review contractors.

Keep the source of each proposed policy requirement visible:

These sources work together. A local choice cannot justify leading a provider, and professional guidance cannot by itself establish every element of a legal violation. If authorities appear inconsistent, identify the exact disputed provision and seek the appropriate coding, compliance, HIM, or legal review. Do not resolve the conflict by choosing whichever source supports the desired payment result.

Read a provision with its scope and examples

Begin with the policy question. Then read the specific operative subsection, nearby qualifications, and the brief's definitions and scope. Record the version and locator so another reviewer can reproduce the conclusion.

Three distinctions prevent common policy errors:

1. A required principle differs from an implementation choice. Section IV preserves nonleading communication, sourced clinical indicators, and independent provider judgment across organizational sizes. It also permits governance and audit designs proportionate to resources. A rural practice needs an accountable process, but the brief does not require it to reproduce a large hospital's committee structure.
2. An example differs from an exclusive requirement. Section XII calls for regular template review and gives annual review as an example. It also identifies event-driven reasons for revision, including coding or regulatory updates, changed clinical criteria, workflow changes, and audit findings. Neither “every twelve months is the only permitted schedule” nor “an approved template is safe until next year's meeting” follows from that passage.
3. A sample topic differs from a complete operational rule. Section XIII supplies a nonexhaustive set of policy subjects. Its general references to response options must be read with the format-specific provisions in Section V. A policy author should not turn a parenthetical example into a universal answer menu or ignore a specific requirement because a later summary is shorter.

This reading method supports a defensible interpretation without treating the document as an inflexible checklist. The detailed drafting rules and worked query examples are taught in Sections 15.2–15.3; the policy task here is to use the correct provision to evaluate the proposed organizational rule.

Build a source-to-policy crosswalk

A crosswalk makes the reasoning visible. It can be a concise working document rather than a separate policy for every subsection. The following is an illustrative review tool, not a nationally required form:

For each row, distinguish an explicit source statement from the organization's selected method. If the organization chooses a quarterly review meeting, identify that as its operating design. If the source calls for patient-specific fields, the implementation must actually permit appropriate customization; a policy sentence alone does not supply the missing system capability.

Apply the correct setting before approving reuse

Section III includes inpatient, outpatient, ambulatory, and professional-fee query practice, with contextual differences. The broad application of nonleading communication does not make every inpatient reporting rule portable.

Worked policy review: A team proposes using its inpatient clarification policy in a physician practice. The draft correctly retains independent provider judgment, but also instructs outpatient coders to report diagnoses documented as probable and assigns a POA indicator to each condition. The correct response is a setting-specific revision. Keep the applicable query principles, remove the inpatient POA process, and reconcile diagnosis reporting with the outpatient provisions in the FY2027 ICD-10-CM Official Guidelines. Do not assume that a shared EHR or the same provider makes the reporting settings identical.

Similarly, determine whether a tool actually requests patient-specific clarification. Calling a function a prompt, alert, or nudge does not exempt query-generating work from the brief. Policy review must consider its actual function and organizational accountability. Section 22.1 examines the technology risks in detail.

Evaluate audit findings and implement the interpretation

Section I explains substantial compliance through the core query principles and cautions against treating an isolated technical deviation as a stand-alone adverse finding. A minor formatting inconsistency alone is different from a question that steers the diagnosis or omits relevant contrary information. Record what happened and assess its substantive effect; neither automatically deny every affected claim nor dismiss a meaningful defect as formatting.

The brief also does not immunize claims from properly grounded review. A coding error, a coverage issue, and alleged fraud require their own applicable facts and authority. The DOJ False Claims Act overview describes a separate legal framework; a policy crosswalk is not a substitute for that analysis.

Close the policy review with a documented interpretation, the affected policy or template, its owner, and an implementation check. Explain the change to staff and relevant vendors, retire or revise obsolete materials, and examine actual use after implementation. Preserve enough version history to explain which instructions applied when. This turns a professional publication into a usable, reviewable policy decision while leaving detailed response placement, communication channels, and retention rules to the appropriate lessons and record owners.