Government College of Engineering Kannur

Department of Computer Science and Engineering

CSD334: Mini-Project
Project Proposal

Proposal Prepared By
Sl No. KTU Reg No. Name of Student Signature of Student
1 KNR22CS013 Anirudhan P V
2 KNR22CS016 Anuvinda K
3 KNR22CS036 Isha Thahaniya T
4 KNR22CS051 Rinsha K K

1. Project Title : GlucoTrack

2. Problem Statement
Many diabetic patients and healthcare professionals rely on manual tracking methods, including physical
lab reports and logs, to monitor blood glucose levels which can be cumbersome, error-prone, and inefficient.
Healthcare providers do not have an easy way to track the prevalence of diabetes across districts or regions
within Kerala, which hinders public health planning and interventions. Additionally,existing systems are
typically disconnected, with no easy way for patients to upload their lab reports and for the system to
automatically calculate and track glucose levels in real-time.
Our project aims to develop a web application that allows individuals to upload their lab reports, calculate
glucose levels automatically, and track their diabetes status over time. The system will also provide a district-
wise report of diabetes prevalence, allowing healthcare providers and public health authorities to assess the
scope of the issue across Kerala. By generating this data, the system aims to improve the management of
diabetes at both an individual and community level.
3. Solution approach
Our proposed web application will offer a user-friendly interface for patients to easily upload their lab
reports, track their health progress, and access detailed analytics on their diabetic condition. Additionally,
healthcare providers will be able to manage patient data, monitor health trends, and generate district-wise
diabetic reports.
(a) User Authentication and Access Control
ˆ Patient Role: Patients can upload their own lab reports and view their health history.
(b) Patient Registration and Profile Management
ˆ The system will allow patients to create and manage profiles, including their basic demographic
information (name, age, gender, address, etc.).
ˆ Patients can specify their district or area to map their health data to the correct region.
(c) Lab Report Upload
ˆ Patients or healthcare providers can upload scanned copies of lab reports.
ˆ The system will support standard formats (PDF, JPEG, PNG) for easy upload.OCR (Optical Char-
acter Recognition) can be used to extract structured data from scanned reports, such as glucose
levels.
(d) Data Extraction and Validation
ˆ OCR & NLP: Extract key medical data from the uploaded lab reports using OCR and Natural
Language Processing (NLP) algorithms.
(e) Data Analysis and Aggregation

1
 ˆ Individual Patient Data: The system will keep track of each patient’s health metrics, noting trends
such as blood sugar levels.
ˆ District-Wise Aggregation: The system will aggregate patient data by district and generate key
statistics like: ¿Total diabetic patients in the district
(f) District-Wise Diabetic Report Generation
ˆ Interactive Dashboard: A dashboard that provides real-time updates of health statistics at the
district level.
ˆ Metrics: Total diabetic patients
(g) Alerts & Notifications
ˆ Send notifications to healthcare providers and patients about abnormal lab results or changes in
health metrics (e.g., a sudden spike in blood glucose).
ˆ Alerts for districts with rising numbers of uncontrolled diabetic cases, so that authorities can take
preventive measures.
(h) Security and Privacy
ˆ Data Encryption: All patient data will be encrypted to maintain privacy.
ˆ Access Control: Different levels of access (admin, healthcare provider, patient) to ensure sensitive
data is only visible to authorized users.
4. Does any other solution already exist for the stated problem? If yes give details.
ˆ Yes, there are existing solutions for tracking and managing diabetes, but they often suffer from various
limitations.
(a) National Diabetes Registries
– Limitations
* Track national/regional prevalence but lack district-level insights and real-time data.
(b) Mobile Health Apps
– Limitations
* Focus on personal diabetes management, not **district-level data aggregation.
A centralized web application can address these limitations effectively

5. In what way is your proposed solution better than the existing solution(s)?
Our proposed solution for glucotrack offers several advantages over existing methods.
(a) District-Level Insights
ˆ Provides granular, district-specific data for targeted interventions.
ˆ Existing solutions lack detailed local insights and often report at a regional or national level.
(b) Accessibility
ˆ Offers a user-friendly, web-based dashboard for stakeholders at all levels
ˆ Existing systems may have limited access for various stakeholders..
(c) Scalability and Adaptability
ˆ Easily scalable to additional districts and adaptable to changing health needs.
ˆ Existing systems may not be flexible or scalable without significant resource investment.
(d) Efficiency
ˆ Streamlined reporting and centralized management reduce time and effort for users and administra-
tors.
ˆ Quicker responses

6. List out the stakeholders of the proposed project.

2
 (a) Users
ˆ Individuals who uploads lab reports.
ˆ Interact directly with the application.
ˆ Patients can access their personal health dashboard showing trends over time (e.g., blood glucose
levels).
(b) Administrators
ˆ Responsible for managing the application.
ˆ Moderate content and ensure smooth operation.
ˆ Handle user inquiries and maintain system integrity.
7. What will be the impact of this project work on society directly or indirectly?
The impact of a glucotrack website on society can be significant, both directly and indirectly.
(a) Direct Impact
ˆ Improved Health Outcomes : The website Enables targeted interventions for better diabetes
management and facilitates early detection and prevention of diabetes-related complications.
ˆ Convenience : Users can easily access their lab report and know their status of diabetes.
ˆ Better Resource Allocation : Identifies areas needing improved healthcare infrastructure
(b) Indirect Impact
ˆ Long-Term Public Health Improvements : Reduces healthcare burden through effective pre-
vention and management and promotes health equity by targeting underserved areas.
ˆ Economic Benefits : Leads to cost savings in healthcare by reducing complications and contributes
to increased workforce productivity through better health.
ˆ Informed Policy and Decision-Making : Provides data-driven insights for evidence-based poli-
cies and guides healthcare planning at the district and national levels.
8. What technologies do you plan to use for the front-end and back-end?
(a) Front-end (Client-side) :
ˆ React.js : A JavaScript library for building user interfaces. It allows developers to create reusable
UI components and manage the state of the application efficiently
(b) Back-end (Server-side) :
ˆ Node.js : A JavaScript runtime environment that allows developers to run JavaScript code on the
server-side. It provides an event-driven architecture that is well-suited for building scalable and
high-performance server applications.
ˆ Express.js : A web application framework for Node.js. It provides a robust set of features for
building web servers and APIs, including middleware support, routing, and HTTP utilities
(c) Database :
ˆ MongoDB : A NoSQL database that stores data in a flexible, JSON-like format. It is schema-less,
allowing developers to store and retrieve data without a predefined schema. MongoDB is commonly
used in MERN stack applications due to its flexibility and scalability.
Together, these technologies form the MERN stack, which provides a comprehensive solution for
building our web applications with a JavaScript-based technology stack

Proposal Approved By
Name of Guide Signature of Guide Date of Approval
Sahana KI