A Synopsis

on

“The Health Diagnosis Chatbot for Symptom Prediction”

Submitted in partial fulfillment of the requirements for the award of the Degree of

Bachelor of Technology

of

Poornima University, Jaipur

Session: 2025-2026

Submitted By:

Bhanu Shakya [11513]

Archi Porwal [12756]

Avinash Chauhan [11032]

Aruna Subba [12240]

IV Year,Computer Engineering

Submitted to: Department of Computer Science & Engineering

Faculty of Computer Science & Engineering,

Poornima University Ramchandrapura, Sitapura Ext., Jaipur,
Rajasthan
[Link]
The rapid growth of digital healthcare solutions has increased the need for intelligent systems that can
provide quick and reliable medical guidance. This project presents an AI-powered Healthcare Chatbot
designed to assist users by answering basic health-related queries, providing symptom-based guidance,
and maintaining conversation history for personalized interaction.
The system is developed as a full-stack web application, consisting of a frontend built using React and
a backend developed with FastAPI. The backend handles user authentication, chat processing, and data
storage using MongoDB, while secure access is ensured through JWT-based authentication. The
chatbot allows users to register, log in, and interact with the system through a conversational interface.
Previous chat sessions are stored and displayed, making the experience continuous and user-friendly.
The main objective of this project is to reduce the gap between users and basic healthcare information
by providing instant responses, especially for preliminary health concerns. Although the chatbot does
not replace professional medical advice, it serves as a supportive tool for awareness and guidance. This
system demonstrates how artificial intelligence and modern web technologies can be integrated to build
scalable and efficient healthcare support applications.
2. Introduction
With the increasing use of digital platforms in healthcare, there is a growing need for intelligent
systems that can provide quick and accessible medical information. Many individuals face difficulties
in getting immediate guidance for basic health concerns due to time constraints, lack of awareness, or
limited access to medical professionals. The proposed AI-powered Healthcare Chatbot is designed to
address this issue by offering instant, conversational health-related assistance through a web-based
platform. The project falls under the field of Artificial Intelligence and Healthcare Informatics,
focusing on improving user interaction and accessibility to preliminary healthcare information.
The system is developed using modern web technologies, where the frontend is built with React to
provide an interactive user interface, and the backend is implemented using FastAPI with Python to
handle business logic and API services. MongoDB is used as the database to store user information and
chat history, while JWT (JSON Web Token) is applied for secure authentication. The rationale behind
developing this project is to provide users with a reliable, easy-to-use healthcare assistant that can
respond to common health queries anytime and maintain personalized conversation history. This
chatbot does not replace medical professionals but acts as a supportive tool for health awareness and
early guidance, making healthcare information more approachable and efficient.

3. Problem Statement
Access to timely and reliable healthcare information remains a significant challenge for many
individuals. People often experience difficulty in understanding basic health symptoms, deciding when
medical attention is necessary, or obtaining immediate guidance due to limited availability of
healthcare professionals, long waiting times, and geographical constraints. Additionally, existing digital
healthcare platforms often lack personalized interaction and continuity, making it difficult for users to
track previous health-related conversations or concerns.
The problem addressed by this project is the absence of an easily accessible, intelligent, and user-
friendly system that can provide instant preliminary healthcare guidance while maintaining
conversation history in a secure manner. There is a need for a solution that bridges the gap between
users and basic medical information by offering real-time responses, secure user authentication, and a
personalized conversational experience, without replacing professional medical consultation.
4. Objectives & Scope
Objectives
1. To design and develop an AI-powered healthcare chatbot that provides instant responses to basic
health-related queries.
2. To create a secure and user-friendly web application with user authentication and personalized chat
history.
3. To integrate modern web technologies and artificial intelligence to improve accessibility to
preliminary healthcare information.
4. To maintain and store previous conversations to offer a continuous and personalized user
experience.

Scope
1. The system focuses on providing general health guidance and awareness and does not replace
professional medical consultation.
2. The chatbot supports registered users with secure login and stores chat history using a database.
3. The project is limited to web-based access and can be extended in the future to support mobile
platforms, multilingual responses, and advanced medical data integration.

