Authorizer Analytics
How the Authorizer is measured
The record for authorization work: services flagged, packets prepared for staff, gaps found, and approvals caught before they lapse.
- Services needing authorizationtrending up142Identified on the schedule ahead of the visit.
- Packets prepared for stafftrending up118Documentation gathered for a person to review.
- Documentation gaps flaggedsteady by designStaff first27Missing items shown before anyone submits.
- Requests tracked to a decisiontrending up96Staff-submitted requests followed to a payer response.
- Approvals flagged before expirytrending up31End dates and visit limits caught before the next visit.
- Denials routed to staffsteady by designStaff first6Sent to people with the record attached.
Illustrative values, not results from a customer deployment. No approval rate or turnaround time is promised.
How the record works
Every authorization moves through four recorded stages. The agent does not submit requests on its own, so submission is recorded as staff work.
- 01
Service identified
Which scheduled visit or order needed authorization, and under which payer's requirements.
- 02
Packet prepared
The documents gathered from the chart and any gaps marked for staff.
- 03
Staff submission
The review and submission done by staff, recorded against the packet.
- 04
Status and expiry
The payer's decision, the approval's end date or visit count, and any alert raised before it lapsed.
What the practice can review
The views the team works from:
-
Upcoming authorization needs
Scheduled services that need an approval, by date.
-
Packet queue
Packets waiting on staff review.
-
Gap list
Missing documentation by request.
-
Request status
Where each staff-submitted request stands with the payer.
-
Expiring approvals
Approvals near their end date or visit limit.
-
Request history
A reviewable trail for each authorization.
How the numbers stay honest
The reporting describes preparation and tracking work. It does not credit the agent with approvals, because staff and providers submit every request and make the clinical case.
The Authorizer is in beta. We agree the reporting fields and payer requirements with each practice during onboarding.
-
Submissions belong to staff
Requests are recorded as staff-submitted, because they are.
-
Denials are reported steady
Routing denials to people is the design, so that number never wears an up-is-good arrow.
-
Gaps stay visible
Missing documentation is counted and kept in the record.
-
No PII in marketing analytics
No patient data, health details, phone numbers, insurance IDs, or free text, ever.
Frequently Asked Questions
No. The values on this page are illustrative. Each practice's own record fills in once the agent runs on its schedule.