Authorizer · Prior Authorization Agent

Keep prior authorizations ahead of the next visit

The Authorizer gathers what each authorization needs for staff, tracks status after staff submit, and flags approvals before they run out.

Beta

The Authorizer introduces itself as an AI assistant for your practice on every call and message, and hands off to your staff whenever someone asks.

Book a demo See how it's measured

The workflow

The Authorizer is in beta, and we configure it with each practice during onboarding. It prepares and tracks authorization work. It does not submit a request on its own.

  1. 01

    Find visits that need authorization

    From the schedule, the agent identifies recurring visits, infusions, procedures, and some imaging or lab orders that the patient's plan requires authorization for.

  2. 02

    Assemble the packet for staff

    It checks the payer's stated requirements and pulls the matching documentation from the chart into a packet, with any gaps marked.

  3. 03

    Staff review and submit

    Staff and providers review the packet, add the clinical justification, and submit the request themselves.

  4. 04

    Track status and expiry

    After submission, the agent tracks the request and flags approvals nearing their end date or visit limit before the next scheduled visit.

What the agent handles

Kidney care runs on recurring services, and each one can carry an authorization with an end date or a visit count. Most of the work is noticing when an approval is about to lapse, more than filing the first request. For [nephrology practices](/specialties/nephrology/), that pressure sits alongside the [insurance verification and prior authorization](/blog/nephrology-insurance-verification-prior-authorization/) load the front desk already carries.

  • Upcoming services flagged

    Scheduled visits and orders that need authorization identified ahead of time.

  • Payer requirements checked

    The documentation a payer asks for, compared with what the chart holds.

  • A packet for staff review

    Supporting documents gathered in one place, ready for a person to review.

  • Gaps marked

    Missing notes, results, or orders listed before anyone submits.

  • Status after submission

    Each staff-submitted request followed to a decision.

  • Expiry and visit-limit alerts

    Approvals close to their end date or visit count flagged before the next visit.

The request belongs to staff and providers

The agent prepares and tracks authorization work. It does not write clinical justifications, submit a request on its own, or appeal a denial. Staff and providers own every request from submission to appeal.

In beta, we set up the workflow and the payer requirements it checks with each practice during onboarding.

  • No clinical justification

    The provider argues medical necessity. The agent never drafts it.

  • Staff submit

    Nothing goes to a payer until a person has reviewed and sent it.

  • Denials stay with people

    A denial goes to staff with the record attached. Appeals are theirs.

  • No hidden gaps

    A missing document is shown as missing, never assumed to be on file.

What the practice can measure

Every authorization leaves a record the team can review:

  • Services needing authorization

    Identified ahead of the visit.

  • Packets prepared

    Ready for staff review.

  • Gaps found

    Documentation missing before submission.

  • Request status

    Pending, approved, or denied, for staff-submitted requests.

  • Approvals nearing expiry

    Flagged before the next scheduled visit.

These are recorded workflow outcomes, not promised approval rates or turnaround times.

FAQ

Frequently Asked Questions

Yes, in beta. Practices can use it today, and we configure it with each one during onboarding. It prepares and tracks requests. Staff submit them.

The rest of the lineup