[Link] Review
In recent years, the use of chatbots in the healthcare domain has gained significant attention due to
advancements in artificial intelligence and natural language processing. Several studies and
applications have explored the use of rule-based and AI-driven chatbots to assist users with symptom
checking, appointment scheduling, and basic medical guidance. Early healthcare chatbots were mainly
rule-based systems that relied on predefined questions and answers, which limited their ability to
handle complex or dynamic user queries.
With the development of machine learning and NLP techniques, modern healthcare chatbots have
become more interactive and capable of understanding user intent. Existing platforms such as symptom
checker applications and virtual health assistants provide preliminary medical advice and help users
assess the severity of their conditions. However, many of these systems lack personalization, secure
authentication, and proper storage of conversation history. Some applications also fail to provide a
seamless user experience due to complex interfaces or limited accessibility.
The proposed AI-powered Healthcare Chatbot builds upon these existing systems by integrating a
conversational interface with secure user authentication and chat history management. Unlike
traditional systems, this project emphasizes continuity of interaction and user-friendly design while
ensuring data security. The literature indicates a growing need for intelligent, accessible, and
personalized healthcare assistance systems, which this project aims to address using modern web
technologies and AI-based interaction.

5. Feasibility Study
A feasibility study is conducted to analyze the practicality, necessity, and significance of the proposed
AI-powered Healthcare Chatbot before development. The study evaluates the project from technical,
economic, operational, and time perspectives to ensure that the system can be successfully developed
and deployed using available resources.

Technical Feasibility
The project is technically feasible as it uses widely adopted and well-supported technologies such as
React for the frontend, FastAPI with Python for the backend, and MongoDB for data storage. These
technologies are open-source, scalable, and suitable for building secure web applications. JWT-based
authentication ensures data security, while modern APIs allow smooth communication between
frontend and backend components. The development tools and frameworks required for this project are
readily available and well-documented, making implementation achievable.

Economic Feasibility
The project is economically feasible since it primarily relies on open-source technologies, which
significantly reduces development and deployment costs. No expensive hardware or licensed software
is required. The application can run on standard systems and can be deployed on affordable cloud
platforms. Therefore, the overall cost of development and maintenance remains minimal.

Operational Feasibility
From an operational perspective, the system is designed to be user-friendly and easy to use. Users can
register, log in, and interact with the chatbot through a simple conversational interface. The chatbot
provides instant responses and maintains chat history, enhancing user satisfaction. The system does not
require specialized training for users, making it operationally feasible for individuals with basic
computer or internet knowledge.
Time Feasibility
The project is time-feasible as it follows a modular development approach. Backend and frontend
components can be developed independently and integrated efficiently. Given the defined scope and
available tools, the project can be completed within the allotted academic timeframe.

Need and Significance

The need for this project arises from the growing demand for accessible and instant healthcare
information. Many users require quick guidance for basic health concerns without immediate access to
medical professionals. This project is significant as it provides a supportive healthcare assistant that
improves health awareness, reduces uncertainty, and demonstrates the practical application of artificial
intelligence in the healthcare domain.

6. Modules in Proposed Project

The proposed AI-powered Healthcare Chatbot is designed using a modular architecture. Each module
is responsible for a specific functionality, ensuring better scalability, maintainability, and ease of
integration. The major modules of the system are described below:

1. User Authentication and Authorization Module

This module manages the complete user access lifecycle, including registration, login, and session
management. During registration, user credentials are securely stored in the database. On successful
login, the system generates a JWT (JSON Web Token) which is used to authenticate subsequent
requests. This module ensures that only authorized users can access the chatbot and their personal chat
history, thereby maintaining data confidentiality and security.

2. Chatbot Processing and Response Generation Module

This is the core intelligence module of the project. It receives user health-related queries from the
frontend and processes them on the backend. The module applies AI-based logic and natural language
understanding techniques to interpret the user’s input and generate relevant responses. It ensures real-
time interaction and provides preliminary healthcare guidance while following defined safety and
informational boundaries.
3. Conversation and Chat History Management Module
This module is responsible for storing, organizing, and retrieving chat conversations. Each user
interaction, including timestamps, user messages, and chatbot responses, is saved in the MongoDB
database. The module allows users to view previous conversations through a sidebar, making the
chatbot experience continuous and personalized. It also supports future features such as chat search and
session-based grouping.

4. Backend API and Business Logic Module

The backend API module acts as the central control unit of the system. Built using FastAPI, it handles
incoming requests from the frontend, validates authentication tokens, processes business logic, and
coordinates communication between different modules. This module ensures efficient data flow, error
handling, and secure interaction between the user interface and the database.

5. Database and Data Management Module

