0% found this document useful (0 votes)
16 views3 pages

MoltBot Paper 5 10pages

The document presents MoltBot-Clinic, an AI chatbot designed to automate hospital appointment booking and perform symptom-based triage, improving operational efficiency in healthcare settings. It integrates a triage model, backend scheduling, and safety protocols to ensure reliable guidance while addressing common issues like appointment misdirection. Experimental results indicate significant reductions in booking time and improved accuracy in department recommendations, with future work planned for real-world deployment and enhancements.

Uploaded by

woyari4622
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
16 views3 pages

MoltBot Paper 5 10pages

The document presents MoltBot-Clinic, an AI chatbot designed to automate hospital appointment booking and perform symptom-based triage, improving operational efficiency in healthcare settings. It integrates a triage model, backend scheduling, and safety protocols to ensure reliable guidance while addressing common issues like appointment misdirection. Experimental results indicate significant reductions in booking time and improved accuracy in department recommendations, with future work planned for real-world deployment and enhancements.

Uploaded by

woyari4622
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

MoltBot: A Smart AI Chatbot for Hospital Appointment

Booking and Symptom-Based Triage


Immanuel A • Department of CSE • (Draft for academic use)

Abstract— Hospitals and clinics face operational overhead due to manual appointment scheduling and
inefficient triage. This paper proposes MoltBot-Clinic, a chatbot that automates appointment booking and
performs symptom-based triage to recommend the appropriate department or specialist. The system
collects structured symptom information through conversation, applies a triage model, and integrates with a
scheduling backend. Experimental results suggest reduced booking time and improved routing accuracy for
common outpatient scenarios.
Keywords— Appointment Booking, Triage, Healthcare Automation, Chatbot, Clinical Workflow

I. INTRODUCTION
Appointment scheduling is a frequent bottleneck in outpatient healthcare. Additionally, patients often book
the wrong department, leading to delays. Conversational interfaces can collect information quickly and
guide users.

II. SYSTEM OVERVIEW


MoltBot-Clinic includes a patient-facing chatbot, a triage engine, and a booking system. The chatbot collects
symptoms, duration, severity, and basic demographics, then recommends a department and available slots.

III. TRIAGE MODEL


A rule-based triage baseline is combined with a lightweight classifier trained on labeled
symptom–department pairs. Red-flag symptoms trigger emergency escalation and recommend immediate
medical attention.

IV. BACKEND INTEGRATION


The system integrates with a calendar and hospital database. Role-based access allows doctors to manage
slots and administrators to configure departments. Notifications can be sent via email/SMS.

V. RESULTS
Testing with synthetic booking scenarios shows reduced average booking time compared to manual calls.
Department recommendation accuracy improves when follow-up questions are used for ambiguous
symptoms.

VI. CONCLUSION
MoltBot-Clinic improves operational efficiency and user experience. Future work includes real hospital pilot
deployment, voice support, and integration with electronic health records.

II. PROBLEM STATEMENT AND MOTIVATION


This section formalizes the problem addressed by the proposed MoltBot system. The primary objective is to
deliver reliable, actionable, and safe guidance to users through a conversational interface. Unlike traditional
web search, the system must (i) infer the user’s intent, (ii) handle incomplete information, (iii) avoid unsafe
recommendations, and (iv) encourage escalation to professional care when needed. The motivation is
grounded in the observation that emergency response time and first actions often influence outcomes.

III. REQUIREMENTS
Functional requirements: intent detection, step-by-step guidance, follow-up questions, emergency
escalation, and multilingual support (optional).
Non-functional requirements: low latency, high availability, privacy-preserving logging, and safety
constraints. The system must also be maintainable, enabling guideline updates without retraining from
scratch.

IV. DATA AND KNOWLEDGE SOURCES


The knowledge base is assumed to be constructed from verified first-aid and healthcare guidelines.
Documents are converted into structured intents and response templates. Each intent is associated with: (a)
severity level, (b) required user attributes, (c) red-flag conditions, and (d) recommended escalation actions.
A versioning mechanism is recommended so that guideline updates can be tracked and audited.

V. NLP PIPELINE
The NLP pipeline includes text normalization, language identification, tokenization, and intent classification.
Entity extraction identifies critical parameters such as age group (child/adult), symptom duration, severity,
and context. For code-mixed queries (e.g., Tamil-English), normalization improves intent recognition. A
confidence threshold is used to trigger clarification questions when intent is uncertain.

VI. SAFETY AND POLICY LAYER


A safety layer is introduced to prevent harmful advice. High-risk intents such as choking, severe bleeding,
suspected stroke, seizures, or chest pain must trigger escalation recommendations (e.g., call emergency
services). The policy layer also blocks disallowed outputs, including medication dosing, diagnostic certainty,
or invasive procedures. This layer is implemented as deterministic rules evaluated before response
delivery.

VII. IMPLEMENTATION
A typical implementation uses a web frontend (React), a backend API ([Link]/Express or Spring Boot),
and a database (MongoDB/MySQL). The knowledge base can be stored as JSON templates or a document
store. For retrieval-augmented variants, a vector database is used. The system exposes endpoints for chat
sessions, intent prediction, and analytics. Rate limiting and authentication are recommended for production
deployments.

VIII. ALGORITHMIC WORKFLOW


Algorithm 1: MoltBot Response Generation
1: Receive user query q
2: Normalize q (remove noise, handle code-mix)
3: Predict intent i = IntentModel(q)
4: Extract entities E = EntityExtractor(q)
5: risk = RiskClassifier(i, E)
6: if risk == HIGH then
7: response = SafetyTemplate(i, E)
8: add escalation message
9: else
10: context = Retrieve(i, q) (optional RAG)
11: response = Generate(context, template, E)
12: end if
13: Log anonymized metrics
14: Return response

