← All speakers

Vivek Muppalla is vice president of AI engineering at Hippocratic AI, building clinical voice agents that help healthcare providers reach more patients while preserving safety, responsiveness, and human oversight. His career spans Amazon Photos, computer-vision simulation at Unity, synthetic data at Scale AI, enterprise language models at Cohere, and patient-facing healthcare systems.

At Scale AI, Muppalla became director of synthetic systems, working on training-data availability, privacy, and bias. His announcement about joining Scale connected synthetic data to obstacles slowing practical AI adoption, while acknowledging that generated datasets still require careful human judgment.

He subsequently became Cohere’s director of forward-deployed engineering and coauthored guidance on enterprise generative-AI projects. His work addressed retrieval quality, customized models, multilingual applications, private deployment, and enterprise data governance. He also contributed to the collective Command A technical report and highlighted Japanese enterprise-model development around Takane.

At Hippocratic AI, Muppalla applies these production disciplines to clinical conversations, where misunderstanding a medication, delaying a response, or scheduling the wrong appointment can directly affect patient care. His systems support proactive outreach and escalate concerning symptoms to human clinicians.

  • Enterprise retrieval that reduces operating costs. Muppalla combines embeddings with cross-encoder reranking to select relevant documents before they enter a model’s context. His explanation of enterprise retrieval illustrates how sharper selection improves answer quality, reduces input-token costs, and supports citations and customer-controlled deployment.
  • Polaris safety architecture. Hippocratic AI’s clinical system pairs a central conversational model with approximately 30 specialists covering medications, laboratory results, scheduling, and related tasks. Specialists operate in parallel, intervene selectively, and are supplemented by tool-call verification and escalation pathways to clinicians.
  • Context-aware clinical speech recognition. Patient conversations involve noisy environments, short answers, unfamiliar drug names, and multiple languages. Muppalla’s approach supplements audio with conversation history and clinical context, uses an adapted Whisper component, preserves vocal cues, and applies additional checks to ambiguous single-word responses.
  • Latency as a budget for clinical intelligence. Quantization, speculative decoding, and key-value-cache optimization create capacity for additional specialist reasoning and verification without sacrificing conversational responsiveness. His account of clinical voice-agent engineering emphasizes tail latency, clinician-assisted evaluation, and healthcare-specific failure modes.
  • Empathy as a measurable safety requirement. The HEART benchmark for supportive dialogue assesses qualities including emotional responsiveness, attunement, and appropriate follow-through. Muppalla treats these interpersonal requirements as essential alongside clinical accuracy, speed, and human oversight.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

Hippocratic AI’s clinical voice system combines contextual speech recognition, parallel specialists, and layered verification to fit safer patient conversations into a telephone call’s latency budget.

  • Who gets a proactive healthcare call?
    0:17 ↗
  • A conversation built from clarification
    2:37 ↗
  • Buying time for more intelligence
    5:10 ↗
  • One voice, a constellation behind it
    7:55 ↗
  • Reasoning cannot repair everything the system mishears
    9:27 ↗
  • Parallel specialists, then verification
    13:04 ↗
  • Reducing inference cost without spending quality
    15:01 ↗
  • A small error rate becomes a daily workload
    16:15 ↗
  • Correctness, harm, and willingness to talk
    17:53 ↗
  • Building the team that sustains the stack
    19:27 ↗

Key ideas

Scroll to read ↓

Enterprise AI depends on more than model quality: retrieval, customization, deployment control and operating cost determine whether a useful prototype can become a production system.

  • What does an enterprise need from a model?
    0:29 ↗
  • Evaluate the workload, then design for its constraints
    2:28 ↗
  • RAG citations and multilingual operating cost
    4:58 ↗
  • Finding the right attention paper
    6:30 ↗
  • Putting the pipeline inside the enterprise
    9:32 ↗
  • Partners, private fine-tuning and customer choice
    11:08 ↗
  • When should classification use a specialized model?
    13:27 ↗
  • A larger context window, with retrieval still doing useful work
    15:10 ↗

References