This module manages persistent storage of all system data, including user profiles, authentication data,
and chat records. MongoDB is used due to its flexibility and scalability, allowing structured and semi-
structured data to be stored efficiently. The module supports fast data retrieval and ensures consistency,
reliability, and future scalability of the system.

6. Frontend User Interface and Interaction Module

The frontend module provides a responsive and intuitive user interface developed using React. It
includes components for user authentication, chat interaction, and chat history display. This module
ensures smooth communication with the backend through API calls and provides real-time updates to
the user. The user-friendly design enhances accessibility and improves overall user experience.

Overall System Integration

All the modules are integrated using a layered architecture where the frontend communicates with the
backend through RESTful APIs, the backend manages processing and security, and the database
ensures reliable data storage. This modular approach allows easy debugging, future enhancements, and
integration of advanced features such as multilingual support, mobile applications, and advanced AI
models.
[Link] Flow Diagram (DFD)

Level-0 DFD: High-level overview of the system

[Link]-Relationship (ER) Diagram

The Entity–Relationship (ER) Diagram represents the structure of the database used in the AI-powered
Healthcare Chatbot system. It illustrates the entities, their attributes, and the relationships between
them.

Entities and Attributes

1. User
 user_id (Primary Key)
 name
 email
 password
 created_at
2. ChatSession
 session_id (Primary Key)
 user_id (Foreign Key)
 start_time
3. Message
 message_id (Primary Key)
 session_id (Foreign Key)
 sender (User / Chatbot)
 message_text
 timestamp

Relationships
 One User can have many ChatSessions
 One ChatSession can have many Messages
 Each Message belongs to one ChatSession
 Entity Relation (ER) Diagram

[Link] Details

a. Software Requirements
The following software tools, libraries, and frameworks are required for the development and execution
of the AI-powered Healthcare Chatbot:
 Operating System: Windows / Linux / macOS
 Programming Language: Python (for backend), JavaScript (for frontend)
 Backend Framework: FastAPI
 Frontend Framework: React with Vite
 Database: MongoDB
 Authentication: JWT (JSON Web Token)
 API Communication: RESTful APIs
 Development Tools:
o Visual Studio Code (IDE)
 o [Link] & npm (for frontend package management)
o Python Virtual Environment (venv)
 Version Control: Git and GitHub
 Containerization (Optional): Docker

b. Hardware Requirements
The hardware requirements for developing and running the project are minimal and can be met by
standard systems:
 Processor: Intel Core i3 or higher
 RAM: Minimum 8 GB
 Storage: At least 20 GB free disk space
 Internet Connection: Required for development, API access, and deployment
 Peripheral Devices: Keyboard, Mouse, Monitor

c. Platform
 Development Platform:
o Local system using Windows, Linux, or macOS
o Code editor such as Visual Studio Code
 Deployment Platform:
o Localhost for testing
o Cloud platforms (optional): AWS / Render / Railway / Vercel (for frontend)
 Database Platform:
o MongoDB Local Server or MongoDB Atlas (Cloud)
10. Methodology

a. Definition
Methodology refers to the structured and systematic approach adopted for the development of the AI-
powered Healthcare Chatbot. It defines the complete process followed from requirement analysis to
final deployment. This methodology outlines the strategies, development models, tools, and techniques
used to design, implement, test, and evaluate the system in order to achieve the project objectives
efficiently.

b. Purpose
The purpose of using a defined methodology is to ensure that the project is developed in an organized
and controlled manner. It helps in proper planning of tasks, effective utilization of resources, timely
completion of the project, and maintenance of software quality. A systematic methodology also enables
continuous testing, identification of errors at early stages, and smooth integration of various system
components. Additionally, it supports scalability and future enhancement of the healthcare chatbot.

c. Content
Approach
The project follows the Agile Software Development Model, which emphasizes iterative development
and continuous feedback. Instead of developing the entire system at once, the project is divided into
smaller modules such as authentication, chatbot interaction, chat history management, and user
interface design. Each module is developed, tested, and refined in cycles (sprints). This approach
improves flexibility, allows early detection of issues, and ensures that the system meets user
requirements effectively.

Techniques
Several techniques are employed during the development of the project:
 Natural Language Processing (NLP) Techniques: Used to understand and process user
health-related queries in conversational form.
 RESTful API Design: Enables smooth communication between frontend and backend
components.
 JWT-Based Authentication Technique: Ensures secure access and protects user data.
 Database Design and Normalization Techniques: Used to efficiently store and retrieve user