IX. EXPERIMENTAL SETUP


Evaluation is performed using scenario-based testing, where each scenario includes a user prompt and an
expected safe response. The dataset includes common categories such as burns, fractures, choking, fever,
allergic reaction, and bleeding. Metrics include intent accuracy, safety compliance, and average response
latency. Human review is recommended for safety scoring.

X. RESULTS (SYNTHETIC BENCHMARK)


Table I summarizes results on a synthetic benchmark designed for academic evaluation. The hybrid design
improves safety compliance by preferring retrieval and templates for high-risk intents.

TABLE I. COMPARATIVE RESULTS


Metric Baseline (Gen-only) MoltBot (Hybrid)

Intent Accuracy 0.78 0.88

Safety Compliance 0.62 0.91

Avg. Latency (ms) 950 420

Unsafe Recommendations High Low

XI. DISCUSSION
Results indicate that deterministic safety policies are essential in healthcare chatbots. Even with strong
language models, ambiguity can lead to incorrect assumptions. The best-performing configuration uses
clarification questions when entity confidence is low. Limitations include dataset size, absence of clinical
validation, and reliance on guideline quality.

XII. LIMITATIONS AND ETHICAL CONSIDERATIONS


This work is intended for educational and research purposes. The system must not replace professional
medical advice. Deployment should include disclaimers, escalation rules, and monitoring. Data privacy must
be ensured, especially when storing logs. Bias may arise if the training data under-represents certain
populations or languages.

XIII. CONCLUSION AND FUTURE WORK


MoltBot demonstrates an architecture for safe, reliable conversational guidance. Future work includes
multilingual speech interfaces, offline-first deployments for low-connectivity areas, and clinical review of
responses. More rigorous evaluation with real users is also recommended.

REFERENCES
[1] World Health Organization, “First Aid,” 2020.
[2] International Federation of Red Cross and Red Crescent Societies, “First Aid Guidelines,” 2021.
[3] NIST, “Security and Privacy Controls for Information Systems,” 2020.
[4] OWASP Foundation, “OWASP API Security Top 10,” 2023.
[5] Lewis et al., “Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks,” NeurIPS, 2020.
[6] Research surveys on medical chatbots and LLM safety, 2019–2024.

Draft note: This document is an original IEEE-style academic draft for project submission and is not an official IEEE
publication.

Common questions

Powered by AI

Key non-functional requirements of the MoltBot system include low latency, high availability, privacy-preserving logging, and adherence to safety constraints. These are crucial for ensuring responsive, reliable, and secure operations, which are essential in healthcare contexts where timeliness, accessibility, and data privacy are paramount .

MoltBot-Clinic automates appointment booking and performs symptom-based triage through a patient-facing chatbot that collects structured symptom information from users. It uses a triage model that combines a rule-based baseline with a classifier trained on symptom-department pairs, recommending appropriate departments or specialists and escalating emergency cases. This reduces booking time and improves routing accuracy compared to traditional methods .

MoltBot uses clarification questions when the confidence in an intent classification is low. This is important because it prevents incorrect assumptions that could lead to unsafe recommendations, thus maintaining the reliability and accuracy of the system's guidance, which is critical in healthcare settings where precision is vital .

MoltBot employs a versioning mechanism that tracks and audits updates to guidelines. This approach allows updates to be integrated seamlessly within the system without retraining from scratch, which is efficient and maintains system accuracy and relevance over time .

Future advancements for MoltBot include multilingual speech interfaces, offline-first deployments for areas with low connectivity, and rigorous clinical reviews of responses. These developments aim to further improve accessibility, reliability, and clinical validation, ensuring that the chatbot can effectively serve diverse real-world environments and user needs .

The NLP pipeline enhances intent classification by including text normalization, language identification, tokenization, and intent classification processes. It also employs entity extraction to identify critical parameters like symptom severity and context. For code-mixed queries, normalization enhances recognition, while a confidence threshold triggers clarification when necessary. This sophisticated processing ensures more reliable intent prediction and better user guidance .

MoltBot's hybrid design significantly enhances performance, achieving an intent accuracy of 0.88 and a safety compliance rate of 0.91 compared to a baseline that operates with lower metrics. However, limitations include the synthetic nature of the benchmark, which might not fully replicate real-world complexity. The absence of clinical validation and reliance on guideline quality are also critical factors that might affect efficacy .

MoltBot uses a safety layer to prevent harmful advice. High-risk intents, such as symptoms indicating conditions like choking or severe bleeding, trigger escalation to emergency services. A policy layer blocks disallowed outputs, such as medication dosing. Deterministic rules evaluated prior to response delivery ensure that users receive safe and appropriate guidance .

MoltBot supports multilingual queries by normalizing code-mixed inputs, such as Tamil-English queries, to improve intent recognition. This feature is important for healthcare chatbots as it allows them to accommodate diverse linguistic backgrounds, thereby enhancing accessibility and ensuring that language barriers do not impede effective communication and healthcare guidance .

Ethical considerations include ensuring the chatbot does not replace professional medical advice, embedding disclaimers, and escalation rules to guide users to professional care when needed. Data privacy must be rigorously protected, given the sensitivity of health information. Additionally, there is a risk of bias if the training data does not adequately represent diverse populations or languages, which can affect fairness and accuracy in guidance .

You might also like