Hospital Intelligent Triage: Multi-Intent AI
One Agent for location queries and medical consultation. Auto-route by intent, collect patient info, recommend departments and doctors.

Executive Summary
Hospital outpatient lobbies face two high-frequency question types daily: "Where is XX examination/service?" and "What department should I visit for my symptoms?" Traditional solutions involve multiple triage nurses working in shifts, but peak hours still see long queues, low efficiency, and inevitable nurse fatigue.
This article demonstrates how to build an Intelligent Triage Agent using Tencent Cloud ADP, leveraging multi-intent recognition to automatically identify patient needs and route to different workflows:
- Location Query: Directly output location guidance for examination rooms/service windows
- Medical Consultation: Collect age, gender, and symptoms โ Recommend department โ Check if appointment needed โ Recommend on-duty doctors
Key Highlights:
- Multi-intent recognition covering multiple scenario types with one Agent
- Slot-filling mechanism ensuring complete information collection
- Knowledge base maintains weekly schedules for doctor recommendations
1. Scenario Analysis: Two Core Needs at Triage Desks
1.1 Demand Distribution
Analysis of one week's triage records at a hospital outpatient lobby shows patient inquiries mainly fall into two categories:
| Need Type | Percentage | Typical Questions |
|---|---|---|
| Location Queries | ~40% | "Where is the CT room?" "Which floor for blood tests?" "How to get to insurance window?" |
| Medical Consultation | ~30% | "What department for headaches?" "Which doctor for my child's fever?" "Any slots in orthopedics today?" |

1.2 Traditional Pain Points
| Pain Point | Manifestation |
|---|---|
| Repetitive Work | Triage nurses answer countless "Where is XX" questions daily |
| Inaccurate Guidance | High pressure during peak hours leads to occasional errors |
| Difficult Lookup | Nurses struggle to check which doctors are on duty and slot availability |
| Peak Congestion | Severe queuing from 8-10 AM, increasing patient anxiety |
2. Agent Design: Multi-Intent Recognition + Routing
2.1 Overall Architecture
Patient Question
โ
โโโโโโโโโโโโโโโโโโโโโโโ
โ Multi-Intent โ
โ Recognition โ
โโโโโโโโโโโโฌโโโโโโโโโโโ
โ
โโโโโโโโโโโโโโโโโโโโดโโโโโโโโโโโโโโโโโโโ
โ โ
โโโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโ
โ Location โ โ Medical โ
โ Query Flow โ โ Consultation โ
โ Direct Output โ โ Collect Info โ
โโโโโโโโโโโโโโโโโ โโโโโโโโโฌโโโโโโโโ
โ
โโโโโโโโโโโโโโโโโ
โ Recommend โ
โ Department โ
โโโโโโโโโฌโโโโโโโโ
โ
โโโโโโโโโโโโโโโโโ
โ Need โ
โ Appointment? โ
โโโโโโโโโฌโโโโโโโโ
โ
โโโโโโโโโโโโโโโโโ
โ Recommend โ
โ On-Duty Doctorโ
โโโโโโโโโโโโโโโโโ
2.2 Multi-Intent Recognition
The Agent first determines which category the patient's question belongs to:
| Intent Type | Recognition Keywords/Patterns | Processing Flow |
|---|---|---|
| Location Query | "where is" "how to get to" "which floor" "which window" | Directly query and output location info |
| Medical Consultation | Symptom descriptions, "what department" "which doctor" "any slots" | Enter consultation workflow |
Example Dialogues:
Patient: Which floor is the CT room on?
Agent: Based on your query, please go to B1 Floor, Imaging Diagnostic Center, CT Room.
Patient: I've been having headaches lately
Agent: To recommend the right department, please tell me:
1. What is your age?
2. What is your gender?2.3 Medical Consultation Flow Details
When identified as "Medical Consultation" intent, the Agent enters the information collection flow:
Step 1: Collect Basic Information (Slot Filling)
| Required Info | Purpose | Example Question |
|---|---|---|
| Age | Different age groups have different common conditions | "What is your age?" |
| Gender | Some departments are gender-related | "What is your gender?" |
| Symptoms | Core basis for recommendation | "Please describe your main symptoms" |
Step 2: Recommend Department
Based on collected information and preset triage rules, recommend the best-matching department:
Patient: I'm 18, male, my eyes are itchy and I can't see clearly.
Agent: Based on your symptoms, please go to 5th Floor, ENT & Oral Center, Ophthalmology Department for treatment.Step 3: Check Appointment Need
After recommending a department, the Agent proactively asks about appointment needs:
- If patient says yes โ Enter doctor recommendation flow
- If patient says no โ End conversation or ask about other questions
Step 4: Recommend On-Duty Doctors
Query the department's schedule for the day and recommend available doctors:
Agent: Based on your symptoms, today you can register with Dr. Zhang, Chief Physician, at 5th Floor Area A, Ophthalmology Clinic.
3. Building with Tencent Cloud ADP
3.1 Create Agent and Configure Role
Role Configuration (Example):
You are an intelligent triage assistant for a hospital, helping patients with two types of questions:
1. Location queries: Provide specific locations for examination rooms and service windows
2. Medical consultation: Collect patient information and recommend appropriate departments and doctors
Important rules:
- You only provide triage services, no medical diagnosis
- Must collect age, gender, and symptoms before recommending departments3.2 Configure Knowledge Bases
Location Information Knowledge Base (Example):
| Department/Service | Location |
|---|---|
| CT Room | 2F East, Outpatient Building |
| Blood Test Room | 1F West, Outpatient Building |
| Insurance Window | 1F Lobby, Outpatient Building |
| Pharmacy | 1F North, Outpatient Building |
| ... | ... |
Schedule Information Knowledge Base (Example):
| Doctor | Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|---|
| Zhang (Chief) | AM | AM | Off | AM | AM | AM | Off |
| Wang (Attending) | PM | Off | AM | AM | PM | Off | PM |
| Li (Attending) | AM | AM | AM | AM | AM | AM | Off |
| Liu (Resident) | PM | AM | AM | PM | AM | Off | Off |
| ... | ... | ... |
3.4 Configure Workflow
Intent Recognition Node:
- Input: Patient question
- Output: Intent type (Location Query / Medical Consultation)
Location Query Node:
- Input: Query content
- Process: Search location knowledge base
- Output: Location guidance
Medical Consultation Node:
- Input: Patient question
- Process: Slot filling (age, gender, symptoms) โ Triage rule matching โ Department recommendation
- Output: Recommended department + appointment need check
Doctor Recommendation Node:
- Input: Department name
- Process: Search schedule knowledge base
- Output: Today's on-duty doctor recommendation

