19.02.2013 Views

2006 proposed fee schedule - American Society of Clinical Oncology

2006 proposed fee schedule - American Society of Clinical Oncology

2006 proposed fee schedule - American Society of Clinical Oncology

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

indirect expenses for this procedure <strong>of</strong> $132,055,728. The<br />

process is repeated across all procedures performed by the<br />

specialty, and the indirect expenses for each service are<br />

summed to arrive at the total specialty indirect PE pool <strong>of</strong><br />

$6,745,545,434.<br />

TABLE 4--Calculation <strong>of</strong> Indirect Expense<br />

Standard Methodology<br />

Physician<br />

Work*<br />

Total Direct<br />

Expense<br />

Total<br />

(A) (B) (C)<br />

(a) CPT 00001 $81.43 $234.04 $315.47<br />

(b) Allowed Services 418,602<br />

(c) Subtotal $132,055,728<br />

(d) All Other Services $6,613,489,706<br />

(e) Total Indirect Expense $6,745,545,434<br />

*Calculated by multiplying work RVU <strong>of</strong> 2.36 by 1995 conversion factor <strong>of</strong> $34.5030.<br />

Step 5--Calculation and Application <strong>of</strong> Indirect Scaling<br />

Factors<br />

Similar to the direct costs, the indirect costs are<br />

scaled to ensure that the total across all procedures<br />

performed by the specialty equates with the total indirect<br />

costs for the specialty as reflected by the SMS data. To<br />

accomplish this, the indirect costs calculated in Step 4<br />

(Table 4) are scaled to SMS data. The calculation <strong>of</strong> the<br />

indirect scaling factors is as follows:<br />

● The specialty’s total SMS indirect expense pool is<br />

divided by the specialty’s total indirect expense pool<br />

calculated in Step 4 (Table 4), to yield the indirect<br />

expense scaling factor.<br />

38

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!