Evaluating Ambient Clinical Scribes in India: The Need for Multilingual Real-World Clinical Conversation Data
Siddharth D Jaiswal, Krithi Shailya, Ashish Makani, Suvrankar Datta, Sunayana Sitaram, Mohit Jain
原文摘要
Ambient clinical scribes (ACS) are being rapidly deployed at scale across Global South healthcare settings to reduce clinicians' documentation time, especially in overburdened environments such as India. These ACS are primarily developed or distilled from models built and validated on Global North speech, languages and consultation styles. Indian clinical encounters are brief, triadic, multilingual, code-mixed with low-resource languages, and conducted in highly resource-constrained, noisy settings -- increasing the likelihood of ASR and note-generation errors manyfold. We argue for a standardized evaluation infrastructure to assess whether these systems are safe, reliable, and well-suited to the Indian healthcare setting. We substantiate our claims through a mixed-methods study -- a systematic survey of publicly available patient-clinician conversational datasets, a quantitative comparison of some simulated datasets against conversational and cultural markers drawn from the Indian clinical-communication literature, and semi-structured interviews with four organizations building and deploying ACS in India. Our survey shows that there are no large-scale, publicly available, real-world benchmarks for ACS in India, with existing datasets being overwhelmingly synthetic or simulated. We note that amongst the available simulated datasets that we compare, the Global North datasets diverge significantly from the expected conversational and cultural structures of their Indian encounters. Finally, our interviews reveal that deploying organizations have each built proprietary, incomparable evaluation pipelines, creating a fragmented ecosystem with no independent and reliable basis for procurement. We call for the development of a publicly shared, real-world, multilingual benchmark for ACS evaluation and outline the properties and policies such a benchmark would require.
cs.CY · cs.HC