Skip to content

Visit coding

In development

Visit coding prepared from the signed note.

CodeIQ Visit is in development. It reviews the signed clinic note and proposes the E/M level and diagnosis codes the documentation supports, for the physician to confirm.

The problem

The note and the billed level do not always match.

In a retrospective review, many level-3 visits had documentation that supported a higher level. That shows where coding review could help. It does not mean those visits should have been billed differently.

How it works

Prepared by OpAgent. Decided by your team.

  1. 01

    What OpAgent prepares

    A proposed E/M level and diagnosis codes, each linked to the supporting text in the signed note.

  2. 02

    What the physician reviews

    The physician confirms or changes the codes. CodeIQ Visit does not submit claims.

  3. 03

    Where approved work goes

    Confirmed codes would be saved to the encounter in athenaOne. This workflow is not offered to practices yet.

Availability

In development

Being built or evaluated. Not offered to practices yet.

Evidence

What has been measured

Measured

52.3%

Level-3 established visits whose signed note supported level 4

Population
Established-patient visits billed as 99213 at one participating orthopedic practice
Sample
3,985 graded visits
Period
Retrospective sample, August 2026 benchmark
Compared with
The visit level that was billed

Limitation: Shows where to audit, not that every visit should have been billed higher. No encounter was re-billed.

How this was measured →

Detailed methods →

Related workflows

How it connects

  • OpAgent WrapIn development

    The note and documentation review that coding depends on.

  • ReQoverIn development

    Planned connection. Payment review after the visit is billed.