Infinx Healthcare: AI-Powered Prior Authorization and Revenue Cycle Services at Scale

Infinx combines AI automation with managed services for prior auth and RCM — targeting the mid-market health system that needs more than point solutions.

Prior authorization consumed an estimated $3.5 billion in administrative costs across the U.S. healthcare system in 2022, according to CAIR Coalition research, and the burden has only intensified as payer policy complexity compounds. Infinx Healthcare, founded in 2012 in San Jose, California, started as a radiology-focused prior auth shop and has since evolved into a full-stack revenue cycle platform that pairs AI automation with a managed services delivery model — a combination that mid-market health systems are increasingly shopping for as point solutions proliferate and integration fatigue sets in. With $194 million in total capital raised and backing from KKR and Norwest, Infinx now has the balance sheet to compete on scale, and its recent acquisition of i3 Verticals' healthcare RCM business signals an inorganic growth agenda that billing directors need to understand before they sign.

Executive Summary

  • Infinx reports 85%–90% of revenue is recurring or reoccurring, with EBITDA margins in the 20%–30% range — financial durability metrics that exceed most pure-play RCM software vendors and position the company as a credible long-term partner rather than a pre-revenue startup.
  • The RCM Plus platform targets a 2–5% net patient revenue uplift and 20% net new collections from A/R and denied claims, claims that should be stress-tested in any contract negotiation through SLA language tying fees to performance baselines.
  • Backed by KKR (Asian Fund IV) and Norwest with $194M raised, growing 50%–70% historically through organic growth and acquisitions, Infinx is in active acquisition mode — buyers must assess contract continuity and service-level protections in the event of further consolidation.

For billing directors evaluating Infinx, the core question is not whether the technology works in isolation — it does, to a measurable degree — but whether the hybrid model of AI agents plus offshore-capable managed services staffing actually reduces your cost-to-collect or simply redistributes administrative labor under a different vendor logo. The answer depends heavily on implementation rigor, EHR integration depth, and how performance SLAs are structured at contract execution. This article breaks down each of those dimensions with the specificity that a vendor's sales deck will never offer.

The Landscape: Prior Auth In 2026

The American Medical Association's 2024 prior authorization physician survey found that 94% of physicians report prior auth burdens as causing care delays, and 78% report that PA burdens have increased over the prior five years. CMS's Interoperability and Prior Authorization Final Rule (CMS-0057-F), finalized January 17, 2024, requires impacted payers — Medicare Advantage organizations, Medicaid managed care plans, CHIP managed care entities, and QHP issuers on the Federally Facilitated Exchanges — to respond to prior authorization requests within 72 hours for urgent cases and seven calendar days for non-urgent requests, transmitted via HL7 FHIR-based APIs, with compliance deadlines beginning January 1, 2026 for most impacted payers. That regulatory shift changes the competitive calculus for vendors like Infinx, because electronic submission and status tracking — previously a vendor differentiator — becomes a baseline expectation under the rule, not a premium capability. Vendors who cannot integrate with payer FHIR endpoints at scale will find their automation value propositions eroded.

Note for buyers: The rule applies to the specified payer categories above. Traditional Medicare fee-for-service and commercial fully-insured payers not on the Federally Facilitated Exchange are not subject to CMS-0057-F's FHIR API mandates, meaning FHIR-based PA submission will be uneven across your payer mix through at least 2027. Vendors claiming universal FHIR connectivity across all payer types are overstating the current state of payer infrastructure.

Simultaneously, the mid-market health system segment — roughly $200M to $2B in net patient revenue — remains chronically underserved by both ends of the vendor spectrum. Enterprise RCM platforms like Epic Resolute and Oracle Health's billing suite are deeply embedded but require expensive configuration to optimize prior auth workflows. Pure-play prior auth point solutions like Cohere Health or Rhyme (formerly PriorAuthNow) address specific workflow gaps but stop short of full-cycle managed services. Mid-market systems need a vendor that can automate submission, manage exceptions through human expertise, chase denials, and generate AR analytics in a single engagement — which is exactly the gap Infinx has positioned its Healthcare Revenue OS to fill.

Infinx's origin story is instructive here. The company launched in 2012 specifically to solve manual prior auth for a large radiology group, which means its automation logic was built from ground-level clinical workflow observation rather than top-down product design. That practitioner-first foundation shows in the platform's work queue prioritization and exception routing capabilities, which are designed to surface the cases most likely to slip through, not simply process volume for vanity metrics.

How The Platform Works

