A prior auth packet for an MRI with the order, locked note, prior imaging and PT evaluation attached and the treatment plan form drafted

Send prior auths from the chart.

Your coordinators know the case in minutes. Typing it into the payer's portal, form or phone line takes the rest. A Clicks agent builds the request from the chart, submits it wherever the payer wants it, and logs the confirmation back in the EHR.

Watch an AI agentprepare a prior auth

In eClinicalWorks, the agent opens the chart, downloads the order, the locked note, the prior MRI and the PT evaluation, fills the treatment plan form, and uploads the packet for review.

eClinicalWorks demo using fictional patient data in a test environment.

Stop retyping the chart into payer portals

The surgeon decided the patient needs the MRI before any of this starts. What follows is the same case, entered again in whichever portal, form or phone line the payer wants this week. In a survey of 353 hip and knee surgeons, 93% reported a high administrative burden from prior auth, and 71% employed at least one person only for it (Pereira et al., Journal of Arthroplasty, 2023).

Where does this payer want it?

One plan takes MRIs in its own portal, another routes them to eviCore or Carelon, a third wants a fax. The routing changes and nobody tells your team.

Is everything in the packet?

The order, the locked note, prior imaging and therapy notes all have to go with the request, or it comes back.

Why type it twice?

Every field already sits in the chart. Coordinators retype it into the portal, then retype the confirmation number back.

Who calls the payer?

When the portal sends the request to the phone, someone sits on hold to finish it.

Who knows the payer rules?

Payer-specific knowledge lives in one coordinator's head, and it leaves when they do.

Hand every step after the order to an agent

Review every packet until you trust it

We start with your own cases. The agent prepares the same requests your coordinators do, and your team checks every packet before anything goes out on its own.

  1. 01ShadowThe agent prepares requests your coordinators already submitted, and we compare the results.
  2. 02Side by sideIt prepares new requests. Your coordinators review every packet before it goes out.
  3. 03Go liveClean requests go out on their own. Your team sees only the exceptions.

Get answers before you hand off prior auth

Which payers and portals does it work with?

Any portal, form or phone line your team can use, including Availity, eviCore and Carelon, and state forms such as the New Jersey APTP. When a payer changes its routing, the agent adapts. Your team does not have to.

Does the agent decide medical necessity?

No. The provider decides what the patient needs before the agent starts. The agent works from what the provider documented and never adds a diagnosis.

Which EHRs does prior auth submission work in?

eClinicalWorks, athenahealth, ModMed, Epic, NextGen Healthcare, and any other system your team can log into. The agent works the same screens your coordinators use, so there is no integration project.

What if the payer asks for something that is not in the chart?

The agent sends the case to your team with exactly what is missing. It does not guess, and it does not create documentation.

Does it follow up after submission?

Yes. The agent checks status on a schedule, calls when the portal has no answer, and sends the records the payer asks for until the decision lands.

Keep reading

Cut APTP admin to zero with 24% fewer admin denialsThe provider only reviews and signs.Follow up on prior auths until the decision landsWhat happens after submission, and what the agent takes over.Why prior auth takes so much timeWhere the minutes go between the order and the confirmation number.

Ready to take the typing out of prior auth?

No risk, no commitment. We prove value before you pay.