Feat/unified patient dashboard
This merge request adds the frontend implementation of the Unified Patient Dashboard, providing a consolidated, read-only view of patient information. Since the backend API endpoint is currently under development by another team member, the dashboard is implemented using mock data and is ready for real API integration.
Issue Context
This MR addresses issues observed in the volunteer workflow while implementing the Unified Patient Dashboard.
After registering a new patient, doctor assignment was not working as expected, and navigation across volunteer modules needed consistency.
What Was Done
- Implemented Unified Patient Dashboard under Volunteer Actions
- Connected Patient Dashboard to real backend API (no mock data used)
- Ensured patient search and dashboard load using book number
- Fixed navigation so all Volunteer Action cards route correctly
- Improved Assign Doctor flow for newly registered patients
- Identified and handled prerequisite dependency (vitals / active visit)
- Added clear frontend guidance when doctors are not available due to workflow state
Current Behavior
- Patient Dashboard fetches real-time aggregated data from backend
- Assign Doctor works consistently once prerequisites are met
- Navigation works across all volunteer modules without dead ends
Scope
- Frontend changes only
- No backend logic modified
Testing
- Registered a new patient and verified dashboard loading
- Checked navigation for all Volunteer Action options
- Confirmed real API data rendering on dashboard!
BEFORE SCREEN SHORT
After screenshorts
Edited by Vandana reddy Balannagari