4. Dialogue Examples
4.1 Location Query Scenario
Patient: Where is the parking lot?
Agent: Based on your query, please go to B2 Floor, Patient Parking Lot.4.2 Medical Consultation Scenario (Complete Flow)
Patient: I've been having stomach pain lately
Agent: Please provide a valid age.
Please specify your gender (male/female).
Patient: 28
Agent: Please specify your gender (male/female).
Patient: Female
Agent: Based on your symptoms, today you should go to 2nd Floor, Internal Medicine Clinic Cluster, Gastroenterology Department for further treatment.
Patient: Which doctor can I register with?
Agent: Based on your symptoms, today you can register with Dr. Zhang, Chief Physician, at 2nd Floor Internal Medicine Clinic Cluster, Gastroenterology Department.5. Compliance & Boundaries
5.1 Strict Red Lines
| Prohibited Action | Explanation |
|---|---|
| Disease Diagnosis | Cannot say "You have XX disease" |
| Treatment Advice | Cannot say "You should take XX medication" |
| Condition Assessment | Cannot say "Your condition is serious/not serious" |
5.2 Emergency Handling
When urgent symptoms are detected, direct to emergency immediately:
Patient: I suddenly have high fever and joint pain
Agent: Please provide a valid age.
Please specify your gender (male/female).
Patient: 19, male
Agent: Based on your symptoms, today you can register with Dr. Zhang, Chief Physician, at 1st Floor Emergency Department.
6. Results
6.1 Core Metrics
| Metric | Target | Actual |
|---|---|---|
| Intent Recognition Accuracy | โฅ90% | 93.5% |
| Department Recommendation Accuracy | โฅ85% | 88.2% |
| Average Response Time | โค3s | 1.8s |
| Patient Satisfaction | โฅ4.0/5.0 | 4.4/5.0 |
6.2 Business Value
| Value Point | Improvement |
|---|---|
| Triage desk queue time | Reduced 50% |
| Nurse repetitive Q&A workload | Reduced 65% |
| Patient department-finding time | From 8 min to 2 min |
| 24/7 service coverage | 80% night consultation resolution |

7. Extension Directions
7.1 Feature Extensions
| Extension | Description |
|---|---|
| Examination Booking | Integrate with booking system for examination appointments |
| Report Query | Integrate with lab system for report interpretation (values only, no diagnosis) |
| Insurance Consultation | Add insurance policy knowledge base |
| Multi-language | Support English, Cantonese, and other languages |
7.2 Multi-Modal Interaction
| Interaction Method | Use Case |
|---|---|
| Touchscreen | Self-service kiosks in outpatient lobby |
| Voice Interaction | Elderly patients, visually impaired |
| Mini-program | Younger patients, advance consultation |

Summary
This article demonstrated how to build a hospital intelligent triage assistant using Tencent Cloud ADP. The core design principles are:
- Multi-Intent Recognition: One Agent covering "Location Query", "Appointment Query", and "Medical Consultation" scenarios
- Slot Filling: Ensure collection of age, gender, and symptoms for medical consultations
- Routing: Location queries output directly; medical consultations follow complete flow
- System Integration: Connect with scheduling system for real-time doctor recommendations
- Compliance First: Strictly distinguish triage service from medical diagnosis
Start now and build your intelligent triage assistant with Tencent Cloud ADP!
โ Start Free Trial

