Your highest-volume provider billed 99215 on 4% of established patient visits last year. This January, after a new documentation workflow went live, that number hit 19%. Six weeks later a commercial payer sends a pre-payment review letter requesting 40 charts. Now you are pulling records, redacting nothing, emailing a zip file to an address you have never seen before, and hoping somebody signed a Business Associate Agreement with the review vendor.

This guide is for the administrator sitting in that seat. It covers what the 99215 RVU actually is, where to verify it each year, how practices document code selection without your office guessing at clinical judgment, and the records-handling and vendor obligations that attach the moment high-level visit coding draws attention.

What Is the 99215 RVU? The Short Answer

99215 is the highest-level office or other outpatient visit code for an established patient. Its relative value units are assigned by CMS in the Medicare Physician Fee Schedule and published annually in the Relative Value Files.

Three components make up the 99215 RVU total:

  • Work RVU — 2.80 since the 2021 office visit revaluation, up from 2.11 before it.
  • Practice expense RVU — differs between non-facility (your office) and facility (hospital outpatient) settings, and CMS adjusts the methodology from year to year.
  • Malpractice RVU — the smallest component, also revised periodically.

Recent non-facility totals for 99215 have landed in the neighborhood of 3.6 to 3.8 RVUs. Payment is not the total RVU times a flat rate. Each component is multiplied by its own locality-specific geographic practice cost index, summed, and then multiplied by the conversion factor. That is why the same 99215 pays differently in Manhattan and rural Kansas.

Pull the authoritative numbers yourself from the CMS PFS Relative Value Files rather than trusting a fee schedule your clearinghouse loaded three years ago.

Why 2026 Broke the Single-Number Answer to "What Does 99215 Pay?"

Under the statutory update schedule set by MACRA, 2026 is the first year Medicare applies two conversion factors: a higher annual update for clinicians who qualify as participants in advanced alternative payment models, and a lower one for everyone else. Same 99215 RVU, two different Medicare allowables depending on the billing clinician's participation status.

Operationally, that means your fee schedule maintenance is no longer a single annual import. If you have providers on both sides of that line, your practice management system needs to reflect it, and your patient estimates and coinsurance calculations need to reflect it too. Give this to one named person with a February deadline, not to "billing" as a department.

It also means any vendor-supplied fee schedule, revenue projection, or compensation model built on a single conversion factor is now approximate at best. Ask your revenue cycle vendor in writing which factor they applied.

How Practices Document 99215 Code Selection Without Guessing at Clinical Judgment

Since 2021, established patient office visit level selection rests on either medical decision making or total time on the date of the encounter. Your administrative job is to make both paths auditable. It is not to tell a clinician what level a visit was.

The Time Path and the Documentation Trap

99215 corresponds to 40–54 minutes of total time on the date of the encounter, including qualifying non-face-to-face work performed that day. Practices that rely on the time path need a documented time statement in the note, and they need it to be a real number rather than a template default.

Templates that auto-populate "45 minutes" are the single most common finding in internal audits of high-level visit coding. If your EHR inserts a time value that a clinician must affirmatively edit, you have built a defect into every chart. Have your compliance lead sample ten notes per provider per quarter and check whether the time values vary. If they never vary, escalate before a payer finds it.

The Medical Decision Making Path

The MDM path turns on the number and complexity of problems addressed, the amount and complexity of data reviewed and analyzed, and the risk of complications from management decisions. Those are clinical determinations. Your role is to confirm that the note contains enough documented detail for a reviewer to follow the reasoning, and to route ambiguity back to the clinician as a query rather than resolving it in the billing office.

Write that boundary into your coding policy explicitly: coders may query, coders may not upgrade or downgrade a level on their own judgment. Log every query and its resolution. When an auditor asks how you control coding accuracy, that log is your answer.

Using the 99215 RVU in Compensation and Productivity Without Creating a Compliance Problem

Work RVUs are the standard currency for provider compensation and productivity benchmarking. The 2.80 work RVU on 99215 versus 1.92 on 99214 creates a measurable financial incentive at the individual clinician level, which is precisely why regulators and plaintiffs' counsel look at level distribution curves.

Three controls keep an RVU-based comp model defensible:

  1. Distribute level-of-service distributions to providers quarterly, benchmarked against specialty peers and against the provider's own prior-year pattern. Silent drift is the problem; visible drift is a conversation.
  2. Separate the audit function from the revenue function. Whoever reviews coding accuracy should not report to whoever owns collections targets.
  3. Document your response to outliers. An outlier who received education and improved is a compliance program working. An outlier nobody addressed for three years is an exhibit.

