Startup Ideas · 13 min read

YC RFS Healthcare — Specific Problems YC Wants Solved

Short answer

Healthcare has appeared in every YC Request for Startups edition since 2024, making it one of the most consistently prioritized sectors in YC's current investment thesis. Unlike some RFS categories that describe a broad technology direction, YC's healthcare RFS is unusually specific — naming particular workflow failures, particular cost drivers, and particular user experiences that YC partners believe are ready to be disrupted. This specificity is itself a signal: it means partners have done the research, have talked to companies in these spaces, and are ready to fund the right team.

The Core YC Healthcare Thesis

This page breaks down every specific healthcare problem YC has called for across its 2025 RFS editions, what the fundable solution looks like for each, and how healthcare founders should position their applications.

YC's healthcare thesis has evolved from "technology-enabled care" (where YC funded care delivery companies like Forward Health, Cerebral, and Carbon Health) to "AI that fixes healthcare's structural inefficiencies." The shift reflects two things: the maturation of AI capabilities that make previously impossible workflow automation now possible, and a growing recognition that healthcare's cost problem is primarily an administrative and coordination problem rather than a clinical one.

The specific number YC partners have cited: approximately 30% of US healthcare spending goes to administrative costs — billing, prior authorization, documentation, compliance, and coordination — not to actual care. This administrative burden is what the current YC healthcare RFS is primarily aimed at.

The Answer Layer: Specific Healthcare Problems YC Wants Solved

Clinical Documentation and the Ambient AI Scribe

The most consistently cited specific problem across multiple 2025 RFS editions: physicians spend 2+ hours per day on documentation — electronic health record entry, clinical note writing, and after-visit documentation — for every hour they spend with patients. This documentation burden is a leading cause of clinician burnout and a direct driver of reduced patient access (a physician spending 2 hours on documentation has proportionally less time for patient visits).

What YC wants: AI that listens to clinical conversations (with patient consent), understands medical context, and automatically generates accurate, structured clinical notes — reducing documentation time from hours to minutes. YC has already funded companies in this space (Abridge, Nabla, Ambience Healthcare) but considers the problem far from fully solved, particularly outside large hospital systems.

Specific gaps YC has called out:

  • Ambient documentation for specialties outside primary care (emergency medicine, surgery, mental health, home care)
  • Ambient documentation that integrates natively with all major EHR platforms rather than requiring a parallel workflow
  • Documentation AI for non-English-speaking patient populations

Prior Authorization Automation

Prior authorization — the process by which insurers require clinicians to request approval before ordering specific tests, medications, or procedures — is described by YC as one of the most wasteful and clinically harmful administrative processes in American healthcare. The numbers: physicians report spending an average of 13 hours per week on prior authorization; 94% of physicians report that prior auth delays or denials have harmed patients.

What YC wants: AI that automates the prior authorization process end-to-end — pulling relevant clinical evidence from the patient record, matching it to the insurer's specific coverage criteria, submitting the request, and tracking the response — without requiring physician time for routine authorizations.

Specific gaps YC has called out:

  • Real-time prior auth (pre-service determination before the patient encounter) rather than retrospective submission
  • Prior auth AI that works across all payer types (commercial, Medicare Advantage, Medicaid) and their different criteria systems
  • Appeals automation for denied authorizations

Medical Coding and Revenue Cycle Automation

Translating clinical encounters into the billing codes (ICD-10, CPT, HCPCS) that insurers use for reimbursement is a skilled, time-intensive task performed by specialized medical coders. Coding errors cost healthcare providers an estimated $125B per year in denied or underpaid claims, while over-coding creates compliance exposure.

What YC wants: AI that reads clinical documentation and accurately generates complete, defensible medical codes — reducing the need for large medical coding teams and improving the accuracy and completeness of coding without increasing compliance risk.

Specific gaps:

  • Coding AI for complex specialties (surgery, oncology, cardiology) where code selection requires deep clinical judgment
  • Audit trail and explainability for AI-generated codes that satisfies compliance requirements
  • Real-time coding feedback for clinicians during documentation (rather than retrospective correction)

Healthcare Revenue Cycle Management

Beyond coding, the broader revenue cycle — claims submission, denial management, payment posting, patient billing, and collections — remains heavily manual at most health systems. Denial rates for initial claims run 5-10% at many providers, and working those denials requires significant administrative staff.

What YC wants: AI that automates the full revenue cycle workflow — from claims scrubbing before submission through denial appeal to final payment reconciliation — reducing staff requirements and improving net collection rates.

Patient Communication and Engagement

The patient experience outside clinical encounters — appointment scheduling, care instructions, medication reminders, test result communication, and follow-up coordination — is largely handled through systems designed for manual operation (phone trees, generic patient portals) that produce poor patient engagement and significant staff burden.

What YC wants: AI-powered patient communication that is conversational, personalized, and proactive — reducing the administrative burden on front desk and care coordination staff while improving patient adherence and satisfaction. This category has overlap with the Voice AI RFS category: YC specifically wants voice AI that can handle high-volume patient communication workflows (appointment reminders, pre-visit instructions, post-discharge follow-up) without human involvement for routine interactions.

