R1 Acquires Humata Health and Moves Prior Authorisation Into the Revenue-Cycle Operating System

R1 announced on 18 August 2026 that it had entered into an agreement to acquire Humata Health, a company focused on AI-powered prior authorisation. The stated purpose is to enhance Phare OS, R1’s revenue-cycle platform, with policy monitoring and agentic workflows that can create effective authorisation submissions before a claim is submitted. The companies expect the transaction to close by the end of the third quarter of 2026. Confirmed fact [1]

The commercial logic is upstream. R1 already positions Phare OS around pre-bill workflow automation spanning authorisation, utilisation review, documentation and coding. Humata adds a specialist workflow that identifies requirements, assembles the clinical case, provides evidence for payer attestations and manages the request through approval. The acquisition is therefore an attempt to move from revenue-cycle visibility to a more active authorisation decision and execution layer. Acquiry inference

Nothing in the announcement confirms a purchase price, cash versus equity split, revenue contribution, customer cohort, employee count, deal protection, earn-out, management rollover, buyer-side adviser or regulatory condition. Those omissions matter. They make a valuation, accretion or return-on-invested-capital conclusion impossible at this stage. Public-record boundary

Humata’s disclosed capability set is unusually consequential for an RCM platform because it is not just a document-generation tool. R1 describes a workflow that monitors changing authorisation policies, determines requirement logic, produces an AI-driven clinical bundle, supports payer attestations and manages requests to final approval. Company-stated capability [1]

Determine whether prior authorisation is required and what the payer expects.

Assemble relevant clinical documentation into an authorisation case.

Provide support for the payer’s stated evidence requirements.

Connect and manage the request through review and response.

Feed a decision back into the pre-bill workflow before the claim is submitted.

The acquirable advantage, if the claimed workflow performance survives integration, is the operating data that accumulates around exceptions: which documentation works for a given policy, where the payer requests more information, when a pathway fails and what must be changed before the patient appointment or claim reaches the next stage. This is an integration thesis, not evidence that the data has been legally or technically unified today. Acquiry inference

Humata and R1 do not disclose revenue, pricing model, gross margin, net retention, implementation cost, transaction cost or contribution margin. A conventional SaaS unit-economics assessment is therefore unavailable. The relevant public record instead contains workflow outcomes claimed by Humata. These should be treated as directional commercial evidence, not independently validated KPI data. Disclosure limitation

For R1, the economic opportunity is best expressed as a chain rather than a reported number: fewer preventable denials, fewer manual touches, fewer reschedules and faster progression to a clean claim could raise provider revenue performance and lower the service cost of delivery. The missing variables are conversion, customer eligibility, payer-specific performance, sales cycle, contract structure and human-review requirements. Acquiry inference

R1’s own operating system narrative is modular. Its foundation comprises Phare Intelligence, Payer Atlas and a data platform; its workflow modules extend from prior authorisation through utilisation management, coding, denials and accounts receivable. R1 says Phare OS carries more than $76 billion of net patient revenue, processes more than 600 million payer transactions annually and has more than 1,500 payer connections in Payer Atlas. Company-reported scale [2]

Humata maps directly to two foundational layers. R1 says the target will enhance Phare Intelligence and Payer Atlas. That combination matters because it binds clinical interpretation and policy logic to payer-specific execution rather than treating prior authorisation as a generic prompt or document task. It also creates an opportunity to deploy adjacent Audit and Denials modules with minimal incremental data integration, according to R1. Company-stated integration plan [1]

Distribution

R1’s installed provider footprint can potentially turn Humata from a specialist point solution into a component of a broader revenue-cycle relationship.

Data compounding

R1’s stated payer-connection and transaction scale can improve the value of an authorisation workflow only if the data rights, interfaces and feedback loops are integrated safely.

Cross-sell

The buyer has stated that authorisation customers can deploy additional Phare modules with minimal incremental data integration. This is the clearest public cross-sell claim.

PE value creation

R1’s private owners have an obvious incentive to accelerate software-enabled operational leverage. That is contextual, not a disclosed deal rationale.

There is no public consideration for this transaction, and the public record does not support an EV / revenue precedent analysis. The more useful precedent lens is structural: RCM platforms, EHR vendors and payers are all seeking to control the prior-authorisation interface, because it sits at the intersection of clinical documentation, payer policy, scheduling, utilisation and payment. Healthcare Dive noted that Epic had launched an instantaneous prior-authorisation-requirement check in the same period. Market observation [6]

That does not make Humata interchangeable with those platforms. It clarifies the deal logic: R1 is buying specialised automation before the interface becomes fully standardised or absorbed into a larger enterprise workflow. Acquiry inference

Note This is an operating-position comparison. It is not a revenue, market-share or valuation comparison and should not be read as one.

Humata disclosed a $25 million financing round in June 2024. It did not disclose a valuation in the available public source, and R1 did not disclose transaction consideration in the acquisition announcement. Therefore, no funding-to-exit uplift, revenue multiple, cost-synergy multiple or buyer return can be calculated responsibly. Confirmed disclosure boundary [4]

Humata says it raised $25 million in a financing announced on 20 June 2024. The round was led by Blue Venture Fund and LRVHealth. Other named investors included Optum Ventures, 406 Ventures, Highmark Ventures and VentureforGood. R1 additionally identifies Sandbox Clinical Venture Fund among Humata’s strategic healthcare investors. Confirmed financing record [4] [1]

Humata Health founded

Founded by Jeremy Friese, MD, according to the target’s 2024 funding announcement. [4]

