Your compensation committee meets Thursday, and someone is going to ask why one physician's work RVU total trails a colleague's by double digits when both saw a similar volume of new patients. The answer almost always lives in the distribution between 99203 and 99204 — which is why the 99204 RVU ends up on a slide in front of people who have never opened a fee schedule file.

This guide is for the administrator, billing lead, or privacy officer who has to make that number defensible. It covers where the value comes from, how often it moves, how practices document code selection without straying into clinical territory, and — the part most operations guides skip — which vendors touch that data and whether you have a signed agreement with each of them.

How the 99204 RVU Breaks Down

Every code in the Medicare Physician Fee Schedule carries three relative value units, and 99204 is no exception:

  • Work RVU (wRVU) — the physician effort component. This is the number your compensation formulas almost certainly key on. For several years running, the work RVU assigned to 99204 has been 2.60, unchanged since the 2021 office-visit revaluation.
  • Practice expense RVU (PE) — staff, supplies, and overhead. It splits into facility and non-facility values. The non-facility figure is meaningfully higher, because in an office setting your practice absorbs the overhead.
  • Malpractice RVU (MP) — the smallest of the three, and the one nobody argues about.

Add the three together for the setting in question, apply your locality's geographic practice cost indices, multiply by the conversion factor, and you have the Medicare allowable. In recent years the non-facility total for 99204 has run in the low fours before geographic adjustment.

Do not carry any of those numbers forward on faith. CMS republishes the full RVU file annually, and mid-year corrections happen. Verify against the current-year file using the CMS Physician Fee Schedule Look-Up Tool before anyone builds a budget on it.

The conversion factor is the part that moves

The relative values for office visits have been comparatively stable. The conversion factor has not. It changes each year, has repeatedly been the subject of late-December congressional action, and beginning in 2026 the statute directs different annual update percentages depending on whether a clinician qualifies as an advanced APM participant. Your finance team may now be modeling with more than one conversion factor for the same code.

Practical consequence: if your physician compensation plan pays on work RVUs alone, conversion factor volatility hits the practice's margin, not the physician's paycheck. If it pays on collections, the physician absorbs it. Know which model you signed before the question comes up in a hallway.

Why 99204 Is the Code Auditors Circle

99204 sits in the middle-to-upper band of new patient office visits. It is common enough to be unremarkable and valuable enough to move revenue at scale. A practice that shifts a few percentage points of new-patient volume from 99203 to 99204 will see the difference in a quarter — and so will any payer running distribution analytics against peer benchmarks.

That does not make a higher 99204 share wrong. Panel complexity, specialty, and referral patterns legitimately drive distribution. It does mean your documentation has to explain itself without a coder standing next to the chart.

How practices determine and document code selection

Under the current office and outpatient E/M framework, code level is selected on either medical decision making or total time on the date of the encounter. Which basis a clinician used should be recorded — not inferred later by a biller trying to reverse-engineer intent.

Operationally, that means three things for your team:

  1. Build the time attestation into the template, with a discrete field rather than free text. Free-text time statements are unsearchable, which makes internal audits expensive.
  2. Do not let front-office or billing staff select or upgrade the level. Coding staff may query; they may not decide clinical complexity. Write that boundary into your billing policy and your coder job description.
  3. Log the query. If a coder asks a clinician to clarify documentation, the query and the response belong in the record with a timestamp. This is the artifact that survives an audit.

Nothing in this section tells you which code fits which patient. That determination belongs to the treating clinician working from the current code set definitions. Your job is to make sure the process is consistent, documented, and reviewable.

The Vendor List Behind Every 99204 RVU Calculation

Here is where operations becomes a privacy problem. Trace the path a single 99204 encounter takes through your systems and count the outside organizations that touch it:

  • Your EHR host
  • The billing service or revenue cycle vendor generating the claim
  • The clearinghouse transmitting it
  • Any coding audit firm sampling your charts
  • Ambient documentation or AI coding-suggestion tools sitting inside the encounter
  • The analytics platform producing your wRVU dashboards
  • The benchmarking service comparing your E/M distribution to peers
  • The consultant who built your compensation model and asked for a data extract