Diagnostic AI for High-Volume, High-Error-Rate Conditions

YC has called for AI that improves diagnostic accuracy in conditions where diagnostic error rates are high, the patient population is large, and the consequences of missed diagnosis are severe. Specific conditions that meet these criteria and have been discussed in YC partner commentary:

  • Sepsis early warning: Sepsis is the leading cause of hospital deaths and is frequently missed until late stages; AI pattern recognition across vital signs and lab values can identify patients hours before clinical deterioration
  • Diabetic retinopathy screening: A preventable cause of blindness with a large at-risk population (all diabetic patients) and a screening workflow that is scalable with AI image analysis
  • Skin condition triage: First-line dermatology screening at primary care or consumer level
  • Mental health screening: Scalable identification of patients at risk for depression, anxiety, or suicidal ideation through structured screening in primary care settings

The Data Layer: YC's Healthcare Portfolio as Signals

CompanyHealthcare ProblemBatchStatus
AbridgeClinical documentation / ambient AI scribeW23$150M+ raised, major health system adoption
Ambience HealthcareAmbient clinical documentationW23$70M+ raised
NablaAI copilot for cliniciansS24Growing European and US adoption
AnteriorClinical decision support / prior authW25$20M raised
TennrHealthcare intake automationS24Active, growing
Hippocratic AIHealthcare AI staffing / patient communicationW24$53M raised
Thoughtful AIHealthcare revenue cycle automationS24Active, enterprise contracts
InfinitusAI for healthcare phone callsS23Active, significant health system adoption

The pattern: companies addressing the administrative burden (documentation, prior auth, revenue cycle) raised larger rounds faster than companies addressing clinical decision support or diagnostic AI, reflecting the more immediate ROI and shorter enterprise sales cycle for administrative automation.

The Context Layer: What Makes a Fundable YC Healthcare Application

Specificity of the workflow problem

The most fundable healthcare applications in YC's portfolio describe a specific workflow failure — not "healthcare is inefficient" but "emergency physicians spend 47 minutes per shift on documentation that our product reduces to 8 minutes." The more specific the workflow, the user, and the measurable outcome, the more credible the application.

Evidence of clinical validity

Healthcare enterprise buyers require evidence that AI tools are accurate and safe before deploying them clinically. The most fundable early-stage healthcare applications have either a pilot with a health system that has produced outcome data, or a study design that will produce outcome data within a defined timeline. Applications that describe the AI product without addressing accuracy or clinical validation leave a critical question unanswered.

Regulatory pathway clarity

Many healthcare AI products require FDA clearance (particularly diagnostic AI) or at minimum a legal analysis of whether they qualify as medical devices. YC-funded healthcare companies address the regulatory pathway explicitly — either confirming that their product does not require FDA clearance and explaining why, or describing their 510(k) or De Novo pathway if it does.

HIPAA and enterprise security posture

Healthcare enterprise buyers will not pilot any product that cannot demonstrate HIPAA compliance and a credible security posture. The most fundable healthcare applications address this directly in the application or describe a concrete plan to achieve SOC 2 Type II and BAA signing capability before enterprise pilots begin.

Keep reading

More on Startup Ideas

Go deeper

Want the full data behind this answer?

Our YC database tracks 5,000+ companies, every batch, with application patterns, founder backgrounds, and pivot stories — the raw material we built this answer on.

FAQ

Frequently asked questions

