The challenge
Three different EHRs across the system — Epic in the flagship hospital, Oracle Health (Cerner) in two acquired community hospitals, athenahealth across the ambulatory network — meant every prior scribe pilot only served one silo.
Provider burnout on the Maslach inventory had climbed for three years running, with statistically significant deterioration in primary care, emergency medicine and hospital medicine.
Before S10.AI
- Three different EHRs across the system — Epic in the flagship hospital, Oracle Health (Cerner) in two acquired community hospitals, athenahealth across the ambulatory network — meant every prior scribe pilot only served one silo.
- Provider burnout on the Maslach inventory had climbed for three years running, with statistically significant deterioration in primary care, emergency medicine and hospital medicine.
- Attrition warning signs were live: early-career physician turnover had doubled year-over-year, and exit interviews cited documentation load as the #1 driver.
After S10.AI
- CRUSH deployed via clinical RPA into Epic, Oracle Health and athenahealth in parallel — no EHR-specific engineering effort and no vendor SOWs beyond the master agreement.
- Federated rollout model: each of the 34 sites had a local physician champion paired with a dedicated S10.AI success lead for the first 30 days.
- AI Team agents took over inbox triage, refill drafting and prior-authorisation letters across all three EHRs on shared workflows — one config, three EHRs.



