How bit-coder91/sanjeevani-rural_health works
Sanjeevani is presented as a rural-health web application for symptom screening, facility discovery, and patient access. The documented user flow is a patient using the web interface to reach Spring API operations; facility search uses patient coordinates and hospital-directory data, while account operations read and update user history. The sampled code confirms these API and CSV behaviors, but not most of the README’s AI, cloud, or IoT claims; those are shown only as documented capabilities, not verified integrations.
Main entry points: ApiController.java API controller · index.html Web interface · RuralHealthApplication.java Spring application · users.csv User records
Components 14
Patient interface
- Web interface
src/main/resources/static/index.html
Spring API
- Spring application
src/main/java/com/ruralhealth/server/RuralHealthApplication.java - API controller
src/main/java/com/ruralhealth/server/controller/ApiController.java - Symptom screening
src/main/java/com/ruralhealth/server/controller/ApiController.java - Follow-up
src/main/java/com/ruralhealth/server/controller/ApiController.java - Image analysis
src/main/java/com/ruralhealth/server/controller/ApiController.java
Facility discovery
- Proximity search
src/main/java/com/ruralhealth/server/controller/ApiController.java - Hospital directory
src/main/resources/hospital_directory.csv - Resource status
src/main/java/com/ruralhealth/server/controller/ApiController.java
Patient accounts
- Account access
src/main/java/com/ruralhealth/server/controller/ApiController.java - Medical history
src/main/java/com/ruralhealth/server/controller/ApiController.java - User records
users.csv
Other components
- Patient
- IoT health data
Connections 15
- Patient → Web interface: uses
README.md - Web interface → Spring application: served by
README.md - Spring application → API controller: starts
src/main/java/com/ruralhealth/server/RuralHealthApplication.java - Web interface → API controller: calls API
README.md - API controller → Symptom screening: routes screening
src/main/java/com/ruralhealth/server/controller/ApiController.java - API controller → Follow-up: routes follow-up
src/main/java/com/ruralhealth/server/controller/ApiController.java - API controller → Image analysis: routes analysis
src/main/java/com/ruralhealth/server/controller/ApiController.java - API controller → Proximity search: routes search
src/main/java/com/ruralhealth/server/controller/ApiController.java - Proximity search → Hospital directory: reads CSV
src/main/java/com/ruralhealth/server/controller/ApiController.java - Proximity search → Resource status: computes estimates
src/main/java/com/ruralhealth/server/controller/ApiController.java - API controller → Account access: routes access
src/main/java/com/ruralhealth/server/controller/ApiController.java - API controller → Medical history: routes history
src/main/java/com/ruralhealth/server/controller/ApiController.java - Account access → User records: reads and writes
src/main/java/com/ruralhealth/server/controller/ApiController.java - Medical history → User records: reads and writes
src/main/java/com/ruralhealth/server/controller/ApiController.java - IoT health data → API controller: sends readings
README.md