Infinx's current platform architecture centers on what the company calls the Healthcare Revenue OS — an operating system framing that signals intent to serve as the connective tissue across patient access, mid-cycle, and backend RCM rather than a single-workflow tool. The core components include AI agents capable of handling reasoning and action workflows for prior authorization submission, eligibility verification, status tracking, coding audit, and denial follow-up. When the AI agent encounters a case that requires judgment — complex clinical criteria, peer-to-peer escalation, or payer-specific edge cases — the system routes to an Infinx RCM expert rather than failing silently. That human-in-the-loop architecture is the differentiator the company leads with, and it is operationally meaningful: fully automated prior auth submission has well-documented failure modes when payer portal behaviors change, and having credentialed staff available to intervene prevents the authorization queue from backing up into a claims hold.

On the prior authorization workflow specifically, Infinx automates portal submission across major commercial and government payers, tracks status without manual follow-up calls, and flags cases approaching payer decision deadlines for prioritized human review. The platform also supports peer-to-peer escalation coordination — not a trivial capability, since P2P requests require clinical documentation packaging, physician scheduling, and payer-side physician matching, all of which create drop-off points in manual workflows. The RCM Plus suite extends this into denial management, predictive analytics for future denial prevention, and A/R recovery work queues. The company's stated performance targets for RCM Plus — 2–5% NPR uplift and 20% net new collections from denied claims — are specific enough to anchor contractual SLA discussions.

EHR integration is a practical gating factor for any mid-market deployment. Infinx supports Epic, Oracle Health (Cerner), athenahealth, and Veradigm (formerly Allscripts), covering the majority of mid-market EHR footprints. Integration depth matters more than mere connectivity: a vendor that can only read ADT feeds and write back auth status to a single field is materially different from a vendor with bidirectional workflow integration that surfaces prior auth worklists inside the EHR clinician view. Buyers should request an integration specification document, not just a compatibility list, and should ask specifically whether Epic SmartForms for prior auth and Oracle Health PowerChart workflow integrations are in scope for their contract tier.

Where It Delivers Value

The clearest value delivery in the Infinx model is in high-volume prior auth specialties with predictable payer behavior — radiology, cardiology, orthopedic surgery, and infusion therapy. These are service lines where authorization volumes are large enough to justify automation investment, payer criteria are documented enough for AI rule logic, and manual processing errors are frequent enough that the baseline for improvement is low. Foothill Cardiology Medical Group is a named client that specifically credits Infinx with allowing it to maintain costs while scaling resources quickly, which aligns with the high-volume cardiology prior auth use case the platform was designed around. For these specialties, the automation layer handles routine submissions while exception queues capture the complex cases — a workflow configuration that meaningfully reduces the FTE-hours required per authorization.

By the Numbers

The AMA's 2024 prior authorization physician survey reports 94% of physicians cite prior authorization as directly delaying patient care, making workflow automation in this category a patient safety issue, not just an efficiency metric.

On the managed services side, Infinx's model is best understood as staff augmentation with workflow tooling built in, rather than pure outsourcing. The company provides trained, experienced RCM specialists who work alongside provider billing teams using the Infinx platform. This hybrid model is valuable for health systems that have lost institutional knowledge through staff turnover — a persistent post-pandemic problem — but that are not ready or willing to fully outsource their revenue cycle. The cost-to-collect improvement comes from reducing the salary burden of building internal prior auth and denial management teams while retaining internal oversight. The CFO testimonial from Foothill Cardiology references specifically that "we get the money upfront, we get paid for the services, and everything revolves in a shorter collection cycle" — a cash flow statement that billing directors should probe with their own DSO data before replicating.

Pro Tip

Ask Infinx for specialty-specific auth approval rate benchmarks segmented by payer family — commercial, Medicare Advantage, and Medicaid managed care — before signing. Blended averages obscure performance variance that will surface in your highest-denial service lines first.

The A/R and denial recovery component is where Infinx claims 20% net new collections, a figure that requires context. "Net new" means collections from inventory that would otherwise have aged out or been written off — not 20% added to existing top-line collections. In practice, this materializes most clearly when an organization has an A/R backlog with claims over 90 days and limited internal capacity to work denials. Infinx's work queue prioritization software — which surfaces cases by recovery probability and dollar value rather than date order — is the automation layer that makes this realistic at scale.

Competitive Positioning

Infinx operates in a space with crowded adjacencies. On the pure prior auth automation side, Cohere Health focuses on AI-driven clinical decision support that works with payers to streamline criteria application — its model is payer-partnered, which means it has different incentive alignment than a provider-side vendor. AccuReg targets the patient access workflow including insurance verification and auth management, with a stronger front-end eligibility focus but less depth in denial management and A/R recovery. Neither offers the managed services staffing model that Infinx pairs with its technology.

Watch Out

Cohere Health's payer-side partnerships mean it operates within payer utilization management frameworks and can influence criteria application in ways that reflect payer cost-containment goals. If your health system has a complex case mix or high-cost service lines, a provider-side vendor like Infinx with no payer revenue dependence is structurally better aligned to your interests.