What healthcare problems is YC most focused on funding in 2025 and beyond?
The highest priority healthcare problems in YC's 2025 RFS are: clinical documentation automation (reducing physician time spent on EHR note writing), prior authorization automation (removing the administrative burden of insurance pre-approval workflows), medical coding and revenue cycle automation, patient communication and engagement, and diagnostic AI for specific high-volume conditions. These are consistently cited across multiple RFS editions, signaling sustained YC conviction rather than one-off interest.
Does YC fund healthcare companies that require FDA clearance?
Yes, but the bar is higher and the timeline expectations need to be clearly articulated. YC has funded companies building diagnostics, digital therapeutics, and medical devices that require FDA clearance. What partners want to see is a clear regulatory pathway analysis — which FDA clearance pathway applies (510(k), De Novo, or PMA), what predicate devices exist, and what the expected timeline is. Companies that describe a product that may require FDA clearance without addressing the regulatory pathway leave a significant question unanswered.
What is the difference between healthcare AI that YC will fund versus what they won't?
The clearest distinction is between AI that addresses a specific, measurable workflow problem with a defined customer who has expressed urgency (fundable) versus AI that describes general healthcare improvement without a specific workflow, user, or outcome (not fundable). YC also distinguishes between AI products with a credible accuracy and safety validation story (fundable) versus products that describe AI capabilities without addressing how accuracy is measured or maintained (not fundable). The administrative burden category — documentation, prior auth, coding, revenue cycle — is more reliably fundable than general-purpose clinical AI because the ROI is measurable and the sales cycle is shorter.
How important is HIPAA compliance at YC application stage for healthcare startups?
Partners do not expect full SOC 2 Type II certification at application stage for early-stage companies, but they do expect a clear plan. The minimum expectation: founders should know what PHI (Protected Health Information) their product handles, should understand their HIPAA obligations, and should have a concrete plan for BAA (Business Associate Agreement) capability before their first enterprise pilot. Founders who describe a healthcare product handling PHI without any mention of HIPAA compliance signal that they have not researched the regulatory environment.
What does YC mean by "ambient AI scribe" in the healthcare RFS?
An ambient AI scribe is a product that listens to a clinical conversation between a physician and patient (with consent), understands the clinical content, and automatically generates a structured clinical note in the physician's EHR — without the physician having to type, dictate, or otherwise manually document the encounter. The "ambient" modifier means the documentation happens in the background during the encounter rather than as a separate step after it. YC has funded multiple companies in this space (Abridge, Ambience Healthcare, Nabla) but considers the problem unsolved for many specialties, languages, and healthcare settings.
Is the healthcare revenue cycle a large enough opportunity for a YC-scale company?
Yes. US healthcare revenue cycle management represents an estimated $250B+ market, with administrative costs consuming approximately 30 cents of every healthcare dollar. Even capturing a small fraction of the administrative automation opportunity represents a large business. YC has funded companies in this space (Thoughtful AI, Waystar-adjacent tools) and considers it a genuine large-market opportunity — not a niche. The specific revenue cycle problems that are most fundable at early stage are those with the shortest enterprise sales cycle: typically coding automation and denial management, where ROI is directly measurable in claims revenue.
How should an Indian founder approach the YC healthcare RFS given that Indian healthcare is structurally different from US healthcare?
Indian founders have two valid paths. First, build for the Indian healthcare market specifically — describing the specific Indian workflow problem (which may be acute differently than in the US), the Indian market size, and the Indian-specific regulatory environment. Second, build a product initially for the Indian market that is explicitly designed for eventual US or global expansion — demonstrating why Indian market validation is a credible proxy for US product-market fit. What does not work is describing a US healthcare workflow problem without any Indian market connection — if you have no India-specific insight and no US healthcare relationships, the founder-problem fit question is unresolved.
What YC-funded healthcare companies should founders study before applying?
Abridge (clinical documentation) is the clearest model for how YC evaluates healthcare AI: specific workflow (physician note-writing), specific user (physicians), measurable outcome (time saved and note quality), and a clear path to enterprise health system adoption. Anterior (clinical decision support) shows the prior authorization workflow in detail. Hippocratic AI shows how to frame AI for patient communication. Thoughtful AI shows the revenue cycle automation positioning. Studying these applications — particularly the specific metrics they cited at application stage — calibrates what a credible healthcare AI application looks like in YC's evaluation framework.
What metrics do YC healthcare applications need to show?
At minimum: a specific workflow outcome (time saved, accuracy improvement, cost reduction), evidence of clinical validation or a plan to obtain it, a paying pilot customer or a letter of intent from a credible healthcare institution, and some evidence of HIPAA compliance readiness. The strongest healthcare applications show a combination of: pilot data from a real health system (even 1-3 physicians), measurable outcome data (documentation time reduced from X to Y minutes), and enterprise LOIs demonstrating commercial interest. Pre-revenue applications in healthcare are fundable with a strong founder-problem fit story and a credible validation plan.
How long does it typically take to get a healthcare AI product into clinical use?
The timeline varies significantly by product category. Ambient documentation tools that do not touch the diagnostic or treatment decision have the shortest enterprise adoption timeline — some companies have gone from initial pilot to signed enterprise contract in 3-6 months. Prior authorization automation has a medium timeline of 6-12 months depending on EHR integration complexity. Diagnostic AI requiring FDA clearance has the longest timeline — 12-36 months from product completion to clearance, depending on the pathway and predicate availability. Founders should design their go-to-market for the timeline appropriate to their specific product category.
What is the most common reason healthcare YC applications are rejected?
Not having a specific enough workflow problem. The most common rejection pattern in healthcare is an application that describes the general problem (healthcare is expensive, clinicians are burned out, administrative burden is high) without identifying a specific workflow, a specific user, and a specific measurable outcome that the product addresses. The second most common rejection reason is not addressing the regulatory pathway — specifically for diagnostic products that may require FDA clearance, leaving this question unanswered raises a flag that the founders may not understand the regulatory environment they are building in.
What is the relationship between the healthcare AI RFS and the broader YC full-stack AI company thesis?
They are complementary. YC's full-stack AI company thesis — building AI-native companies that deliver services rather than software — applies directly to healthcare. The healthcare full-stack AI opportunity is in replacing the outsourced administrative services that hospitals and health systems currently purchase from revenue cycle management companies, prior authorization service companies, and medical coding vendors. A full-stack AI company that takes over the prior authorization workflow for a health system is not just a software product — it is a service replacement, with stronger unit economics and higher switching costs than a SaaS tool.

An independent resource · Not affiliated with Y Combinator · Last updated 2026-08-04