Client Meeting Minutes I - Sidduri2025/RehabEdge GitHub Wiki

Meeting Minutes โ€“ RehabEdge Project (Group 4)

  • Date: Wednesday, 09/03/2025,Time: 05:00 PM, Location: Zoom Meeting

Who Was Present

  • Jhansi Akshara Sanagala - Frontend Developer (responsible for building the mobile/web interface for patients).
  • Vaishnavi Sidduri -Project Manager & Backend Developer (responsible for managing tasks, client communication, and backend API development).
  • Praneetha Reddy Lakkam - Tester & Documentation Lead (responsible for quality testing of the application and preparing project documentation).
  • Chaithanya Reddy Pailla - Database Administrator (responsible for designing and maintaining the database for problem detection logs and patient records).

Meeting Agenda

  • Review MVP Scope โ€“ Confirm decision to start with hand-related problems only, since full-body detection requires a large dataset and more time.
  • Demonstrate AI Prototype โ€“ Present the initial AI module detecting simple hand issues such as restricted movement, improper angle, or abnormal tremors.
  • Patient Reminders โ€“ Show how the mobile app reminds patients of their daily hand therapy tasks, and how additional alerts are triggered when repeated problems are detected.
  • Backend Data Logging โ€“ Review how detected hand problems are categorized, logged, and stored in the backend database for doctor access.
  • Doctor Dashboard Mockup โ€“ Display weekly summaries of patient hand problems (type, frequency, severity) in chart form, and how this helps doctors track recovery trends.
  • Client Feedback Session โ€“ Gather input on MVP progress, validate whether starting with hand problems is acceptable, and discuss expectations for Phase 2 (expansion to other body parts and advanced analytics).

Specific Questions Asked (and Who Asked Them)

  • Jhansi: โ€œIs it acceptable to limit MVP to hand problem detection, or should we attempt partial whole-body detection as well?โ€
  • Vaishnavi: โ€œShould the reminders be designed specifically for hand therapy routines, or remain as general therapy notifications?โ€
  • Chaithanya: โ€œWhen storing data, should we capture raw movement details or only record detected problems and corrective actions?โ€
  • Praneetha: โ€œShould the doctor dashboard provide detailed breakdowns of each hand problem type, or is an overall weekly summary sufficient for now?โ€

Specific Answers Given (and Who Gave Them)

  • Jhansi: Starting with hand problems is the right approach because it is practical, requires a smaller dataset, and makes MVP development manageable. Expansion to other body parts can be done in later phases.
  • Vaishnavi: Reminders should be specific to hand therapy sessions. Patients should know exactly which exercise or hand therapy routine to follow when they receive notifications.
  • Chaithanya: Only problem detections, severity, and frequency need to be logged. Storing raw video or movement data is not required due to privacy concerns.
  • Praneetha: For MVP, a weekly summary with a breakdown of problem types (slouching hand, improper angle, stiffness, tremor, etc.) is sufficient. In later phases, more detailed per-session reports may be added.

Action Items โ€“ What to Show in the Next Client Meeting

In the next client meeting, the team will demonstrate the prototype detecting hand-related problems with real-time corrective feedback in the patient app. The backend will support both daily therapy reminders and problem-based alerts, while the database will log problem type, severity, and frequency. A doctor dashboard preview will show weekly progress trends using these logs. Testing results and updated documentation will also be presented to ensure qual

Next Client Meeting

  • Wednesday (09/10/2025): Focus on Agenda #2 and #3 (MVP features + AI model choice).
  • Friday (09/12/2025): Focus on Agenda #4 and #5 (backend plan + deliverables for demo).