PRIOR AUTHMONITOR

Follow the rules. Understand the workflow. Protect access to care.

Coverage desk

Decision-Timeframe Operations

Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.

Aetna contract metrics need a declared weighting method

Aetna's 84-page 2025 disclosure presents medical-service prior-authorization percentages by Medicare Advantage contract. Any multi-contract result must name its contract roster, aggregation question, compatible weight for every included value, missing-data rule, and calculation version; the PDF does not provide request counts for a volume-weighted payer total.

UHC requirement files need plan-and-date version control

UnitedHealthcare publishes plan-specific advance-notification and prior-authorization resources and directs professionals to check by member in its portal for the most accurate response and a Decision ID. Operations teams need to preserve which plan, service, effective-date file, and member-specific result governed each request.

CMS: A CRD check does not start the decision clock

CMS's current Prior Authorization API FAQ says a Coverage Requirements Discovery response can identify whether prior authorization is required and what documentation is needed, but does not itself submit the request or start the payer's decision timeframe. Operators need separate discovery, submission-receipt, information-request, determination, notice, and appeal events.

An Evolent specialty authorization needs a contract-specific decision-authority record

Evolent presents specialty care-management programs that can combine clinical pathways, prior authorization, provider engagement, peer review, analytics, and value-based models. When a plan delegates review activity, the case record still needs to identify which organization and qualified reviewer held authority for the particular specialty, benefit, member, request, and decision date.

Anterior's reasoning log is not the payer determination

Anterior describes modular AI for clinical workflows, utilization-management tasks, immutable audit and AI reasoning logs, and human-in-the-loop collaboration. Those records can support review, but the payer determination still needs the applicable request, policy, evidence, authorized reviewer, scope, reason, and notice.

Cohere connects utilization management and payment integrity—but authorization is not a claim decision

Cohere Health presents payer clinical operations spanning prior authorization, utilization management, appeals, care, quality, and claims-related work. Connecting those records can reduce blind handoffs, but a prior-authorization result does not by itself determine eligibility, coding, contract terms, payment policy, or final claim disposition.

Waystar's authorization-required check and the payer decision are separate records

Waystar documents tools that analyze order data to determine whether authorization is required, initiate and attach requests, retrieve status, and support real-time approval workflows. A provider-side requirement result or retrieved status still needs the named payer or authorized delegate, benefit, service, effective policy, request identifier, evidence, and final determination behind it.

Humana's zero-day median is not a same-day prior-authorization guarantee

Humana's 2025 report for Medicare Advantage contract H4461 shows a zero-day median alongside a one-day mean for standard requests and a zero-hour median alongside a five-hour mean for expedited requests. A median describes the middle observation—not every case or a service commitment.

X12 278 standardizes a service-review exchange—not claim payment

X12's 278 request-and-response transaction carries health-care-services review information between operating parties. It does not decide eligibility, benefits, medical necessity, final claim adjudication, or payment by itself.