Physicians could feel a little looser on their spending thanks to a hold on the 2011 Medicare Physician Fee Schedule cut.
On Nov. 18, the U.S. Senate unanimously consented to halt the Medicare planned conversion factor cut for a 31-day period. The U.S…
A major insurer will now pay for turbinate fracture in addition to septoplasty. Thanks to advocacy from the American Academy of Otolaryngology–Head and Neck Surgeons (AAO-HNS), Aetna has overturned its coverage position on 30520 and 30930 billed on t…
When your urologist fragments more than one stone located in two different locations within the urinary tract during one operative session, the proper coding might leave you scratching your head: Can you ever report both procedures? If you can, how do you sequence the codes? Tackle these tough questions by reviewing a sample scenario.
Your urologist performs a ureteroscopic laser lithotripsy of a left ureteral stone and lithotripsy of a bladder stone. How should you code these procedure performed during one operative session?
Separately Report Procedures Based on Anatomy
Depending on where the stones are in the urinary tract, you may be able to separately report and be paid for multiple fragmentation procedures during the same session. For a ureteroscopic fragmentation of a ureteral or renal pelvic stone your urologist performs, you’ll report 52353 (Cystourethroscopy, with ureteroscopy and/or pyeloscopy; with lithotripsy [ureteral catheterization is included]). Remember that 52353 applies to “any type of fragmentation, whether you use a Holmium laser, a Candela laser, a mechanical lithotripsy, or an ultrasonic lithotripter,” says Michael A. Ferragamo, MD, FACS, clinical assistant professor of urology at the State University of New York at Stony Brook. If your urologist also fragments a bladder calculus during the same session, your coding will then depend on the different and separate anatomical location of the stones. Therefore, in the sample scenario, you can separately report those procedures. “We are dealing with two separate portions or parts of the urinary tract – a ureteral stone and a bladder stone,” Ferragamo explains.
According to the Correct Coding Initiative (CCI), codes 52317 (Litholapaxy: crushing or fragmentation of calculus by any means in bladder and removal of fragments; simple or small [less than 2.5 cm]) and 52318 (…complicated or large [over 2.5 cm]) are bundled with 52353. Because both bundles have a…
Question: Sometimes I cannot find my two-code pair in the CCI edits. How do I know which code would be considered a column 1 code and which would be considered a column 2 code, so that I could put my modifier on the correct code?
Answer: If the codes are not listed, the codes are not bundled per the Correct Coding Initiative (CCI). You would not need a CCI modifier, such as 25 (Significant, separately identifiable evaluation and management service by the same physician on the same day of the procedure or other service), 57 (Decision for surgery), or 59 (Distinct procedural service), to override the edit when appropriate.
A private payer could have a black box edit. You would need to check with a rep for a recommendation.
Watch out: Just because a code does not have a bundle in CCI does not mean a modifier is out of the picture. While you won’t need a CCI modifier to override the edit, you might need apayment modifier.
You can find Medicare’s other allowed modifiers for any given CPT code in the Medicare Physician Fee Schedule (MPFS). Columns Y-AC indicate if modifier 51 (Multiple procedure), 50 (Bilateral procedure), etc. apply.
To determine which code receives modifier 51, you need to know the code’s relative value units, which are also listed in the MPFS. Private payers may not adjust claim items in descending order as Medicare’s Outpatient Code Editor software does. If you append modifier 51 to a higher valued item, the private payer may apply the adjustment based on your coding, costing you payment. You should instead list the items in descending relative value order from highest to lowest. Append modifier 51 to the lower priced procedure as necessary. The insurer will then apply the typical 50 percent,…
When reporting diabetic foot ulcer treatment involving tissue cultured skin substitutes to the lower extremity for a Medicare beneficiary in 2011, you’ll use two temporary G codes.
Providers were concerned about the different global periods for two t…
March 21, 2007
Dear JCAAI Member:
We recently surveyed JCAAI members regarding reimbursement for an E&M service on the same day as a skin test or on the same day as an injection (95115 – 95117). Well over 80% are paid for an E&M service on the same day as a skin test. Far fewer are paid for an E&M service on the same day as an injection. In particular, the majority of allergists reported that they were not paid for an injection on the same day they billed a minimal office visit (99211).
Under Medicare policy, neither the injections codes nor the skin testing codes have global periods. Codes that have global periods (typically procedure codes) usually cannot be billed with an office visit because the E & M service is considered bundled into the procedure. Codes that do not have global periods do not include any bundling of E & M services; thus, coding policy generally permits them to be billed on the same day as an E & M without the use of modifier-25. However, as our survey results indicate, not all payers are aware of or are following this policy. This may be because, until January 1, 2006, the injection codes were classified as global period codes (which meant that they could not be billed with an E & M service without the use of modifier-25). JCAAI was successful in getting Medicare to change this so that you are allowed to bill an E & M service (including 99211) with allergy injection codes without meeting the requirements for modifier-25. The primary reason for this change was to allow a physician to bill 99211 when dealing with clinical issues surrounding allergy injection administration (e.g., directing a nurse giving injections as to what the nurse should do if…