What this page covers
Urology billing services manage a procedure ladder that runs from the office to the operating room: diagnostic cystoscopy (52000) carries no global period, TURP (52601) carries 90 days, and staged stone care in between rides on modifiers 58 and 78. Around the procedures sit prior authorization for BPH treatments such as UroLift and Rezum, NCCI edits across the urodynamics codes, and buy-and-bill drugs like intravesical BCG (J9030) billed in per-milligram units. Flexbone runs eligibility, authorization, modifier and unit checks, and denial work for urology groups inside your EHR and billing system.
How do global periods work in urology billing?
The global period follows the setting up the ladder. Diagnostic cystoscopy (52000) and most of its office family, including biopsy and fulguration variants, carry a 0-day global, so a same-day evaluation and management visit pays only with modifier 25 and documentation of a separately identifiable service. Major surgery such as TURP (52601) and prostatectomy carries a 90-day global under the Medicare fee schedule, which bundles routine follow-up into the surgical fee: an unrelated visit inside the window needs modifier 24, and an unrelated procedure needs 79. Because the office procedures carry real patient cost sharing, benefits belong in front of the visit rather than after it. Flexbone runs the eligibility and benefits check before the appointment, then verifies the modifier logic against the global calendar before the claim files.
Get an outside read on your urology billing workflow
In 30 minutes we map your current volume, the payers and systems involved, where staff time goes, and the highest-ROI calls and follow-ups Flexbone can take off your team first, scoped to the work you actually run.
How are staged stone procedures billed?
Stone care is where the staging modifiers earn their keep. An obstructing stone often gets a stent first, then a definitive ureteroscopy with laser lithotripsy (52356) days or weeks later, inside the global period the first procedure opened. That second procedure bills with modifier 58 as a planned, staged service and pays in full. An unplanned return to the operating room for a related problem, such as retained fragments or a complication, bills with modifier 78 and pays at a reduced rate. Confusing the two either forfeits revenue or draws a denial, and shockwave lithotripsy (50590) with a planned second treatment raises the same question. The claim must also agree with the authorization and the operative note on laterality. Flexbone checks stage, side, and approval agreement pre-submission, and its denials management agents work whatever still comes back.
Which urology procedures and drugs need prior authorization?
The BPH device procedures carry the heaviest requirement. UroLift (52441, 52442) and Rezum (53854) commonly require prior authorization with documentation that medication therapy, typically alpha blockers or 5-alpha-reductase inhibitors, was tried and failed, and Medicare and commercial plans apply different criteria. Urodynamics adds a bundling problem rather than an authorization one: the cystometrogram codes (51728, 51729) sit inside NCCI edits with their companion studies, and the voiding pressure code 51797 bills only as an add-on to them. On the drug side, intravesical BCG bills as J9030 in 1 mg units alongside the instillation code 51720, so the unit count must match the documented dose. Flexbone determines each requirement, submits the request, and tracks it to a decision. The urology and gynecology PA page covers the procedure criteria.
How does Flexbone run urology billing?
Flexbone deploys browser and voice agents across the urology revenue cycle. Agents verify eligibility and benefits before the visit, determine the authorization requirement for BPH procedures, imaging, and drugs, submit and track the requests, check global-period and staging modifiers and drug units before claims file, and work the denial queue by CARC code inside your EHR and billing system. The front-office side, procedure scheduling and the surveillance recall that PSA monitoring and stone follow-up depend on, is covered on the AI for urology page. Results write back with an audit trail, and exceptions route to your billers with the context attached, so staff time goes to the claims that need judgment rather than the ones that need keystrokes.
How Does a Flexbone Deployment Work?
Every deployment starts from the work as your team does it today, not from a product demo. The steps below are the same whether the first agent answers phones, checks eligibility, or files incoming documents.
- Audit first, then automate. We listen to a sample of your calls and read the work queues, then agree with your team on which work to automate first. The audit is complimentary.
- Forward-deployed engineers map your SOPs. An engineer sits with the staff who do the work and turns your written and unwritten rules into agent logic.
- Agents act on your rules, and exceptions go to a person. Each step follows logic built from your SOPs. A case outside those rules, or one the agent is not confident about, goes to your team with the context attached.
- Every action leaves a record. A check in a web application saves a screenshot, a call saves a transcript, and results are written back where your team already looks.
- Start with one or two agents on the systems you already run. The agents work in your EHR, practice management system, phone system, and the web applications your staff use, as they are configured today, so nothing is migrated or rebuilt.
- The same team stays after go-live. We monitor results, tune the agents as payers and workflows change, and add agents as new work is found.
The engagement model is described in more detail in forward-deployed engineering for healthcare contact centers.