19.02.2013 Views

Notice: This CMS-approved document has been submitted - Philips ...

Notice: This CMS-approved document has been submitted - Philips ...

Notice: This CMS-approved document has been submitted - Philips ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>CMS</strong>-1403-FC<br />

same as the sum of the current work RVUs (weighted by<br />

projected frequency of use) for each family of codes.<br />

Comment: Some commenters believed these codes should<br />

have <strong>been</strong> considered as part of the 5-Year review process<br />

and the increase in work RVUs should have <strong>been</strong> absorbed<br />

through the BN work adjuster. The commenters also<br />

disagreed with the application of BN and noted that this<br />

created rank order anomalies. The commenters requested<br />

that if BN is applied, it should be implemented across the<br />

entire fracture family of codes, which would include codes<br />

that have not <strong>been</strong> surveyed (Harvard valued codes).<br />

Response: The commenters did not submit sufficient<br />

information to demonstrate that the application of BN<br />

created rank order anomalies for these codes. We note that<br />

the base codes for each fracture family of codes could be<br />

<strong>submitted</strong> to the AMA RUC for re-valuation. <strong>This</strong> would<br />

enable the codes within the family, several of which have<br />

not undergone an AMA RUC review, to be properly aligned in<br />

comparison to the base codes within each family.<br />

2. Cardiac MRI Codes<br />

For CY 2008, the CPT Editorial Panel created eight new<br />

Cardiac Magnetic Resonance Imaging (MRI) codes and deleted<br />

five existing Cardiac MRI codes due to technological<br />

changes and advances in MRI scanning. We established a<br />

898

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

Saved successfully!

Ooh no, something went wrong!