Kaiser claims automation means Epic Resolute, and the vendor list is shorter than it looks

Yes. Kaiser Permanente's enterprise EHR, KP HealthConnect, is built on Epic Systems software and hosts records for more than ten million members. That matters because in an Epic shop, claims live in Epic Resolute, Epic's revenue cycle billing application. Resolute splits into Hospital Billing (HB), Professional Billing (PB), and Single Billing Office (SBO). The expensive manual work is billers opening claim-edit and denial work queues in the Epic client and typing corrections account by account. So Kaiser-style claims automation is, concretely, automating the Resolute work queues in the Epic desktop client, not a generic claims API.

No. Olive AI, once valued near four billion dollars, shut down its business in October 2023. It sold its clearinghouse and patient access units to Waystar, its prior authorization unit to Humata Health, its utilization management unit to Availity, and its business intelligence to BurstIQ. If you are comparing Olive against the others as a live, standalone option, the comparison is out of date. The pieces of it now live inside other companies on the same list.

They are the same company. nThrive announced its name change to FinThrive in March 2022 as part of a rebrand. So listing nThrive and FinThrive as two separate vendors to evaluate double-counts one revenue cycle management company. FinThrive is the current name.

They can drive the Epic client, but it is the brittle part of those deployments. Epic is usually delivered to billers over Citrix, and pixel-matched or selector-based bots break when the published client shifts, when Epic ships a quarterly upgrade, or when a layout moves. To get reliable, teams often get pushed toward an Epic interface or API project, which turns a bot into a months-long Center of Excellence engagement. Mediar takes a different route: it reads Resolute fields by name from the Windows accessibility tree, so a renamed button or a moved field does not stop the run.

No, they are different layers. Akasa runs generative AI for mid-cycle work, coding, prior authorization, and clinical documentation, inside your existing Epic or Cerner without a rip and replace. Waystar is a claims clearinghouse and payments platform that moves the 837 out and the 835 back; it facilitated over six billion transactions in 2024 and went public on Nasdaq that June. Mediar is neither a coding model nor a clearinghouse. It is the desktop execution layer that works the Resolute account screen when a human would otherwise be typing. The three can coexist: Akasa suggests the code, Waystar moves the claim, Mediar works the denial queue.

Resolute is Epic's revenue cycle billing application, covering Hospital Billing, Professional Billing, and Single Billing Office. Billers reach it through Epic's user interface, historically Hyperspace, the long-standing Windows desktop client, and increasingly Hyperdrive, Epic's newer Chromium-based client. Both are desktop applications a person logs into and clicks through. There is no public claim-level API that lets an outside tool open and resolve a Resolute work queue, which is why the automation has to drive the client a biller drives.

Mediar is SOC 2 Type II certified and HIPAA compliant, and deploys on-prem or in your cloud. Because it runs on the same workstation or virtual desktop a biller uses, the protected health information stays inside your environment; the agent operates the existing client rather than exporting data to a separate service.