Ambience Healthcare

Ambience Healthcare builds an AI operating system for clinical documentation that pairs an ambient scribe with a suite of point of care automation modules. Founded in 2020 by Mike Ng and Nikhil Buduma, who met at MIT, the company has raised roughly $373 million, most recently a $243 million Series C in July 2025 led jointly by Oak HC/FT and Andreessen Horowitz at a valuation near $1 billion, with earlier backing from Kleiner Perkins, the OpenAI Startup Fund, and Optum Ventures. Cleveland Clinic selected Ambience over four rival scribes for a five year deployment, and the platform runs at UCSF, Memorial Hermann, John Muir Health, The Oncology Institute, and GI Alliance.

The flagship AutoScribe listens to a visit and produces a fully structured note within about twenty seconds, classifying each statement into the right documentation section and adapting to the provider's style, with specialty tuned models covering more than 200 specialties including emergency and hospital medicine. What separates Ambience from scribe only tools is the surrounding suite: AutoCDI validates the note against ICD-10 and CPT coding requirements at the point of care with audit trails for revenue cycle teams, AutoAVS generates patient friendly after visit summaries in the patient's language, AutoRefer drafts referral letters, and AutoPrep reads prior charts to prepare a visit agenda. A Chart Awareness platform launched in February 2026 grounds notes in the full longitudinal record, including prior notes, labs, imaging, medications, and problem lists. Integrations cover Epic, Oracle Health, and athenahealth through native APIs.

Ambience sells annual enterprise contracts priced per clinical full time equivalent and publishes no pricing. Third party analyses put base AutoScribe near $2,800 to $3,200 per provider per year, with the full module suite reaching $4,000 to $5,000 or more. There is no self serve path, and support is English first, which keeps the product squarely aimed at large health systems rather than independent practices. The bet is that documentation, coding integrity, and revenue cycle belong in one pipeline rather than in separate tools.