$25m financing announced

Blue Venture Fund and LRVHealth led the disclosed round. Valuation and total capital raised are not disclosed in the cited record. [4]

R1 announces agreement to acquire Humata

Terms undisclosed; Lazard named as Humata’s exclusive financial adviser. [1]

The platform publishes weekly rankings of which models carry the volume. In June 2026 DeepSeek led at 17.6 per cent, followed by Anthropic at 14.8, Google at 12.5 and OpenAI at 8.4. Xiaomi, MiniMax and Tencent each held roughly eight per cent.

Aggregated by origin, Chinese providers account for 46.4 per cent of weekly tokens against 35.7 per cent for United States providers. In mid-2025 the Chinese share was around two per cent on the same platform.

Second-order effects follow from that mix. The routing layer is genuinely multi-model, since no single provider holds eighteen per cent. And the revenue mix is changing underneath the volume, because a flat percentage fee on a cheaper token produces less absolute revenue. That is the deflation question, and it is visible in the platform's own published data.

Weekly token share by provider, June 2026. The absence of a dominant segment is the platform's commercial argument, and the shift in the mix is its central economic risk.

No transaction valuation has been disclosed. The table below is an operating-value map, not a purchase-price allocation or an attribution of financial benefits.

CMS’s Interoperability and Prior Authorization final rule places a hard timing and data-exchange frame around the market. Impacted payers face operational requirements generally beginning 1 January 2026, while API development and enhancement requirements generally begin 1 January 2027. The rule requires timeframes of 72 hours for expedited requests and seven calendar days for standard requests, with scope exclusions, and calls for specific denial reasons beginning in 2026. Regulatory fact [5]

For R1, this creates a plausible timing advantage. A platform that can translate clinical data and payer policy into an electronic authorisation request should become more relevant as the standardised data and API environment matures. The contrary risk is equally important: greater standardisation can commoditise parts of the workflow, lowering the value of connective infrastructure unless R1 differentiates on accuracy, coverage, orchestration and outcome data. Acquiry inference

Humata will compete with, integrate with or be constrained by four distinct categories: EHR-native workflow capabilities, payer portals and emerging prior-authorisation APIs, specialist automation vendors and broader RCM platforms. The public record is insufficient to rank individual competitors, estimate share or assert technical superiority. The market position that matters is the ability to achieve a complete, auditable request-response loop without creating new work for clinicians or revenue-cycle teams. Analytical framework

EHR-native

Strength: point-of-care access. Risk to R1: workflow adoption can hinge on EHR integration quality.

Payer-controlled

Strength: policy and decision authority. Risk to R1: API coverage and operating rules are externally controlled.

Specialist PA automation

Strength: focused authorisation domain expertise. Opportunity: Humata adds this specialist layer to R1’s broader platform.

End-to-end RCM

Strength: downstream operational data and customer access. Risk: platform complexity can slow implementation and product iteration.

R1 says Humata’s technology will connect to Phare OS and that the Humata team will enhance R37, R1’s agentic-AI development lab, after closing. The rational first integration is not a broad platform migration. It is a governed loop between a defined authorisation cohort, the relevant payer requirements, the required clinical documents and the downstream adjudication outcome. R1 plan + Acquiry integration inference [1]

Retain specialist workflow velocity and customer continuity while formal integration begins.

Link Humata to Phare Intelligence, Payer Atlas and governed data pathways.

Launch defined payer, specialty and provider cohorts with measurable controls.

Use the shared data layer to demonstrate Audit and Denials expansion value.

Expand only when accuracy, exceptions, cycle time and economic outcomes are evidenced.

R1 becomes privately held

TowerBrook and CD&R complete their acquisition of R1 at an approximately $8.9 billion valuation. [3]

Humata announces $25m financing

Funding is led by Blue Venture Fund and LRVHealth. [4]

CMS operating provisions begin

CMS process-related requirements generally begin, subject to the rule’s scope and applicable payer type. [5]

R1 announces Humata acquisition agreement

R1 frames the transaction around Phare OS and real-time authorisations. [1]

Expected transaction close

Expected close date stated in the announcement. Completion remains unconfirmed at the time of publication. [1]

CMS API requirements generally begin

Impacting payer API development and enhancement requirements generally begin. [5]

The public evidence supports the strategic rationale. Humata gives R1 a specialist authorisation capability exactly where Phare OS needs to act before downstream claim friction appears. R1 brings the distribution, payer context and modular platform that could compound the value of that capability.

The public evidence does not support a view on price discipline, target quality, accretion or returns. The deal’s success will be decided by payer-specific interoperability, clinical and policy accuracy, implementation discipline and the ability to convert discrete authorisation performance into repeatable Phare OS cross-sell. Until those outcomes are published, the correct posture is strategically positive, financially unscorable.

Formal confirmation that the transaction has closed and any additional disclosed conditions or terms.

Specific sequencing of Humata into Phare Intelligence, Payer Atlas, Audit and Denials.

Initial provider, payer or specialty launch cohorts with an observable workflow scope.

Disclosure of live payer connections, API coverage, exception pathways and policy refresh cadence.

Independent or cohort-level evidence behind first-pass approval, write-off, reschedule and staff-touch claims.

How Humata’s founder, product leaders and implementation talent are positioned inside R37 and Phare OS.

This report uses public company announcements, a CMS fact sheet and identified independent media coverage. Company-reported metrics are labelled accordingly. No valuation, implied multiple, accretion or return is estimated because consideration and target financials were not disclosed.