IoT-Based Patient Health Monitoring with Heart Rate and SpO2
IoT-Based Patient Health Monitoring with Heart Rate and SpO2 is a camera and visual-monitoring prototype that can be demonstrated with camera image, video frame, snapshot, or detected motion event. A realistic FYP outcome is a working prototype where the controller or Raspberry Pi captures images and applies simple image processing or event detection, then produces captured evidence, recognition result, alert notification, or dashboard image log. The important proof is repeatable image samples, detection result, timestamp, confidence/condition notes, and event history, not just a device that powers on.
Project Snapshot
Quick Summary
IoT-Based Patient Health Monitoring with Heart Rate and SpO2 is a camera and visual-monitoring prototype idea for students who need a working demo with camera image, video frame, snapshot, or detected motion event. A good version focuses on captured evidence, recognition result, alert notification, or dashboard image log using Camera, ESP32-CAM/Raspberry Pi, OpenCV or dashboard, with testing evidence for lighting, camera angle, dataset examples, false detections, and repeatable demo scenes.
Difficulty
Intermediate
Time Required
4-8 weeks for wiring, coding, dashboard/app integration and repeated testing
Cost
No fixed price. Cost depends on selected controller, sensors, communication modules, casing, dashboard/app features and documentation scope.
Components
MAX30102, ESP32, IoT, Health
How This Project Works
The prototype collects camera image, video frame, snapshot, or detected motion event using the selected modules.
The controller performs the controller or Raspberry Pi captures images and applies simple image processing or event detection.
The result is shown through captured evidence, recognition result, alert notification, or dashboard image log.
Testing records lighting, camera angle, dataset examples, false detections, and repeatable demo scenes so the demo can be explained during viva.
Components
MAX30102
View MAX30102 component guide
ESP32
View ESP32 component guide
IoT
Technology or project feature
Health
Technology or project feature
Build Scope Options
Basic prototype
Core demo using Camera, ESP32-CAM/Raspberry Pi, OpenCV or dashboard, Storage/alert with visible input and output response.
Intermediate prototype
Adds dashboard/database logging, alerts, calibration notes, and cleaner wiring for reliable demonstration.
Advanced prototype
Adds casing, mobile/cloud features, multi-node setup, image processing, maps, or reporting depending on scope.
Expected Demo Outcome
- Shows captured evidence, recognition result, alert notification, or dashboard image log from real or realistic camera image, video frame, snapshot, or detected motion event.
- Stores or displays image samples, detection result, timestamp, confidence/condition notes, and event history as report evidence.
- Demonstrates the main camera and visual-monitoring prototype workflow end to end.
- Includes a clear test scenario for lighting, camera angle, dataset examples, false detections, and repeatable demo scenes.
Accuracy & Limitations
This is realistic for FYP when the scope stays controlled: Limit the first version to one visual task and controlled lighting before adding advanced AI claims.
Prototype reliability depends on correct wiring, stable power supply, and proper module selection.
Sensor readings can vary with placement, calibration, environment, and demo conditions.
IoT demos depend on stable WiFi, hotspot, or internet access unless an offline backup mode is prepared.
Validation & Testing Plan
Run repeated tests under controlled demo conditions and record readings or status changes.
Verify lighting, camera angle, dataset examples, false detections, and repeatable demo scenes before adding extra features.
Capture photos, dashboard screenshots, serial logs, or database entries as testing evidence.
Document sensor/module limits honestly so the report does not overclaim industrial accuracy.
Troubleshooting
If readings are unstable, test the sensor separately before connecting the dashboard or app.
If the module resets, check power supply, common ground, loose jumper wires, and current requirements.
If alerts or cloud updates fail, test WiFi, hotspot, SIM balance, API token, and internet connection early.
If the demo is hard to explain, focus on one repeatable workflow for captured evidence, recognition result, alert notification, or dashboard image log.
Common Mistakes
- Choosing a scope that is too large for the available FYP timeline.
- Limit the first version to one visual task and controlled lighting before adding advanced AI claims.
- Writing objectives that do not match the actual prototype or software demo.
- Preparing no backup demo flow for viva day.
- Using weak power supply, loose jumper wires, or unprotected sensors during demonstration.
- Skipping calibration or test readings before presenting results.
Suggested Report Sections
Problem statement and project background
Objectives focused on camera and visual-monitoring prototype and achievable prototype scope
System block diagram showing camera image, video frame, snapshot, or detected motion event -> processing -> captured evidence, recognition result, alert notification, or dashboard image log
Methodology using MAX30102, ESP32, IoT, Health with data flow and user/prototype workflow
Testing results for lighting, camera angle, dataset examples, false detections, and repeatable demo scenes
Limitations, discussion, and future improvements
Alternatives
Related Projects
IoT-Based Smart Mirror with Health Monitoring and Daily Routine Alerts
IoT, Display, ESP32
IoT based Health Monitoring and Alerting System
IoT, ESP32, Health
IoT-Based Bridge Condition Monitoring System with Structural Health Alerts
IoT, Vibration, ESP32
Solar Panel based Plant Environmental Monitoring System with Battery Percentage Monitoring
IoT, Solar, Soil Sensor
IoT-Based Smart Kitchen Appliance Monitoring System with Alerts
IoT, Current Sensor, ESP32
Remote Pet Monitoring System with Health Tracking via IoT
IoT, Camera, ESP32
FAQ
Is "IoT-Based Patient Health Monitoring with Heart Rate and SpO2" suitable for FYP?
Yes. This title can be suitable for FYP or Projek Akhir Tahun when the scope is controlled. The recommended scope is limit the first version to one visual task and controlled lighting before adding advanced ai claims.
What difficulty level is this project?
The suggested difficulty is Intermediate. The actual difficulty depends on whether you choose a basic, intermediate, or advanced prototype scope.
What platform can this project use?
This project can be planned using Camera, ESP32-CAM/Raspberry Pi, OpenCV or dashboard, Storage/alert. The final platform can be adjusted based on supervisor requirements and the chosen scope; common alternatives include Arduino, ESP32, Raspberry Pi, or another controller depending on the required features.
Is there a fixed project price?
No fixed price is published because the final quotation depends on project scope, features, timeline, hardware, software, and documentation requirements.
Can Rectronx help with documentation and demo preparation?
Yes. Rectronx can help with project planning, prototype development, coding explanation, report structure, testing evidence, and demo preparation.