Skip to main content

How do I review coding audit results?

Open encounters in the Audit Result queue, leave notes in the comments box, and approve, reject, or hold each audit result.

Written by James Smith

Ember AI codes charts and routes the results to a reviewer for confirmation. This article covers how to review an encounter, leave notes, and approve, reject, or hold each result.

Who this is for

Anyone reviewing coding audit results, typically physicians, coders, auditors, or RCM leads working out of the work queue.

Opening an encounter

Open the Audit Result work queue. Click any encounter to review it.

Reading the encounter

The encounter form shows the chart, Ember's coding output, and any flags or notes. Scroll the form body to read through everything. The action bar stays pinned to the bottom-left of your viewport while you scroll, so the buttons are always reachable.

Leaving Comments

Type any notes in the comments box on the encounter. Comments are saved when you take an action on the encounter (Approve, Reject, or Hold). There's no separate save step.

Multiple team members can leave comments on the same encounter, and you can see what others have already left. Use comments to:

  • Explain why you're rejecting or holding

  • Flag a documentation gap for the provider

  • Ask a coder to take a second look

  • Respond to a teammate's earlier note

Approving, rejecting, or holding

When you're ready to act, use the buttons at the bottom-left or the keyboard shortcuts:

Action

Shortcut

Approve

A

Reject

R

Hold

H

Approve is the leftmost / primary action. The action bar pins to the bottom-left of your viewport so it's reachable on any screen size, no horizontal or vertical scrolling needed. Shortcut hint chips show next to each button on desktop to help you learn them.

Typing in the comments box? Shortcuts pause while your cursor is in the comments textarea or any other input. You can type freely, shortcuts only fire when you're not actively editing text.

Did this answer your question?