The answer depends on what the visit actually documented.

Rule. Exception. Documentation.

Every answer names the controlling rule, the edge case that overrides it, and the exact documentation required to defend the code selection on audit.

Questions are grouped by clinical scenario. Find the situation that matches yours, not a keyword that might.

Boundary cases — where two codes share overlapping scope — are treated as their own category, not footnotes.

— Organized by scenario

Find the situation, not the keyword.

Categories reflect how coding decisions actually arise — by visit type, procedure context, or documentation gap — not by code number range.

E/M Visit Coding

Procedures & Modifiers

Documentation Requirements

When does the visit level change?

Which modifier applies here?

What must the record contain?

MDM thresholds, time-based billing, new vs. established patient rules, and the documentation elements that move a 99213 to a 99214.

Bilateral procedures, assistant surgeon modifiers, same-day E/M with a procedure, and when modifier 25 is defensible versus when it draws scrutiny.

Minimum note elements by code, audit-ready phrasing for common scenarios, and the specific gaps that trigger downcoding on post-payment review.

Example boundary pairs

+ Boundary-Case Category

Where two codes share the same territory.

99213 vs. 99214

MDM complexity is the deciding axis. Which data points were ordered, reviewed, or acted upon — and does the note prove it?

99213 vs. 99214

Boundary cases are treated as a distinct FAQ category — not footnotes. Each entry identifies the deciding factor: the clinical detail or documentation element that commits the code one way.

Separate procedures performed on the same date: is each independently reportable, or does bundling apply under NCCI edits?

▸ Submit a question

Don't see your scenario covered?

Send the specific code situation — include the visit type, the codes in question, and what the note currently supports. We'll give you a direct answer.