How ridhibrata-das/ai-based-healthcare-monitoring-system-using-iot works
Project Type and Purpose
• This is a full-stack IoT + mobile + ML system for healthcare monitoring and assistance.
• Key parts:
• Smart Band (IoT device) that gathers vitals via sensors and pushes them to a database.
• Mobile Application (Android, Java) serving two portals (patient & doctor), displaying vitals, history, scheduling, chat.
• Chatbot Service (BioGPT-PubMedQA Prefix-Tuned) for medical Q&A, deployed on Hugging Face and consumed via REST API.
• Backend API layer (PHP + MySQL) that exposes endpoints for authentication, CRUD on vitals, symptoms, schedules, chat logs.
• Offline ML-fine-tuning pipeline (Python, PyTorch, PEFT, LoRA) producing the deployed model.
Major Components
• Smart Band Hardware
• Sensors: Max30100, LM35, BMP180, TFT screen
• Microcontroller: Arduino Nano + ESP8266 Wi-Fi
• Firmware: .ino files, Proteus simulation
• Backend Server
• PHP scripts (conn.php, login.php, add.php, get.php, etc.)
• MySQL Database (Database.sql)
• Mobile Application
• Android Studio project (Java, XML layouts, Gradle)
• Architecture: MVVM (LiveData, ViewModel)
• Networking: OkHttp, Volley
• UI modules: sign/login, doctor portal, patient portal, chat, scheduling, history, settings
• Chatbot Service
• Hosted BioGPT-Finetuned model on Hugging Face Inference API
• REST endpoint with authorization header
• ML Fine-Tuning Pipeline (offline)
• Jupyter Notebook (.ipynb) for prefix tuning on PubMedQA dataset
• PyTorch + Transformers + PEFT + LoRA
• TPU execution, produces final model artifact
Relationships & Data Flows
• Smart Band → (HTTPS/MQTT) → PHP API → MySQL → reads/writes vitals
• Mobile App
• Fetches vitals, symptoms, schedules via PHP API → MySQL
• Sends new symptoms, schedule requests → PHP API
• Calls Hugging Face Chatbot API → receives generated responses
• Doctor & Patient portals are two client-side modules interacting with the same backend & chatbot API.
• Offline ML pipeline is decoupled; its output (model) is published to HF and consumed by the mobile app at runtime.
Architectural Patterns & Design Principles
• Client-Server: mobile app as client, PHP server as monolith.
• MVVM on Android: separation of UI, business logic, data via ViewModel & LiveData.
• Sensor-to-DB ingestion: IoT edge device pushing metrics in real time.
• External Service Integration: Hugging Face API as third-party ML microservice.
• Modularization: separate PHP scripts per resource; separate Activity/Adapter classes per feature.
Essentials Checklist
• Callouts for major frameworks/technologies: Arduino IDE, Android Studio, Volley/OkHttp, PHP, MySQL, PyTorch, Transformers