Prior authorization

What does a prior authorization nurse do?

A prior authorization nurse reviews requests for medical services, medications, or procedures before they happen, verifying that the clinical documentation supports the request under the applicable coverage criteria. The job is precision intake work: validating identifiers, dates, units, and place of service, catching missing documentation early, and routing each request to approval, additional information, or physician review.

What happens to a prior authorization request?

A request arrives with clinical documentation attached. The nurse validates the administrative packet first (member, provider, procedure codes, dates, units, place of service), then reads the clinical evidence against criteria. Complete, clearly supported requests can be approved at the nurse level; anything else goes back for information or forward to a physician reviewer.

One missing identifier or a mismatched authorization can stall a request for days, which is why prior-auth work rewards meticulous checking over speed. The most common production failure is routing an incomplete packet as complete.

Why does prior authorization exist at all?

Payers use prior authorization to confirm medical necessity before expensive or high-risk care is delivered, rather than disputing it afterward. Whatever one thinks of the policy debate, the operational reality is a large, growing volume of requests, each of which needs a licensed clinician to read the evidence, and that clinical labor is the job.

The workload data is striking: the process consumes significant staff time on the provider side per physician each week, which is also why provider organizations hire nurses to run prior-auth desks - the same skill set, pointed the other way.

What skills separate strong prior-auth nurses?

Clean-packet discipline: never inferring a required field from an unrelated note, never assuming facts across separate encounters, and always checking authorization dates, units, and place of service against the request. Strong reviewers also write information requests that name exactly what is missing, so the round trip happens once instead of three times.

The judgment component is knowing when a request is outside nurse authority. Approvals within criteria are nurse work; potential adverse determinations are physician work, and the nurse's contribution is a complete, accurate referral.

  • Detect missing required intake fields before reading clinical content
  • Validate authorization dates, units, and place of service every time
  • Request the right missing information in one pass
  • Escalate cleanly when the determination is not yours to make

The numbers behind this guide

Every statistic above traces to a citation. See all our evidence.

Frequently asked questions

Is prior authorization nursing remote?
Frequently, yes. Prior-auth review is document and portal work, and payers, pharmacy benefit managers, and BPO firms commonly staff it remotely. Some provider-side prior-auth desks remain on site within hospital revenue-cycle departments.
How many prior-auth requests does a nurse handle per day?
Practitioner accounts describe roughly 40-60 straightforward requests per day for prior-auth reviewers, versus roughly 15-30 for concurrent review. Volumes vary by employer, request complexity, and the mix of pharmacy versus procedure requests.
What is a clean packet?
A request whose administrative fields are complete and internally consistent and whose clinical documentation directly supports the service requested. Clean packets can be decided in one pass; everything else generates delay.

Put it into practice

Keep reading

Education only. Not medical advice, and not legal advice on coverage decisions. Salary figures are cited third-party estimates, not promises. All practice cases on RemoteNurse are synthetic and contain no PHI.