The Tech Stack That Builds
Hospital-Specific AI
From 14-language translation to hospital data training, RAG search, and voice AI. Kind Doctor's proprietary Deep Tech completes a unique AI for every hospital.
3 Core Technologies Behind Hospital-Specific AI
Kind Doctor's technology stack builds a unique AI response infrastructure for each hospital.
Hospital-Specific AI Architecture
Not a generic chatbot. We collect hospital websites, news articles, blogs, YouTube, PDFs, and consultation data — then build a dedicated RAG pipeline through document parsing, medical term normalization, and vector embedding.
Multilingual Information Guidance Engine
Not a translation AI. Hospital-specific RAG + medical-information prompt design + bidirectional voice-text processing helps users worldwide understand each hospital's information in their own language.
Inquiry → Hospital Confirmation → Deposit Flow Assist
It doesn't end with the inquiry response. A state-based workflow engine + event trigger system + country-specific payment modules keep the inquiry flow visible on the hospital's screen so nothing slips through.
RAG PIPELINE
How a hospital-specific LLM is built
From the hospital's own materials to a 14-language guidance response — without mixing data with other hospitals.
Hospital Materials
Document Parsing
Extract from PDF / HTML / video transcripts
Medical Term Normalization
Aligns clinical vocabulary across languages
Vector Embedding
Per-hospital indexed in Qdrant
Hospital RAG Index
Closed by default — no cross-hospital mixing
14-Language Guidance Response
Generated only from approved hospital data
안녕하세요, 어떤 도움이 필요하신가요?
WORKFLOW STATE MACHINE
A state-management engine, not auto-confirmation.
Every state transition is event-based and visible to the operator. The hospital still confirms each step.
Inquiry intake
AI guidance done
Hospital confirmation needed
Deposit requested
Hospital final check
Pre-visit guidance
Inquiry intake
01AI guidance done
02Hospital confirmation needed
03Deposit requested
04Hospital final check
05Pre-visit guidance
06States are organized via events; the hospital reviews and decides.
Integrated Operating Infrastructure
Inquiry, booking, and response data are never siloed. Kind Doctor unifies every flow into a single operating infrastructure.
External Channel Link Management
Distinguishes inquiry routes from each external channel the hospital operates and surfaces the inquiry history on the hospital's operations screen.
Patient Response Auto-Logging
Inquiry session data is auto-logged and visible on the hospital's operations screen. Procedure interest, country, traffic source, and booking-request status are tracked together.
Unified Operations Dashboard
Inquiries by country, response by language, awaiting hospital confirmation, deposit-request status, and consultation handoff status — all in one real-time view.
Country-Specific Payment Module
Supports global pre-payment (visit deposit). Helps patients understand each payment step in their local currency and language.
State-Based Workflow Engine
Inquiry · booking-request · deposit-request · awaiting-hospital-confirmation states are organized via events so operators can scan the flow at a glance.
DATA ISOLATION
Per-hospital data separation
Hospital data layers are stored separately. Patient personal data is never used as AI training data.
Patient personal data is not used as AI training data.
Each hospital's data is isolated from others (Closed by Default).
Public hospital content and patient personal data are stored in separate vaults.
Layer 1
Public hospital content
Layer 2
Staff FAQ
Layer 3
In-house SOP knowledge
Layer 4
Inquiry logs (per hospital)
Layer 5
Patient personal data — isolated, never used for training
HOSPITAL ADMIN VIEW
What the hospital actually sees
Not ad performance or revenue projection. Response, state, language, and country are organized for operations.
No ad conversion, visit-confirmation rate, or revenue projection. Only the response flow is organized.
Kind Doctor is not a public chatbot.
Hospital-specific independent LLM + Hospital-exclusive AI · Multilingual medical information engine · Inquiry-confirmation-deposit state management · Unified external-channel · inquiry · response operating infrastructure One AI per hospital — infrastructure that builds your hospital's own AI.