Be a VC scout 🤩❓, First AI native hospital, Ambient scribes are dead as a category 🎙️, Alexandria
Scrub Capital is looking for scouts. If you’re a clinician-builder, this is how you get into VC without leaving the bedside.
Scrub Capital — the physician-led health tech venture fund that closed Fund 1 oversubscribed beyond $10M in Q1 2026 — is starting a scout program ideal for clinician builders. This is not your average, fund: notably Jon Slotkin, one of the three GPs of the fund, is a neurosurgeon and Chief Medical Officer for Strategy and Growth at Geisinger.
The scout opportunity: bring deal flow from networks the fund can’t access on its own. If you’re a clinician who builds things and also notices what other clinicians are building, this is the intersection. You don’t need to leave your clinical job. You don’t need to raise a fund. You need a thesis, a network, and the ability to spot the clinician-founder who’s three months from quitting their job to build full-time.
I often find you might be able to do more good at scale helping others than starting your own thing. Most clinician-builders think the path to VC is “build a company, get funded, exit, then become an investor.” The scout model skips the exit. You invest your attention and network access, not your capital. And the fund gets something no traditional VC scout can offer — clinical pattern recognition on whether a product actually works at 2 AM.
💡 80/20: If you’ve been building in a clinical niche and you keep seeing the same problems that nobody is solving well, write a one-page thesis: “I believe [category] is under-invested because [specific clinical insight that non-clinicians miss].” That’s the pitch for a scout conversation. The bar isn’t deal volume — it’s deal quality, and you bring the quality by being a subject matter expert.
The ambient scribe is dead. What replaced it is much bigger.
Two things happened in the same week that, taken together, end the ambient scribe as a standalone product category.
First: Abridge announced multi-year content partnerships with NEJM and JAMA. Clinicians using Abridge can now query peer-reviewed evidence — grounded in both published research and the patient sitting in front of them — during the clinical encounter. This is not a documentation tool with a search bar bolted on. This is a clinical decision support system that happens to also write the note. Abridge serves 250 health systems and will support more than 100 million patient-clinician conversations this year.
Second: Ambience Healthcare unveiled a multiyear platform roadmap at its inaugural Apex Summit, expanding from ambient documentation into five domains: clinical workflows, revenue integrity, patient engagement, care orchestration, and clinical research. They previewed “Kait,” an AI patient agent for between-visit care management, and announced performance-based coding contracts that tie their compensation directly to revenue outcomes. Ambience claims 80%+ clinician utilization and NPS above 60.
Read those two moves together. Abridge pivoted up the clinical value chain — from documentation to decision support. Ambience pivoted across the operational value chain — from documentation to everything. Neither company is building a scribe anymore. They are building the operating system layer that sits between the clinician and every other system in healthcare.
The ambient scribe was always a wedge. The encounter is the richest structured data source in medicine — every diagnosis considered, every medication discussed, every referral weighed. The companies that captured it first had the cheapest entry point into clinical workflows. Now they’re using that position to expand into the things that actually make money: coding accuracy, CDS, care coordination, and longitudinal patient management.
😤 Haters
“Scribes still save time — a large study of 1,800 clinicians found 16 minutes saved per 8-hour shift.” True. And modest. One extra patient every two weeks. The time savings alone never justified the vendor price, which is why every ambient vendor is now pivoting to revenue capture. The ABA published a policy brief calling it the “coding arms race” — ambient tools that up-code documentation are the real business model, not time savings. If you’re building an ambient tool and your pitch is still “saves clinicians time,” your competitor’s pitch is “pays for itself through coding uplift.” You’re in the wrong fight.
“These are two companies. The market is bigger than Abridge and Ambience.” It is. And the market just watched the two leaders publicly abandon the category name. Nuance/Microsoft is already there with DAX Copilot inside Epic. Google is pushing Med-PaLM into documentation-and-beyond. The standalone scribe companies — the ones that only write notes — now have exactly zero room. The feature is commoditized. The platform race is on.
“CDS is a graveyard. Abridge won’t succeed where UpToDate alerts failed for 20 years.” Maybe. But the difference is surface area. UpToDate fires alerts that clinicians dismiss. Abridge is inside the conversation — the CDS is grounded in what the patient actually said, not a generic rule. Whether that’s enough to overcome alert fatigue is an open question. But the integration of NEJM and JAMA citations into encounter-level context is a genuinely new approach, not a repackaged alert.
💡 80/20: If you’re building anything in the ambient/documentation space, answer this question today: are you a feature or a platform? If your tool only writes notes, you are a feature that Abridge, Ambience, or Nuance will replicate in a quarter. The viable builder positions are: (1) verification — the quality layer that audits what the platform produces, (2) specialty depth — the domain-specific model for derm, psych, or peds that the generalists won’t invest in, or (3) the thing the platform can’t do — patient-facing, out-of-EHR, or cross-system. Pick one.
→ Full write-up
UT Austin is building the first AI-native hospital from scratch. $750M. Opens 2030.
UT Austin announced the UT Dell Medical Center — a greenfield academic medical facility with AI systems embedded throughout its physical infrastructure from day one. $750M from Michael and Susan Dell, plus $100M from the Coxe family. The CIO, Claus Jensen, framed the design question: “What does a hospital look like if you design the entire clinical, operational, and physical system around intelligence from day one?” The answer includes an Intelligence Performance Center as the hospital’s operational brain, Living Digital Twins predicting patient deterioration 24-72 hours ahead, environmental sensors, integrated robotics, and full MD Anderson Cancer Center integration. Target: top-10 national ranking within a decade.
😤 Haters
“Every new hospital says it’s going to be ‘smart’ and then opens with the same Epic install as everyone else.” Fair historical pattern. The difference here is timing and funding. $850M in committed philanthropy, a greenfield site with no legacy infrastructure to accommodate, and a 2030 opening date that lands squarely in the window where clinical AI tools are mature enough to embed structurally rather than bolt on. The question isn’t whether they’ll have AI — it’s whether designing around it from the start produces a measurably different care delivery model. We’ll know in four years.
“This is an academic hospital project — clinician-builders should care about startups, not health-system construction.” Disagree. This is a four-year product lab with $850M in funding, a mandate to build differently, and a hiring pipeline that will need clinical informaticists, AI product managers, and clinician-developers who understand both the workflow and the toolchain. If you want to build clinical AI inside a system that’s designed to use it — not fight it — this is the rare case where the health-system path might be better than the startup path.
💡 80/20: Watch the UT Dell Medical Center hiring pipeline over the next 12 months. Greenfield AI-native builds need clinical informatics, AI product, and developer roles that don’t exist at most health systems. If you’re a clinician-builder considering the health-system track, this is the profile: a system that was designed for your skillset, not one that’s trying to retrofit it.
Atropos Health launched a 33-million-artifact evidence library that outperformed GPT-5.4 and Claude Opus on clinical questions.
Atropos Health launched Alexandria — a precision Real-World Evidence library with 33 million pRWE artifacts at launch, targeting 2 billion by end of 2026. On 5,000+ real clinician questions, it outperformed GPT-5.4, Claude 4.6 Opus, Llama 4, and Gemini 3.1 Pro by 2-3x. The distribution play is the real story: “First Edition” partnerships with Meta, Microsoft, Heidi Health, Vim, Avo, and others give Alexandria workflow reach to roughly one-third of U.S. physicians and half of major health systems.
😤 Haters
“Real-world evidence libraries are not new. UpToDate, DynaMed, and ClinicalKey have existed for decades.” The evidence format is new. These aren’t curated editorial summaries — they’re machine-generated pRWE artifacts from claims and EHR data. The 2-3x performance claim over foundation models on clinical questions is bold and needs independent validation, but if it holds, it means domain-specific evidence retrieval still beats general-purpose LLMs on clinical accuracy. That matters for every builder deciding between “fine-tune a foundation model” and “build a retrieval layer.”
“Meta and Microsoft as distribution partners sounds impressive but means nothing for clinical adoption.” It means the evidence layer is going to show up inside the ambient scribes and clinical copilots that clinicians are already using. That’s not a search bar — that’s embedded CDS. Whether clinicians trust it is a different question, but the distribution problem is solved.
💡 80/20: If you’re building clinical AI and your evidence grounding strategy is “prompt the foundation model and hope it’s right,” Alexandria just raised the bar. The builder question is: do you build your own retrieval layer, license Atropos, or accept the hallucination risk? For most small teams, licensing a purpose-built evidence layer will be cheaper and more defensible than building one.
⚡ From the Wire
“Healthcare implemented ambient AI backwards.” Angel Mena, MD (CMO of Symplr) said it plainly on This Week Health this week: health systems layered AI onto broken processes without fixing them first. The conversation covers ambient documentation, quality metrics, and the credentialing chaos hiding inside every health system. For builders: if you’re automating a workflow, the first question is whether the workflow itself is broken. Ambient AI on a broken credentialing process doesn’t produce better credentialing — it produces faster bad credentialing.