On this page
Key takeaways
- Track the block-to-ablation path as a sequence of states, so every patient is either moving, waiting on a named step or closed by a physician decision.
- Response documentation is the most common silent stall, because it often lives in free text or a phone note.
- Approved authorizations that never become booked cases are easy to find and quick to fix.
- Procedure-day cancellations need their own rebooking owner, separate from new orders.
- Physicians decide whether a patient moves forward; operations teams make sure the decision is not lost.
To track patients from diagnostic block to radiofrequency ablation, place every patient who has had a diagnostic block into one named state (response pending, decision pending, authorization pending, approved and unbooked, booked, completed) and look for patients who have stopped moving. A sequence that ends because a physician decided it should end is complete. One that ends because nobody recorded the next step is the gap.
Pain practices know this path well, but few can see it across all patients at once. The steps live in procedure notes, phone notes, the authorization queue and the procedure schedule, and each has a different owner.
Why is this sequence so easy to lose?
It is easy to lose because it has many hand-offs, each with a different owner, and each one waits on something. A typical path includes a first diagnostic block, a period where the patient reports response, a physician review, often a second block, a new authorization request where the payer requires one, scheduling the ablation, and a follow-up visit. Payer policies commonly ask for documented response to diagnostic blocks before approving ablation, so the paperwork between steps matters as much as the procedures.
Clinical criteria, the number of blocks, and whether a patient moves forward are decided by the treating physician under the practice's approved protocols and the payer's policy. None of that is an operations call. What operations can own is making sure each decision is captured and acted on.
- First blockDiagnostic block scheduled and completed.
- Response recordedResponse captured where the practice agreed to record it.
- Physician decisionPhysician decides on a further block, ablation or another plan.
- AuthorizationRequest submitted where the payer requires it; approval tracked.
- Case bookedAblation scheduled, with driver and medication instructions confirmed.
- Follow-up visitPhysician reviews the result and sets any next step.
A patient should always sit in one named state. Patients with no state, or stuck in one too long, are the list.
Which states can a patient be in?
A shared vocabulary of states is the most useful thing a pain practice can build here. Once every patient sits in exactly one state, stalls become visible.
| State | What it means | Typical owner | Stall signal |
|---|---|---|---|
| Response pending | Block completed; response not yet recorded | Nurse or MA | No response entry after the window your team sets |
| Decision pending | Response recorded; no documented next step | Physician | Response on file, no order and no plan note |
| Second block ordered | Further diagnostic block ordered | Procedure scheduler | Order with no booked date |
| Authorization pending | Request submitted for the ablation | Auth coordinator | No payer decision after the window your team sets |
| Approved, unbooked | Authorization approved; no case scheduled | Procedure scheduler | Approval on file, no case |
| Booked | Ablation scheduled | Procedure scheduler | Canceled with no new date |
| Completed | Ablation done; follow-up due | Front desk | Follow-up visit not booked |
| Closed | Physician or patient decided not to proceed | Physician | Should carry a documented reason |
The table is a template, not a protocol. Your physicians may skip states, add others, or use different terms. What matters is that the states are agreed, written down and applied the same way across providers.
Where does the sequence stall most often?
The sequence most often stalls in four places: response after the diagnostic block is never captured, the physician's decision is recorded but nothing is ordered, an approved authorization never becomes a booked case, or the procedure is canceled and never rebooked. Each needs a different owner.
Response never captured
Response after a diagnostic block is often recorded in a pain diary, a phone note or free text. If it is not recorded in a place anyone checks, the patient never reaches a physician decision. This is the quietest stall, because nothing looks overdue: there is no open order and no canceled appointment. The fix is agreeing with physicians on one consistent place and format to record response, without operations defining what the response should be.
Decision recorded, nothing ordered
Sometimes the physician notes a plan in the visit but the order is not entered, or is entered with a code the scheduling team does not watch. The patient was told something would happen next, and nothing does.
Approved and never booked
When an authorization comes back approved, the auth coordinator moves on to the next request. If approval does not create a scheduling task, the case simply waits. This stall is usually the fastest to fix, because the patient has already agreed and the payer has already approved.
Canceled on procedure day
Ablations are canceled for practical reasons: no driver after sedation, a medication hold that was not arranged with the prescribing clinician, an illness, a change in coverage. The slot is refilled from a waitlist, and the canceled patient is left without a date. These need a rebooking owner, as described in canceled procedure recovery.
Illustrative example: counting stalled sequences
The figures here are invented and round, only to show the arithmetic. Suppose a practice reviews every patient with a first diagnostic block in the past six months: 300 patients. Of those, 120 are closed by a documented physician decision or patient choice, and 90 are booked or completed. That leaves 90 patients in an open state.
If 35 sit in response pending, 20 in decision pending, 15 in approved and unbooked, 10 in authorization pending and 10 canceled with no new date, the work splits naturally: nurses on response, physicians on decisions, schedulers on the approved and canceled groups, auth on the pending requests. The formula is total sequences, minus closed, minus booked or completed, equals open sequences; each open sequence is then grouped by state. This is also the honest way to report diagnostic block to RFA conversion: sequences closed by a documented decision versus sequences still open, never as a target for ablations.
What should a weekly sequence huddle cover?
A short weekly huddle with a physician lead, the auth coordinator and the procedure scheduler keeps the sequence moving. A practical agenda:
- Approved and unbooked cases, oldest first. Assign each a call.
- Procedure-day cancellations from the past week with no new date.
- Response pending beyond the agreed window. Nurses report back on outreach.
- Decision pending. The physician lead reviews or assigns each to the treating physician.
- Authorization requests with no payer response beyond the window your team sets.
Track how long patients sit in each state as well. If approved-and-unbooked cases routinely wait longer than the authorization itself took, the fix is a hand-off rule, not more staff. Keep the huddle to the list. Clinical discussion about a specific patient belongs with the treating physician, not the group.
Every open sequence is also an open order or an unresolved step, so the same discipline used for tracking unresolved medical orders applies: no item closes without a reason, and a logged call is not a resolution.
How does Nuvory follow these sequences?
Nuvory links each patient's procedure history, orders, authorization status where recorded, appointments and referrals each night, and looks for a sequence with no recorded next step. A pain physician at your practice signs off each rule, including how your practice records block response, after spot-checking real patients. Nuvory never decides medical necessity or whether a patient qualifies for ablation. The revenue leakage intelligence for pain management page shows the full workflow, procedure recovery covers open orders more broadly, and orthopedic imaging follow-up covers a related hand-off. More service lines are in the specialty playbooks.
Block-to-ablation sequence checklist
- Agree with physicians on one consistent place to record post-block response.
- List patients with a completed diagnostic block and no recorded response.
- List patients with a recorded response and no physician decision on next steps.
- Match ablation orders to authorization status and booked cases.
- Flag approved authorizations with no booked case after the window your team sets.
- Track procedure-day cancellations with no new date separately.
- Close sequences only with a documented physician decision or patient choice.
- Review sequence states weekly in a short huddle with scheduling and auth.
Frequently asked questions
Does tracking block-to-ablation conversion mean pushing patients toward RFA?
No. The goal is that every sequence ends with a documented decision, made by the physician with the patient. A sequence closed because the physician decided not to proceed is complete. Only sequences with no recorded next step, or stuck in one state, belong on a work list.
Who should record response after a diagnostic block?
That depends on your workflow. Some practices have nurses call patients, others use diaries returned at a visit. What matters is that physicians agree on one consistent place and format, so the record can be found. Operations should not define what counts as a meaningful response.
What about patients who return months after an ablation?
Repeat procedures are decided by the physician when symptoms return, and the patient often has to make the first call. Practices can make sure the follow-up visit after each ablation is completed and the physician's plan is documented, so patients know how to reach the practice later.