and chat data.
  Modular Programming Technique: Ensures separation of concerns, easier debugging, and
maintainability.

Tools
The following tools and technologies are used throughout the development process:
 Programming Languages: Python (backend), JavaScript (frontend)
 Backend Framework: FastAPI for API creation and business logic handling
 Frontend Framework: React with Vite for building responsive user interfaces
 Database Management System: MongoDB for storing user and chat data
 Version Control System: Git and GitHub for source code management
 API Testing Tool: Postman for testing backend APIs
 Development Environment: Visual Studio Code
 Containerization Tool (Optional): Docker for simplified deployment

Steps (Detailed Project Execution Flow)

1. Requirement Analysis:
Functional and non-functional requirements are identified by analyzing user needs and project
objectives.
2. System Design:
Overall system architecture is designed, including database schema, ER diagram, and Data
Flow Diagrams (DFD).
3. Frontend Design and Development:
User interfaces such as login, registration, chat window, and chat history panel are designed and
implemented using React.
4. Backend Development:
APIs are developed using FastAPI to handle authentication, chatbot requests, and database
operations.
5. AI Chatbot Integration:
AI-based logic is integrated to process user inputs and generate meaningful healthcare-related
responses.
6. Database Implementation:
MongoDB collections are created for storing user details and chat history.
 7. System Integration:
Frontend and backend modules are connected, ensuring smooth data exchange and secure
communication.
8. Testing and Validation:
The system undergoes functional testing, API testing, and security testing to verify correctness
and reliability.
9. Deployment:
The application is deployed on local or cloud platforms for evaluation and demonstration.
10. Evaluation and Maintenance:
System performance is evaluated, and improvements are made based on feedback and testing
results.

11. Proposed Work Flow

The proposed workflow of the AI-powered Healthcare Chatbot project is divided into multiple phases.
Each phase is planned with a specific duration to ensure systematic development and timely completion
of the project.

Proposed Phase and Duration Chart

Duration Start End

Phase Description
(Weeks) Week Week

Phase 1: Requirement Identification of system requirements,

1 Week 1 Week 1
Analysis objectives, and scope

Study of existing healthcare chatbot

Phase 2: Literature Review 1 Week 2 Week 2
systems and related work

Technical, economic, and operational

Phase 3: Feasibility Study 1 Week 3 Week 3
feasibility analysis

System architecture design, DFDs,

Phase 4: Design 2 Week 4 Week 5
ER diagrams, and UI design

Frontend and backend development,

Phase 5: Development 4 Week 6 Week 9
database implementation

Phase 6: Testing Functional testing, integration testing, 2 Week Week

 Duration Start End
Phase Description
(Weeks) Week Week

and bug fixing 10 11

Phase 7: Documentation & Final report preparation and system Week Week
1
Deployment deployment 12 12

Total Project Duration

📌 12 Weeks

Project Schedule (Gantt Chart Description)

The project schedule follows a sequential workflow where each phase depends on the completion of
the previous phase. The Gantt Chart visually represents the timeline of each phase across the project
duration.

Explanation
 Early phases focus on planning and analysis
 Middle phases emphasize design and development
  Final phases ensure testing, documentation, and deployment
 This workflow ensures systematic progress and minimizes project risks

12. Conclusion / Expected Outcome and Benefits to Society

The AI-powered Healthcare Chatbot project aims to provide an efficient, accessible, and user-friendly
platform for delivering preliminary healthcare information. By integrating artificial intelligence with
modern web technologies, the system enables users to receive instant responses to basic health-related
queries while maintaining secure and personalized chat history. The successful implementation of this
project demonstrates the practical application of AI in the healthcare domain and highlights the
effectiveness of full-stack web development in solving real-world problems.

Expected Outcomes
 A fully functional web-based healthcare chatbot capable of handling basic health queries.
 Secure user authentication and personalized interaction through stored chat history.
 Improved accessibility to preliminary healthcare guidance anytime and anywhere.
 A scalable and modular system that can be enhanced with advanced AI models and additional
features in the future.
Benefits to Society
 Provides quick and easy access to healthcare information, especially for users with limited
medical resources.
 Helps in spreading health awareness and reducing uncertainty regarding common symptoms.
 Saves time for both users and healthcare professionals by addressing basic queries digitally.
 Encourages the adoption of technology-driven healthcare solutions, contributing to digital