Against the large RCM outsourcing firms — R1 RCM and Ensemble Health Partners — Infinx occupies a meaningful middle ground. R1 and Ensemble are built for enterprise health systems with $2B+ in NPR; their managed services models involve deep integration into hospital operations, and their pricing reflects the overhead of large engagement teams. Infinx targets hospitals and ambulatory surgery centers in the mid-market, where the engagement model is more modular and pricing is more accessible. The trade-off is that Ensemble and R1 carry deeper payer contracting intelligence and broader denial analytics data sets accumulated over larger claim volumes. Infinx's acquisition of i3 Verticals' healthcare RCM business accelerates its move up-market by adding client volume and operational capacity, but buyers should assess whether that integration is complete before committing to enterprise-scale engagements.

VendorPrimary ModelPrior Auth DepthManaged ServicesTarget Segment
Infinx HealthcareAI + Managed ServicesFull workflow + P2P supportYes — staff augmentationMid-market hospitals, ASCs
Cohere HealthAI Clinical Decision SupportPayer-side criteria automationNoPayers + provider partners
AccuRegPatient Access SaaSEligibility + auth initiationLimitedMid-market ambulatory
R1 RCMEnterprise OutsourcingIntegrated with full-cycle RCMYes — full outsourcingLarge health systems
Ensemble Health PartnersEnterprise OutsourcingIntegrated with full-cycle RCMYes — full outsourcingLarge IDNs

The 7 Powers Lens: Infinx Strategic Durability

The 7 Powers framework, developed by Hamilton Helmer, provides RCM buyers with a structured way to evaluate whether a vendor's competitive advantages are durable — not just whether the product is good today, but whether the company will remain a strong partner in three to five years as the prior auth automation market consolidates. For Infinx specifically, understanding its power profile matters because the company is in active acquisition mode, growing 50%–70% annually through both organic and inorganic channels. A vendor scaling that quickly needs durable economic moats to avoid margin erosion from integration complexity, talent dilution, or competitive imitation. The table below assesses all seven powers for Infinx as of mid-2026.

PowerStrengthAssessment
Scale EconomiesModerateAI automation cost per authorization declines at scale; managed services staffing does not. Mixed model limits pure scale benefits.
Network EconomiesWeakNo multi-sided payer-provider network effect. Payer portal automation improves through data but is not network-dependent.
Counter-PositioningModerateHybrid AI + managed services model is difficult for pure-play SaaS vendors to replicate without building a staffing infrastructure.
Switching CostsStrongDeep EHR integration, trained staff embedded in client workflows, and historical auth data create high displacement cost for buyers.
BrandingWeakLimited brand recognition outside RCM professional circles. Not a meaningful purchase driver at this stage.
Cornered ResourceModerateKKR/Norwest capital provides acquisition currency. Proprietary payer portal automation logic and training data are defensible assets.
Process PowerStrong14 years of prior auth workflow design across radiology, cardiology, orthopedics, and hospital billing creates hard-to-replicate operational playbooks.

Switching Costs Are the Core Moat

Switching costs are Infinx's most durable power, and billing directors need to understand this from both sides. For buyers already under contract, switching costs are real: Infinx staff become embedded in daily workflows, historical authorization data lives in the Infinx platform, EHR integrations are configured and tested, and work queues are trained to client-specific payer mix. Replacing that infrastructure requires a parallel-run period of three to six months minimum, during which authorization queue management risk is significant. The practical implication is that once deployed at scale, Infinx engagements are sticky — which is a feature if performance is strong and a trap if performance degrades and the vendor relationship sours. Billing directors should negotiate exit provisions at contract inception, not after the platform is live.

Process Power as a Genuine Differentiator

Infinx's 14-year operating history in prior auth and RCM, beginning with the manual-intensive radiology authorization workflows of its founding client, has produced a depth of specialty-specific process knowledge that newer AI-only vendors cannot replicate through training data alone. Radiology auth criteria vary by payer, modality, and clinical indication — the logic trees required to automate those correctly across 50-plus payer configurations represent years of iteration. The same applies to cardiology device authorizations and orthopedic surgical procedure approvals, where payer-specific documentation requirements are often unpublished and learned through submission experience. That operational knowledge is embedded in the platform's rule logic, exception routing, and staff training protocols, and it is not easily imitated by a competitor who enters the market with a language model and an API connection.

Biggest Strategic Vulnerability

