Quick answer: R1 RCM and Waystar are not the same category. R1 is an enterprise RCM partnership and operating model (people plus Phare OS) aimed at health systems. Waystar is a clearinghouse and payments platform with AltitudeAI. Choose R1 when you are outsourcing or co-sourcing the revenue cycle. Choose Waystar when you want to keep RCM in-house and change how claims are routed and analyzed.
Inclusion criteria: Head-to-head on deployment model, EHR fit, payer coverage, and whether you must replace a clearinghouse or BPO.
Honest limitations: Substrate does not replace a clearinghouse, EHR, coder, or patient-billing platform. It automates post-submission AR. Claim status includes denial root-cause analysis (eligibility, records, medical necessity, wrong route), not just a 277 code or an 835 variance. Clinical edge cases still go to staff. Coding, CDI, and patient-facing billing are out of scope.
At a glance
Where R1 RCM wins
- Health systems that want a partner to run or co-run the revenue cycle
- Coding, CDI, and denial programs bundled with labor
- Buyers already in an R1 conversation at CFO / board level
Where Waystar wins
- In-house teams that need 837/835 scale and AltitudeAI on their own staff
- Denial prevention and remits without a BPO contract
- Faster path if you already submit through Waystar
Also consider Substrate
Also consider Substrate when the gap is post-submission follow-up on the current PM: live in days, EDI and portal coverage across 3,500+ payers, PM writeback with a video audit trail, and denial root-cause analysis as part of claim status (eligibility, records, medical necessity, or wrong route) rather than a 277 code or an 835 variance alone. Substrate does not replace a clearinghouse, EHR, coder, or patient-billing platform. It is software on your PM, not an R1 partnership and not a Waystar migration. Use it when you keep the team and the clearinghouse and still need portal status plus the unpaid reason.
Research sources
R1 partnership materials, Waystar clearinghouse and AltitudeAI pages, and HFMA-style build-vs-outsource discussions. Confirm scope and exit clauses in legal review.