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.

specialties listed infrequently as performing a certain<br />

procedure. The assumption was that the infrequent instances<br />

<strong>of</strong> these specialties in our data represent aberrant<br />

occurrences and removing the associated risk factor from the<br />

malpractice RVU calculation would improve accuracy and<br />

stability <strong>of</strong> the RVUs.<br />

We excluded evaluation and management (E&M) services<br />

from the analysis. Medicare claims data show that E&M codes<br />

are performed by virtually all physician specialties.<br />

Therefore, in the case <strong>of</strong> E&M codes, it is likely that even<br />

the low relative percentages <strong>of</strong> performance by some<br />

specialties would accurately represent the provision <strong>of</strong> the<br />

service by those specialties.<br />

For all services other than E&M services, we believe<br />

removing data attributable to specialties that occur in our<br />

data less than 5 percent <strong>of</strong> the time would most<br />

appropriately balance the objective to identify aberrant<br />

data (claims with a specialty identified that is highly<br />

unlikely to have performed a particular procedure) while<br />

including specialties that perform a procedure a small<br />

percentage <strong>of</strong> the time. We believe a higher threshold would<br />

result in the removal <strong>of</strong> data for specialties actually<br />

performing the procedure, while a lower threshold would<br />

likely fail to remove some aberrant data, particularly for<br />

95

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

Saved successfully!

Ooh no, something went wrong!