Who Assembles the Physician Certification and PA Package Before the Fourth Dialysis Round Trip, and Who Tracks the 60-Day Reauthorization Clock?
The dialysis runs are going fine. Three round trips a week, same patient, same schedule, and the RSNAT authorization has been holding.
What Keeps a Dialysis RSNAT Authorization From Lapsing Mid-Schedule
The goal is a valid authorization covering the scheduled round trips, with the reauthorization filed before the clock runs out, so transports are far less likely to run uncovered. Here is what does that, move by move.
1. Assemble the Certification and PA Package Before the Runs Require It
RSNAT approval hinges on documentation the agency has to gather before the transports that need it begin: the physician certification statement, the medical justification for repetitive non-emergent ambulance transport, and the trip schedule. CMS allows a prior authorization request to cover a set number of round trips over a 60-day period, so the package has to be built and submitted ahead of the runs, not scrambled after the fourth trip already went out. Assembling it early is the difference between covered transports and a gap you find on the remittance.
2. Chase the Physician Certification on a Schedule, Not at the Deadline
The single hardest piece is the physician certification statement, because it lives in a nephrology practice that is busy with its own patients and does not share the agency's deadline. Chasing it the week the authorization is due is how it slips. Instead, request it early, follow up on a set cadence, and track which certifications are outstanding so none of them becomes the reason a valid patient's transports run uncovered. The certification is valid for a defined period, so it has to be current, not just on file once.
3. Track Every 60-Day Clock and Resubmit in the Reauthorization Window
The clock that sinks agencies is the 60-day authorization period. CMS guidance is that the next request should not go in before roughly day 45 of the current period, about two weeks before expiration, so there is a real window to hit and a real way to miss it. Track every patient's authorization end date on one calendar and file the reauthorization inside that window. An authorization that lapses on a Friday because nobody was watching the date is the most avoidable freeze in this whole workflow.
4. Protect the Transports That Run While a Decision Is Pending
Even done right, some transports run while a request is in review, and a review can take up to a week. Those runs cannot just be sent and forgotten. Track which trips fall in a pending window, hold or flag the claims appropriately, and release them cleanly once the decision lands, so a batch of legitimate round trips does not get billed unauthorized and frozen in prepayment review. Owning the pending window is how the schedule keeps moving without the claims piling up in limbo.
5. Hand RSNAT Authorization to a Dedicated Team
Agencies that stop losing dialysis transports to lapsed authorizations do it by handing RSNAT to a dedicated team: remote specialists who assemble the package, chase the certification, track every 60-day clock, and protect the pending runs, live in 1 to 2 weeks. Operations goes back to running the trucks, a trained backup covers every gap, and the reauth calendar stops being the thing nobody owns until it fails. Below is what it sounds like when nobody owns it yet, in providers' own words.
Key Pain Points and Discussions by Providers
representative composite examples based on common workflow discussions
“The authorization lapsed on a Friday and nobody caught it until the next remittance. Two weeks of thrice-weekly round trips had already gone out unauthorized, and now they are frozen in prepayment review while we scramble for records. The patient never stopped needing dialysis.” composite example: billing manager, ambulance service
“Getting the physician certification out of the nephrology office is the whole battle. They are busy with their own patients and they do not share our deadline, so the statement shows up late and the authorization slips before we ever get it filed.” composite example: operations manager, EMS agency
“Nobody owns the 60-day clock. Everyone assumes someone else is watching the reauth date, and then it expires mid-schedule and we are running unauthorized trips we cannot bill. It is not a clinical problem, it is a calendar problem nobody was assigned.” composite example: revenue cycle lead, non-emergent transport service
“We filed the reauthorization late once and the whole batch went to prepayment review. Now every one of those round trips is sitting frozen while a records request grinds, and the cash flow hit from one missed date is brutal.” composite example: practice administrator, ambulance service
“When we started tracking every patient's authorization end date on one calendar and filing the reauth in the window, the lapses just stopped. The runs were always necessary. We just had to stop finding out about the expiration on the remittance.” composite example: billing director, regional transport agency
Our Answer
Here is what we actually do. A dedicated remote specialist assembles the RSNAT package before the transports require it, chases the physician certification statement out of the nephrology practice on a set cadence rather than at the deadline, and tracks every patient's 60-day authorization clock on one calendar so the reauthorization is filed inside the window CMS defines. They also flag the transports that run while a decision is pending so those claims do not get billed unauthorized and frozen. Our teams include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, working inside your billing and scheduling systems and the Medicare portal, with approved AI tools assisting with first-pass package and tracking the deadlines while a human verifies every submission. This is our prior authorization support paired with an AI-first workflow, in one paragraph.
Why This Keeps Happening
If the patient clearly needs the transports, why does the authorization lapse? Because RSNAT approval does not run on clinical need, it runs on paperwork and a calendar, and both sit partly outside the agency's control. The physician certification statement has to come from a nephrology practice that is busy with its own patients and does not feel the agency's deadline, so it arrives late or not at all. CMS structures the program around a defined 60-day authorization period, so even a clean approval expires on a set date, and a thrice-weekly dialysis schedule keeps running straight through that date whether or not anyone renewed it. The need never lapses; the authorization does.
The timing rules are unforgiving in a way that punishes the busy. CMS guidance is that a request may cover a set number of round trips across a 60-day period, and the next request should not go in before roughly day 45 of the current one, about two weeks before it expires, which means there is a narrow window to file the reauthorization and an easy way to miss it entirely. When that window lands in an operations team already running trucks and crews, it does not get a dedicated owner; it gets forgotten until a remittance shows unauthorized trips. Closing that gap is exactly what an AI prior authorization workflow with human oversight is built to do.
And the cost of one missed date is not one claim, it is a batch. A dialysis patient runs three round trips a week, so a lapse that goes unnoticed for two weeks is a dozen transports billed unauthorized, and those tend to land in prepayment review together, freezing payment while records requests grind. The agency delivered every one of those runs in good faith, and now the cash is stuck behind a calendar miss. The lost revenue is real, the review is slow, and almost all of it was preventable with someone owning the clock.
Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:
| What you tried | What actually happened | Who ended up doing the work |
|---|---|---|
| Assumed the authorization was still valid and kept running trips | It had lapsed on a Friday; two weeks of round trips billed unauthorized and froze in prepayment review | Nobody; everyone assumed someone else was watching |
| Chased the physician certification at the deadline | The nephrology office is busy and does not share the deadline, so the statement arrived too late to file in time | Whoever remembered, when it was already due |
| Left the 60-day reauth clock to operations | No single owner meant the reauth window was missed and the authorization expired mid-schedule | The operations team, on top of running trucks |
| Gave RSNAT to a dedicated remote specialist | Package assembled early, certification chased on a cadence, every 60-day clock tracked and refiled in the window | Someone whose whole job it is |
The Solution
So what does "someone whose whole job it is" look like on a dialysis patient? The specialist assembles the RSNAT package before the transports require it, then goes after the hardest piece early: the physician certification statement, requested from the nephrology practice on a set cadence and followed up until it lands, instead of scrambled the week the authorization is due. Most RSNAT lapses are a certification-and-calendar problem, and that is exactly what dedicated prior authorization support is built to solve, before a valid patient's transports ever run uncovered.
Then comes the clock. The specialist tracks every patient's 60-day authorization end date on one calendar and files the reauthorization inside the window CMS defines, roughly two weeks before expiration, so the coverage never lapses on a Friday nobody was watching. And for the transports that run while a decision is pending, they flag those claims so a legitimate batch of round trips does not get billed unauthorized and frozen. The schedule keeps moving, and the claims stop piling up in limbo.
Behind all of it, Approved AI tools may assist with the first pass and a trained human reviewer verifies. The workflow assembles the package, tracks every reauth deadline, and flags the pending-window transports; a person confirms the certification and medical justification are right and owns every submission to the Medicare portal. Every security control that protects the patient data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving certification and transport records through an authorization workflow is only safe when the controls are real.
Who Actually Does This Work
Fair question: why would an outsourced team hold your RSNAT calendar better than your own staff? Because tracking authorization clocks and chasing physician certifications is their entire day, not the thing they squeeze between dispatch and payroll. The people running your authorizations include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, all trained in US prior authorization and non-emergent ambulance transport workflows. They know how CMS structures the RSNAT 60-day period, what a valid physician certification statement has to contain, and how to work a nephrology office to get it on time. That is not a generalist task handed to whoever is free; it is a specialty.
We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ team members, 24/7 coverage, and the AI-assisted plus human-verified workflow you just read about behind every one of them. A typical agency is live in 1 to 2 weeks, at approximately 68% below equivalent in-house staffing costs. Trained backup coverage is included in the managed-service model.
And the security piece your compliance officer will ask about: Staffingly maintains active ISO/IEC 27001:2022 certification and operates under HIPAA-compliant controls and signed BAAs. SOC 2 Type II reporting and security controls apply according to the relevant entity, client environment, facility, device, and workflow. Venn Blue Border and related workstation restrictions are used where applicable. Staffingly maintains $5M in professional liability (E&O) and cyber insurance as part of its enterprise risk-management program; the full detail lives in our HIPAA and security posture.
Put the routine and the people together, and a specific list of things simply stops happening.
Ready to Stop Losing Dialysis Runs to Lapsed Auths?
Comparing the best EMS and ambulatory billing companies? See how a dedicated remote team compares, then browse every pain point we solve.
How We Build a More Durable Process
A person alone is not the fix, and neither is a bot alone. The fix is a documented RSNAT workflow: every recurring patient's authorization end date on one calendar, the certification-request cadence per referring practice, the reauthorization window per CMS rules, and the pending-transport flagging, all written down and worked the same way for every patient. Before we take a single authorization for a new agency, we chart your recurring dialysis and non-emergent patients and their authorization dates so we can see exactly which clocks are at risk, and we build the workflow against your real caseload, not a generic template.
From there the workflow becomes a living playbook rather than a date in one coordinator's head. It records how to get a certification out of each referring practice, when to file each reauthorization, how to handle transports that run during review, and the escalation path when a certification is late. It is written down, kept current as CMS updates the program, and owned by the team. When your specialist is out, a trained backup works the same calendar the same way, so no authorization lapses because one person is away.
That is the difference between reacting to this month's lapse and fixing the process for good, and it is what a dedicated prior authorization partner actually buys you. A coordinator leaving used to mean the reauth calendar fell apart and authorizations started lapsing mid-schedule again. Under this model the calendar keeps running, the playbook stays, the backup steps in, and a lapsed RSNAT authorization stops being the thing that quietly freezes your dialysis transports.
The Whole Thing in Four Sentences
RSNAT authorizations lapse mid-schedule because approval depends on a physician certification the agency has to chase from a busy nephrology practice and a 60-day clock that expires silently while thrice-weekly transports keep running, not because the patient stopped qualifying. Assuming the authorization holds, chasing the certification at the deadline, or leaving the clock to operations all fail the same way. The fix is to assemble the package before the runs require it, chase the certification on a cadence, track every 60-day clock and refile in the window, and protect the transports that run while a decision is pending. A regional non-emergent transport agency can use this workflow without exposing patient information or naming client organizations.
If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.
Ready to stop losing dialysis runs to lapsed auths? Start with a Two-Week Free Trial: your real RSNAT caseload, dedicated specialists chasing the certifications and holding the reauth calendar, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.
One Flat Weekly Rate. 45 Hours of Coverage.
No hourly meters, no setup fees, no security deposits, no long-term contracts. Two-Week Free Trial. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.
One dedicated remote specialist assembling RSNAT packages, chasing physician certifications, and tracking every reauthorization clock, single ambulance service or EMS agency
5+ remote specialists covering RSNAT prior authorization and reauth calendars across a multi-station EMS agency or several service areas
10+ remote specialists, multi-agency EMS network, or regional non-emergent transport platform running RSNAT authorization across many recurring patients
45 hours of coverage at one flat weekly rate.
For a simple annual comparison, 40 hrs x 52 weeks = 2,080 hours. A Staffingly plan: 45 hrs x 52 weeks = 2,340 hours a year, that is 260 additional hours included in your flat rate. $399/week x 52 = $20,748 a year / 2,340 hours = $8.87 per hour.
Hold Your RSNAT Calendar This Month
You have seen the whole method. The trial lets you test it on your own recurring caseload, with a tracker your team can watch every day.
Start My Two-Week Free TrialWant Us to Stop Losing Dialysis Runs to Lapsed Auths?
Tell us your situation and we will map your RSNAT reauthorization calendar and the certification chase behind it. A team member will follow up with next steps.
Frequently Asked Questions
Where the Claims on This Page Come From
Sources & References
- CMS Prior Authorization of Repetitive, Scheduled Non-Emergent Ambulance Transport (RSNAT). Federal program rules for RSNAT prior authorization, including the 60-day authorization period, round-trip limits, and the physician certification statement. cms.gov
- CMS RSNAT Frequently Asked Questions and Provider Guidance. Federal guidance on reauthorization timing, physician certification statement validity, and review timeframes for repetitive non-emergent ambulance transport. cms.gov
- Ambulance Reimbursement Systems, Non-Emergent Transport and Prior Authorization Guidance. Trade guidance on RSNAT documentation, certification, and reauthorization operations for ambulance agencies. arsnetwork.com