Prior authorization is the first real gate in the revenue cycle.
A claim built on a missing or flawed authorization is dead before it ships, no matter how squeaky clean the rest of the paperwork is.
That's why you need to get this stage right.
Everything downstream (the coding, the claim, the cash) depends on the payer already having said yes.
Here's what prior authorization actually requires for DME, where it tends to stall flat out, and where prior authorization automation earns its place.
What Does Prior Authorization Require for DMEPOS?
Prior authorization is the payer's permission, granted in advance, to provide a specific item to a specific patient. For a growing list of DMEPOS categories, that permission has to be in hand before delivery, not after.
Getting it comes down to proving the item is medically necessary and covered under the patient's plan. In practice that means assembling a specific set of documents:
- A valid physician's order for the item
- Documentation of medical necessity that matches the payer's coverage criteria
- The right supporting records, chart notes, test results, or a certificate of medical necessity where one applies
- Dates and signatures that line up across every document
Submit that package, and the payer reviews it against their rules for that item and that plan. Approve, and you're clear to deliver and bill. Deny, and you're back to gathering what was missing, while the patient waits.
The catch is that "the payer's rules" aren't one set of rules. They vary by payer, by plan, and by product category, and they change. What clears one plan gets kicked back by another for a document it never asked you to send the first time.
Where Does Prior Authorization Stall?
Most authorization delays trace back to a short list of causes. None of them are exotic. They're the ordinary friction of a manual, high-volume process.
Incomplete documentation. The single biggest cause. A missing chart note, a medical necessity statement that doesn't match the payer's exact criteria, an order without the right detail — any gap sends the request back.
Payer variation. Each payer has its own forms, its own criteria, and its own submission process. A team juggling a dozen payers is tracking a dozen different rulebooks, and it's easy for the wrong form or an outdated requirement to slip through.
Timing. Authorizations have windows. Submit too early or too late, or let an approval expire before delivery, and you're starting over.
Confusion about what needs authorization at all. Some items require auth, some don't, and some qualify for an exemption. Chasing an authorization you didn't need wastes time; assuming an exemption you don't have creates a denial. (We cover this in detail in DME prior authorization exemptions.)
Each of these is small on its own. Together they turn authorization into one of the slowest, most rework-prone stages in the cycle.
The Cost of a Slow Authorization
A stalled prior auth goes beyond being a simple billing problem into a full-fledged patient problem.
Every day an authorization sits unresolved is a day a patient waits for equipment they need: the CPAP, the wheelchair, the oxygen. The clinical need doesn't pause while the paperwork catches up. Delay long enough and care that was ordered simply doesn't arrive on time.
There's a business cost stacked on top of that. Staff hours pour into resubmitting requests and calling payers for status. Cash that depends on the claim can't start moving until the auth clears. And an authorization that's rushed or incomplete raises the odds of a denial later, so the delay at the front of the cycle becomes rework at the back.
Where Does Prior Authorization Automation Actually Help?
Prior authorization is repetitive, rules-based, high-volume work. That's exactly the kind of work automation is good at, and exactly why it's one of the highest-value places in the revenue cycle to apply it.
Prior authorization automation helps most with the parts that don't need judgment:
- Checking whether an item requires authorization against current payer rules, so no one guesses.
- Flagging missing documentation before submission, so a request goes out complete the first time instead of bouncing back.
- Tracking status and deadlines across payers, so nothing expires or falls out of the queue unnoticed.
- Keeping payer requirements current, so the team isn't working from a rulebook that changed last quarter.
What it doesn't do is replace the people who handle the exceptions. A complicated medical necessity case, a payer dispute, a patient situation that doesn't fit the template — that's judgment work, and it stays with your team. The honest promise of automation here is narrow and real: it clears the routine so your staff can spend their time on the requests that actually need a human.
Handled that way, a stage that used to be a bottleneck stops being one. Requests go out complete. Deadlines get met because the system is watching them. And your team's attention goes where it's worth the most.
Here's a practical checklist:
If you want to sharpen this stage without a big project, start here:
- Confirm the requirement first. Before anyone gathers documents, know whether the item needs authorization for that payer and plan — or qualifies for an exemption.
- Build the request complete. Treat a resubmission as a failure to prevent, not a normal step. Gather the full documentation package before the first submission.
- Match the payer's exact criteria. Medical necessity language should map to what that specific payer requires, not a generic version.
- Watch the clock. Track submission windows and approval expirations so nothing lapses before delivery.
- Protect your team's time for the hard cases. Let the routine checks run automatically so your staff can focus on the requests that need real judgment.
The Bottom Line
Prior authorization is the gate the whole claim has to pass through first.
Get it right and everything downstream moves faster.
Get it wrong and the cleanest claim in the world still gets denied.
It can stall out for seemingly ordinary reasons: missing documents, shifting payer rules, missed deadlines.
Those are exactly the reasons prior authorization automation is built to handle. Clear the routine, keep your people on the exceptions, and authorization stops being the place cash and care get stuck.
The next gate is the claim itself. That's where a clean first pass keeps everything you just approved from turning into a denial, which is what we cover in clean claims the first time.
For the full picture of how this stage connects to the rest, start with our guide to the DME revenue cycle.