Every one of those handles protected health information on your behalf. Every one requires a business associate agreement before the data moves, and the agreement has to cover what HHS specifies — permitted uses, safeguards, subcontractor flow-down, breach notification timing, and return or destruction at termination. HHS maintains guidance on business associate obligations that your legal review should track against.

The gap I see most often is the analytics and benchmarking layer. Practices are meticulous about the clearinghouse and casual about the dashboard vendor, because the dashboard "only shows RVUs." It shows RVUs derived from encounter-level records tied to patient identifiers, and it usually retains them. If you discovered a benchmarking vendor on your list without a current agreement, 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 — rather than waiting three weeks for outside counsel to redline a template.

Two contract terms worth arguing over

Retention. Ask how long the vendor keeps encounter-level data after the reporting period closes. Many keep it indefinitely to power trend charts. Decide whether you want that, and write the answer into the agreement.

Secondary use. Benchmarking products need pooled data to function. Read the clause that lets the vendor use your data for "product improvement" or "aggregate industry reporting." Confirm whether that pooling happens on de-identified data and, if the vendor claims de-identification, which method they used. HHS explains the Safe Harbor and expert determination standards; a vendor that cannot say which one applies has not done it.

Billing Records Are Part of the Designated Record Set

A patient requests "everything you have." Your front desk pulls the clinical chart and sends it. That request was not fully satisfied.

The designated record set includes billing and payment records used to make decisions about the individual. That means the claim, the code billed, the payer response, and the explanation of benefits data sitting in your practice management system fall inside the scope of a HIPAA right of access request. If a patient asks why their new patient visit was billed at a particular level, the records-handling obligation is real and the clock is 30 days.

Three operational fixes:

  1. Write a records request checklist that names both the clinical system and the billing system as sources. Assign a named owner in each.
  2. Log the fulfillment date against the request date. If you need the single 30-day extension, document the reason and notify the patient in writing before the original deadline expires.
  3. Do not charge for the extension or for staff search time. Fee limits under the access right are narrow. Review the HHS individual right of access guidance with whoever prices your record copies.

A Twelve-Month Operating Calendar for RVU Data

November–December. The final Physician Fee Schedule rule publishes. Pull the RVU file, load next year's values into your compensation model and your fee schedule, and flag any code whose values moved. Confirm your billing vendor loaded the same file.

January. Verify the first claims cycle prices correctly. A stale conversion factor in one system and a current one in another produces reconciliation noise that takes months to unwind.

Quarterly. Run E/M distribution by clinician. Look at the 99204 share against the prior quarter and against your own historical baseline before you look at any external benchmark. Sudden shifts deserve a conversation; steady differences between clinicians usually reflect panel composition.

Semi-annually. Sample charts for documentation completeness — specifically whether the basis for level selection is recorded. Keep the sampling methodology written down so the audit is reproducible.

Annually. Reconcile your vendor inventory against your signed BAAs. Anyone who received an RVU extract, a chart sample, or a claims file in the past twelve months belongs on the list. This is also the moment to refresh your security risk analysis, since the systems holding this data are the same ones your analysis has to cover. If that assessment lives in a spreadsheet somebody updated in 2023, tools that automate the risk analysis and policy set will get you further than another calendar reminder.

What to Check Before Thursday's Meeting

Confirm the 99204 RVU values in your compensation model match the current-year CMS file, not last year's. Confirm which conversion factor applies to which clinician. Confirm your coding staff have documented authority to query but not to change levels. Confirm your billing system is named in your records request procedure.

Then look at the analytics vendor producing the slide deck and ask when you last signed an agreement with them. If the answer is a shrug, build the BAA now — before the extract goes out for the next reporting cycle. It takes less time than the meeting will.