transformation in the healthcare sector.
[Link] Members

Bhanu Shakya 2022/11513 Agentic AI & Backend Developer

Archi Porwal 2022/12756 Full stack Developer

Aruna Subba Limbu 2022/12240 FrontEnd Developer

Avinash Chauhan 2022/11032

Data Engineer

Mrs. Neha Jain Assistant Professor , Poornima University Signature

14. Bibliography
1. Ian Sommerville, Software Engineering, 10th Edition, Pearson Education, 2016.
2. Pressman, R. S., Software Engineering: A Practitioner’s Approach, 8th Edition, McGraw-Hill
Education, 2015.
3. FastAPI Documentation, FastAPI – Modern, Fast Web Framework for Building APIs with
Python.
Available at: [Link]
4. React Documentation, React – A JavaScript Library for Building User Interfaces.
Available at: [Link]
5. MongoDB Documentation, MongoDB Official Documentation.
Available at: [Link]
6. JWT Introduction, JSON Web Tokens.
Available at: [Link]
7. GitHub Repository, Health Chatbot Project.
Available at: [Link]
8. Research Articles on Healthcare Chatbots and AI-based Conversational Systems from IEEE
Xplore and Google Scholar.
1. Abstract
2. Introduction
The introduction part will include the brief introduction about the project to be developed,
technology used, field of project (if specialized one), any special technical terms about the
project. Rationale: Justification, why needed? (1-2 paragraph)
3. Problem Statement
Clearly articulate the problem or challenge the project aims to address.
4. Objectives & Scope: [3-4]
5. Literature Review:
Describe previous related work and existing projects
6. Feasibility Study: (should not exceed 1 page)
This will describe the very first step of software engineering i.e. feasibility study of the project
that include the feasibility, need and significance of the project
7. Modules in Proposed Project
Break down the project into major functional modules. Describe each module, its purpose, and
its role in the overall project architecture.
8. Data Flow Diagram (DFD)
Provide the DFD to represent the flow of data within the system.
Level-0 DFD: High-level overview of the system.
9. Entity-Relationship (ER) Diagram
Include the ER Diagram to illustrate the database schema and relationships between entities.
10. Technical Details (h/w and s/w requirements) including platform
a. Software Requirements: List software tools, libraries, and frameworks.
b. Hardware Requirements: Specify required hardware specifications.
c. Platform: Mention development and deployment platforms.
11. Methodology
a. Definition:
Methodology refers to the systematic process or approach you will follow to develop the
project. It includes the strategies, techniques, and methods employed to achieve the
project's objectives.
b. Purpose:
It explains how the project will be carried out in terms of planning, execution, and
analysis.
c. Content:
Approach: Agile, Waterfall, or any specific model used.
Techniques: Algorithms, frameworks, or processes.
Tools: Specific software or programming tools utilized in development.
Steps: Sequential description of tasks, e.g., data collection, preprocessing, model
building, testing, etc.
12. Proposed Work Flow
Proposed Phase and Duration Chart
Duration Start End
Phase Description
(Weeks) Week Week
Phase 1: Requirement Analysis
Phase 2: Literature Review
Phase 3: Feasibility Study
Phase 4: Design
Phase 5: Development
Phase 6: Testing
 Phase 7: Documentation &
Deployment

The Schedule of the project (Gantt chart/ PERT chart)

13. Conclusion / Expected outcome and benefits to society
14. Team Members
a. Passport Size Photo
Student-1 Name……Registration No……. Role in Project……..Signature
b. Passport Size Photo
Student-2 Name……Registration No……. Role in Project……..Signature
15. Guide Name……………. Designation…………Signature
16. Bibliography
 Other things to consider include:

 Font: Times Roman font, and 12 point size, text Alignment: Justify
 Use 2.5 cm margins on the left, top, right, and bottom
 The synopsis should be printed on A4 size paper
 Margin Left:1.5, Right:1, Top:1 Bottom:1
 Print diagrams on a light or white background
 Arrange tabular matter clearly
 Use a full stop (.) to indicate the decimal point
 Place the caption for a figure at the bottom of the figure
 Place the caption for a table at the top of the table
 Both Student Name and Page No @ Bottom in footer (except Title Page)
 The synopsis should be brief enough to explain the project's objective and implementation
 The synopsis should include a project timeline (Gantt chart/ PERT chart)
 The synopsis should include the group details, such as the enrollment number, branch/sem,
mobile, and college email ID