Follow the rules. Understand the workflow. Protect access to care.
Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.
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.
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'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.
HealthHelp describes utilization-management intake through a portal, fax, phone, and electronic connectivity. Channel choice can reduce friction, but the operating record must still reconcile every artifact to one scoped authorization request, preserve corrections and supplements, and prevent duplicate or silently merged determinations.
VirtualHealth presents HELIOSum as supporting prior authorization, utilization management, medical-necessity review, grievances and appeals, configurable routing, and care-management workflows. A shared platform can carry evidence across the lifecycle, but it should not let an authorization status stand in for the separately governed review, appeal, and grievance records that follow.
MCG says CareWebQI gives payer reviewers access to regularly updated care guidelines and a workflow for saving member-specific clinical decision documentation. A saved review remains defensible only when it preserves which clinical facts and guideline version the reviewer actually used at that point in the episode.
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.
Infinx describes prior-authorization workflows that obtain approvals and send an approval package back to the electronic medical record. That handoff can reduce manual retrieval, but the organization still needs to prove that the authorization matches the patient, benefit, service, units, dates, provider, facility, and schedule that will actually be used.
CMS says certain regulated payers must implement and maintain prior-authorization APIs beginning January 1, 2027, and its provider guidance emphasizes roadmaps, modules, testing, training, and pilots. An available interface is an important milestone, but it does not prove that a real request can travel from order to determination without losing evidence, status, or accountability.
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.
HealthEdge describes GuidingCare as supporting the authorization lifecycle and identifies prospective, concurrent, and retrospective utilization review as distinct assessments. A shared workflow can connect them, but it should not collapse their timing, evidence, authority, or effect into one status.
Carelon's provider page directs specialty and post-acute care providers to portals where they can submit prior-authorization cases or check case status and links to clinical guidelines and plan-specific contact paths. That workflow can carry a request, but the portal does not independently define the member's applicable benefit, exclusions, effective coverage, or final payment terms.
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.
Cotiviti's official record says it completed the acquisition of Edifecs in March 2025, and current Edifecs product paths now point into Cotiviti's web estate. Buyers should update ownership and support records without assuming that a licensed gateway, interface, configuration, contract, or production workflow changed in the same way.
EviCore says intelliPath can create a case from an order or scheduled activity, submit it for approval or review, and update status. The clinical order, authorization case, review, and determination remain separate records.
Voice automation can reduce manual follow-up and capture payer responses without converting a phone result into proof of the request, determination, scope, or effective dates.
Predictive insight can prioritize utilization-management work, but it does not replace the request record, medical-necessity review, payer determination, or documented exception path.
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.
Optum documents evidence-based InterQual content across medical and behavioral health and separate delivery technologies for review. A licensed criterion remains one review input; the payer's benefit, policy, population, exception, and decision authority still need their own record.
Redox documents a FHIR API action for submitting service and medication authorization requests, but the connection must support a digital workflow and responses may be synchronous or asynchronous. An available action is not proof that every payer or request path is reachable.
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.
URAC's Health Utilization Management program applies to eligible U.S. organizations and named clinical-review functions. A platform feature, automation rate, or vendor logo does not by itself establish that accreditation scope.
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.
Cigna's provider page assigns different purposes, requirements, channels, and decision limits to three related workflows. Treating them as one authorization status loses the payer and provider responsibilities that control the request.
The provider's public workflow connects prescription-benefit data, drug-specific questions, clinical attachments, determinations, and renewals; it does not establish coverage for medical-service authorization.
The reporting template separates standard and expedited medical-service requests, outcomes, appeals, and decision timing while recommending counts beside percentages so readers can see scale.
The current Da Vinci guide defines a FHIR prior-authorization request and response workflow while preserving the separate X12 mapping, licensing, and regulatory boundary that implementers still have to govern.
The Da Vinci guide uses computable questionnaires, rules, and EHR context to gather payer-requested documentation, but publication of the guide does not prove that a payer connection or decision works in production.
Coverage Requirements Discovery can bring payer requirements into a provider workflow before a request is sent. It does not submit or decide the authorization.
NCQA joins objective criteria, relevant clinical information, and qualified review in one framework. A faster transaction is not the full control.
CMS requires impacted payers to provide a specific reason for denied prior-authorization decisions beginning in 2026, while the API provisions add structured status exchange in 2027. The reason must survive the workflow, not appear only in a final notice.
CMS's July 20 FAQ says the Prior Authorization API need not produce real-time decisions. Clinical review, reasons, status, and deadline evidence still matter.
Seven additional HCPCS codes became subject to nationwide prior authorization as a condition of payment, while CMS also introduced an exemption path for qualifying suppliers.
CMS-0062-P would bring drug authorizations into a broader interoperability framework while also proposing updated standards and transaction requirements.
The March 31 reporting milestone creates a new, imperfect public evidence layer for examining payer authorization volume, outcomes, and decision timeframes.
CMS now requires MA organizations to submit information about internal coverage criteria used by the organization or its delegates for Part C prior authorization.
The initial Decision Intelligence Ecosystem connects Anterior, Latitude Health, and Case Health AI to GuidingCare, signaling a modular market for clinical review intelligence.
The three Da Vinci implementation guides define connected but distinct stages for discovering requirements, assembling documentation, and exchanging authorization requests and responses.
The provider-side offering combines rules, payer connectivity, automation, EHR completion, and human operations across determination, submission, and follow-up.
Beginning March 7, 2026, EviCore took on additional inpatient and outpatient authorization categories for specified Cigna Healthcare plans.
The joint offering pairs Availity's payer-provider network with Onyx's FHIR platform for payer API, data transformation, prior authorization, and reporting requirements.
The payer committed to removing about one-third of outpatient prior-authorization requirements, expanding one-day decisions, and launching a national gold-card program.
The federally named version becomes required January 1, 2028 and includes specific electronic prior-authorization transactions alongside broader e-prescribing changes.
