CPT 93000 is a code-level RVU reference topic. Once the service has been selected through the applicable coding and documentation process, the useful questions are: which RVU components apply, which site-of-service column should be used, which locality adjusts the estimate, and how should the result be separated from physician compensation?
This article explains that workflow without selecting a code for a patient, replacing CPT guidance, or presenting an RVU as a guaranteed fee. For a live code-level estimate, open the RVU Calculator for CPT 93000 and keep the code, setting, locality, and data year with the copied result.
What to review for CPT 93000
The RVU record should be read as a group of related fields, not as one payment number. Review the work RVU, the applicable practice expense RVU, the malpractice RVU, the facility or non-facility setting, and the GPCI values for the locality being modeled.
| Field | Why it matters |
|---|---|
| Work RVU | Represents the physician-work weight used in productivity and many compensation models. |
| Practice expense RVU | Represents practice-resource assumptions and may differ between facility and non-facility columns. |
| Malpractice RVU | Represents the professional-liability component used in the Medicare payment formula. |
| GPCI and locality | Adjust the components for the geographic payment locality rather than for a state average. |
| Conversion factor | Converts the geographically adjusted total RVU into a Medicare payment estimate for the selected year and payment status. |
Work RVU is not the Medicare payment
Work RVU is the part most often used for physician productivity. Medicare payment modeling uses the work, practice expense, and malpractice components together, with a separate GPCI applied to each component. A compensation plan may use work RVU alone and may apply a negotiated dollars-per-wRVU rate that has no fixed relationship to the Medicare conversion factor.
That distinction prevents two common errors: treating the work RVU as a fee, or applying a contract rate to a Medicare payment estimate. Record which question the calculation is answering before interpreting the result.
Payment estimate workflow
Use the following sequence after the code has been selected:
- Confirm that the code and documentation basis are appropriate for the service being reviewed.
- Choose the facility or non-facility practice expense column that matches the payment scenario.
- Select the CMS locality rather than using a statewide average when a locality is available.
- Choose the applicable conversion-factor status and data year.
- Run the estimate in the CPT 93000 calculator view.
- Save the assumptions with the result so another reviewer can reproduce it.
The calculation order can be represented safely as plain text:
Adjusted total RVU =
(Work RVU x Work GPCI)
+ (Selected PE RVU x PE GPCI)
+ (MP RVU x MP GPCI)
Medicare payment estimate =
Adjusted total RVU x Conversion FactorThe formula is a payment estimate under the selected assumptions. It is not a payer remittance, an allowed amount, or a substitute for the current CMS source file.
Comparing CPT 93000 with related cardiology services
Comparison is useful only when the assumptions stay controlled. Keep the locality, setting, conversion-factor status, and data year fixed, then change the code. Do not compare a work RVU from one code with a non-facility payment estimate from another and call the difference a productivity or reimbursement effect.
For a related cardiology procedure, review the CPT 93015 RVU Guide and open the CPT 93015 calculator view. The comparison should identify whether the difference comes from work RVU, practice expense, malpractice, setting, or locality.
Productivity and compensation interpretation
If the goal is productivity, start with the credited work RVU and the contract’s schedule year, threshold, exclusions, modifier rules, and reconciliation timing. If the goal is Medicare payment, use all three RVU components and the applicable GPCI values. These are related workflows, but they should not be merged into one dollar figure.
The cardiology wRVU benchmarks article provides role and volume context. It does not replace the written compensation agreement or prove that a particular target is attainable.
Source and year controls
CMS updates the Physician Fee Schedule and related RVU inputs by data year. The CMS CY 2026 Medicare Physician Fee Schedule final-rule summary is a policy reference, while the calculator uses the structured CPT and GPCI data loaded for the selected year. Keep those roles separate and verify the source row when a value is used in a contractual or operational decision.
What this page does not decide
- It does not determine whether CPT 93000 is the correct code for a service.
- It does not determine a payer’s allowed amount or remittance.
- It does not establish a physician’s contract credit or dollars-per-wRVU rate.
- It does not replace current CPT, CMS, payer, compliance, or legal review.
FAQ
Does CPT 93000 have one fixed Medicare payment?
No. The estimate depends on the RVU components, facility or non-facility setting, locality-specific GPCI values, conversion-factor status, and data year.
Can I use the work RVU as the payment amount?
No. Work RVU is one component. A Medicare payment estimate also uses practice expense, malpractice, GPCI, and the applicable conversion factor.
Can this article determine the correct CPT code?
No. Code selection depends on the service, documentation, CPT rules, payer policy, and compliance review. Use the RVU workflow after the code has been selected.