R1 RCM API
No public API. R1 RCM ingests hospital revenue-cycle data through an internal Unified Data Exchange wired to EMRs, payers, and banks. Integration is delivered as a service engagement with bespoke connections, not a developer product.
Frequently asked questions
R1 RCM scores F on Supergood's API Report Card. No public API. R1 RCM ingests hospital revenue-cycle data through an internal Unified Data Exchange wired to EMRs, payers, and banks. Integration is delivered as a service engagement with bespoke connections, not a developer product.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
R1 RCM provides healthcare revenue cycle management for hospitals, health systems, and physician groups, combining technology (its Phare / Revenue Operating System with agentic AI) and managed services to handle patient access, claims, billing, and collections from intake to final payment.
Healthcare RCM / Billing, Typically for hospitals, health systems, and large physician groups. Provider organizations outsource or augment revenue-cycle operations: patient registration/eligibility, claim adjudication, denial management, billing, and collections run through R1's platform and teams.
One of the largest RCM providers in the US, managing revenue cycle for major health systems; publicly traded with very large scale.
Yes, Holds hospitals' claims, billing, eligibility, denials, and patient-revenue data, the financial system-of-record for provider revenue.
~20+ years old (founded 2003 as Accretive Health); modernizing with an AI-driven 'Revenue Operating System' (Phare) atop large-scale operations.
No public developer documentation or self-serve API. Integration handled via services/data-exchange, not open API. Full sourced list under Sources below.
Common alternatives include Optum (UnitedHealth), Ensemble Health Partners, Conifer Health Solutions, Waystar. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Not that we could find. As of August 2026 there is no official R1 RCM MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. R1 RCM doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.