Compensation dashboards built on the 99215 RVU also usually live in a spreadsheet or BI tool outside your EHR. Confirm that those extracts are de-identified or, if they carry encounter-level patient identifiers, that the platform hosting them is covered by a signed agreement and included in your risk analysis.

When a Payer Audits Your 99215 Volume, PHI Leaves the Building

Here is where a coding article becomes a privacy article. High-level visit coding attracts pre-payment review, post-payment review, and recovery audits. Every one of those events means charts move from your custody to somebody else's.

Disclosures to Health Plans

Sending requested records to a health plan for payment-related review is a permitted disclosure for payment purposes. It does not require patient authorization. It does require you to apply the minimum necessary standard — send the encounters and supporting documentation requested, not the entire longitudinal chart because exporting the whole record was faster.

Practical control: require that every records production for an audit be logged with the requester, the date range, the specific encounters produced, the transmission method, and the staff member who sent it. When a second request arrives eight months later, you will need to know exactly what already went out.

The BAA Gap That Shows Up in Almost Every Coding Audit

Plans routinely outsource chart review to third-party audit contractors. When such a contractor is acting on the plan's behalf, the plan owns that relationship. But look at your own side of the transaction: the outside coding consultant you hired to defend the 99215 sample, the independent auditor doing your quarterly reviews, the transcription or ambient documentation vendor generating the note that supports the time statement, the secure file transfer service you used to send 40 charts.

Each of those is a business associate creating, receiving, maintaining, or transmitting PHI for you. Each requires a signed agreement before the first chart moves. HHS's guidance on business associate relationships is unambiguous on the point, and "the audit was urgent" has never been an accepted defense.

Audits are exactly the moment practices discover they have no paper. If you need a contract in hand today rather than after a two-week legal cycle, you can generate a signature-ready Business Associate Agreement through a six-step wizard and export it as PDF or DOCX — one-time purchase, no subscription. Get it signed before the file transfer, not after.

Ambient Documentation Vendors Deserve a Separate Line

If your clinicians use an AI scribe or ambient listening tool, that vendor is processing the encounter audio and drafting the note that carries your time statement and MDM narrative. Three questions for your vendor file:

  • Is the recording retained, and for how long?
  • Is patient data used to train models, and is that use carved out in the agreement?
  • Which subcontractors touch the audio, and are they flowed down under the BAA?

Those answers belong in your risk analysis, not in a sales deck. If your current documentation set does not cover this category of vendor, automating your risk analysis and policy set is faster than rewriting a 2019 template by hand.

A Twelve-Month Operating Calendar for High-Level Visit Coding

January. Import the current year's Relative Value Files. Verify the 99215 RVU components against the file, not against a vendor summary. Confirm which conversion factor applies to each billing clinician. Update patient estimate tools.

February. Reconcile the first month of payments against the loaded fee schedule. Underpayments here compound for eleven months if nobody checks.

Quarterly. Ten-chart-per-provider internal review of level selection and time documentation. Distribute distribution curves. Log queries and outcomes.

Semiannually. Reconcile the vendor list against signed BAAs. Anyone who touched a chart during an audit response goes on that list. Confirm expiration and subcontractor terms.

Annually. Refresh front-desk and billing training on records production limits, the query-not-upgrade rule, and the audit response workflow. Document attendance.

Assign These Four Roles by Name

  • Fee schedule owner — imports RVU files, verifies conversion factors, reconciles payments.
  • Coding audit lead — samples charts, runs queries, reports to compliance rather than to revenue.
  • Records production custodian — the only person who releases charts for audits, and the keeper of the disclosure log.
  • Vendor and BAA owner — maintains the list, holds the signatures, blocks data transfers to unsigned parties.

One person can hold two of these in a small practice. Nobody should hold all four, and the coding audit lead should never also be the records production custodian during an active payer review.

Do This Before Your Next Payer Letter

Verify the 99215 RVU values in your system against the current CMS file. Pull your level distribution by provider for the last four quarters. Then open your vendor list and find the coding consultant, the auditor, and the file transfer service — and confirm each one has a signed agreement on file. If any line is blank, build and export the agreement you need now, before the next chart request forces the decision for you.