Client Meeting II - Sidduri2025/RehabEdge GitHub Wiki

Meeting Minutes – RehabEdge Project (Group 4)

  • Date: Friday, 09/12/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

  • Finalize functional requirements for the RehabEdge system based on the project requirements document.
  • Prioritize Mandatory (SHALL) vs Recommended (SHOULD) vs Optional (MAY) requirements for the MVP.
  • Discuss which requirements will be implemented in Phase 1 (MVP) and which will be deferred to future phases.
  • Backend considerations: logging, history storage, and security (encrypted credentials, no plain text passwords).
  • Frontend/UI design alignment: confirm how patient and doctor dashboards will differ.
  • Notifications and reminders: define frequency, triggers, and delivery mechanism.
  • Security and compliance: confirm requirements for authentication, password storage, and role-based access.

Specific Questions Asked (and by whom)

  • Jhansi: Should MVP include both patient and doctor account management or focus on patients only for phase one?
  • Vaishnavi: Do we need to implement real-time corrective feedback (Recommended) in the first version, or should we limit MVP to posture detection only?
  • Chaithanya: Is role-based access control (patient vs doctor) a strict requirement for MVP or can it be phased in later?
  • Praneetha: Is offline functionality (Optional) important for MVP, or can it be postponed? Group (collective): What level of notifications are required — daily reminders only, or also escalation alerts for doctors when patients miss sessions?

Specific Answers Given (and by whom)

  • Jhansi: Confirmed that both patient and doctor accounts will be included in MVP, though doctor accounts can start with limited features.
  • Vaishnavi: Decided that real-time corrective feedback is important but not required for MVP; the MVP will only include posture detection.
  • Chaithanya: Emphasized that role-based access control is necessary in MVP to ensure data is segmented properly between patients and doctors.
  • Praneetha: Concluded that offline logging is not part of MVP but should be added to the roadmap for future phases.
  • Group consensus: MVP will implement daily reminders and doctor notifications when patients miss multiple sessions since they are key to patient engagement.

Action Items

For the next client demo, the team will implement all mandatory requirements including secure patient and doctor accounts, encrypted authentication, daily reminders, posture detection via device camera, exercise history storage, and a doctor dashboard to track weekly progress. Role-based access control and notification alerts for missed sessions will also be part of the MVP to ensure usability and security. Recommended features like real-time corrective feedback and personalized plans will be documented for later phases, while optional features such as virtual appointments and offline logging are deferred to the roadmap. The immediate focus will be on delivering a stable and functional MVP that demonstrates the core therapy and monitoring capabilities.

Next Meeting

  • Wednesday, 09/17/2025 at 07:00 PM (Zoom Meeting)
  • Friday, 09/19/2025 at 07:00 PM (Zoom Meeting)