AI-Augmented Patient Care: Bangalore Baptist Hospital

BBH carries a profile that makes a generic hospital deployment insufficient. Its Hebbal main campus and two satellite clinics handle 440,000+ OPD visits annually, with online appointment booking currently disabled and patients directed to call instead, generating call volume the front desk cannot fully absorb. Its 50-bed hospice at Devanahalli and five home-care teams cover four rural taluks on weekdays, but evenings and weekends create gaps in caregiver support. Its Community Health Division screens 35,000 villagers annually across 50 villages, but post-camp referrals are mostly unacted-upon because there is no systematic mechanism to call patients back. Across this footprint, voice calls in Kannada, Telugu, and English reach patients that SMS portals never will.

Kathan sits underneath BBH's existing workflows rather than around them. The Context Engine retrieves each patient's profile (language, treating doctor, campus, palliative or chronic disease enrolment, no-show or referral history) and loads it into the agent before the first ring. Every call references the specific procedure, camp, or care plan attended, in the patient's own language. Critical responses route to the right human in real time: an emergency keyword to the doctor on call, a caregiver crisis to the palliative nurse on call, an unacted critical referral to the Community Health Division coordinator.

Seven use cases were scoped, each addressing a distinct communication gap inside BBH. They span outpatient operations, inpatient recovery, the flagship palliative programme, chronic disease management, lab reporting, the Community Health Division, and patient experience.

Patient Feedback is the fastest path to a credible signal (2 to 3 weeks to pilot) because it leans on Kathan's proven NPS engine. Appointment Management follows immediately for direct operational impact (4 to 6 weeks). CHD Outreach Callbacks (4 to 6 weeks) stand apart from the main campus workflows and serve as a low-risk first test of Kannada-language capability in a rural context. Post-Discharge Check-Ins, Palliative Care Support, and Chronic Disease Follow-Up share a common HIMS clinical data bridge as their dependency and can deploy in parallel once that integration is stable (6 to 8 weeks each). Test Report Notifications has the deepest integration scope (HIMS lab webhook plus identity verification plus secure PDF delivery) and rolls out last (8 to 10 weeks).