Infinx's strategic vulnerability is the tension between its managed services growth and its AI automation positioning. The 20%–30% EBITDA margin is healthy, but managed services staffing at scale compresses margins relative to pure SaaS. As the company acquires RCM businesses — including the i3 Verticals healthcare RCM acquisition — it adds headcount and operational complexity that can dilute the automation narrative. If Infinx is perceived by the market as primarily a staffing company that has bolted on AI, rather than an AI platform that uses human experts as a quality layer, it will face downward pricing pressure from lower-cost offshore RCM firms and upward pressure from enterprise software platforms extending into the RCM space. The 50%–70% growth trajectory requires continuous investment in the automation layer to maintain its technological differentiation against that competitive gravity.

Implementation Experience

Implementation quality at Infinx varies in ways that are predictable based on engagement scope and EHR environment. Buyers report that the client portal's search and audit functionality — the ability to pull up a patient record, see all submitted authorizations, call log history, and reference numbers in a single view — is operationally strong and reduces the back-and-forth between billing team and Infinx staff. That visibility is a genuine improvement over legacy fax-and-phone auth workflows where status information lived in a specialist's notebook. The challenge is in the integration go-live period: EHR integrations for Epic and Oracle Health require IT resource commitment from the provider side, and health systems that underestimate that resource requirement experience delayed productivity realization.

Watch Out

If your Epic environment uses heavily customized build or your Oracle Health instance has significant custom extensions, allocate at least one dedicated IT analyst to the Infinx integration project for the first 90 days. Understaffing the IT side is the most common root cause of delayed go-live and early performance shortfalls in mid-market deployments.

The training period for Infinx managed services staff on specialty-specific payer criteria is reported as four to six weeks for standard commercial payers and longer for complex Medicare Advantage plan variations. During this ramp period, clients should expect a reduced throughput rate and should communicate that to their clinical scheduling teams to avoid authorization queue bottlenecks for new patient scheduling. The Infinx model of weekly virtual executive sessions is a useful governance mechanism during implementation — billing directors should take advantage of that access rather than waiting for quarterly business reviews.

Pricing And Roi Analysis

Infinx does not publish pricing publicly, which is standard for complex managed services engagements where scope varies significantly. Based on publicly available vendor profile data and market intelligence, the pricing model operates on two primary structures: per-authorization fees for technology-led prior auth workflow automation, and per-FTE managed service fees for broader RCM outsourcing engagements. Some clients report hybrid arrangements where a base platform fee covers technology access and per-unit pricing applies to transaction volume above a contracted threshold.

The ROI case for prior auth automation is straightforward when authorization denials are quantified. A 500-bed hospital processing 4,000 authorizations per month at a manual cost of $10–$14 per authorization (inclusive of labor, telephony, and rework) faces $40,000–$56,000 per month in direct prior auth processing cost before denial downstream impact. Reducing that per-auth cost by 40%–60% through automation — a realistic outcome in high-volume, payer-predictable service lines — generates $16,000–$34,000 in monthly savings before factoring in denial rate improvement. The 2–5% NPR uplift claim from Infinx's RCM Plus platform is harder to model without client-specific data, but for a $300M NPR health system, 2% represents $6 million in incremental revenue — a figure that justifies significant vendor investment if achievable.

By the Numbers

For a mid-market health system with $300M in net patient revenue, the RCM Plus platform's stated 2% NPR uplift target translates to $6 million annually — against which even a $1.5M–$2M annual managed services engagement represents a strong ROI on paper.

The hidden cost risk in managed services pricing sits in scope creep. Infinx engagements can expand from prior auth to denial management to coding audit to full A/R recovery as the vendor demonstrates value and the client team becomes dependent on the Infinx workflow. Each expansion is individually justifiable, but the aggregate cost of a fully integrated Infinx managed services engagement can approach the cost of the internal FTEs that were eliminated. Billing directors should establish a scope baseline with associated unit economics at contract signing and require renegotiation benchmarks if scope expands beyond 20% of original contract value.

Pro Tip

Require quarterly cost-per-clean-claim and cost-per-authorization reporting as a contractual deliverable from day one. Without that data, scope expansion discussions will be driven by vendor narrative rather than your own unit economics.

What To Do Monday Morning

  1. 1
    Pull Your Prior Auth Denial Rate by Specialty and Payer Family

    Before any Infinx demo, run a 90-day analysis of your prior auth-related denials segmented by specialty (radiology, cardiology, orthopedics, infusion) and payer family (commercial, Medicare Advantage, Medicaid managed care). Request that your current billing system or clearinghouse export CO-50 (non-covered service), CO-15 (authorization absent or exceeded), and CO-197 (precertification/authorization absent) denial codes at the claim line level. This baseline gives you a specific performance floor against which to hold Infinx accountable in SLA negotiations — and it will immediately reveal which service lines and payers represent the highest-dollar opportunity for automation improvement.

2. **Demand Specialty-Specific Approval Rate References