Scheduled-procedure prior authorization

How do we submit a scheduled procedure's prior authorization from the EHR order with the payer's required documents checked first, chase the gaps on the procedure-date clock, and write the decision back?

Start from the order and check the payer's list before sending. When a procedure that needs authorization is ordered, Callvu prefills the request from the EHR (the patient, the coverage, the codes, the ordering and rendering providers, the facility, the date), classifies the payer's requirements for that service (whether authorization is needed, the clinical criteria, the documents, the submission channel, the decision timeframes under the payer's rules and the CMS rule), checks the chart against the list and chases the gaps (a note, an imaging result, a conservative treatment record) from the clinician or an outside provider on a clock set from the procedure date, submits a complete request, tracks the payer's decision on its timeframe, routes a denial or a peer-to-peer offer to the clinician in the Decision Desk, and writes the authorization number and validity or the denial to the EHR so scheduling and billing see it.

In scopeComplex: multi-party handoffsCallvu moves: prefill, classify, chase and verify, decide, write back

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The authorization request went to the payer with the wrong code and no imaging, and the denial arrived two days before the surgery.

Today, without Callvu

The order is placed; the authorization team opens a work queue item; someone assembles a request from the chart and sends it through the payer's portal or by fax. The payer pends it for a missing document, the pend letter arrives by mail, the request is resubmitted, and the decision lands too late for the scheduled date. The patient is rescheduled or the procedure proceeds without authorization and the claim is denied.

Every payer publishes what it needs for each service: the authorization requirement, the medical policy and its criteria, the documents, the channel and the timeframes. The CMS interoperability and prior authorization rule now sets decision timeframes for the impacted payers (seventy-two hours for expedited, seven calendar days for standard requests), reasons for denials and a public reporting of metrics. The chart either has what the list needs or it does not, and checking before sending is what prevents the pend.

A complete request sent early, tracked on the payer's clock, is an authorization in hand before the date.

How it runs

From the requestto the system of record.

A procedure that requires prior authorization is ordered in the EHR with a scheduled or expected date. Callvu opens the authorization from the order.

Ordering clinician: Supplies missing clinical documentation and takes peer-to-peer or appeal decisions in the Decision Desk.
Authorization team: Sees status by procedure date and resolves payer exceptions.
Payer: Receives the request through its channel and returns the decision.
Patient: Is told the status and, where needed, what the plan requires of them.
Callvu: Prefills from the EHR, classifies the payer's requirements, checks and chases, submits, tracks, routes and writes back.

Prefill and classify
The request is prefilled from the EHR order and the registration record (the patient and member identifiers, the plan, the diagnosis and procedure codes, the providers and their identifiers, the facility and setting, the date); the payer and the service classify the requirements: whether authorization is required, the medical policy and clinical criteria, the documents the payer lists, the submission channel (an electronic transaction, the portal, fax), the urgency and the decision timeframe.
Chase and verify the documents
The chart is checked against the payer's list (the clinical notes with the findings the criteria name, the imaging and lab results, the conservative treatment history, the functional assessments, the specialist's recommendation); each gap is chased from the clinician through their inbox task or from an outside provider through a link, on a clock that works back from the procedure date and the payer's timeframe; each document is read on arrival and checked against the criteria before the request goes.
Submit, track and decide
The complete request is submitted through the payer's channel with the documents attached and the submission recorded; the payer's response is tracked against its timeframe, with a pend answered from the chart or chased, and a decision that is late escalated through the payer's process; an approval proceeds by rule; a denial, a modified approval, a peer-to-peer offer, or a request the payer says is not required goes to the ordering clinician in the Decision Desk with the payer's reasons and only the allowed outcomes (accept, schedule the peer-to-peer, appeal, change the order, or proceed with the patient's informed financial consent).
Write back
The authorization number, the validity dates, the authorized units and setting, or the denial with its reasons and the appeal deadline, are written to the EHR against the order and the encounter, scheduling and the day-of readiness check read the status, billing finds the number on the claim, and the renewal process is set where the authorization expires before the care ends.

Where it ends: The request left complete against the payer's own list, was tracked on the payer's clock, and the EHR holds the authorization or the clinician's decision on the denial before the procedure date. The Decision Trace shows the requirements, each document against the criteria and any decision; the Audit Trace shows the chases, the submission, the payer's response and the write with time.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

Regulations

Payer prior authorization rules: Each payer publishes the services that require prior authorization, the medical policies and clinical criteria it applies, the documentation it requires, the submission channel and the decision timeframes for standard and urgent requests, with the appeal rights on a denial; state laws add prior authorization standards for commercial plans (response times, gold carding, continuity on plan changes) in many states; the classification applies the payer's and the state's rules to each request.
CMS prior authorization rule (the Interoperability and Prior Authorization final rule, CMS-0057-F): For Medicare Advantage, Medicaid and CHIP managed care and fee-for-service, and qualified health plan issuers on the federally facilitated exchanges, the rule requires decisions within seventy-two hours for expedited requests and seven calendar days for standard requests from 2026, a specific reason for any denial, public reporting of prior authorization metrics, and a prior authorization application programming interface for providers from 2027 that returns the documentation requirements and the decision status.
HIPAA transaction standards (the X12 278 referral and authorization transaction) and the Privacy Rule: Electronic authorization requests use the standard transaction where the payer supports it, and the clinical documents are protected health information disclosed for payment under the minimum necessary standard.

Company policies

The payer's list is checked against the chart before any request is sent; a request never goes out to find out what is missing.
The chase works back from the procedure date and the payer's timeframe.
A denial or a peer-to-peer offer is the clinician's decision, with the payer's reasons in front of them.
The EHR is the system of record for the authorization, read by scheduling and billing.

Controls

Prefill from the EHR order and registration.
Payer requirement classification with timeframes.
Chart check against the list and gap chases with criteria checks.
Submission through the payer's channel with tracking and escalation.
Decision Desk for denials, modifications and peer-to-peer offers.
EHR write with validity, units and the renewal trigger.

Clocks and deadlines

Payer decision: The payer's timeframe, and under the CMS rule seventy-two hours expedited and seven calendar days standard for the covered payers.
Procedure date: The real deadline; submission and chases are scheduled against it with the payer's timeframe subtracted.
Authorization validity: The approved dates and units, with the renewal process set before expiry.

Documents and checks

The prefilled request and the payer's requirement list
The chart check and each document chased and checked
The submission record and the payer's response
Any clinician decision
The EHR authorization record

In the Decision Trace

The requirements and why.
Each document against the criteria.
Any decision and the person.

In the Audit Trace

Each chase and arrival with time.
The submission with channel and time.
The payer's response and the write with time.

The handoff

Between the front doorand the back office.

The front door

The EHR order; the clinician's inbox task for a missing note; an outside provider's link for a record.

The back office

The authorization team sees status by procedure date and handles only payer exceptions; scheduling and billing read the EHR.

The Decision Desk

A denial, a modified approval, a peer-to-peer offer or a payer saying authorization is not required goes to the ordering clinician in the Decision Desk with the payer's reasons and only accept, schedule the peer-to-peer, appeal, change the order, or proceed with the patient's informed financial consent.

Proof

In scope.Proof at scale, not one process at a time.

The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.

23 hospitals in the Ministry of Health network run on Callvu.

Across Callvu customers

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Questions

What buyers ask next,answered plainly.

What is checked before the request is sent?

The chart against the payer's published list for the service: the notes with the findings the criteria name, the imaging and labs, the conservative treatment history; each gap is chased before submission.

How fast must the payer decide?

Within its own timeframe, and for the payers covered by the CMS rule within seventy-two hours for expedited and seven calendar days for standard requests, tracked on the request.

What happens on a denial?

The ordering clinician decides in the Decision Desk with the payer's reasons: accept, schedule the peer-to-peer, appeal, change the order, or proceed with the patient's informed financial consent.

Related processes

Authorization renewals and extensions Peer-to-peer review scheduling Medication prior authorization Payer document requests Try it in the sandbox All healthcare processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.